Previous Topic: Install, Configure, and Deploy on One ComputerNext Topic: Deployment Prerequisites for WebSphere


Choosing a Configuration Type

The following diagram describes the basic configuration types:

Diagram that shows the basic configuration types.

External System Level Configuration

Lets you update your application easily, and then you copy the application to multiple systems, without having to reconfigure the product.

Your configuration files are located in a directory outside of the CA OM Web Viewer web application on the same computer. The web application reads this directory location from the CAOMWV12_HOME Environment Variable.

You are not required to redeploy your CA OM Web Viewer application after you modify the settings. Only a web application restart is required. This configuration option lets you update your application easily, and then copy the CA OM Web Viewer application WAR or EAR file to multiple systems, without having to reconfigure the WAR or EAR file.

Important! This configuration is recommended for most environments. However, there are certain situations when you want to use another configuration type. If you intend to run two instances of CA OM Web Viewer on one computer, do not use External System Level Configuration. Instead, use Application Level External Configuration or Application Level Internal Configuration.

Application Level External Configuration

Lets you have two or more copies of the product on one Java application web server, or on one computer.

Your configuration files are located in a directory outside of the CA OM Web Viewer web application on the same computer. The web application reads this directory location from a parameter within web.xml.

Note: In some situations, you are required to redeploy your CA OM Web Viewer application after settings changes. Often, only a web application restart is required.

Important! To deploy the product to multiple servers using application level external configuration files, use the same path to your configuration files on all servers. If you do not use the same path, you have to apply patches to each system separately. With different configuration paths on each server, you cannot apply a patch to only one EAR or WAR file, for example, on a test computer, and then copy that same EAR or WAR file to each server where you to run the product, for example, on several production computers.

Application Level Internal Configuration

Your site security restrictions do not allow web applications to access files outside of the web application.

Your configuration files are located in a directory inside of the CA OM Web Viewer web application. The web application uses the default directory within the web application.

Note: You are required to redeploy your CA OM Web Viewer application after settings changes.

Important! To deploy the product to multiple servers using internal configuration files, you have to apply patches to each system separately. With internal configuration, you cannot apply a patch to only one EAR or WAR file, for example, on a test computer, and then copy that same EAR or WAR file to each server where you to run the product, for example, on several production computers.