Deployment Using TIBCO Administrator or 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 deploy.
Do not use the fault tolerance features of TIBCO Administrator. Instead use the Agent.AgentClassName.maxActive property (see Table 13, Agents Tab Settings and Properties). To maintain one active and one standby agent, deploy two agents of the same class and set the maxActive property to 1. (You can also deploy more than two agents and set the property to a larger number for different use cases.)
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). 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 application, you can navigate here by expanding the explorer nodes on the left to Application Management > application_name > Configuration.)
5.
To set deployment wide and engine level settings, such as the CDD and processing unit, and global variable overrides, do the following.
a.
In the Configuration Builder panel, 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.
Deployment Settable Variables
b.
c.
Click Save when you are done. The Configuration Builder panel appears again.
PUID and CDD
d.
At the Configuration Builder panel, select the application-name.bar entry. It’s one level below the top level in the hierarchy. Then select the Advanced tab.
e.
Service Settable Variables
f.
g.
Click Save when you are done. The Configuration Builder panel appears again.
6.
a.
In the Configuration Builder panel, click the service name. The service is nested under the application name. It has the same name as the application, with the extension .bar). 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.
By default an engine starts when you deploy it. You can also start and stop engines as separate actions.
7.
8.
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: