25.01.2015 Views

Managing Ensemble Productions - InterSystems Documentation

Managing Ensemble Productions - InterSystems Documentation

Managing Ensemble Productions - InterSystems Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Queues<br />

There is no menu on the Queue Contents page. You can return to the <strong>Ensemble</strong> home page by clicking [<strong>Ensemble</strong>] in the<br />

title bar navigation path.<br />

Under the Queue Contents page title bar are two display areas, one above the other. The top display lists messages. The<br />

bottom display provides detailed information about the message that is currently selected in the list. If nothing is selected,<br />

the bottom display is empty. You can drag the boundary between the displays to resize them as needed. In some cases you<br />

must use the scroll bars to see the full contents of either display.<br />

In the top display is a table called Message Queue Contents. Each row of the table lists one of the messages currently<br />

waiting on the queue that you selected in the [<strong>Ensemble</strong>] > [Queues] page. Each row of the table has the following columns:<br />

• Priority — The priority of the message relative to others in the queue: RealTime (1), High (2), Normal (3), or Low (4).<br />

The <strong>Ensemble</strong> messaging engine assigns priority values to messages automatically, in the course of normal processing,<br />

for its own use. Message priority cannot be programmed into a message class or configured in any way. Priority values<br />

are based in part on whether the message is synchronous (High) or asynchronous (Normal). Also, messages that start<br />

or stop a production are assigned greater priority than other types of message.<br />

• Index — This integer value starts at 1 for the first message placed on the queue after the production starts, and increments<br />

by 1 for each successive message. A message has the same Index value for the entire time it is on the queue. Index<br />

values are never reused.<br />

• MessageId — The object identifier for the message.<br />

In each row, the background color indicates the message’s overall status, as follows:<br />

• Red — The message encountered an Error.<br />

• Orange — The message is Queued.<br />

• Green — The message marks the start of a session.<br />

• Silver — The message arrived after a timeout expired. It has been marked as Discarded.<br />

• Orange — The message is Suspended.<br />

• White or pale blue, in alternating rows — These messages are OK.<br />

To the right of each row in the Queue Contents table are two commands:<br />

• Details — Click this command to display detailed information about the message in that row.<br />

• Abort — Click this command to abandon any ongoing attempts to send the message.<br />

At the top of the display is an Abort All command. If clicked, a confirmation dialog displays. If you confirm the operation,<br />

all queued messages shown on this page are deleted, and the display returns to the [<strong>Ensemble</strong>] > [Queues] page.<br />

11.2 Message Details<br />

If you select a message in the [<strong>Ensemble</strong>] > [Queues] > [Contents] page and request further details, message details display<br />

in the bottom half of the screen. Message details provide full information about every data field in the currently selected<br />

message.<br />

Two tables display the contents of the message header and message body, left and right respectively.<br />

On the left is the Message Header, which displays the entire contents of the message header. Fields include:<br />

• — The object identifier for the message header. Whenever a message header and message body are combined<br />

together as a message, the ObjectId value in the header is used to identify the combined message object. As a result,<br />

100 <strong>Managing</strong> <strong>Ensemble</strong> <strong>Productions</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!