Previous Topic: Deployment Prerequisites for Apache TomcatNext Topic: Environment Considerations

Deploying › Deploying Your Configuration Settings Changes

Deploying Your Configuration Settings Changes

External System Level Configuration

You must restart the product for the configuration change to take effect.

If you deployed the product on a different system, copy the updated configuration files (the configuration directory) to the other system, before you restart CA OM Web Viewer.

Note: For more information about deployment scenarios, see Installation Scenarios.

Application Level External Configuration

In all cases, you must restart the product for the configuration change to take effect.

If you changed your Application Level External configuration directory location, or if this is the first time you added an Application Level External Configuration directory location:

Redeploy your changed WAR or EAR file, if you were using a WAR or EAR file.

If you are using the embedded Apache Tomcat:

  1. Stop your Apache Tomcat application server.
  2. If you are using the embedded database, copy your apache-tomcat-#.#.##/webapps/CAOMWebViewer12/database directory from your Apache Tomcat install to an alternate location.
  3. If you are using the embedded database, delete the CAOMWebViewer12 directory from the webapps directory of your Apache Tomcat install.
  4. Restart your Apache Tomcat application server.
  5. If you are using the embedded database, copy your apache-tomcat-#.#.##/webapps/CAOMWebViewer12/database directory to your Apache Tomcat install from your alternate location that you defined in Step 2.
  6. Restart your Apache Tomcat application server.

Application Level Internal Configuration

If you were using a WAR or EAR file, with internal configuration files, you must always redeploy you EAR or WAR file.

If you are using the embedded Apache Tomcat:

  1. Stop your Apache Tomcat application server.
  2. If you are using the embedded database, copy your apache-tomcat-#.#.##/webapps/CAOMWebViewer12/database directory from your Apache Tomcat install to an alternate location.
  3. If you are using the embedded database, delete the CAOMWebViewer12 directory from the webapps directory of your Apache Tomcat install.
  4. Restart your Apache Tomcat application server.
  5. If you are using the embedded database, copy your apache-tomcat-#.#.##/webapps/CAOMWebViewer12/database directory to your Apache Tomcat install from your alternate location that you defined in Step 2.
  6. Restart your Apache Tomcat application server.

File Permissions Considerations

This section describes how to set permissions for Linux, USS, and UNIX-type deployments.

When CA OM Web Viewer is configured for either System Level External Configuration or Application Level External Configuration, the Java web application server must have the following minimum file permission access to CAOMWV12_HOME folder contents:

Folder File Access

<CAOMWV12_HOME>

derby.log rw- (6)

\config <all contents, recursive> r- (4)

\database <all contents, recursive> rw- (6)

\logs <all contents, recursive> rw- (6)

Access in this case refers to either User or Group access, depending on if you server is running as the same user as the installer, or only in the same group, The accesses listed can be set at the system level, if the installer and server are not in the same group, but this is not recommended, as it is an insecure setup.

If these minimum permissions are not met, CA OM Web Viewer may fail to start correctly, because it cannot read its configuration settings; or may start but users are unable to get a report list, because it cannot read/write to the run-time database.