CDD Configuration Procedures : Configuring the Processing Units Tab (All OM Types)

Configuring the Processing Units Tab (All OM Types)
To configure a processing unit, you add the items you configured earlier, and any additional properties required.
If you don’t find a configuration item you require, click the appropriate tab and add it, then return to Processing Units tab and continue configuration.
Processing units are used in deploytime configuration, in the topology file. One processing unit named default is provided out of the box. You can change this name. It has no significance.
To Add a Processing Unit
See Processing Units Tab — General Settings and Properties for guidelines on the settings and properties.
1.
Click Add to add more processing units as needed.
2.
For deployment, TIBCO Administrator by default looks for a processing unit called default and a CDD file called default.
3.
4.
5.
If you use TIBCO BusinessEvents Data Modeling, check the Enable DB Concepts checkbox to enable database concept functionality on this processing unit.
6.
In the Agents section, click Add and select an agent.
7.
Agent Instance Properties and Deployment  The agent key identifies an instance of this agent class uniquely at runtime. It is used to retrieve scorecards from the backing store. Scorecards are local to an agent instance. The agent priority also differentiates between deployed instances of an agent class for failover and failback purposes if you use fault tolerance.
Ensure that you deploy a processing unit containing such agent-specific values one time only. Create as many processing units as you need to provide appropriate values in deployed instances of the agent class. See Deployment-Specific Processing Units for more details.
8.
The Http Properties for a processing unit are used to configure the internal HTTP server, used with the HTTP Channel. See HTTP Channel Configuration Properties in TIBCO BusinessEvents Developer’s Guide.