admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2022-01-04 23:22:39 +00:00
parent 512c0c50d5
commit 7aac0db692
6 changed files with 16 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/8.0/ayanova/docs/ops-install-windows-iis.md
View File

@@ -206,9 +206,11 @@ Click on OK to save the settings and procede to the next step.
#### Edit Application Pool
Several settings **must** be made in the Application Pool for AyaNova.
Three settings must be changed in the Application Pool for AyaNova to work properly.
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:
Under the Server's node in the Connections panel select "Application Pools" then right click the AyaNova site application pool which will have the same name as the Site name configured in the previous step ("AyaNova") to open the application pool context menu.
Select "Advanced settings" from the context menu:
![edit app pool](img/ops-install-windows-server-iis-edit-app-pool.png)
@@ -218,11 +220,11 @@ In the application pool dialog "(General)" section set the .NET CLR version to "
![set clr version](img/ops-install-windows-server-iis-app-pool.png)
(this may seem counterintuitive since AyaNova uses .net but AyaNova uses .net Core, not the .net referred to here)
This may seem counterintuitive since AyaNova uses .NET but AyaNova uses .NET Core, which is not the same .NET referred to here.
##### Adjust Idle timeout
In the application pool dialog "Process Model" section the Idle timeout setting must be set to zero to prevent IIS from shutting down AyaNova when usage is low which would prevent AyaNova from processing background tasks like the daily backup or generating Workorders from PM's etc.
In the application pool dialog "Process Model" section the Idle timeout setting must be set to zero to prevent IIS from shutting down AyaNova when usage is low which would prevent AyaNova from processing background tasks like the [daily backup](ops-form-backup.md) or generating Workorders from PM's etc.
The default is 20 minutes but we need it to be set to `0` to completely turn off idle timeouts:
![idle timeout](img/ops-install-windows-server-iis-app-pool-idle-timeout.png)
@@ -231,7 +233,7 @@ The default is 20 minutes but we need it to be set to `0` to completely turn off
In the application pool dialog "Recycling" section there are two settings that must be configured to prevent AyaNova from being restarted when it's actively processing a backup job or generally busy with Users.
It's a good idea to allow IIS to recycle periodically however, by default it will do it every 1740 minutes which eventually will conflict with AyaNova's scheduled daily backup job or at a time when usage is high during the day so we need to turn that off and instead set it to recycle at a specific time of day that will not conflict with the daily backup or a busy time for AyaNova usage.
It's a good idea to allow IIS to recycle periodically however, by default it will do it every 1740 minutes which eventually will conflict with AyaNova's scheduled [daily backup](ops-form-backup.md) job or at a time when usage is high during the day so we need to turn that off and instead set it to recycle at a specific time of day that will not conflict with the daily backup or a busy time for AyaNova usage.
For the purposes of this document we'll assume the AyaNova server is not in peak demand overnight and the backup will be configured for 11:59pm making 3am a good time to recycle, however you should adjust this based on your specific site needs.
@@ -244,7 +246,7 @@ Next we need to add a "Specific Time", the entry box is in 24 hour time format s
![recycle time](img/ops-install-windows-server-iis-app-pool-recycling-time.png)
Typically 3am is a good time as the backup in our scenario starts at 11:59pm and should be completed by 3am and users won't be accessing the server at 3am however you must adjust this time to be appropriate for your site specific needs. The AyaNova server will restart in well under a minute but it would break the backup if it was in progress and potentially interfere with active users.
Typically 3am is a good time as the backup in our scenario starts at 11:59pm and should be completed by 3am and users won't be accessing the server at 3am however you must adjust this time to be appropriate for your site specific needs. The AyaNova server should completely restart in less than a minute but it will affect the backup if it was in progress and potentially interfere with active users.
Save the recycle time once entered and click on Ok to save and continue to the next step.