This commit is contained in:
Binary file not shown.
|
After Width: | Height: | Size: 60 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 27 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 107 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 101 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
@@ -6,6 +6,7 @@ This type of installation is suitable for both outside internet access and insid
|
||||
|
||||
Once the AyaNova server is installed and hosted within IIS, nothing needs to be installed for the end users who will access the AyaNova app on a computer or device with a modern web browser with Javascript enabled.
|
||||
|
||||
|
||||
## AyaNova web app system requirements
|
||||
|
||||
Any modern browser (not Internet Explorer) with Javascript enabled and a minimum device screen width of 360 pixels.
|
||||
@@ -20,13 +21,16 @@ Any modern browser (not Internet Explorer) with Javascript enabled and a minimum
|
||||
- PostgreSQL Server: installation guide [https://www.postgresqltutorial.com/install-postgresql/](https://www.postgresqltutorial.com/install-postgresql/)
|
||||
- ASP.NET Core Runtime Hosting bundle v6.0.0 or newer : Download [https://dotnet.microsoft.com/permalink/dotnetcore-current-windows-runtime-bundle-installer](https://dotnet.microsoft.com/permalink/dotnetcore-current-windows-runtime-bundle-installer)
|
||||
|
||||
## Network requirements to access IIS from the internet
|
||||
## Security and Network requirements to access IIS from the internet
|
||||
|
||||
In order to access the AyaNova server through IIS from the internet a static IP address is required as well as configuration of the router to allow incoming connections to the IIS server.
|
||||
In order to access the AyaNova server through IIS from the internet a static IP address is required, optionally a registered domain name as well as appropriate configuration of IIS and the router to allow secure, incoming connections to the IIS server from anywhere.
|
||||
|
||||
Network router configuration and security settings are complex and require the assistance of a networking professional familiar with exposing an IIS server to the Internet. Support or instructions for this process are highly equipment and situationally dependent and therefore beyond the scope of this manual or the support we can provide. If you are not familiar with this process it is highly advised to hire a professional to set that part up.
|
||||
IIS, domain name settings and network router configuration and security settings for external internet access are complex and require the assistance of a networking professional familiar with the process of exposing an IIS server to the internet.
|
||||
|
||||
Support and/or instructions for this process are highly equipment and situationally dependent and therefore beyond the scope of this manual or the support we can provide. If you are not familiar with this process it is highly advised to hire a professional to set that part up. We provide the instructions here to get IIS running with AyaNova *inside* your network so it's ready for the next steps of exposing it to the outside world which will require site and equipment specific steps best done by a network professional.
|
||||
|
||||
Note that external access should be configured _after_ AyaNova server is set up and working via IIS _inside_ the network and it may save time to have that ready before getting the assitance of a network technician to enable and _confirm_ outside access to AyaNova by configuring IIS to use HTTPS a domain name and appropriate port exposure through the router.
|
||||
|
||||
Note that external access can be configured _after_ AyaNova server is set up and working via IIS _inside_ the network and it may save time to have that ready before getting the assitance of a network technician to enable and _confirm_ outside access to AyaNova.
|
||||
|
||||
## Folders
|
||||
|
||||
@@ -99,7 +103,7 @@ AyaNova is built upon the ASP.NET Core runtime version 6.0 or newer and it shoul
|
||||
|
||||
### AyaNova server installation
|
||||
|
||||
Once you have ensured the two pre-requisites above are installed and available; download and run the AyaNova network installer: [https://www.ayanova.com/Downloads/v8/ayanova-lan-setup.exe](https://www.ayanova.com/Downloads/v8/ayanova-lan-setup.exe). Follow the prompts and complete the installation.
|
||||
Once you have ensured the two pre-requisites above are installed and available; download and run the AyaNova network installer: [https://www.ayanova.com/Downloads/v8/ayanova-lan-setup.exe](https://www.ayanova.com/Downloads/v8/ayanova-lan-setup.exe). Follow the prompts to complete installation but **DO NOT** select to start AyaNova with Windows, IIS will be responsible for starting and stopping AyaNova.
|
||||
|
||||
#### Server configuration
|
||||
|
||||
@@ -142,28 +146,67 @@ In some cases where a critical configuration value is completely missing, the se
|
||||
|
||||
Only after you have confirmed that AyaNova server is working and you can login should you proceed to the next step of enabling IIS to work with AyaNova.
|
||||
|
||||
### IIS final configuration to work with AyaNova
|
||||
### IIS AyaNova site configuration
|
||||
|
||||
At this point there is a working AyaNova server and all that is left is to set up a Site within IIS management console to host AyaNova in IIS so users can access AyaNova from inside or outside of your network.
|
||||
|
||||
Stop AyaNova server if it is still running from the previous step by following the instructions in the server console window. From this point on IIS will be controlling the starting and stopping of the AyaNova server.
|
||||
|
||||
|
||||
|
||||
- Open IIS manager:
|
||||
|
||||
From a server version of Windows:
|
||||
Tools->Manage menu item from server manager:
|
||||
|
||||
|
||||
From a non-server version of Windows:
|
||||
Access IIS manager from the Start menu Administrative tools menu item:
|
||||
|
||||
|
||||
- Create the AyaNova IIS site:
|
||||
In the Connections panel open the server's node, right click on Sites to add a new site.
|
||||
|
||||
|
||||
In the Add Website dialog box configure the website settings, the Site Name, Physical Path and Port are the only required settings to be changed.
|
||||
|
||||
Here is an example configuration that is suitable to allow internal users to access AyaNova over port 8080 via HTTP (not https) and is suitable to test AyaNova internally but is not suitable for outside access:
|
||||
|
||||
|
||||
Note that the Site name was set to "AyaNova", the physical path is set to the program files folder where AyaNova.exe resides after installation, the image shows the default location. The Port setting here has been set to 8080 which is intended to not conflict with a default website that comes with IIS which is already on port 80 the web browser http default port. Do not choose the same port number as AyaNova (by default 7575), that port must be left free for AyaNova to use to communicate with IIS.
|
||||
|
||||
Click on OK to save the settings and procede to the next step.
|
||||
|
||||
- Edit Application Pool
|
||||
Under the Server's node in the connections panel select Application Pools right click the sites application pool which will have the same name as the Site name configured in the previous step and select "Basic settings" from the context menu:
|
||||
|
||||
|
||||
In the application pool dialog set the .NET CLR version to "No Managed Code":
|
||||
|
||||
(this may seem counterintuitive since AyaNova uses .net but AyaNova uses .net Core, not the .net referred to here)
|
||||
|
||||
Click on Ok to save and continue to the next step
|
||||
|
||||
- Open AyaNova app through IIS
|
||||
Right click on the AyaNova site created earlier in IIS Manager and select "Manage website" and then "Browse". The AyaNova web app should open to the login page.
|
||||
|
||||
If you receive an error message from IIS "HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid." This means you did not follow the steps in the correct order and asp.net core was installed before IIS was enabled. In order to fix this run the hosting bundle setup again that was installed previously to ensure it recognizes IIS and enables proper operation.
|
||||
|
||||
At this point there is a working AyaNova server and all that is left is to connect IIS to it so users can access AyaNova from inside or outside of your network.
|
||||
|
||||
#### Next steps
|
||||
|
||||
Server installation is complete. Users will require the URL to use in their browser to access the AyaNova APP, see the AYANOVA_USE_URLS in the configuration section above.
|
||||
Server installation under IIS for internal access is complete. Users will require the URL to use in their browser to access the AyaNova APP that was opened in the last step to test AyaNova substituting the server's IP address for the "localhost" part of the URL.
|
||||
|
||||
For connection from the internet your network adminstrator will need to setup IIS with the correct port and optionally domain name and open the port on the router to allow outside connections and finally provide your users with the correct URL to access AyaNova from outside your network.
|
||||
|
||||
For Server Operations role review the [Server operations](ops-intro.md) configuration and maintenance guide.
|
||||
|
||||
For the Business administration role, now that the server is up and running AyaNova business settings can be configured, review the [Getting started](adm-getting-started.md) guide for Administrators.
|
||||
|
||||
After the installation has completed the configuration must
|
||||
|
||||
### Adjust defaults
|
||||
|
||||
At the end of setup the ayanova-launcher application will start if selected (or you can run it from the desktop icon) and in turn it will start the Postgres server, AyaNova server and then open the default web browser to both the AyaNova server interface and the AyaNova User interface.
|
||||
|
||||
## Starting and stopping AyaNova server
|
||||
|
||||
To shut down the AyaNova server press the ctrl-c key combination in the ayanova-launcher window.
|
||||
To start the AyaNova server use the installed desktop or start menu icon to run the ayanova-launcher.
|
||||
IIS will manage starting and stopping AyaNova as required. There should be no reason to start AyaNova server directly.
|
||||
|
||||
## Getting started and using AyaNova
|
||||
|
||||
|
||||
Reference in New Issue
Block a user