ADC Guidance in your Deployment in Vocera Engage

This high level list describes the key generic information needed to deploy an ADC in your Vocera environment.

If your company plans to use an ADC, request a Vocera Support case for guidance on a recommended configuration. Further guidance on vendor specific configuration and deployment should be sought from the ADC vendor directly.

To set up servers for high availability, perform the following steps:

Create two virtual servers or virtual IP (VIP) addresses (internal and external) if using split DNS for FQDN.
Obtain the internal IP addresses of the two Vocera Engage servers.
Create two servers/nodes which will identify the two Vocera Engage servers.

Create a health monitor with the following specifications.

Field	Text
URL	http://<url_or_ip>/active
send string	"HEAD /active HTTP/1.0\r\n\r\n"
Responses from the servers	Active server: "HTTP/1.1 200 OK" Standby server: "HTTP/1.1 404 Not Found"
interval	10 seconds
timeout	31

Apply the health monitor created above to the two Vocera Engage servers/nodes.

Create the virtual server's IPs (VIP for internal/external) for each service pointing to the servers/nodes.

Required services (internal/external VIP)

Service	Protocol	Port
XMPP	tcp	5222
Web Services	tcp	443

Optional adapters if configured (internal VIP)

Obtain the protocol and the port for the enabled Vocera adapters from the Vocera Engage IP Port Reference Guide. Navigate to the Adapter Ports heading in the "Vocera Engage Internal IP Ports" section to obtain an adapter's port and protocol requirements.