![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
In this scenario, a file notification project has been modified using TIBCO BusinessWorks. The buildear utility builds an EAR file for deployment. Based on the EAR file, the AppManage utility creates a deployment configuration file which includes XML tags for each deployment option. Using a text editor, the machine binding tags are edited. The AppManage utility is then used to deploy the application.The project is configured using TIBCO Designer. After all components in an archive resource are configured, the buildear utility can be used to build the EAR file.You can have multiple archive resources defined in a project. The -ear option allows you to provide the location of the archive resource that contains the changed components. You can get the archive resource URI in TIBCO Designer by selecting the archive and clicking Resource > Inspect Resource. The Resource Inspector dialog shows the URI next to theicon.
The -o option identifies the location and name of the output EAR file. The EAR file name must use the .ear suffix. If not specified, the EAR file location for the Enterprise Archive is used.The -p option provides the location of the TIBCO Designer project where the archive has been created.The deployment configuration file is created by the AppManage utility based on information in the EAR file. The -out option provides the name and location of the deployment configuration file. The file is created with XML tags for all required schema and substitution variables for each machine binding tag.Before editing the file, copy it and name it based on the application and administration domain into which the application will be deployed. Open the new file and change the substitution variables defined by the AppManage utility for the processes. In this example the <machine> XML tags are modified with the name of the machine on which the processes run.The generated file includes substitution variables for the machine element value. The variables use the syntax, %%<archive-type>-machine%% (a combination of percent symbols, archive type and computer name). During deployment you must configure an element that uses such a variable by replacing the substitution value with the actual value, without the percent symbols.The following command line uploads the EAR file and the deployment configuration file into the tp001 domain. The -deploy action indicates that the application is to be uploaded and deployed in one operation. The -ear option specifies the EAR file to load and the -deployconfig option specifies the name of the deployment configuration file. The -app option provides the application name. The admin account is used in this example. If you are using a normal user account, it must have the Administer permission set for the application. Note that the application name and administration domain name are case sensitive.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |