25.01.2015 Views

Managing Ensemble Productions - InterSystems Documentation

Managing Ensemble Productions - InterSystems Documentation

Managing Ensemble Productions - InterSystems Documentation

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuration Settings<br />

Description<br />

Enabled<br />

Foreground<br />

external side might mean that the business service now needs a different class of adapter to communicate with the<br />

other enterprise. This would indicate a change to the Class field. The Name field allows continuity across this<br />

change.<br />

If you change the host class, the General Settings retain their values, but you must configure the Specific Settings,<br />

as these may be entirely different for the new host class.<br />

Comments that describe the business host class. This read-only field displays the first line of the class annotation<br />

in the code. If there is no annotation in the code, the Description field contains the text N/A.<br />

By default, the Enabled check box is selected for every business host. When you select Enabled, the business host<br />

— identified by Name — is enabled. When a business host is enabled, it is registered with the production, and<br />

instances of the business host accepts and processes messages whenever the production runs. You can clear the<br />

Enabled check box, if needed.<br />

For example, if there is a communications breakdown on the external side, an email server goes down, or something<br />

similar happens, you can disable the associated business service until throughput is restored. When the Enabled<br />

check box is clear, the business service is still present in the configuration, and its queue continues to accept<br />

messages, but none of these messages are processed until the business service is enabled again.<br />

By default, this check box is clear. Select it for debugging or diagnostic purposes only. Jobs in operational systems<br />

almost never run in the foreground. When the Foreground check box is selected, any system jobs used by the<br />

business service run in a Caché Terminal window at the front of the console display. This allows debugging or<br />

trace messages to be displayed in the Terminal window. See the section “Testing and Debugging <strong>Productions</strong>”<br />

in the “Creating a New Production” chapter of Developing <strong>Ensemble</strong> <strong>Productions</strong>.<br />

Log Trace Events<br />

Trace messages are informational text messages that <strong>Ensemble</strong> can deliver to the Terminal window and, optionally,<br />

to the <strong>Ensemble</strong> event log. Trace messages are unrelated to Visual Trace, which provides a graphical view of<br />

<strong>Ensemble</strong> message objects as they travel through a production.<br />

By default, the Log Trace Events check box is clear. When selected, it enables logging of all trace messages issued<br />

by this business host. Logging means that <strong>Ensemble</strong> will write the trace messages to the console Terminal window<br />

(as usual) but it will also automatically store copies of these messages in the event log.<br />

Inactivity Timeout<br />

Pool Size<br />

A business host has an Inactive status after it has not received any messages within the number of seconds specified<br />

by the Inactivity Timeout field. The <strong>Ensemble</strong> Monitor Service periodically reviews the status of business services<br />

and business operations within the production, and marks the item as Inactive if it has not done anything within<br />

the Inactivity Timeout period. The business host status (OK, Error, Inactive) can be seen on the [<strong>Ensemble</strong>] > [Host<br />

Monitor] page. The default value is 0 (zero). If a business host has an Inactivity Timeout setting of 0, it will never<br />

be marked Inactive, no matter how long it stands idle.<br />

Specifies how many system jobs to allocate to run this business host; the default is 1. Other values are appropriate<br />

in specialized circumstances as described in the General Settings notes for the particular business host type.<br />

For a full discussion of appropriate pool sizes for different types of production, see the Pool Size section in the<br />

“Production Concepts” chapter of Developing <strong>Ensemble</strong> <strong>Productions</strong>.<br />

<strong>Managing</strong> <strong>Ensemble</strong> <strong>Productions</strong> 57

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!