Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 10 Deployment Using TIBCO Administrator and at the Command Line : Deploying a Project in a TIBCO Administrator Domain

Deploying a Project in a TIBCO Administrator Domain
After you do any actions explained in Before Deploying a Project in a TIBCO Administrator Domain, and build the EAR file, you are ready to configure for deployment and deploy.
Do not use the fault tolerance features of TIBCO Administrator. Instead use the Agent Classes tab > AgentClassName > Max Active setting (see Agent Classes Tab Settings and Properties). To maintain one active and one standby agent, deploy two agents of the same class and set the Max Active setting to 1. (You can also deploy more than two agents and set the property to a larger number for different use cases.)
To Configure and 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 at installation. It is 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). You can change default names:
Name: Set by default to the TIBCO BusinessEvents Studio project name
Deployment Name: Set by default to the TIBCO BusinessEvents Studio project name prepended with the domain name.
e.
Click Save.
If the application does not appear in the list of applications, check Before Deploying a Project in a TIBCO Administrator Domain and ensure you have met all prerequisites.
You see the Configuration Builder panel. (For existing applications, you can navigate here by expanding the explorer nodes on the left to Application Management > application_name > Configuration.)
5.
To set deployment wide settings such as deployment-wide global variable overrides, select the application (which is at the top level in the hierarchy) and select the Advanced tab.
Ensure that the Transport field is set to local. This is the only supported transportation option. An example application level Advanced tab is shown next:
Click Save when you are done. The Configuration Builder panel appears again.
6.
To set project-related settings that apply to all deployed engines on all machines, at the Configuration Builder panel, select the application-name.bar entry. It’s one level below the top level in the hierarchy. Then select its Advanced tab.
As desired, enter the name of the CDD file and processing unit (PUID) you want to use for all deployed engines. You can use a relative or absolute path.
The engine looks first in the file system, under the given path. If the path is specified as a relative path, it is relative to the working directory (in this case: ...tibco/tra/domain/domainName/application/appName/
If no CDD is found in the file system, the engine looks within the EAR, under the given path. If the path is specified as a relative path, it is relative to the project root.
You can also override any service-settable global variable values as desired. Values entered here apply to all deployed engines.
Click Save when you are done. The Configuration Builder panel appears again.
7.
a.
In the Configuration Builder panel, click the service (application.bar) name. The service name is nested under the application name. In the General tab, Target Machines panel, the current machine is available by default.
b.
Select Add to Additional Machines and select the machines to which you will deploy the application.
You can select the same machine more than one time, if you want to deploy the application more than once on a machine. For example, you would do this when you want to deploy two different processing units to one machine.
c.
Click Save.
8.
Now you can set project-related settings that apply to deployments on specific machines. At the Configuration Builder panel, select a machine-level entry (machineName - projectName). These entries appear below the application-name.bar entry. Then select its Advanced tab. You see a dialog similar to the following:
The same project-related options are available here as at the .bar level, but here they apply to the selected machine (or rather, the selected deployment to a machine). As desired, enter the name of the CDD file and processing unit (PUID) you want to use for this deployed engine. You can use a relative or absolute path.
Here you can also override any service-settable global variable values as desired.
Click Save when you are done. The Configuration Builder panel appears again.
9.
You are now ready to deploy. By default an engine starts when you deploy it. You can also start and stop engines as separate actions.
Navigate to the application’s main Configuration Builder dialog and click the Deploy button.
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:

Copyright © TIBCO Software Inc. All Rights Reserved