How to edit a deployment configuration file for Tomcat while deploying TIBCO BusinessWorks Collaborator 5.5.1 application using Appmanage?
book
Article ID: KB0084807
calendar_today
Updated On:
Products
Versions
TIBCO BusinessWorks Collaborator
-
Not Applicable
-
Description
Resolution: During deployment of an application using Appmanage, first 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 XML tags need to be edited for Tomcat as follows.
Fill the fields in the deployment configuration file as shown below. Find the comments for each field and configure the values accordingly.
<service name="TIBCOsta_ps.war"> <enabled>true</enabled> <!-- This field's value should be 'true' --> <bindings> <binding name="TIBCOsta_ps"> <!-- binding name should be same as service name excluding '.war' --> <machine>inti</machine> <!-- This field's value should be your hostname --> <product> <type>appserver_tomcat</type> <!-- type should be 'appserver_tomcat' --> <version>5.5</version> <!-- version should be '5.5' --> <location>/tibco/env/i05tib/apache-tomcat-5.5.20</location> <!-- Give the location of your tomcat in this field --> </product> <container>server-11018</container> <!-- The value of this field should be 'server-<port no used for tomcat>' --> <description></description> <contact></contact> </binding> </bindings>
Make the above changes for all the four services- TIBCOsta_ps.war, TIBCOpps.war, TIBCOpas_pps.war and WorkflowArchive.war in the configuration file. Only the value for field <binding name> will vary for the above services.
Issue/Introduction
How to edit a deployment configuration file for Tomcat while deploying TIBCO BusinessWorks Collaborator 5.5.1 application using Appmanage?
Additional Information
Refer to the TRA documentation -> Scripting Deployment User’s Guide
-> Getting Started -> ‘Simple Application Deployment’ for more
references regarding application deployment using Appmanage.