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 />
When you click Apply to save changes made in the configuration form, <strong>Ensemble</strong> outputs your settings to the production<br />
class in the form of an XML document embedded in the XData ProductionDefinition section of the class.<br />
• Cancel — Undo the changes highlighted in yellow on the configuration page.<br />
• Help — View context-sensitive information about this page.<br />
• Start Production — Start the production whose configuration you are viewing.<br />
• Stop Production — Stop the production that is running in the active namespace.<br />
The next three commands allow you to add new configuration items to the production. Clicking one of these commands<br />
does not generate any new host classes. Any item that you add at this step must already have a corresponding host class<br />
that has been written and compiled in <strong>Ensemble</strong> Studio. These commands simply tell the production which items you want<br />
it to contain:<br />
• Add Service — Add a business service to the production.<br />
• Add Process — Add a business process to the production.<br />
• Add Operation — Add a business operation to the production.<br />
Beneath the row of commands are the settings you can configure for a production; they are grouped into the following three<br />
categories:<br />
• Production Settings<br />
• Additional Production Settings<br />
• Defaults for Additional Production Settings<br />
5.2.1.1 Production Settings<br />
The configuration page allows you to configure the following Production Settings common to all productions:<br />
Name<br />
Description<br />
The production name. This field has a gray background, which means you can view it, but you cannot edit it.<br />
Comments that describe the production.<br />
Actor Pool Size<br />
Number of system jobs available in a public pool of jobs for use by business processes that have no private pool<br />
of jobs. Allow enough for requests to keep moving through the message queues, but no more.<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 />
Testing Enabled<br />
Select this check box to enable use of the <strong>Ensemble</strong> Testing Service pages to test this production. Clear this check<br />
box to disable the testing service.<br />
Log Unassigned 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 />
52 <strong>Managing</strong> <strong>Ensemble</strong> <strong>Productions</strong>