2.2 Upgrading CMS

Upgrading an existing Managed Objects myCMDB installation to Operations Center CMS, a database process performs a conversion of references (including element names, relationship names, attribute values, etc.) to migrate the existing myCMDB hierarchy into a new CMS hierarchy.

Before upgrading an installation of Managed Objects myCMDB to Operations Center CMS, it is important to perform a native database-level backup of the Configuration Storage database.

IMPORTANT:XML-based configstore exports are not sufficient as backups before upgrading to Operations Center CMS. It is necessary to perform a native database-level backup of the Configuration Storage database. Additionally, existing myCMDB XML-based imports are not compatible with the new CMS hierarchy.

To upgrade a myCMDB installation to Operations Center CMS:

  1. Perform a backup of the Configuration Storage database at the native database-level.

    For more information about the Configuration Storage database, see the Operations Center 5.6 Server Configuration Guide

  2. Stop the Operations Center server.

    For more information about stopping the Operations Center server, see Starting and Stopping the Server in the Operations Center 5.6 Server Installation Guide.

  3. Install NetIQ Operations Center and Operations Center CMS over the existing installation directories.

  4. Execute one of the following SQL scripts at the native database level against the Configuration Storage database to perform the upgrade.

    • MS SQL Server: /OperationsCenter_CMS_install_path/webapps/noc/scripts/mssql/cms_mssql.sql

    • Oracle: /OperationsCenter_CMS_install_path/webapps/noc/scripts/oracle/cms_oracle.sql

    Various Configuration Storage database tables, such as CFG_ATOM, CFG_ATTRIBUTE, CFG_ENTRY, are updated.

    IMPORTANT:It is important that the upgrade script be run prior to the first login to CMS. On the first login, a new CMS service model hierarchy is automatically created. If the upgrade script is run after an initial CMS login, problems will occur as the scripts assume there is no existing CMS hierarchy. If this does happen, delete the new CMS hierarchy and then run the upgrade script.

  5. Start the NetIQ Operations Center server and the CMS server.

    In the Operations Center console, the pre-existing myCMDB hierarchy under Service Models is now renamed to CMS.

    For more information on starting the Operations Center server, see Starting and Stopping the Server in the Operations Center 5.6 Server Installation Guide.

    For more information on starting the CMS server, continue to Section 2.3, Starting and Stopping CMS.