Description:
This workaround is for deploying multiple TIBCO BusinessWorks Collaborator (BWC) (5.5.x) Applications in a single Tomcat instance. The following steps should be adhered to for the workaround. Basic working installation of BWC 5.5.x, including registration of Servlet engine and BWC component in the domain, is mandatory before using the steps for the workaround.

How to deploy Multiple TIBCO BusinessWorks Collaborator applications on a single Tomcat instance.

Steps to deploy Multiple BWC applications on a single Tomcat instance. Consider two BWC applications with App1.ear and App2.ear files to deploy.

Step 1). Deployment of First Application (App1.ear).

Deploy fist application App1.ear through Administrator. The first application should be deployed with conventional steps with no workaround specific changes. Successful deployment of the first application should start five services from five deployed archives.  (TIBCOsta_ps.war, TIBCOpps.war, TIBCOpas_pps.war, WorkflowArchive.war, App1Processes.par).

Step 2). Modification of Second Application (App2.ear).

Before deployment of the second application (App2.ear), modify the application.xml file under the META-INF folder of App.2ear (ear_root\META-INF\application.xml). Change the default values (TIBCOsta_ps and WorkflowArchive) of <context-root> element for modules with ID TIBCOsta_ps and WorkflowArchive. After modification it should look like the following.

<application>
    <display-name>TIBCO Portal Application</display-name>
    <description>TIBCO Portal Application</description>
    <module id="TIBCOsta_ps">
        <web>
            <web-uri>TIBCOsta_ps.war</web-uri>
            <context-root>TIBCOsta_ps_app2</context-root>
        </web>
    </module>
    <module id="TIBCOpps">
        <web>
            <web-uri>TIBCOpps.war</web-uri>
            <context-root>TIBCOpps</context-root>
        </web>
    </module>
    <module id="TIBCOpas_pps">
        <web>
            <web-uri>TIBCOpas_pps.war</web-uri>
            <context-root>TIBCOpas_pps</context-root>
        </web>
    </module>
    <module id="WorkflowArchive">
        <web>
            <web-uri>WorkflowArchive.war</web-uri>
            <context-root>WorkflowArchive_app2</context-root>
        </web>
    </module>
</application>


Note: <context-root> values of the above mentioned modules (TIBCOsta_ps and WorkflowArchive) should be changed for each subsequent deployment. These values should be different in each application.xml of BWC application ear archive.

Step 3). Uploading of Modified EAR.

Upload EAR from the Upload EAR file section of Administration.

Step 4). Configuration of Uploaded Application.

In the new application configuration panel which comes up after uploading of EAR, disable the services for following archive.

1). TIBCOpps.war
2). TIBCOpas_pps.war

Save this configuration.

Step 5). Deployment of the Application.

After doing all required conventional configuration for the enabled archives, deploy this second application. Successful deployment should not generate any error on the Administrator console.

Attachments:
========