Note: To access the Health & Status, you will need Maintenance Administration privileges.
The Health & Status maintenance feature checks all the various services and infrastructure that runs WEBcnx, from details about the databases to whether the workflow and scheduled services are running correctly. If something doesn't appear to be working properly in WEBcnx, this should be the first place to check. Of course, if the site is completely down and you're unable to log in then you will need to check all the services on the server first or contact a member of the Arden support team for further help.
The Health & Status is broken down into a number of sections:
- Application - The Application page provides information about the installed version of WEBcnx, including the application name, version and the minimum version of nServer that is required to run the current version of WEBcnx
- Server - Details of the server the WEBcnx site is running on, including the server name, IP address and the OS Version number
- Web Server - An overview of the state of the web server WEBcnx is running on, providing information about memory, thread and CPU states
- Configuration - The Configuration page lists all relevant keys from the web.config and their values. This is an easy way to check how various features are configured such as the default language WEBcnx is running in (DefaultCultureId) and the number of recent tasks shown in the "Tasks I've Recently Viewed" saved search (MaximumRecentTasks)
- WEBcnx Database - Provides details of the Connection String that WEBcnx uses to connect to the WEBcnx database. This includes the name of the database and the name of the server it's hosted on. It also shows the minimum supported version of SQL Server
- Impact Database - Provides details of the Connection String that WEBcnx uses to connect to the Impact database. This includes the name of the database and the name of the server it's hosted on.
- nServer - The version of nServer and the name of the server that it's running on
- Licence Server - Details of the address and port Licence Server is running on, along with the number of each type of user licences loaded onto the Licence Server
- Direct Impact Connection - For most areas functionality that uses data from the Impact database, customer lists, users, designs, etc. WEBcnx uses nServer to fetch that data. In some cases, the Direct Impact Connection is used for performance reasons where it is more optimal to bypass nServer; some aspects of searching for and viewing documents use this method. It is optional but is usually configured for most installations
- Scheduler Service- Details of the Scheduler Service that is used to perform various actions behind the scenes:
- TerminateWorkflowsTask - Terminates suspended workflows that have not been resumed before their timeout termination date
- GenerateNotificationsForSuspendedWorkflowsTask - Checks suspended workflows that need notifications generating
- ResumeRunnableWorkflowsTask - Checks suspended workflows that need resuming
- ManageLDAPUserGroupsTask - responsible for the automatic management of the WEBcnx user groups LDAP users are associated with based on their LDAP authorisation security groups
- DeleteZombieDocuments - Deletes any "zombie" documents. If you simply close your browser or navigate elsewhere during the creation of a task and you've added some documents then there will be some documents in a "zombie" state, i.e. related to a task guid which will never exist. This task clears those up
- HotFolder - Processes workflows triggered by "hot folders"
- AutomatedEmailTask - Distributes task overdue notifications
- ProofScope - If ProofScope has been purchased, this section provides server details of where ProofScope is hosted and WEBcnx's connection to it
- Workflow - Details of the workflow service name, the version of workflow running and the workflow endpoint details
Alongside each page, the Health & Status service will report on whether the section is Healthy or there's a Fault. A Fault in any of these settings is not an indication that there is actually a problem, just that the Health & Status check was unable to successfully test that feature. A typical example of a safe Fault would be for ProofScope, if that module is not purchased.
If you have administration privileges and can't see the Health & Status section, you may not have this configured correctly in your web.config file. Read the following for information on configuring the Health & Status.