Deployment-Specific Processing Units and Global Variables

In general, you can reference one processing unit multiple times to create different processing unit configurations (PUCs). However processing units that have deployment-specific settings cannot be used in this flexible manner.

  • Agent-Instance-Specific Properties: If a processing unit contains agent-instance-specific properties such as agent key and priority settings, use it in only one PUC, which is used in only one DU that is itself used only once in the deployment.
  • Host-Specific Processing Units: Processing units can host-specific settings. If a deployment unit contains a PUC that references such a processing unit, link it only to the appropriate host for deployment. For example, the Coherence cache provider property tangosol.coherence.localhost property is a host-specific setting, and so is the TIBCO BusinessEvents DataGrid property be.engine.cluster.as.listen.url.
  • Global Variables: Global variable overrides (if any) set in the master CDD are used for command-line deployment. They can be overridden by TIBCO BusinessEvents Monitoring and Management settings. If you plan to deploy using MM, override global variables using MM, instead of in the CDD file.