When a VST deployment has both the Vocera Messaging Platform and the Vocera Voice Server in its on-premises environment, users are synced between the three servers.
When a Vocera Messaging Platform server and a Vocera Voice Server are integrated properly, the VMP syncs all users and groups from the VS. This behavior is not related to VST—it is part of the basic VS-VMP interaction.
When the two systems are then integrated with VST, VMP syncs the VSTContacts group and its members from the Vocera Voice Server as part of this basic sync operation. These users are synced to the VMP database; however, when VMP syncs the members of VSTContacts to the VST server, it uses a web service to request the most recent membership from VS—not the database.
The connector that is built into the VMP machine maintains a web socket connection to VST. Every 90 minutes, VST uses this connection to request a sync of users in VSTContacts from VMP. VMP in turn uses the vst.war web service to retrieve members of VSTContacts from the Vocera Voice Server and then syncs these users to VST with the web socket connection. VST creates an External User for each member of the group; all of these VSTContacts users will appear on VST handheld clients as contacts.
The VMP server manages the membership of the VSTUsers distribution list (DL). This DL is automatically created by the VMP, and its members are auto-synced from VST (usually in real time; it may take up to 10 minutes in certain situations). All of the members of VSTUsers appear as contacts for VCS users who have permissions to the DL.
VMP populates the VSTUsers DL by syncing members of the VST organization to which it is directly connected. In addition VMP syncs the native VST users who are members of the organizations with which it is affiliated. VMP does not sync external users from its affiliated organizations unless they are linked to native user profiles.
For example, suppose the on-premises Vocera system of Hospital A is connected to VST and affiliated with Hospital B and Hospital C, but not with Hospital D, as shown below.
The on-premises VMP of Hospital A syncs the native VST users of its own organization, as well as the native VST users of Hospital B and Hospital C, as shown below.
In the VCS app:
- The first user appears because the VCS contacts list includes all VS users
- The second user appears because the VCS contacts list includes members of the VSTUsers DL.
In the VST app:
- The first user appears because the VST contacts list includes all native VST users
- The second user appears because the VST contacts list also includes the External Users from VSTContacts.
