Check that clinical applications are correctly connected, and inspect the status of any queues that are holding healthcare messages.
When you have successfully completed all the prerequisite tasks, continue by using the following steps:
Connections with a warning are shown at the top of the table. You can sort the columns by clicking the headings. When the table is refreshed, the connections with a warning are again displayed at the top of the table. Move your cursor over the column headings for a description of the column.
A warning is displayed if the Open column shows 0 for a source or destination application. This warning means that your application is not connected. Investigate the causes. For example, the application might have stopped, or be offline.
Queues with a warning are shown at the top of the table. You can sort the columns by clicking the headings. When the table is refreshed, queues with a warning are again displayed at the top of the table. Move your cursor over the column headings for a description of the column.
A warning is displayed if the queue depth reaches the high depth limit, which is a percentage of the maximum depth. Identify why the queue is becoming full. For example, the application might have stopped taking messages off the queue.
To change the percentage settings for the Low Depth Limit or High Depth Limit columns, or to change the values for the Max Depth column, edit the queues on the queue manager.
Information that the broker uses to monitor your clinical applications is stored in user-defined properties of the message flow. To display these properties, right-click the flow, and then select
.Nodename/IPAddress:Port
For
example, SendHL7/localhost:2222