Upgrading MVMA

This topic describes how to upgrade MVMA. 

Before you begin 

See Upgrade-process-overview.

Related topic

Upgrading-and-migrating

To upgrade MVMA

  1. Back up the installation directory by zipping it and storing it somewhere safe.

  2. To accelerate the upgrade process, the contents of the work directory can be deleted before running the upgrade installation. 

    Important

    Note the default installation path is C:\BMC\MVMA on Windows and /opt/BMC/MVMA on Linux. You might need to adjust the path to your current installation.

To upgrade installation on Windows

  1. MVMA services must be stopped prior to upgrading.
  2. Navigate to the directory where the installation files are located.
  3. Change the directories to .\Disk1\InstData\Windows\VM.
  4. Run install.exe from the directory. A message is displayed indicating that the wizard is being prepared.
  5. On the Wizard introduction page, select Next. 
  6. Select one of the following installation sets based on your middleware administration infrastructure (IBM MQ, TIBCO EMS, or both) and then click Next.
    The subsequent installation steps reflect your choice.
  7. Read and accept the License Agreement that is displayed on the next Wizard page, and click Next.
  8. Set the installation destination to the directory where your previous MVMA installation exists. click Choose to choose the location of the existing installation and then click Next.
  9. You should get the message “The MainView Middleware Administration Installation had detected an existing installation. In Order to update the existing installation the MainView Middleware Administration Service must be stopped. You must make sure the service is stopped before continuing.” Click Next.          
  10. Click Install. Pre-installation summary is displayed on screen. 
  11. When the Install Complete page is displayed, click Done to exit the wizard.

To upgrade installing on Linux using the console option

  1. In a console, navigate to the directory where the installation files are located
  2. Run the command ./Disk1/InstData/Linux/VM/install.bin –i console
    A console opens to inform you that the installer is being launched.
  3. On the license screen, read the license terms and press Enter.
  4. Read the remaining information and type Y to accept licensing terms.
  5. Type in the destination to the directory where your previous MVMA installation exists. Note that MVMA services must be stopped prior to upgrading. 
  6. You should get the message, "The MainView Middleware Administration Installation had detected an existing installation. In Order to update the existing installation the MainView Middleware Administration Service must be stopped. You must make that the service is stopped before continuing.” press Enter.          
  7. If TIBCO EMS support is included in your installation, enter a destination folder where EMS files are stored (example: /opt/tibco/ems/<version>/lib, where <version> is the EMS version; for example /opt/tibco/ems/8.6/lib). Press Enter.

  8. When installing TIBCO EMS components, either the server machine must have TIBCO EMS installed or these specific TIBCO files must be copied to the server machine:

    Important

    For TIBCO EMS 8.6 to 10.1:  jms-2.0.jar, tibjms.jar, tibjmsadmin.jar

    For TIBCO EMS 10.2 or later:  jakarta.jms-api-2.0.3.jar, tibjms.jar, tibjmsadmin.jar

  9. Review the pre-installation summary. Press Enter.
  10. The installation is completed.

Perform the following steps post installation

  1. Prepare the directories for MongoDB to place its log files and the MVMA database as described in, see Prepare MongoDB
  2. Upgrading MVMA preserves the following files and folders, but we recommend that you review them after the new installation to confirm their preservation:
    1. etc/known_hosts
    2. security/*
  3. Clear your browser cache to verify that the browser has preserved the upgraded Web-UI components. If these components have not been preserved, interference with cached components of an earlier version of the product might cause unpredictable results when the browser renders the Web UI.

  4. To disable weak cipher suites, make sure that weak cipher suites are disabled by opening configuration/services/org.apache.felix.http.cfg and verifying that the following list is assigned to the org.apache.felix.https.jetty.ciphersuites.excluded configuration setting:

     org.apache.felix.https.jetty.ciphersuites.excluded=SSL_RSA_EXPORT_WITH_RC4_40_MD5,.*DES.*,.*CBC.*,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_GCM_SHA384

  5. To disable older TLS versions, make sure that older TLS versions are disabled by opening configuration/services/org.apache.felix.http.cfg and verifying that the following list is assigned to the org.apache.felix.https.jetty.protocols.excluded configuration setting:

    org.apache.felix.https.jetty.protocols.excluded=TLSv1,TLSv1.1

    Important

    Do not start the MVMA service before completing the data migration as described in the next section.

To migrate data from MVMA 9.1 to MVMA 9.2

This section demonstrates how to use the exportMongoDB and importMongoDB utilities installed with MVMA 9.2 to migrate your database when upgrading from MVMA 9.1 to MVMA 9.2 or later.

Before you begin

Verify that the following prerequisites are met:

  • During the upgrade installation, confirm the previous MVMA 9.1 is backed up to the installV92Backup sub-directory located in the MVMA 9.2 installation directory mvma92_installpath.
  • Verify that the MongoDB database and the MongoDB database configuration from MVMA 9.1 were backed up into the migrate sub-directory of the MVMA 9.2 installation directory.
  • MongoDB database server that you intend to use with MVMA 9.2.00 is installed on the system (mongodb_target_installpath).
  • MongoDB database tools compatible with the MongoDB database server that you intend to use with MVMA 9.2.00 are installed on the system (mongodb_tools_target_installpath).
  • You have already created the new empty data directory for MongoDB to be used with MVMA 9.2 on the system. (for example,<mvma92_db_root>\data\db where <mvma92_db_root> refers to the root of the directory configured for the MongoDB server to store the data for MVMA 9.2. Note the previous versions of MVMA this was in the data/db sub-directory of the MVMA installation folder by default. Starting with MVMA 9.2, we do not recommend to store the MongoDB database in the installation folder to prevent unintentional data loss or corruption, as this path is no longer managed by the product and will not be included in future updates or fixpacks.
  • You have all MVMA services and any MongoDB server stopped at this point.

Perform the following steps, depending on the platform you are using:

  • For Windows

    1. Open a command prompt to the MVMA 9.2 installation directory mvma92_installpath.
    2. Change to the migrate subdirectory running cd migrate.
    3. Start MongoDB from MVMA 9.1 with the MVMA 9.1 data and configuration running: '..\installV92Backup\mongodb\mongodb-win32-x86_64-3.2.17\bin\mongod -f etc\data.conf --logpath data.log'
    4. Verify from MongoDB's log file data.log written to the current working directory that MongoDB used with MVMA 9.1 is running properly.
    5. Open another command prompt to the MVMA 9.2 installation directory mvma92_installpath.
    6. Run 'bin\exportMongoDB.bat installV92Backup\mongodb\mongodb-win32-x86_64-3.2.17'
    7. When the command has completed successfully, verify that mongodb_export directory is created in the current working directory and contains the MVMA collections exported from MongoDB in JSON format.
    8. In the command prompt you have started MongoDB belonging to MVMA 9.1, press CTRL+C to stop the running MongoDB server.
    9. Start MongoDB to be used with MVMA 9.2 with the intended data directory and log path running: <mongodb_target_installpath>\bin\mongod --dbpath <mvma92_db_root>\data\db --logpath <mvma92_db_root>\logs\data.log
    10. Verify from the MongoDB logs that MongoDB has started properly.
    11. Switch to the command prompt from which you have previously exported MongoDB for MVMA 9.1.
    12. Run bin\importMongoDB.bat <mongodb_tools_target_installpath>
    13. Verify that the command has completed successfully.
    14. Start MVMA 9.2 services. To start the MVMA service on Windows, see Starting services after installation
    15. Verify that MVMA 9.2 started properly.
    16. In a browser, verify that you can log in to MVMA 9.2 as expected and that you get expected objects in the MVMA UI after login.
  • For Linux

    1. Open a command prompt to the MVMA 9.2 installation directory mvma92_installpath.
    2. Change to the migrate subdirectory running cd migrate.
    3. Start MongoDB from MVMA 9.1 with the MVMA 9.1 data and configuration running: '../installV92Backup/mongodb/mongodb-linux-x86_64-3.2.17/bin/mongod -f etc/data.conf --logpath data.log'
    4. Verify from MongoDB's log file data.log written to the current working directory that MongoDB used with MVMA 9.1 is running properly.
    5. Open another command prompt to the MVMA 9.2 installation directory mvma92_installpath.
    6. Run './bin/exportMongoDB.sh ./installV92Backup/mongodb/mongodb-linux-x86_64-3.2.17'
    7. When the command has completed successfully, verify that mongodb_export directory is created in the current working directory and contains the MVMA collections exported from MongoDB in JSON format.
    8. If in the command prompt you have started MongoDB belonging to MVMA 9.1, press CTRL+C to stop the MongoDB server.
    9. Start MongoDB to be used with MVMA 9.2 with the intended data directory and log path running: <mongodb_target_installpath>/bin/mongod --dbpath <mvma92_db_root>/data/db --logpath <mvma92_db_root>/logs/data.log
    10. Verify from the MongoDB logs that MongoDB has started properly.
    11. Switch to the command prompt from which you have previously exported MongoDB for MVMA 9.1.
    12. Run ./bin/importMongoDB.sh <mongodb_tools_target_installpath>
    13. Verify that the command has completed successfully.
    14. Start MVMA 9.2 services. To start the MVMA service on Linux, see Starting services after installation
    15. Verify that MVMA 9.2 started properly.
    16. In a browser, verify that you can log in to MVMA 9.2 as expected and that you get expected objects in the MVMA UI after login.

For more information see, Migrating-data

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*