Managing Ensemble Productions - InterSystems Documentation
Managing Ensemble Productions - InterSystems Documentation
Managing Ensemble Productions - InterSystems Documentation
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Configuration<br />
Adapter SETTINGS<br />
Below the Adapter Class, various other fields display. The exact fields vary depending on the adapter class.<br />
Whatever is listed in the SETTINGS parameter for the business operation class or its associated adapter class<br />
appears in the Specific Settings. When you hover the cursor over a field name, if there is a description of this field<br />
in the class code, its description displays. Validation for the data you enter is performed using the data types in<br />
the class code.<br />
Reply Code Actions<br />
Retry Interval<br />
Comma-separated list of code-action pairs, specifying which action the business operation takes on receipt of<br />
various reply status conditions.<br />
See Reply Code Actions Setting for details.<br />
Number of seconds to wait between attempts to connect with a destination outside <strong>Ensemble</strong>.<br />
Alert Retry Grace Period<br />
Business operations can be configured with an Alert Retry Grace Period during which errors relating to external<br />
connections do not trigger alerts, even if Alert On Error is True. This grace period accommodates a business<br />
operation that attempts an external connection with a configured Retry Interval and Failure Timeout. During its<br />
retry sequence, the business operation may encounter connection failures that become unimportant after one of<br />
its retry attempts succeeds. Thus, if a business operation first encounters an error, but later achieves success within<br />
the time allotted by the Alert Retry Grace Period, no alert is triggered even though an error occurred.<br />
Setting Alert Retry Grace Period to 0 disables this feature for the business operation.<br />
Failure Timeout<br />
Credentials<br />
Total number of seconds to keep trying to connect with a destination outside <strong>Ensemble</strong>. After this number of<br />
seconds has elapsed, the business operation discards the message data and returns an error code. To ensure that<br />
no message is ever skipped, enter a Failure Timeout value of –1, which means “never time out.” Use a setting of<br />
–1 when complete data delivery is critical, for example in health care applications.<br />
Some outbound adapters make remote connections that require a username and password. <strong>Ensemble</strong> stores these<br />
login credentials in a centralized table that can be viewed and edited only by users with access to the [<strong>Ensemble</strong>]<br />
> [Maintenance] > [Credentials] page. Each entry in the Credentials table has an ID by which you can refer to it<br />
when configuring adapters for the production.<br />
If an outbound adapter requires credentials, the Specific Settings include a Credentials field. If this field is present,<br />
it must contain an ID from the table on the [<strong>Ensemble</strong>] > [Maintenance] > [Credentials] page. If there is no current<br />
Credentials entry for the remote system that this business operation needs to connect to, you must create it. After<br />
creating the new entry in the [<strong>Ensemble</strong>] > [Maintenance] > [Credentials] page, go back to the configuration page<br />
and enter the new ID in the Credentials field.<br />
5.2.6 Reply Code Actions Setting<br />
The Reply Code Actions setting allows you to supply a comma-separated list of code-action pairs, specifying which action<br />
the business host takes on receipt of various reply status conditions. The format of the list is:<br />
code=actions,(code,code)=actions, ... code=action<br />
The following table lists the types of reply status condition identified by code.<br />
62 <strong>Managing</strong> <strong>Ensemble</strong> <strong>Productions</strong>