Managing Ensemble Productions - InterSystems Documentation

More documents

Recommendations

Info

Maintenance A refresh operation as frequent as every 5 seconds might be helpful or distracting, depending on how you are using the portal. To change the rate, enter a new value in this field. If you never want an automatic refresh to occur, set the value to 0 (zero). • Auto-Start Production — You can configure Ensemble so that a specific production starts automatically at system startup, and stops automatically at system shutdown. In the Production list, click a production name. To disable automatic production start, click the blank entry; this is the default. For more details, see the Production Life Cycle section of the “Production Concepts” chapter of Developing Ensemble Productions. When you are finished making changes in the Maintenance page, click Save to apply the changes. 12.1 Suspended Messages The [Ensemble] > [Maintenance] > [Suspended] page allows you to study and resubmit messages that have entered a suspended state. Some business operations are designed to set the status of any failed messages to suspended. Alternatively, you can suspend a message from the Instances display on the [Ensemble] > [Host Monitor] page. In either case, such a message goes on a special queue where Ensemble keeps all suspended messages. You can use the Suspended Messages page to find and examine these messages. An inspection of the routing information or contents of a specific message might reveal the reason why the message failed. For example, if the problem is that an external destination went out of service, you can make a change to reestablish communication with that server. Then you can resubmit the suspended messages to the external server from this page. You can display the Suspended Messages page by clicking Maintenance on the Ensemble menu and then clicking Suspended Messages from the Maintenance menu. If some messages in the currently running production are suspended, the page lists them. If no messages are suspended, the list is empty. The list displays message information as described in the following table. Column Check box # ID Time Created Session Error Source Target Description Mechanism for selecting messages for the Resubmit, Edit & Resubmit, Discard, and Delete commands. An incremental count of the number of entries in the table. The unique identifier for the instantiated message. The date and time when this message was instantiated. The unique identifier of the session to which this message belongs. A session marks the beginning and end of all the activities prompted by a primary request message from outside Ensemble. A quick overview of the results returned by the message to the configuration item that sent it, the Error field can have the values OK, Error, Retry, or Inactive. OK means normal behavior; Retry means the message experienced a failure but the item that sent it is configured to retry the failed message. Error means an error was reported somewhere in the activity. Inactive means that the item that sent the message has been idle for longer than its Inactivity Timeout setting, and may require diagnostic action. The name of the configuration item that sent the message. The name of the configuration item that is the intended recipient of the message. 104 Managing Ensemble Productions
Purge Management Data To the right of each row are two commands which you can click to display additional message information: • Click Details to display the message details in the lower portion of the page. • Click Trace to display a visual trace of the path of the message object through the production on the Ensemble Visual Trace page. Above the list of suspended messages is a choice of commands to perform on these messages: • Resubmit — Select one or more check boxes in the column at the left of each message you want to resubmit and click to resubmit the messages. As message similar to the following displays for each successfully resubmitted message: Resubmit suspended message ID '7' completed. Any message that you resubmit retains the same Session identifier and transmits the same Header object. The description in the message header contains text indicating this is a Resubmitted message. • Edit & Resubmit — Edit a single message before resubmitting; this command is only valid if you select exactly one message. See the Resend Editor for Resubmitting Messages section for details. • Discard — Remove the message from list on the Suspended Messages page. The message is still accessible from the Ensemble Message Browser. • Delete — Remove all record of the message from the Ensemble database. CAUTION: You cannot undo the Discard or Delete operations. 12.1.1 Resend Editor for Resubmitting Messages When you select one message to resubmit from the [Ensemble] > [Maintenance] > [Suspended] page, you have the option to edit the body of the message before resubmitting it. 1. Click Edit & Resubmit to display the Ensemble Resend Editor page. 2. Use the entry fields to update the message body data. The fields vary depending on the method signature of the message. If the method has no properties, none are displayed. If you are editing a virtual document message (HL7, X12), you can edit data in the message content and also edit object properties in the box below the content box. 3. Click Resubmit to resubmit the original message header with your edited message body contents to the target. 4. After a successful resubmit, the page refreshes with text indicating the Header and Msg Body identifiers. Click Trace to see the visual trace of the resubmitted message. Any message that you edit and resubmit retains the same Session identifier and transmits the same Header object, but it contains an updated Msg Body object with a new identifier. The description in the original message header contains text indicating that this message has been resubmitted and includes the original Msg Body object identifier. 12.2 Purge Management Data The [Ensemble] > [Maintenance] > [Purge] page allows you to delete outdated entries from the event log, message warehouse, business process archives, and business rule log. You can only purge entries associated with the currently running production. You can display the Purge page as follows: 1. From the Ensemble menu, click Maintenance. Managing Ensemble Productions 105
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 44 and 45:
What to Manage • Mode — The exe
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: 12 Maintenance The [Ensemble] > [Ma
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?