Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see MainView Middleware Monitor 9.2.

Installing the MVMM Server Fix Pack


Install MVMM Server Fix Pack on your MVMM service machine.  Fix Packs are cumulative and contain all updates from the previous Fix Packs. A new Fix Pack renders all previous Server Fix Packs obsolete.

Warning

Important

In this procedure, nnn represents the Server Fix Pack version.

Success

Best practice
Back up the database and product installation directories regularly. 

Before you begin

  1. Make sure that the 9.0.00.550 GA or Server Fix Pack from the last release is installed.

    Warning

    Important

    While installing GA, if you are prompted to run the Security Configuration tool, do not run it at this stage. Run it after applying the Agent Fix Pack, see Step 7 in Installing-the-MVMM-Agent-Fix-Pack.

  2. Review the Fix Pack's notes and instructions. You can extract the README.txt file from the downloaded Fix Pack zip file by running the following command for your service platform:

    • Windows
      unzip -o FixPack9000.nnn_Server.zip FixPack9000.nnn_Server\README.txt
    • Unix 
      unzip -o FixPack9000.nnn_Server.zip FixPack9000.nnn_Server/README.txt

To install the MVMM Server Fix Pack

Warning

Important

If you are running services on Microsoft Windows, run all commands in an elevated (or Administrator) command prompt.

  1. (Recommended) Create a directory named FixPacks under your server installation directory (if it does not already exist). 

    Information
    Example
    • UNIX
      If the product is installed in /opt/MVMM, create the directory /opt/MVMM/FixPacks.
    • Windows
      If the product is installed in D:\MVMM, create the directory D:\MVMM\FixPacks.
  2. Download the Fix Pack file (FixPack9000.nnn_Server.zip) to the FixPacks directory.
  3. Unzip the archive. 

    Information
    Example
    • UNIX
      If the product is installed in /opt/MVMM, run the following command: 
      cd /opt/MVMM/FixPacks 
      ../AGENT_DIST/9.0.00/LINUX/X64/unzip FixPack9000.nnn_Server.zip
    • Windows
      If the product is installed in D:\MVMM, run the following command:  
      cd /d D:\MVMM\FixPacks 
      ..\AGENT_DIST\9.0.00\WINDOWS\unzip.exe FixPack9000.nnn_Server.zip
  4. You should now have a directory named FixPack9000.nnn_Server in the FixPacks directory.

    Information
    Example
    • UNIX
      If the product is installed in /opt/MVMM, the directory /opt/MVMM/FixPacks/FixPack9000.nnn_Server should now exist.
    • Windows 
      If the product is installed in D:\MVMM, the directory D:\MVMM\FixPacks\FixPack9000.nnn_Server should now exist. 
  5. Stop the services and verify that they have stopped. If you are installing this Fix Pack immediately after installing MVMM, the services have probably not been started.
  6. Run the Fix Pack installation script. It doesn't matter which directory you are in when you run the script. The default action is to install the Fix Pack. To see the help, run the script with the --help option. 

    Information

    • UNIX
      If the product is installed in /opt/MVMM, run the following command:
      /opt/MVMM/FixPacks/FixPack9000.nnn_Server/mvmm_fixpack_tool.sh
    • Windows
      If the product is installed in D:\MVMM, run the following command:
      D:\MVMM\FixPacks\FixPack9000.nnn_Server\mvmm_fixpack_tool.bat
    If you choose to unpack the FixPack9000.nnn_Server.zip file in a different location, then you must specify the product location when running the installation script. 

    Information
    Example
    • UNIX
      If you are installing the product in /opt/MVMM and the Fix Pack is in /local/MVMM/FixPacks/FixPack9000.nnn_Server, run the following command:
      /local/MVMM/FixPacks/FixPack9000.nnn_Server/mvmm_fixpack_tool.sh --product_path /opt/MVMM
    • Wind
      If you are installing the product in D:\MVMM and the Fix Pack is in F:\FixPacks\FixPack9000.nnn_Server, run the following command: F:\FixPacks\FixPack9000.nnn_Server\mvmm_fixpack_tool.bat --product_path D:\MVMM
  7. Check the output of the script and its log file, correct any issues, and repeat step 6. If you encounter any issues that you cannot resolve, contact BMC Support.
  8. (Windows customers only) Install the required Microsoft runtime libraries by running the following command in the installation directory:
    vcredist_x64 /install /quiet /log vcredist_x64_install.log 

    Error
    Warning

    Running this command reboots some machines. Make sure that you close all applications and save your work before running this command.

  9. If you are installing MVMM for the first time, follow the steps in Installing-the-core-components-of-the-product after applying the Fix Pack. Otherwise, continue with the steps that follow. Run the dbschema_sync command to apply DB schema corrections. For information about the command parameters, see find_sql_rollup-and-dbschema_sync-command-parameters.
  10. If you choose to use a user who is a member of the database_login group, follow these steps:

    1. In the installation directory run the command for your service platform:

      • UNIX
        ./qpas -j 
      • Windows
        qpas -j

      The command continues to run.

    2. In another command window, access the installation directory and run the command for your service platform:
      • UNIX
        ./dbschema_sync userid -i [-p password | -s]
      • Windows
        dbschema_sync userid -i [-p password | -s]
    3. Check the output of the command. If any issues exists, correct them. If required, repeat these steps. If you encounter any issues that you cannot resolve, contact BMC Support.
    4. To stop the qpas command initiated in step a, press Ctrl+C.

    If you choose to use your DB credentials, follow these steps:

    1. In the installation directory, run the command for your service platform:
      • UNIX
        ./dbschema_sync -i -d db_type db_name db_userid [-p db_password | -s]
      • Windows
        dbschema_sync -i -d db_type db_name db_userid [-p db_password | -s]
    2. Check the output of the command. If any issues exists, correct them. If required, repeat these steps. If you encounter any issues that you cannot resolve, contact BMC Support.
  11. Start the MVMM services.
  12. For each client system follow these steps:

    • For a client system on which a Java Web Start Monitor Console is being used:
      1. Flush the Java cache by running the following command: javaws -Xclearcache
      2. Refresh the Management Console by pointing the web browser to the application service and selecting Management Console from the entry page.
    • For a client system on which the stand-alone Monitor Console is being used:
      1. If you have previously used a Java Web Start Monitor Console but no longer need to, flush the Java cache (which also removes the desktop shortcut) by running the following command: javaws -Xclearcache
      2. Download and install the updated stand-alone Monitor Console. For more information, see Accessing-the-Monitor-Console.

 

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

MainView Middleware Monitor 9.0