Deploying a TIBCO BusinessEvents Project : Deployment in a TIBCO Administrator Domain

Deployment in a TIBCO Administrator Domain
You can use TIBCO Administrator for deploying and undeploying, starting and stopping BusinessEvents servers, and for setting deploy-time properties.
Within an EAR file, a BAR file contains the compiled agent files. The BAR file appears here in the TIBCO Administrator UI:
Application Management > application_name > Configuration > application_name.bar
The default value of application_name is provided by the name of the enterprise archive resource.
TIBCO Administration Domains
When you install TIBCO Administrator, you are prompted to create an administration domain and to create a username and password. You can use this domain or create another one (using Domain Utility) for your BusinessEvents applications and the hardware they run on. The first time you log in to the TIBCO Administrator user interface, you must use the username and password entered during installation of the TIBCO Administrator software. You can then create additional users and passwords as needed.
If TIBCO Administrator was already installed before you installed BusinessEvents, you may have to contact the person responsible for administering the software to get login credentials for an existing administration domain.
Property Overrides
Properties set in TIBCO Administrator override those set in be-engine.tra and any supplementary property files; which override properties set in the CDD file. Also note that TIBCO Administrator generates a TRA file on deployment and then reads properties from that generated file.
Using AppManage for Scripted Deployment to a Domain
Instead of using the TIBCO Administrator user interface, you can perform scripted deployment to a TIBCO Administrator domain using the AppManage utility. Use of AppManage is not explained in BusinessEvents documentation. See TIBCO Runtime Agent Scripting Deployment User’s Guide for details.
Specifying Global Variable Values in TIBCO Administrator
Global variables you define in a project appear automatically in TIBCO Administrator, on the application’s Advanced tab. To navigate to this tab, expand Application Management > Application_Name > Configuration, click the application name in the Configuration Builder panel, and then click Advanced. You see the list of global variables. Provide a value in the Value field. Save and deploy.
Before Deploying a Project in a TIBCO Administrator Domain
1.
Note that these names are case sensitive.)
2.
You only place the CDD inside the EAR for deployment using TIBCO Administrator. In all other cases the CDD is outside the project and not included in the EAR.
When you deploy, the processing unit named default starts.
Deploying a Project in a TIBCO Administrator Domain
After you have built the EAR you are ready to deploy.
To Deploy a Project EAR in a TIBCO Administrator Domain
1.
2.
Web browser: http://host-name:port/ (where host-name is the machine name and port is the HTTP port specified during installation, 8080 by default)
3.
Select the administration domain for the application and provide the username and password assigned during installation, or other administrator user credentials.
4.
a.
Click Application Management (in the left panel).
b.
Click the New Application button.
c.
At the Upload EAR File dialog, click Browse, select the EAR file you want to deploy, and click OK.
d.
At the New Application Configuration dialog, set the Application Parameters and Services settings as desired (click Help for details) and click Save. By default, Name is set to the EAR file name and Deployment Name is set to the EAR file name prepended with the domain name.
5.
Expand to Application Management > application_name > Configuration.
Setting Engine Properties
6.
As desired, in the Configuration Builder panel, click the BAR name (application_name.bar) and select the Advanced tab. Set properties as desired. Click Save.
When you deploy the BusinessEvents engine using TIBCO Administrator, the property values set on the Advanced tab override values set for the same properties in the engine property (TRA) file.
7.
As desired, in the Configuration Builder panel, click the application name and set values in the Advanced tab, for example, for global variables. Click Save.
8.
a.
In the Configuration Builder panel, click the application name. In the General tab, Target Machines panel, the current machine is available by default.
b.
As desired, select Add to Additional Machines to deploy the application to multiple machines. Select the machines to which you will deploy. You can also select the same machine more than one time, if you want to deploy the application more than once on a machine.
c.
Click Save.
9.
10.
At the Deploy Configuration dialog, configure settings if desired then click OK. The application deploys, and the Configuration dialog displays again.
You can check the Show deployed configuration checkbox to display the Deployed Configuration panel and verify success: