Chapter 12 In-Process ActiveMatrix BusinessWorks Integration : Deploying the Integration Project

Deploying the Integration Project
These summary instructions assume you are familiar with deployment procedures in BusinessEvents and in ActiveMatrix BusinessWorks.
You must include all ActiveMatrix BusinessWorks processes used for the integration project when you build the PAR, not just those that call a rule function or that are called by a rule function. For example a process may itself contain a process call to perform some related action. You must include that called process too.
When ActiveMatrix BusinessWorks is the Container
Build two EAR files and deploy them as follows
1.
2.
3.
4.
Upload the ActiveMatrix BusinessWorks EAR into TIBCO Administrator. Before deploying, provide the value for the global variable you defined to identify the location of the deployed BusinessEvents application (see Specifying the Rule Service Provider for ActiveMatrix BusinessWorks Containers).
If the BusinessEvents application is deployed to a TIBCO Administrator domain, use the server-based repository URL (this URL is the value of the TIBCO.repourl property in the generated TRA file for the application). TIBCO-supported protocols are tibcr, HTTP, HTTPS, or file (Local).
If the BusinessEvents application is not deployed to a TIBCO Administrator domain, provide the path to the BusinessEvents EAR file, and the EAR file name itself.
5.
When BusinessEvents is the Container
Deploy the EAR file in the usual way.
Disabling the PAR  When you start the BusinessEvents application using TIBCO Administrator and you have specified the location of the ActiveMatrix BusinessWorks process engine using a PAR, disable the PAR.
To disable the PAR, uncheck the Enable Service checkbox, or select the Advanced tab for the deployment and make sure that the "start deployed instance after deployment" is unchecked before deploying.