This commit is contained in:
@@ -156,35 +156,46 @@ Stop AyaNova server if it is still running from the previous step by following t
|
||||
|
||||
#### Open IIS manager
|
||||
|
||||
From a server version of Windows:
|
||||
Tools->Manage menu item from server manager:
|
||||
From a server version of Windows...
|
||||
|
||||
Click on 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:
|
||||
From a non-server version of Windows...
|
||||
|
||||
Access IIS manager from the Windows Start menu in the Windows Administrative Tools start menu folder:
|
||||
|
||||
|
||||
|
||||
#### 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.
|
||||
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:
|
||||
Under the Server's node in the Connections panel select Application Pools then right click the sites application pool which will have the same name as the Site name configured in the previous step ("AyaNova") 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
|
||||
@@ -193,7 +204,7 @@ Click on Ok to save and continue to the next step
|
||||
|
||||
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 generally means you did not follow the steps in the correct order and ASP.NET Core was installed **before** IIS was enabled which means IIS doesn't have the proper handlers to run an ASP.NET Core application. In order to fix this run the hosting bundle setup again that was installed previously (repair installation) to ensure it recognizes IIS and enables proper operation.
|
||||
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 generally means you did not follow the steps in the correct order and ASP.NET Core was installed **before** IIS was enabled which means IIS doesn't have the proper handlers to run an ASP.NET Core application. In order to fix this run the ASP.NET Core hosting bundle setup again that was installed previously (repair installation) to ensure IIS is setup with the correct handlers.
|
||||
|
||||
### Starting and stopping AyaNova server
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ The "front end" of AyaNova also known as the "client" is the user interface for
|
||||
|
||||
AyaNova supports many configurations from single user on a single computer, multiple office users on a local area network to large corporate scenarios where AyaNova is accessed globally from the internet.
|
||||
|
||||
AyaNova can be installed on many platforms including a single computer for private use, on-premise with a office network server or hosted on a 3rd party internet hosting provider such as [DigitalOcean](https://www.digitalocean.com/) (Windows or Linux).
|
||||
AyaNova can be installed on many platforms including a single computer for private use, on-premise with a office network server or hosted on a 3rd party internet hosting provider such as [DigitalOcean](https://www.digitalocean.com/).
|
||||
|
||||
The [installation guide](ops-install.md) is the starting point for installing AyaNova to meet specific needs.
|
||||
|
||||
|
||||
@@ -130,7 +130,6 @@ nav:
|
||||
- 'Windows local network': 'ops-install-windows-lan.md'
|
||||
- 'Windows IIS': 'ops-install-windows-iis.md'
|
||||
- 'Linux': 'ops-install-linux.md'
|
||||
- 'Maintenance': 'ops-maintenance.md'
|
||||
- Forms:
|
||||
- 'Introduction': 'ops-intro.md'
|
||||
- 'Server state': 'ops-server-state.md'
|
||||
|
||||
Reference in New Issue
Block a user