The Server Manager module provides centralized service stop and start as well as a full configuration reload functionality for all ADSS Server services, system processes, system cache and configurations. All ADSS Server instances using the same database are shown and thus it is possible to control all services on any ADSS Server instance from this control panel.
From ADSS Server v4.3 onwards, the ADSS Server installation wizard installs three different ADSS Server components:
The Core Instance hosts the automatic back end processes including logs archiving, certificate expiry notifications, certificate auto renewal, alert messages via email, SNMP or SMS, and HMAC auto verification.
The Console Instance hosts the admin console and thus provides the operator interface to manage all services, create new profiles, edit profiles, create service certificates, register trust points, and so on.
The Service Instance hosts all front-end services and the CRL Monitor service. All services can be installed on one server or on different servers for load balancing. If the services are installed on multiple servers then all Server Instances are shown within the Server Manager view. All services can be stopped, started or restarted from the respective action column or the entire configuration can be reloaded. The latter is required when fundamental changes have been made to ADSS Server, such as the addition of an HSM or changes within Trust Manager.
The Schedule Restart is used if user made changes in the configurations and needs to restart the services and user cannot restart the services due to peak hours and want to restart the services later. In the "Schedule Restart At" field user will select the date and time for schedule restart of services and click on Save button will save the date and time of restart. If due to some reason user want to cancel the schedule restart then there is a Clear button to cancel the schedule restart. Clicking on clear will remove the time from the field and will save the configuration.
Schedule Restart will work only one time and after restarting the services, system will clear the schedule restart date/time.System Health
System Health is used to see that how much memory and database connections are being used by the ADSS Server. Click on the System Health button will open a new window where user can see that which of the ADSS Server instances are installed, addresses of ADSS Server instances, status of installed instances, memory status of ADSS Server instances and allocated database connections to the instances.
The screen images below show an example list of registered ADSS Server instances:
Following is the screen of System Health which will show that which of the ADSS Server instances are installed and their statuses. Memory will show the Total Memory which is allocated and how much memory is being used by the instance. Database Connections will show that how much connections are assigned (Total Connections) and how much connections are being used and how much connections are remaining (Free Connections). There are three statuses of "Memory" and "Database Connections" which are OK, Alarming and Critical. As used memory or database connections limit will reach up to 80% of total system will change the status to "Alarming" and as total limit will reach up to 90% system will show the status as "Critical".
Clicking the Restart System button restarts the particulate instance of ADSS Server.
Clicking the Restart All Instance button restarts all instances, i.e. Core, Console and Service.
The link against the Service instance lists all the ADSS Services and configurations that can be started/ stopped/ restarted by selecting the specific option.