Previous Topic: Configure Each Copy of the ProductNext Topic: Install, Configure, and Deploy Multiple Instances on Multiple Computers

Installing › Install, Configure, and Deploy Multiple Instances on One Computer › Deploy Multiple Copies to One Computer

Deploy Multiple Copies to One Computer

You must deploy each copy of the WAR or EAR file that you created.

Follow these steps:

For the embedded Apache Tomcat

Start your Java EE Application Server.

Note: The WAR files are predeployed on Apache Tomcat.

For WAR Files Deployment
  1. If you are deploying more than one copy of the CAOMWebViewer12.war file to Apache Tomcat, you do not deploy additional copies of the castylesr5.1.3.war file.
  2. Rename your WAR files before deployment, so that each CA OM Web Viewer application WAR has a different name. This WAR file name also serves as the context path in the CA OM Web Viewer application web address.

    For example, a WAR named CAOMWebViewer12_US.war produces a web address, such as http://<server>:<port>/CAOMWebViewer12_US.

    Note: For more information about deploying to Apache Tomcat or context paths with Application Level External Configuration, see the deployment prerequisites.

For EAR File Deployment

When deploying the application, you must deploy both EAR files. However, be careful to use a different context path for each web application.

  1. (Optional) Rename the CAOMWebViewer12_ear application.
  2. (Required) Rename the second CAOMWebViewer12_ear application.

    Important! The application names must not match.

  3. If you deploy three or more product instances, repeat Step 2 for each additional instance.
  4. (Optional) Map the context path for CAOMWebViewer12.war Web Module to a different value.

    For example, a context path of CAOMWebViewer12_US produces a web address, such as http://<server>:<port>/CAOMWebViewer12_US.

  5. (Required) Map the context paths of the second CAOMWebViewer12.war Web Module to a different value.

    Important! The context paths of each CAOMWebViewer12.war Web Module must not match.

  6. If you deploy three or more instances of CA OM Web Viewer, you repeat Step 5 for each additional instance.
  7. Map the context path of the CA Styles R5.1.3 Web Module in the second CAOMWebViewer12_ear application to an alternate value, and keep the CA Styles R5.1.3 Web Module untouched in the first CAOMWebViewer12_ear application.

    For example, define a context path of /castylesr5.1.3_alt.

  8. If you deploy three or more instances of CA OM Web Viewer, you repeat Step 7 for each additional instance.

    Note: For more information about deploying to WebSphere or context paths with Application Level External Configuration on WebSphere, see the deployment prerequisites.