8.1.00 Server Fix Pack K

This Fix Pack is to be installed on your TrueSight Middleware and Transaction Monitor (TMTM) service machine (this Fix Pack requires an 8.1.00.425 GA installation with or without earlier Fix Packs). Fix Packs do not contain all of the files that are required for a complete product installation. If you have not installed the GA version of the product, see Installing. 

Fix Packs are cumulative and contain all updates released prior to the Fix Pack. This Fix Pack obsoletes all previous Server Fix Packs.

When installing the 8.1.00 GA version of the product, at the end of the installation, you will be prompted to run the Security Configuration Tool. You should NOT run it at that point, and once the installation is complete, apply this Fix Pack, and then run the Security Configuration Tool.

In previous releases of TMTM, the Monitor Console was only accessible via Java Web Start. Oracle has announced that Java 8 will be the last version to support Java Web Start, see the Oracle Java Roadmap.

As a result of Oracle’s announcement, the Monitor Console is now available in two different ways:

  • The legacy Java Web Start Monitor Console can be used as in previous versions; however, this version requires Oracle JRE 8. This product will continue to provide an Oracle JRE version 8 installable package that you can use, but no further Java updates will be available from BMC. Alternatively, you can choose to use your own Oracle JRE 8 if you have an extended support contract with Oracle (or for as long as your company security standards allow), otherwise BMC recommends you switch to the standalone Monitor Console installation.
  • The standalone Monitor Console is available as part of this Fix Pack, which addresses the ending of support for Java Web Start applications.

For further information on how to access the two versions of the Monitor Console, see Accessing-the-Monitor-Console.

IMPORTANT
  • If you have not installed 8.1.00 Server Fix Pack D or later,
    • You must have 64-bit database clients installed for TMTM to work after applying the Fix Pack. Install the same 64-bit database client on the server machine as your 32-bit client, before installing the Fix Pack. See Upgrading-to-64-bit-database-clients.
    • The 64-bit Windows binaries may require more RAM than the 32-bit binaries. Therefore, you should monitor your RAM usage before applying the Fix Pack to determine whether additional RAM needs to be added. See How-to-estimate-memory-usage-for-the-64-bit-TMTM-services-for-Windows.
  • When using Oracle 12.2 or 18, the database type of Oracle 12.1 should be used. See also Performing-core-components-upgrade.
  • Knowledge Article 000155077 describes how to configure the services running on Linux to use an alternative JRE, for example a JRE installed in /usr/java. This configuration will not work with OpenJDK 11. The installation of this Server Fix Pack removes such a symbolic link, and replaces it with a directory named jre, which contains the OpenJDK 11 run-time files.
  • Ensure that you back up the database and product installation directories on a regular basis. Before you install this Fix Pack or any other Fix, you must ensure that you have a valid recent backup that you can restore from in case any issues occur during the installation of the Fix Pack. The steps for installing the Fix Pack differ from previous Fix Packs, it is now necessary to execute dbschema_sync to apply fixes to the database content.

Tip

For information about issues corrected in this Fix Pack, see Known-and-corrected-issues.

Installing Server Fix Pack K for TMTM 8.1

Installing the Server Fix Pack K for TMTM 8.1 consists of the following steps:

  1. Prepare for the installation of the Fix Pack.

    You should review a Fix Pack's notes and instructions prior to installation.  You can extract the README.txt file from the downloaded Fix Pack ZIP file, with the following command:

    For Windows: unzip -o FixPack8100.425K_Server.zip FixPack8100.425K_Server\README.txt

    For Unix: unzip -o FixPack8100.425K_Server.zip FixPack8100.425K_Server/README.txt

  2. Create a directory named FixPacks under your server installation directory, if it does not already exist.

    UNIX example: 
    If the product is installed in /opt/TMTM, create the directory /opt/TMTM/FixPacks if it does not already exist.

    Windows example: 
    If the product is installed in D:\TMTM, create the directory D:\TMTM\FixPacks if it does not already exist.

  3. Download the Fix Pack file (FixPack8100.425K_Server.zip) to the directory referenced in Step 2.
  4. Unzip the archive. You should now have a directory named FixPack8100.425K_Server in the directory referenced in Step 2.

    UNIX example:
    If the product is installed in /opt/TMTM, the directory /opt/TMTM/FixPacks/FixPack8100.425K_Server should now exist.

    Windows example:
    If the product is installed in D:\TMTM, create the directory D:\TMTM\FixPacks\FixPack8100.425K_Server should now exist.

  5. Stop the services and make sure they have stopped.

  6. Run the Fix Pack installation script; it does not matter what directory you are in when you run it. The default action is to install the Fix Pack. To see the help, run the script with the --help option.

    UNIX example:
    If the product is installed in /opt/TMTM, run the command /opt/TMTM/FixPacks/FixPack8100.425K_Server/tmtm_fixpack_tool.shWindows example:
    If the product is installed in D:\TMTM, run the command D:\TMTM\FixPacks\FixPack8100.425K_Server\tmtm_fixpack_tool.bat

    IMPORTANT: If you choose to unpack the FixPack8100.425K_Server.zip file in a different location, you MUST specify the product location when running the installation script.

    UNIX example:
    If the product is installed in /opt/TMTM, and the Fix Pack is in /local/TMTM/FixPacks/FixPack8100.425K_Server, run the command /local/TMTM/FixPacks/FixPack8100.425K_Server/tmtm_fixpack_tool.sh --product_path /opt/TMTM

    Windows example:
    If the product is installed in D:\TMTM, and the Fix Pack is in F:\FixPacks\FixPack8100.425K_Server, run the command F:\FixPacks\FixPack8100.425K_Server\tmtm_fixpack_tool.bat --product_path D:\TMTM

  7. Check the output of the script, and its log file, correct any issues and repeat. Contact BMC Support if you run into any issues you cannot resolve.

  8. Execute the dbschema_sync command to apply DB schema corrections. See https://docs.bmc.com/docs/TMTM/81/find_sql_rollup-and-dbschema_sync-command-parameters-642528527.html for details of the command's parameters. 
    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

      Note that the command will continue 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, correct any issues and repeat. Contact BMC Software Support if you run into any issues you cannot resolve.
    4. Ctrl-C the qpas command from step a.

    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, correct any issues and repeat. Contact BMC Software Support if you run into any issues you cannot resolve.
  9. Start the TMTM services.
  10. For each client system, perform one of the following:
    • For a client system where a Java Web Start Monitor Console is being used: 
      • Flush the Java cache by running the command: javaws -Xclearcache
      • Refresh the Monitor Console by pointing the web browser to the application service and selecting Monitor Console from the entry page.
    • For a client system where the standalone Monitor Console is being used:
      • If you have previously used a Java Web Start Monitor Console, and no longer need to, flush the Java cache (which also removes the desktop shortcut) by running the command: javaws -Xclearcache
      • Download and install the updated standalone Monitor Console. See Accessing-the-Monitor-Console.


 

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