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 22:43:44 +00:00
parent ca471ac1a6
commit 512c0c50d5
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -132,7 +132,9 @@ The [AYANOVA_DB_CONNECTION](ops-config-db.md) property must be edited and where
The [AYANOVA_USE_URLS](ops-config-use-urls.md) property specifies which TCP / IP Port that AyaNova server should listen on for connections from web browsers. The default value is port 7575 which should be free in most cases, however if you need to use an alternate port due to conflict it must be set here. We recommend using the default 7575 to avoid current or future confusion or conflict with other servers that may be installed or present elsewhere on the network.
Optional but recommended: Add a 32 character [AYANOVA_JWT_SECRET](ops-config-jwt-secret.md) property to the configuration if you want to ensure that logged in User's session can survive a restart of the AyaNova server. If this is not set AyaNova will invalidate all login tokens any time the server restarts by generating a new random JWT secret on boot.
Strongly recommended: Add a 32 character [AYANOVA_JWT_SECRET](ops-config-jwt-secret.md) property to the configuration if you want to ensure that logged in User's session can survive a restart of the AyaNova server. If this is not set AyaNova will invalidate all login tokens any time the server restarts by generating a new random JWT secret on boot and under IIS AyaNova _will_ restart every day so this is really a mandatory setting if you want to preserve user logins over a 24 hour period.
Do _not_ use the value shown here, make sure you change it to any other random 32 characters for security purposes.
```json
{
@@ -206,7 +208,7 @@ Click on OK to save the settings and procede to the next step.
Several settings **must** be made in the Application Pool for AyaNova.
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 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:
![edit app pool](img/ops-install-windows-server-iis-edit-app-pool.png)
@@ -238,10 +240,12 @@ There are two settings to configure in the "Recycling" section of the Applicatio
First we need to turn off the "Regular time interval" 1740 minute recycle by setting it to `0`:
![recycle minutes](img/ops-install-windows-server-iis-app-pool-recycling-minutes.png)
Next we need to add a "Specific Time", the entry box is in 24 hour time format so we will enter `03:00:00` for 3am (again set accordingly for your site needs):
Next we need to add a "Specific Time", the entry box is in 24 hour time format so we will enter `03:00:00` for 3am:
![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.
Save the recycle time once entered and click on Ok to save and continue to the next step.
#### Open AyaNova app through IIS