Install > Introduction

Introduction

Before installing CMS UI, ensure that your system meets the following requirements:

  • UCMDB version. UCMDB Server 2018.05.

  • CMS UI Server. OpenJDK 8 (64 bit) must be installed on the server where you install the CMS UI (the Apache Tomcat version gets its Java from the JAVA_HOME environment variable).

Important The latest version of CMS UI works only with the latest released version of UCMDB server.

The CMS UI installation currently comes in two formats:

  • Windows Installation Package. A zip file called CMS_UI-<display_version_number>_Windows.zip that contains the following packages, depending on the type of installation you have:

    • CMS UI Package. A zip file called CMS_UI-<display_version_number>-all-in-one-standalone.zip that consists of the ucmdb-browser.war file, discovery-log.war file, discovery.war file, and a /conf folder with the CMS UI configuration files. Use this format if you already have an Apache Tomcat Server installed, or you want to install the Tomcat server on your own.

      Note If you are planning to install CMS UI with a Tomcat server, it is not recommended to do this on the same machine that runs the UCMDB Server. For details about installing both applications on the same machine, see Install CMS UI on the Same Machine that Runs the UCMDB Server.

    • Pre-configured Apache Tomcat Server package for Windows. A zip file called CMS_UI-<display_version_number>-tomcat-assembly-windows.zip that consists of a pre-configured Apache Tomcat server for Windows with the ucmdb-browser.war file, discovery.war file, and discovery-log.war file. The CMS UI configuration files reside under the /conf folder.
    • Existing Apache Tomcat server package. A zip file called CMS_UI-<display_version_number>-standalone.zip that consists of the ucmdb-browser.war file, and a /conf folder with the CMS UI configuration files. Use this format if you have an Apache Tomcat sever installed and you want to upgrade the CMS UI to the latest version.

  • Linux Installation Package. A zip file called CMS_UI-<display_version_number>_Linux.zip that contains the following packages, depending on the type of installation you have:

    • CMS UI Package. An archive file called CMS_UI-<display_version_number>-all-in-one-standalone.tar.gz that consists of the ucmdb-browser.war file, discovery-log.war file, discovery.war file, and the CMS UI configuration files. Use this format if you already have an Apache Tomcat Server installed, or you want to install the Tomcat server on your own.

      Note If you are planning to install CMS UI with a Tomcat server, it is not recommended to do this on the same machine that runs the UCMDB Server. For details about installing both applications on the same machine, see Install CMS UI on the Same Machine that Runs the UCMDB Server.

    • Pre-configured Apache Tomcat Server package for Linux. An archive file called CMS_UI-<display_version_number>-tomcat-assembly-unix.tar.gz that consists of a pre-configured Apache Tomcat server for Windows with the ucmdb-browser.war file, discovery.war file, discovery-log.war file, and the CMS UI configuration files.
    • Existing Apache Tomcat server package. An archive file called CMS_UI-<display_version_number>-standalone.zip that consists of the ucmdb-browser.war file, and the CMS UI configuration files. Use this format if you have an Apache Tomcat sever installed and you want to upgrade CMS UI to the latest version.

Caution Apart from the OOTB files, DO NOT ADD any additional resources into the <UCMDB_Server_Home>\deploy directory. Because UCMDB will try to deploy every file from this location, which may cause the ucmdb-browser.war file not deployed completely, and as a result the CMS UI will fail to start.

Send Help Center feedback