Pause and resume Vocera Data Export Adapter processing in the Vocera Platform.
Start the Adapter
After creating the necessary rules, navigate to the Vocera Data Export Adapter in the Vocera Platform. See Working with the Data Export Rules for additional information.
Select Start to start the adapter. The example below has been started and displays Active status.
Testing a Database Connection
A test connection to a database can be performed from the sidebar of the adapter page. In the Configuration Test section, select Test to request a test database connection using the current configuration. A report of a successful or failed connection request will display underneath the Test button. If a test connection fails, the conditions for its failure are shown in the report.
Pausing and Resuming the Adapter
The client can pause the Vocera Data Export Adapter as needed. For example, the facility may have planned downtime for server maintenance. In this case, the client would want to pause the flow of messages to their database until the maintenance is completed and they are ready to begin accepting messages again.
When the Vocera Data Export Adapter is sending information to the client database, the Adapter is processing... message will show in the green box as indicated below.
Select the Pause Processing button to pause the delivery of messages to the client database.
The messages will be queued while the adapter is paused. The Adapter is processing... message will change to Adapter Processing is Paused and will display the date and time the pause button was selected as shown below. There is no time limit on the pause function. The queue will continue to fill until the Resume Processing button is selected or the one million message limit is reached.
Audit log code 641 is generated when the Pause Processing button is selected. If a message is queued after the adapter is paused, Audit Log code 640 is generated to remind the user that the adapter is still paused.
To resume the flow of messages, select the Resume Processing button. The message changes to Adapter is processing... and Audit Log code 642 is generated.
