Before you begin configuration work, read Design Considerations and ensure your project meets the requirements and guidelines.In order to use the integration features when running in a BusinessEvents container, you must configure the environment as explained in this section.You must provide all the required engine and environment properties for ActiveMatrix BusinessWorks in the BusinessEvents TRA file, or in a property file used with the -p option.
The values shown in this section work with various test projects. Depending on the ActiveMatrix BusinessWorks services used in your project, you may have to make additional changes.
BusinessWorks version 5.3.3 If you use BusinessWorks 5.3.3, ensure that you have applied hot fix 8 before performing this procedure.
1.
2. Ensure that the property tibco.env.BW_HOME is present and uncommented.
3. Add the following properties and their values, taken from the bwengine.tra file, if they are present there:
4. Add the classpath to the ActiveMatrix BusinessWorks libraries to the tibco.env.CUSTOM_EXT_PREPEND_CP property. Below is an example property:tibco.env.CUSTOM_EXT_PREPEND_CP=%BW_HOME%/hotfix/lib%PSP%%BW_HOME%/lib%PSP%%BW_HOME%/lib/palettes%PSP%%TRA_HOME%/hotfix/lib/palettes%PSP%%TRA_HOME%/lib/palettes%PSP%%TRA_HOME%/hotfix/icjava/6.2/lib%PSP%%TRA_HOME%/icjava/6.2/lib
5. tibco.env.CUSTOM_EXT_APPEND_CP=%TPCL_HOME%/tomcat/5.5/compatible/libtibco.env.CUSTOM_EXT_APPEND_CP=%TPCL_HOME%/tomcat/5.5/compatible/libYour property values will depend on what products you have installed. For example, TIBCO BusinessFactor prepends the classpath with the classpath to its libraries.
6. Add the java.property.palettePath property and configure it as needed to include the path to all palettes used in the integration. For example:
java.property.palettePath %BW_HOME%/lib/palettes%PSP%%BW_PLUGINS_HOME%/lib/palettes%PSP%%TRA_HOME%/lib/palettes
7. For startup outside of a TIBCO Administrator domain (simple command-line startup), or from BusinessEvents debugger, add the following property:tibco.bwrepourl = path-to-TIBCO Designer-projectAdd to the be-engine.tra file any ActiveMatrix BusinessWorks engine properties that must be set for deployment. As with any engine property that you want to change at deploy time, you can enable the properties to be configured in TIBCO Administrator at deploy time (see Customizing the List of Properties on the Advanced Tab for details).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 16, ActiveMatrix BusinessWorks integration Properties for BusinessEvents Containers (Sheet 1 of 3) for details).
● If you want to use the same non-default names, except that the ActiveMatrix BusinessWorks HMA is appended with -bw, then define the non-default name using the Hawk.AMI.DisplayName property
● 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. Note that 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.
● And BusinessEvents and ActiveMatrix BusinessWorks are deployed using separate EAR filesThen you must identify the ActiveMatrix BusinessWorks processes to the BusinessEvents runtime engine, using the tibco.bwrepourl property.To configure this property, provide the repo URL for the deployed ActiveMatrix BusinessWorks application (and not the EAR file or TIBCO Designer project location). See Example Repo URL Values for accepted formats.(Note that for startup outside of a TIBCO Administrator domain, you must always add the tibco.bwrepourl property and its value is the path to the TIBCO Designer project, as explained in Task A).As for other properties, you can configure the tibco.bwrepourl property in the be-engine.tra before deploying, or on the TIBCO Administrator Advanced tab for the application (the property is available on the Advanced tab by default).
Recommendation: Deploy PAR and BAR in One EAR File Add the PAR (process archive) resource to the EAR resource that contains the BAR (BusinessEvents archive) resource. Configure the PAR resource to include all processes used in the integration.Note: Before deploying the ActiveMatrix BusinessWorks instance using TIBCO Administrator, first disable the PAR. The PAR must not start at runtime.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
See Design Considerations Related to Container for advice on using checkpointing in ActiveMatrix BusinessWorks when BusinessEvents is the container.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 in all be-engine.tra files:tibco.bwengine.name all-same-engine-nameYou can specify the property and its value in the be-engine.tra files, or in the TIBCO Administrator Advanced tab at deploytime.
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. Used in certain circumstances for ActiveMatrix BusinessWorks integration projects where BusinessEvents is the container.Required when deploying to a TIBCO Administrator domain, and BAR and PAR are in different EAR files. In this case the value is the repo URL for the deployed ActiveMatrix BusinessWorks application repository. Supported formats for the ActiveMatrix BusinessWorks repository URL are tibcr, http, https, and file (local). See If PAR and BAR are Deployed in Separate EAR Files for details about using this property.For startup outside of a TIBCO Administrator domain, you must always add the tibco.bwrepourl property and its value is the path to the TIBCO Designer project (see Task A). 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 in-process 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 in-process 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.