Using a BusinessEvents container requires additional configuration so that 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.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.
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. Example Repo URL ValuesThe repo URL format depends on the deployment transport used. Supported formats for the URL are tibcr, http, https, and file.
tibco.bwrepourl=tibcr@domain name-deployment name:service=repo rvService:daemon=repo rvDaemon:userName=uid:server=domain_name:password=encrypted_ password
tibco.bwrepourl=http://machine_name:domain_http_port?domain_name-deployment-name&server=domain_name&timeout\=600&userName=uid&password\=encrypted_password
1.
2. Add the following properties and their values. Take values from the BW_HOME/bin/bwengine.tra file, if they are present there:
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 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.When BusinessEvents is the container, the ActiveMatrix BusinessWorks TIBCO Hawk microagent (HMA) name is the same as the BusinessEvents HMA name, appended with -bw. The name is defined using the Hawk.AMI.DisplayName property (see Table 38, ActiveMatrix BusinessWorks integration Properties for BusinessEvents Containers for details).
• 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 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 BusinessEvents HMA.Used only when 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 BusinessEvents has the same name as the BusinessEvents instance. If you will use ActiveMatrix BusinessWorks checkpointing, and if 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-nameYou 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 BusinessEvents is the container, and used only if the following is true:Use this property to ensure that the same ActiveMatrix BusinessWorks engine name is specified in all nodes. The name of the TIBCO Hawk microagent (HMA) instance used for BusinessEvents. You can change the name as desired. The default name uses this format:For container mode BusinessEvents-ActiveMatrix BusinessWorks integration projects where BusinessEvents is the container, 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 BusinessEvents-ActiveMatrix BusinessWorks integration projects where 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 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 BusinessEvents HMA using be.hawk.microagent.name.
• Define the name of the ActiveMatrix BusinessWorks HMA using Hawk.AMI.DisplayName (or just use the default).
Copyright © TIBCO Software Inc. All Rights Reserved.