ActiveMatrix BusinessWorks Integration : Configuring the Environment For TIBCO BusinessEvents Containers

Configuring the Environment For TIBCO BusinessEvents Containers
Using a TIBCO BusinessEvents container requires additional configuration so that TIBCO BusinessEvents can locate ActiveMatrix BusinessWorks resources at runtime.
First perform all steps in the section Configure the TRA Files and then all steps in this section.
 
Task A Add the Repo URL for BusinessWorks to the CDD
This task assumes all other cluster deployment descriptor (CDD) configuration has been done. For more information about editing the CDD file, see Chapter 3, CDD Configuration Procedures, in TIBCO BusinessEvents Administration.
1.
2.
3.
For all inference agent classes that will run ActiveMatrix BusinessWorks, edit the BusinessWorks Repo URL field: add the path to the runtime TIBCO Designer project.
4.
Use this CDD when deploying the TIBCO BusinessEvents project.
Example Repo URL Values
The repo URL format depends on the deployment transport used. Supported formats for the URL are tibcr, http, https, and file.
Rendezvous transport format:

 
tibco.bwrepourl=tibcr@domain name-deployment name:service=repo rvService:daemon=repo rvDaemon:userName=uid:server=domain_name:password=encrypted_ password

 
Local transport (also known as file transport) format:

 
tibco.bwrepourl=domain_home>/domain_name/datafiles/deployment_name_root

 
HTTP transport format:

 
tibco.bwrepourl=http://machine_name:domain_http_port?domain_name-deployment-name&server=domain_name&timeout\=600&userName=uid&password\=encrypted_password

 
Task B Modify the TIBCO BusinessEvents TRA File
be-engine.tra
1.
Open the BE_HOME/bin/be-engine.tra file for editing.
2.
Add the following properties and their values. Take values from the BW_HOME/bin/bwengine.tra file, if they are present there:
   tibco.env.BW_HOME
   tibco.env.BW_MIGRATION_APPEND_VERSION
   tibco.env.BW_PLUGINS_HOME_OLD
   tibco.env.BW_PLUGINS_HOME
   tibco.env.TPCL_HOME
   tibco.env.TRA_HOME
   tibco.env.TRA_APPEND_VERSION
   tibco.env.HAWK_HOME
   java.property.palettePath
3.
Copy the following properties and their values from the bwengine.tra file to the be-engine.tra file and rename them: add BW_ to the property name as shown.
4.
In the value of all properties listed in step 3, remove references to any TIBCO BusinessEvents library, if there are any.
The be-engine.tra file (as shipped) uses the above names in various path properties, so you do not have to make any additional modifications.
5.
Task C Configure for Non-Default TIBCO Hawk Microagent Names
When TIBCO BusinessEvents is the container, the ActiveMatrix BusinessWorks TIBCO Hawk microagent (HMA) name is the same as the TIBCO BusinessEvents HMA name, appended with -bw. The name is defined using the Hawk.AMI.DisplayName property (see Table 42, ActiveMatrix BusinessWorks integration Properties for TIBCO BusinessEvents Containers for details).
If you want to use default HMA names, skip this task.
Choose a method of specifying non default names:
If you want to use the same non-default names, except that the ActiveMatrix BusinessWorks HMA is appended with -bw: Define the non-default name by adding the Hawk.AMI.DisplayName property to the Processing Units tab property sheet in the Cluster Configuration editor.
If you want to use different names for the ActiveMatrix BusinessWorks and TIBCO BusinessEvents HMAs, do the following: Define the name to be used by the ActiveMatrix BusinessWorks HMA using Hawk.AMI.DisplayName property. Whatever name you specify will be automatically appended with -bw.
Add a property called be.hawk.microagent.name and define its value as the desired name of the TIBCO BusinessEvents HMA.
Task D Configure for ActiveMatrix BusinessWorks Checkpointing (if Used)
Used only when TIBCO BusinessEvents is the container. See Design Considerations Related to Container for advice on using checkpointing in this case.
By default, an ActiveMatrix BusinessWorks instance running inside TIBCO BusinessEvents has the same name as the TIBCO BusinessEvents instance. If you will use ActiveMatrix BusinessWorks checkpointing, and if TIBCO BusinessEvents engine instances are deployed with different names, you must add a property that specifies the same ActiveMatrix BusinessWorks instance name to all processing units. Add the property to all processing units, using the Cluster Configuration editor, Processing Units tab property sheet.
tibco.bwengine.name all-same-engine-name
You can specify the property and its value in the CDD, or in the TIBCO Administrator Advanced tab at deploy time.
The name of the ActiveMatrix BusinessWorks engine. Used for ActiveMatrix BusinessWorks integration projects where TIBCO BusinessEvents is the container, and used only if the following is true:
The name of the TIBCO Hawk microagent (HMA) instance used for TIBCO BusinessEvents. You can change the name as desired. The default name uses this format:
com.tibco.Adapter.{be-engine|bw-engine}.DOMAIN. DEPLOYMENT.COMPONENT_INSTANCE
For container mode TIBCO BusinessEvents-ActiveMatrix BusinessWorks integration projects where TIBCO BusinessEvents is the container, TIBCO BusinessEvents internally appends -bw to this name and uses it for the ActiveMatrix BusinessWorks HMA name. However, if be.hawk.microagent.name is used the behavior is different.
See be.Hawk.microagent.name for related information.
This property is used only for container mode TIBCO BusinessEvents-ActiveMatrix BusinessWorks integration projects where TIBCO BusinessEvents is the container. This property is not present by default. You must add it if you want to use it.
If you want to use different names for the ActiveMatrix BusinessWorks and TIBCO BusinessEvents TIBCO Hawk microagents (HMAs), but you don’t want to use the Hawk.AMI.DisplayName naming scheme (where both HMAs have the same name, except that the ActiveMatrix BusinessWorks name is appended with -bw), then do the following:
Define the name of the ActiveMatrix BusinessWorks HMA using Hawk.AMI.DisplayName (or just use the default).