This section lists the prerequisites for Vocera Analytics Server, Voice Server, Engage Appliance, and Vocera Messaging Platform.
Before you install Vocera Analytics, ensure that you have the following prerequisites:
| Host | Prerequisites |
|---|---|
| Vocera Analytics Server | Safelist the <Vocera Analytics Install Drive>\VASuite.exe folder. |
| Internet Explorer 11 Web Browser (latest update) on Windows Server
2016 using Document Mode 10 or higher must be installed. For
instructions to view Document Mode, see https://docs.microsoft.com/en-us/internet-explorer/ie11-deploy-guide/fix-compat-issues-with-doc-modes-and-enterprise-mode-site-list#test-your-sites-for-document-mode-compatibility. Note: It may be necessary to add
specific URLs for Vocera Analytics to the Compatibility View,
depending on the specific security policies implemented at your
site.
|
|
| Ensure that Java is enabled on your Web browser. For instructions to enable Java, see https://java.com/en/download/help/enable_browser.xml. | |
| Ports 9443 and 9445 should be open and should not be blocked. | |
| Voice Server | Safelist the <Vocera Analytics Install Drive>\VASuite.exe folder. |
| Port 9445 should be open and should not be blocked. | |
| To install Vocera Analytics agent, you would need administrator privileges. | |
| To configure Vocera Analytics with Voice Server as source, you would need Voice Admin Console administrator credentials. | |
| Ensure that you update the log retention policy for Voice Server. For more information, refer to Log Retention Policy for Voice Server. | |
| Engage Appliance | SSH access to Engage Appliance must be granted. From Vocera Analytics Server you would need an SSH connection to Engage appliance. |
| Vocera Messaging Platform | For VMP remote agent, if you are using VMP versions 5.2.2, 5.2.3, 5.3, or 5.3.3, perform the following:
Note: Do not execute these queries together. If you execute these queries together, and any query fails, the subsequent queries in the sequence will not be executed. Hence you must execute each query separately.
Note: While executing these queries, you may encounter the error message: Column name 'RowUpdated' in <table name> is specified more than once. You can ignore this error message and proceed with the configuration.
|