Steps for Shutting Down

Use these steps to shut down VAM.

Note: You must shut down or log out from all other external devices that are connected to the VAM application server before shutting it down. Otherwise, the current operations in the devices will be terminated abruptly and users will be logged out. The effect of a shutdown depends on the current running operation.

Shut down the following before shutting down the VAM application server:

All iOS and Android clients (devices).
All browsers where the configuration portal is opened and in use.
All external hardware integrations, such as patient monitor and BedMaster applications.

Stop the Windows services listed below in the following order:

Vocera Alarm Message Generator
Vocera Alarm Escalator
Vocera Alarm Media Parser
Vocera Alarm Monitoring
Vocera Alarm Clean Up Service
Vocera Alarm Notification Service
Vocera Alarm Server Health Monitor
Vocera Archiver Service

Stop the following Analytics services:

Vocera Alarm Analytics Engine
MySQL

Stop the Mirth Connect Service.

Stop the following servers:

Stop IIS services, especially the ASP.NET State Service and the World Wide Web Publishing Service.
Stop SQL server services, such as SQL Server and SQL Server Agent.

To restart VAM, restart the services in the reverse of the order in which they were stopped. Database servers and their services should be started first, then IIS services, and then Windows services.

An easier shutdown procedure is also available:

The easy way to shut down the VAM application is to shut down the application and database servers. Power off the systems unless other services are being used.
The easy way to restart the VAM application is to restart the application and database servers.

Notes:

If the SQL database server is restarted, all of the Windows services listed here need to be restarted. There may be some issues, depending on the current running environment: for example, a user may be logged out or an error, exception, or crash may have occurred in the iOS app, Android app or VAM Console. In general, there will not be any major issues, but this is not guaranteed, as this depends on the current operation.
There is no impact on failover if the above steps are followed, especially shutting down the external devices and hardware before shutting down the application server. Otherwise, the individual alerts and requests will not be processed properly or will be missed from the application server.
If the server has to be restarted, for example because of maintenance or a Windows update, it is advisable to restart at midnight or on the weekend when the load is lighter. Since load balancing is used, there will not be any downtime when the server is restarted if only one server is restarted at a time.