Installing › Install, Configure, and Deploy on One Computer › Deployment Prerequisites for WebSphere

Deployment Prerequisites for WebSphere

Before you deploy CA OM Web Viewer on WebSphere, verify that you applied all fixes for the WebSphere server.

To deploy as a WAR file on WebSphere, set the Class loader order to Classes loaded with local class loader first (parent last) at both the module, and application level, in order to load libraries within the CA OM Web Viewer package first.

Notes:

• If you selected to produce an EAR file during installation, this setting is included in the EAR file automatically, so you can deploy this EAR file on WebSphere without changing this setting.
• For a web server to host multiple instances of CA OM Web Viewer, Java memory space needs to be large enough.
• With multiple instances of CA OM Web Viewer, you can deploy another server as a load balancer to dispatch requests. The load balancer must support session affinity or session stickiness to ensure that requests of the same session are directed to the same server.

Choose the appropriate configuration for your application.

System Level External Configuration

If you are using a System Level External Configuration, you must set the CAOMWV12_HOME variable within WebSphere. You set up a new environment variable named CAOMWV12_HOME in the Java and Process Management > Process definition > Environment Entries section of your Application Server. Then, restart your WebSphere server in order for the setting to take effect.

Important! Add CAOMWV12_HOME as an environment variable not as a property in order for CA OM Web Viewer to recognize CAOMWV12_HOME

Application Level External Configuration

When deploying using Application Level External Configuration, and you need to deploy more than one EAR file, be careful to use a different context path and application name for each web application deployed on WebSphere.

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 3 for each additional instance.
4. (Optional) Map the context paths 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.

Notes:

• When deploying multiple CA OM Web Viewer instances with different configuration on WebSphere, the class loader policy for server-specific application settings must be set to Multiple. For more information about how to set server-specific application settings, see your WebSphere documentation.
• When using different database systems with different CA OM Web Viewer instances deployed on WebSphere, WebSphere variables for specific database JDBC driver paths may be required to resolve the JDBC driver class loading. For more information about WebSphere variable settings, see your WebSphere documentation.
• For more information about WebSphere settings, see your WebSphere documentation.

Application Level Internal Configuration

Remove the CAOMWV12_HOME environment variable from within WebSphere, if it exists.