Managing Ensemble Productions - InterSystems Documentation

More documents

Recommendations

Info

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
Working with Messages Message Task Filter the message log for the currently running production by entering search criteria such as time of day or session identifier. View the contents of two messages and compare them, side by side. View message body contents. View message header and body contents for a message. Periodically save older messages to a separate archive for long term storage. Resend selected messages. View messages that have entered a Suspended state. Resend selected messages. View a visual trace of the delivery of a message, from original source all the way through to fulfillment (or failure). Test HL7 or X12 messages, by viewing and transforming them. Test a production by sending request messages and receiving responses. Sequence of Portal Commands Message Browser, Filter Message Browser, Compare Messages Message Browser, Contents Message Browser, Details Maintenance, Archive Manager Message Browser, Resend Messages Maintenance, Suspended Messages Message Browser, Trace EDI / HL7 Manager, Message Viewer Testing Service 3.10.1 Message Status When you trace messages using the Ensemble Management Portal, you see a visual representation of each message as it travels from one configuration item to the next. The message object can have various status values that indicate its rotation through a normal life cycle. These status values are visible on most Ensemble Management Portal message pages: Created, Queued, Delivered, Deferred, Completed, Discarded, or Suspended. These status values apply to instances of request and response messages individually. Request-response “pairs” are not tracked together, because a request might be repeated several times before it is successfully delivered, some requests have an optional response that can be ignored if it does not arrive, some responses can be deferred for later delivery, and some requests have no response defined for them at all. Message Status Completed Created Deferred Delivered Discarded Queued Suspended Meaning The intended recipient has received the message and has finished processing the message. The message is in transit between sender and target. The message response has been deferred by the business operation for later delivery. The intended recipient has received the message. The message is a response that reached its destination after the timeout period for the corresponding request expired. The message is on a queue. The message was suspended by the business operation after failing to reach its external destination, or by an administrator from the Instances display on the [Ensemble] > [Host Monitor] page. In either case, you can resend the message from the [Ensemble] > [Maintenance] > [Suspended] page or by clicking the Resend Messages command on the [Ensemble] > [Messages] page. Managing Ensemble Productions 37
Page 1 and 2: Managing Ensemble Productions Versi
Page 3 and 4: Table of Contents About This Book .
Page 5 and 6: 9.1 Business Process List .........
Page 7: List of Tables Table 1-1: Ensemble
Page 11 and 12: 1 Ensemble Management Portal This c
Page 13 and 14: Login 1.3 Login The Ensemble Manage
Page 15 and 16: Ensemble Home Page • Jobs — lis
Page 17 and 18: Ensemble Home Page If you click the
Page 19 and 20: Portal Command Summary Page or Comm
Page 21: Portal Command Summary Page or Comm
Page 24 and 25: Management Tasks Task View Alternat
Page 26 and 27: Management Tasks Monitor... Message
Page 28 and 29: Management Tasks 2.9 Viewing Items
Page 30 and 31: What to Manage Production Task Purg
Page 32 and 33: What to Manage • Business process
Page 34 and 35: What to Manage the item to be stopp
Page 36 and 37: What to Manage For example, an item
Page 38 and 39: What to Manage Each dashboard is as
Page 40 and 41: What to Manage At far right, the ti
Page 42 and 43: What to Manage Event Log Task Filte
Page 46 and 47: What to Manage 3.10.2 Messages in P
Page 48 and 49: What to Manage Workflow Task Manage
Page 50 and 51: Productions • Last Stop Time —
Page 52 and 53: Productions If you click this comma
Page 54 and 55: Configuration • Configuration Dia
Page 56 and 57: Configuration The Copy command is u
Page 58 and 59: Configuration 5.1.4 Status Indicato
Page 60 and 61: Configuration When you click Apply
Page 62 and 63: Configuration Column Value Source D
Page 64 and 65: Configuration Beneath the row of co
Page 66 and 67: Configuration From the Production C
Page 68 and 69: Configuration Adapter Class The cla
Page 70 and 71: Configuration Adapter SETTINGS Belo
Page 73 and 74: 6 System Monitor The [Ensemble] > [
Page 75 and 76: 7 Event Log The [Ensemble] > [Event
Page 77: Event Log Purge • Click Reset to
Page 80 and 81: Message Browser • Session — The
Page 82 and 83: Message Browser Some business opera
Page 84 and 85: Message Browser • The segment nam
Page 86 and 87: Message Browser When you have selec
Page 88 and 89: Message Browser If the Color By sel
Page 90 and 91: Message Browser Table 8-2: Options
Page 92 and 93: Message Browser Operator > >= < , >
Page 94 and 95:
Message Browser 8.3.1 Resend Editor
Page 96 and 97:
Business Processes 9.2 BPL Viewer T
Page 98 and 99:
Business Processes - Includes — A
Page 100 and 101:
Business Processes • SessionId
Page 103 and 104:
10 Host Monitor The [Ensemble] > [H
Page 105 and 106:
Monitor Instances To the right of e
Page 107 and 108:
11 Queues The [Ensemble] > [Queues]
Page 109 and 110:
Message Details this value is the s
Page 111 and 112:
12 Maintenance The [Ensemble] > [Ma
Page 113 and 114:
Purge Management Data To the right
Page 115 and 116:
Credentials • Do not purge most r
Page 117 and 118:
Lookup Settings When the Run Archiv
Page 119 and 120:
Enterprise Message Bank Click Save
Page 121 and 122:
Enterprise Message Bank • The Mes
Page 123:
Enterprise Message Bank Pattern cha
Page 126 and 127:
Testing Service Enable Testing If t
Page 129 and 130:
14 EDI / HL7 Manager The [Ensemble]
Page 131 and 132:
Index A actor pool and jobs, 35 and
Page 133 and 134:
starting, 4 tasks to perform, 15 En
Page 135 and 136:
R Reply Code Actions field, 61, 62
show all

Managing Ensemble Productions - InterSystems Documentation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?