Deploying on a Service Level
In the Configuration Builder panel, perform these steps to set project-related settings that apply to all deployed engines on all machines.
- Procedure
- Select the
application-name.bar
entry. It is one level below the top level in the hierarchy. - Select its
Advanced tab.
Note: For TIBCO BusinessEvents, settings at both the application and service levels affect the entire deployment.
- 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.
Note: The TIBCO BusinessEvents engine looks for the CDD and processing unit as follows:
- 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.
- 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:
- You can also override any service-settable global variable values as desired. Values entered here apply to all deployed engines.
Note:
- Service-settable global variables are only available if the Include All Service Level Global Variables check box in the Build Enterprise Archive dialog is selected before generating the EAR file.
- Global Variable Overrides: If you override a global variable at a lower level, subsequent changes at higher levels are ignored.
- Click Save when you are done. The Configuration Builder panel appears again.
- Select the machines in the administration domain to which you will deploy the application.
- 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. - Select
Add to Additional Machines
and select the machines to which you will deploy the application.
Note: 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.
- Click Save.
- Continue with the steps described in Deploying on an Instance Level.