Managing Ensemble Productions - InterSystems Documentation

What to Manage
• Mode — The execution mode for the job: Background or Foreground. This is the value you set when defining the host
using the [Ensemble] > [Productions] configuration display. If you selected the Foreground check box, the Mode field
reads Foreground; otherwise it reads Background.
• Status — Dequeuing, Running, Error, or Quiescent. Most jobs run in less than 1 millisecond, so it is almost impossible
to see an entry on the Jobs page with a Running status, unless it is stuck in an infinite loop of some kind. All jobs
should become Quiescent during production shutdown, and if one does not do so, there may be a problem with it. In
all other cases entries on the Jobs page have a Status value of Dequeuing.
Ensemble may terminate a job, in which case its last known status prior to termination appears in the Status column,
and the background color of the row is red. This is called a “dead” job.
• Detail — This string contains information relating to the Status field. If the status of the job is Running, the Detail field
is blank. If the status of the job is Dequeuing or Quiescent, the Detail field lists the following information:
– The current queue name (for public queues such as Ens.Actor)
– The job ID (for private queues associated with specific business hosts).
• Active Message — If there is currently a message from this job, this column displays it.
• State — Dead, Starting, or Alive.
In each row, the background color indicates the job’s status, as follows:
• Blue — A startup job.
• (Neutral) — Jobs that are Dequeuing, Running, or Quiescent.
• Pink — A job that has Error status but is not dead.
• Red — A dead job.
3.10 Working with Messages
All communication that passes between configuration items in Ensemble is accomplished using messages. A message has
a header, which is the same for all messages and contains data fields that help route the message through the system. A
message also contains a body, which provides different fields depending on the message contents.
Every message class is one of two types: request or response. There may be request classes that do not have a corresponding
response class defined, but every response is (conceptually) paired with a request. Any request class may be synchronous
(waits for a response) or asynchronous (does not wait) in its implementation. These decisions are made by the class developer
and they are not configurable once the production is complete.
Ensemble offers some built-in message classes to handle various types of message content. Other message classes may be
defined by class developers to fulfill a specific production need. Without exception, all instantiated messages have complete
tracking information stored in the Ensemble message warehouse, and this information is available at all times to the
Ensemble Management Portal pages devoted to messages.
Since messages are the primary “currency” of action and communication within Ensemble, there are a large number of
management tasks associated with messages. The following table lists what you can do to work with messages using the
Ensemble Management Portal.
Message Task
Filter and view messages in various ways.
Sequence of Portal Commands
Message Browser
36 Managing Ensemble Productions