Performing core components upgrade

This topic was edited by a BMC Contributor and has not been approved.  More information.

During the upgrade of the core components, the installation program automatically detects the previous version of the product. Following the completion of the first phase of the upgrade, if you use Active Directory to authenticate users, the installation program prompts you to run the Security Configuration Tool to configure authentication for Monitor Edition. At the conclusion of the UI-based upgrade processes, you then must update the database data.

The steps necessary to upgrade the core components are described in the following sections:

Before you begin

  • Ensure that the System requirements and product compatibility for the new release are met for systems affected by the upgrade.
  • Ensure that you have a full backup that is accessible throughout the upgrade process. See Backing up before an upgrade or reinstall for details about how to make a full backup that includes the entire product directory and sub-directories on the server.
  • Ensure that there is a full backup of the product database, or that the database can be restored to a point in time prior to the upgrade. If a recovery proves necessary, a DBA should be available to perform it.
  • To free up disk space, after you have verified your full backup, you should remove the "FixPacks" directory and its sub-directories.  This folder is typically found as a sub-directory of the product installation.
  • Ensure that the license key and company name are valid. If the license key has expired, it can be updated in services.cfg, though we recommend you contact BMC Support for assistance. Note that there is also a CLI called execkey (execkey.bat on Windows and on Linux), which can be run to update the license key and company name; if running Linux in  anon-graphical environment, you can update services.cfg (when services are down).
  • You must have stopped all of the Monitor Consoles.
  • You must have stopped the services in the order specified in Starting and stopping services (the service names might have MQSoftware prefixes).

To update the core components

  1. Ensure that MainView Middleware Administrator is installed and running. This is required for the upgrade to MainView Middleware Administrator Monitor Edition (which replaced the legacy Configuration Manager). See  MainView Middleware Administrator .
  2. If necessary, return to the user under which you want to install and run MainView Middleware Monitor (MVMM).
  3. Use one of the following methods to start the installation program:
  4. Select Update the existing installation.
  5. After accepting the license agreements and reviewing the preinstallation steps, select the services to update, and click Next
  6. Select one of the installation modes, and click Next.
  7. Choose whether to configure the integration with MainView Middleware Administrator now or at a later time. 
    • If you choose to configure the integration now, MainView Middleware Administrator must be running.
    • If you choose to configure the integration later, skip to Step 9.
  8. Enter the host name, port, and project for MainView Middleware Administrator, and click Next.
  9. Enter the trust store path and password, and click Next.
  10. Verify that the certificate was installed, and click Next.
  11. Review your entries for the upgrade and click Install

To apply service and agent Fix Packs

Before continuing with any upgrade tasks, ensure you have applied any service or agent Fix Packs; make sure you follow the instructions in the Fix Pack readme file. The latest Fix Packs can be found under Release notes and notices.

To update the security configuration

Following the completion of the upgrade of the core components, you can choose to retain or update your security configuration. Choosing to update it launches the Security Configuration Tool. The following steps provide a high-level view of the process. For details, see Configuring the Active Directory security mode with the Security Configuration tool.

  1. To update the security information, select Run the Security Configuration Tool, and click Next twice.

  2. Select Active Directory (Delegate Mode), and click Next.
  3. Provide the Active Directory domain name, ports, and Security Transport Type for the Active Directory delegate mode, and click Next.
  4. Enter or confirm the base Active Directory fully qualified domain name, and click Next.
  5. Provide the user name and password for the user that will become the TrueSight Middleware Administrator, and click Next.
  6. Provide the Active Directory Common Name and password, and click Next.
  7. Review, modifying if necessary, the security settings for your environment, and click Next:
    • The value that you provided in Step 6 for the Common Name will replace #LDAPUSER#.
    • The value that you provided in Step 4 for the fully qualified domain name will replace #FQDN#.
  8. Choose the Active Directory domain controller to use, and click Next:
  9. Choose your preference for handling SSL security certificates, and click Next.
  10. Review the security settings, and click Install.
  11. When the security configuration is finished, click Done to exit the Security Configuration Tool and return to the installation program.
  12. After reviewing the instructions to update the database, click Next and then click Done to exist the installation program.

To update the database

The database update process is largely accomplished by running scripts and is basically the same process irrespective of the database brand and the operating system on which it is installed.

You can run these utilities using the database credentials or the MVMM credentials. If you prefer to use the MVMM user id and password rather than the database credentials, you must start the Application Service in a special console mode that brings up jetty and our security service.

If you also intend to update your database credentials during the upgrade process (for example, you are migrating MVMM from one database type to another) , see Updating database properties.


The installer identifies the SQL file to be applied by the database administrator during upgrades; you can manually run the find_sql_rollup script if you forgot or did not make a note of the file during the upgrade (you will also need to run db_schema_sync, as detailed below). Additionally, BMC Support may prompt you to run the script if there was an issue during installation.

  1. In a console window enter the following command:
    qpas –j
  2. In another console window, access the InstallDir .
  3. Run the SQL file identified by the installer, or run the find_sql_rollup utility using one of the following methods.
    See find_sql_rollup and dbschema_sync command parameters for more information.
    • If you access the database directly using a database user, enter:
      find_sql_rollup -d db_type db_name db_userid [-p db_password | -s]
      For parameter descriptions, see the find_sql_rollup and dbschema_sync using a database user directly to the database table in find_sql_rollup and dbschema_sync command parameters.
      find_sql_rollup returns the name of the migration script to use in the next step.
    • If you access the database using an existing MVMM user with access to the database using the MVMM Application Service, you need to start the Application Service using "-j" (as described above), then issue: find_sql_rollup userid [-p password | -s]

      For parameter descriptions, see the find_sql_rollup and dbschema_sync using a MVMM user and the MVMM Application Service table in find_sql_rollup and dbschema_sync command parameters.
  4. Execute the rollup script found by find_sql_rollup against your existing MVMM database as the same user that runs the MVMM services using a utility that ships with your database client, or have your DBA run the script. 
    For commands, see the Creating and initializing the database and scripts section for the database in question.
  5. Perform this step when using DB2; otherwise, skip to Step 6. The SQL roll-up script contains ALTER SQL statements which alter columns in QP_NODES. As a result, the QP_NODES table might be in a REORG PENDING state following the run of the roll-up script. After running the roll-up script, reorganize the QP_NODES table. If the table is not reorganized, dbschema_sync fails. Consult your DBA to reorganize (reorg) QP_NODES.

    REORG command example

    reorg table <bmtm schema>.qp_nodes

    For parameter descriptions, see the find_sql_rollup and dbschema_sync using a database user directly to the database table in find_sql_rollup and dbschema_sync command parameters .

    If you access the database using an existing MVMM user with access to the database using the MVMM Application Service, you need to start the Application Service using "-j" (as described above), then issue:
    dbschema_sync userid [-p password | -s]

    For parameter descriptions, see the find_sql_rollup and dbschema_sync using a database user directly to the database table in find_sql_rollup and dbschema_sync command parameters .

    dbschema_sync propagates object attribute changes to nodes and history templates. When an attribute is added or removed from an object's definition, the changes must be retroactively applied to objects already defined. Changes in the attributes a template supports must be made to the database schema.

    The length of time it takes for dbschema_sync to complete depends on the number of monitored objects in your database and the database schema from which you are upgrading. (Upgrading from a newer database schema takes less time than upgrading from an older schema.) Normally, it takes only a few minutes, but occasionally it can take two hours or more. Other database resources, such as temporary space, can be considered. If you have specific questions about dbschema_sync, contact BMC Support.

    After this utility successfully completes your database is fully upgraded.

  6. Run dbschema_sync using the following method:

    dbschema_sync -d db_type db_name db_userid -i [-p db_password | -s]

    -s reads from stdin for password, and which is mutually exclusive with -p
    -i ignores the result of the check for the total number of database connections 

To restart services and clients

  1. Start the MVMM Services in the correct order.
    See Starting and stopping services for further details.
  2. Start the Monitor Console.

    A WebStart (JNLP) Monitor Console will be automatically upgraded if the Monitor Console is started from the MVMMstart page.

    An installed (standalone) Monitor Console should be uninstalled. The latest version, available on the MVMM start page, should be installed.


    BMC recommends that you delete the Monitor Console from the Java WebStart cache before starting a new Monitor Console. You can do this by opening the Java Control Panel item on each client computer.

    1. On the General tab in the Temporary Internet Files section, select the View option.

    2. Choose to show Applications, and delete the MVMMMonitor Console application

  3. When using event automation, update the perl packages from event automation. See Installing files to automate events.

To free up disk space used by logs from the upgraded release

You may use the do_support utility to purge logs older than 60 days.  

  1. Change the directory to the support_tools sub-directory of your installation.
  2. Run do_support with the -p option to purge logs older than 60 days:

 do_support -p

To verify the MVMA integration

Once the services have been restarted, you can verify the MVMA integration.

Where to go from here

Upgrade your Agent and Extensions as soon as possible. See Upgrading the Agent and Extensions.

Existing transaction pathways continue to function as long as they are not altered and generated. Once a transaction pathway is generated, all hosts that are used by that transaction pathway should have been upgraded. 

Was this page helpful? Yes No Submitting... Thank you