Managing Ensemble Productions - InterSystems Documentation

More documents

Recommendations

Info

Configuration Adapter SETTINGS Below the Adapter Class, various other fields display. The exact fields vary depending on the adapter class. Whatever is listed in the SETTINGS parameter for the business operation class or its associated adapter class appears in the Specific Settings. When you hover the cursor over a field name, if there is a description of this field in the class code, its description displays. Validation for the data you enter is performed using the data types in the class code. Reply Code Actions Retry Interval Comma-separated list of code-action pairs, specifying which action the business operation takes on receipt of various reply status conditions. See Reply Code Actions Setting for details. Number of seconds to wait between attempts to connect with a destination outside Ensemble. Alert Retry Grace Period Business operations can be configured with an Alert Retry Grace Period during which errors relating to external connections do not trigger alerts, even if Alert On Error is True. This grace period accommodates a business operation that attempts an external connection with a configured Retry Interval and Failure Timeout. During its retry sequence, the business operation may encounter connection failures that become unimportant after one of its retry attempts succeeds. Thus, if a business operation first encounters an error, but later achieves success within the time allotted by the Alert Retry Grace Period, no alert is triggered even though an error occurred. Setting Alert Retry Grace Period to 0 disables this feature for the business operation. Failure Timeout Credentials Total number of seconds to keep trying to connect with a destination outside Ensemble. After this number of seconds has elapsed, the business operation discards the message data and returns an error code. To ensure that no message is ever skipped, enter a Failure Timeout value of –1, which means “never time out.” Use a setting of –1 when complete data delivery is critical, for example in health care applications. Some outbound adapters make remote connections that require a username and password. Ensemble stores these login credentials in a centralized table that can be viewed and edited only by users with access to the [Ensemble] > [Maintenance] > [Credentials] page. Each entry in the Credentials table has an ID by which you can refer to it when configuring adapters for the production. If an outbound adapter requires credentials, the Specific Settings include a Credentials field. If this field is present, it must contain an ID from the table on the [Ensemble] > [Maintenance] > [Credentials] page. If there is no current Credentials entry for the remote system that this business operation needs to connect to, you must create it. After creating the new entry in the [Ensemble] > [Maintenance] > [Credentials] page, go back to the configuration page and enter the new ID in the Credentials field. 5.2.6 Reply Code Actions Setting The Reply Code Actions setting allows you to supply a comma-separated list of code-action pairs, specifying which action the business host takes on receipt of various reply status conditions. The format of the list is: code=actions,(code,code)=actions, ... code=action The following table lists the types of reply status condition identified by code. 62 Managing Ensemble Productions
Configuration Settings Table 5–2: Code Values for Reply Code Actions Code E E#statuscode E*text X Meaning Error status returned from message handler. Error status returned from message handler has status code equal to statuscode. Error status returned from message handler contains text string text. There is no reply message object at all. The following values for action may be used alone or combined to form strings. Table 5–3: Action Values for Reply Code Actions Action C W R S D F Meaning Treat the document as Completed OK. Log a warning but treat the document as Completed OK. Retry the message according to the configured Retry Interval and Failure Timeout settings; finally Fail, unless a different action is also specified. Suspend the message, log an error, and move on to try the next message (the default). Disable the business process or operation, log an error, and restore the outbound message to the front of the business host queue. When you choose the disable action for a business process, you must configure the business with a Pool Size = 1 or greater if you want all instances of only this business process to stop. If the business process has a Pool Size = 0, the disable action disables all business processes that share the actor pool. See the Pool Size section in the “Production Concepts” chapter of Developing Ensemble Productions for details. Fail with an error and move on to try the next message. For example: E#6301=R,E#ErrGeneral=R,E=F The default value for the Reply Code Actions string is: E=F Which means when there is an error, fail and move on to try the next message. All codes where the actions consists of only W (log a Warning) are evaluated and warnings generated if they trigger. Other codes are evaluated in left-to-right order, executing the first one that triggers that has a non-warning actions value. Managing Ensemble Productions 63
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 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

Create successful ePaper yourself

Delete template?

Save as template?