Upgrade > Upgrade CMS UI

Upgrade CMS UI

Important  

  • You can upgrade UCMDB Browser to CMS UI version 2018.05, only if the version of the UCMDB server is 2018.05.
  • This section is relevant only for the CMS UI standalone.

To upgrade to the latest version of CMS UI, follow these steps:

  1. Unzip the file CMS_UI-<display_version_number>-standalone.zip to an accessible location:

  2. Stop the web application (Tomcat or UCMDB Server).

  3. Clear the user preferences for the users that have scheduled reports as follows:

    1. Go to JMX Console > UCMDB-UI:name=User Preferences > clearUserPreferences.

    2. In the user name field, enter the user's name.
    3. Click Invoke.
  4. Delete the old ucmdb-browser.war file from <Tomcat installation path>\webapps. Also, in <Tomcat installation path>\webapps delete the ucmdb-browser folder.

  5. Copy the new ucmdb-browser.war file to <Tomcat installation path>\webapps.

    Note If the server is running, use a cut-and-paste operation to put the new WAR file in place, rather than copy-and-paste. Using cut-and-paste copies the file instantly and causes the server to deploy the full application (instead of possibly deploying an incomplete WAR file).

  6. Copy the necessary update resources, depending on the type of installation you have, as follows:

  7. For the SAML authentication mode to work properly, from the CMS_UI-<display_version_number>-standalone.zip//conf folder, copy the saml_configuration.properties file and the server.truststore file to the <Tomcat installation path\conf folder.
  8. From the CMS_UI-<display_version_number>-standalone.zip//conf/esapi folder, copy the esapi.properties file to the <Tomcat installation path>\conf\esapi\ folder.
  9. Read the release notes for the latest version to determine which features and functionality you want to use and update your CMS UI settings accordingly.
  10. Open the ucmdb_browser_lwsso_config.xml file in the \conf folder, and replace the following lines:

    <logoutURLs>
    <url>.*/logout.jsp.*</url>
    </logoutURLs>

    with:

    <logoutURLs>
    <url>.*/logout*</url>
    </logoutURLs>
  11. Check if the following lines exist in the <Tomcat installation path>\conf\context.xml file, and delete them:

    <JarScanner>
            <JarScanFilter defaultPluggabilityScan="false" />
    </JarScanner>
  12. Start the Tomcat server.

All features and functionality from the previous installation are active in the new installation, as well as the new features and functionality for the latest version.