Chapter 26 Deploytime Configuration : Deploying Many Agents on One Machine With TIBCO Administrator

Deploying Many Agents on One Machine With TIBCO Administrator
When you use TIBCO Administrator to deploy a multi-BAR EAR file to a machine, or to deploy the same EAR multiple times to one machine, issues relating to BAR-level property settings can arise. Each BAR represents one agent.
When you look at an uploaded EAR file in TIBCO Administrator, you see that all BAR files in the EAR are represented by one merged bar file, which appears at the level of a service under the application. This is because it is not possible to deploy selected BARs to different servers.
Because the BAR files are merged, you can’t set properties differently for each BAR file using TIBCO Administrator. Certain object management configuration options, however, are set differently for each BAR file (rule session).
In general, here are some approaches you can take to setting values at the rule session level when you need to set values for multiple rule sessions differently:
Create a different global variable for each BAR file’s configuration field, and put the appropriate variable in each BAR’s configuration field in TIBCO Designer. At deploy time, set values as needed using the global variables that appear on the application’s Advanced tab. See Defining and Using Global Variables for more details.
Some property file properties have names to which you can append rule-session or agent-specific names. Add and set those properties in the BE_HOME/bin/be-engine.tra files. See Engine Property File Settings for Persistence Object Management for some examples.
A similar configuration issue can arise if you want to deploy one EAR file to the same machine more than once, for example, setting the database environment directory for a BAR’s persistence data store, when Persistence is used for object management. Guidelines to handle this scenario are provided in the section Database Environment Directory.