Managing Ensemble Productions - InterSystems Documentation
Managing Ensemble Productions - InterSystems Documentation
Managing Ensemble Productions - InterSystems Documentation
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Configuration Diagram<br />
Figure 5–4: Configuration Page Right Column — Business Operation<br />
When not selected, shapes in the diagram have the following background colors:<br />
Color<br />
White<br />
Gray<br />
Orange<br />
Business host status<br />
The item has been added to the production configuration and is enabled.<br />
The item has been added but is disabled. Compare the enabled FindRateFileService with<br />
the disabled FindRateEmailService in the full-size Configuration Page diagram in the previous<br />
section.<br />
The item is referenced by another item within the production, but is not yet added to the<br />
production. The background color changes to white or gray after you add the referenced<br />
item.<br />
5.1.2 Configuration Names<br />
The most important characteristic of any item in a production configuration is its name.<br />
By default, the name of a configuration item is the name of its underlying host class. When this is the case, the package<br />
name displays at the top of the shape. The host class name appears below the package name. For examples, see the business<br />
operations FindRateEmailOperation, FindRateFileOperation, and FindRateTCPOperation in the previous figures.<br />
You can assign the item a name that is different from its host class name. If so, the configured name displays in the item<br />
shape and no package name displays. This is true of the My Terminal Output business operation in the full-size configuration<br />
diagram at the beginning of this chapter.<br />
5.1.2.1 Different Configuration Names, Same Host Class<br />
Naming configuration items independently of their host class names provides flexibility in configuring your production.<br />
For example, if you want to use the same business service host class to communicate with various external sources, but<br />
you want to use slightly different runtime settings in each case, you can do so by assigning a different name to each configuration<br />
of the host class. A change to the underlying class code changes the behavior of all of the items of that class.<br />
Figure 5–5: Different Configuration Names, Same Host Class<br />
<strong>Managing</strong> <strong>Ensemble</strong> <strong>Productions</strong> 47