This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Middleware Monitor
BMC Middleware and Transaction Management
BMC Middleware Management Truesight Middleware Management Truesight Middleware and Transaction Monitor
How can I upgrade the Truesight Middleware and Transaction Monitor through BMC AMIGO program?
What all things I need to make sure before approaching BMC Customer Support
BMC Offers upgrade of BMTM/TMTM product line through AMIGO or Assisting Migration Operations program.
The AMIGO upgrade program is designed to help BMM customers proactively plan
their upgrade to reduce problems and avoid after hours calls. When contacting
support, there are 2 phases for AMIGO upgrade program:
i. AMIGO Starter Phase: When you are beginning the upgrade process and do not have a completed upgrade plan.
The AMIGO Starter phase will answer any high level questions that you have to get you started on your upgrade plan.
ii. AMIGO Review Phase: After you have completed your upgrade plan and have set an upgrade date.
The review will be performed by the on-call team based on your upgrade date.
Before you approach the BMC Customer Support, here are a few things needed to get started:
1 - Download TMTM 8.1 installer
2 - Download the latest TMTM server fixpacks from the BMC EPD site. At the time of writing this article FixPack8100.425G_Server is the most recent version available for download. Note that The Server fixpack only affects the server components, and the agent fixpack affects only the agent components. Both are required to update the product, i.e. server fixpacks do not contain agent updates.
Earlier versions of TMTM had 32 bit services, after the release of TMTM 8.1 Fixpack D, the services now have 64 bit support and uses OpenJDK as opposed to Oracle JRE.
Since the TMTM fixpacks (Server & Agent) are cumulative, if you install the latest fixpack available then you would be running 64 bit services.
3 - Download the latest TMTM agent fixpacks from the BMC EPD site. At the time of writing this article FixPack8100.425F_Agent is the most recent version available for download. Note that The Server fixpack only affects the server components, and the agent fixpack affects only the agent components. Both are required to update the product, i.e. server fixpacks do not contain agent updates.
As explained in the previous point, the earlier versions of TMTM agents and extensions had 32 bit services, after the release of TMTM 8.1 Fixpack E, the services now have 64 bit support and uses OpenJDK as opposed to Oracle JRE. Being cumulative in nature, if you install the latest fixpack, the agent and extensions will run as 64 bit services.
4 - Decide if you will be using TSMA/MVMA full-license or TSMA/MVMA-Monitor Edition. If you are currently using TMTM v 8.0.0.x, then you have the Configuration Manager. This component however has been taken out of TMTM in v 8.1. All its features are now available as part of the BMM Admin product called as Mainview Middleware Administrator (formerly Truesight Middleware Administrator).
5 - Download Mainview Middleware Administrator v 9.0 or TrueSight Middleware Administrator v 8.2.
MVMA v9 is the latest offering for BMM Admin product, the latest available fixpack at the time of writing this article is Fixpack B.
6 - Make sure that WMQ client is installed on the same server where MVMA/TSMA is going to be installed.
MVMA/TSMA uses the IBM MQ Client to connect to the queue managers and hence this requirement must be met. Without this, the MVMA/TSMA won't work.
The MVMA/TSMA can be installed on the same server where TMTM runs or could be installed on another server.
7 - Download TSMA-fixpack A (only if using TSMA 8.2) or MVMA-fixpack B (only if using MVMA 9.0). At the time of writing this article, Fixpack B is the most recent version available for download.
8 - Verify you have the TMTM database connect information:
How to determine what Database user that the BMTM/TMTM services use:
Go to Security tab in BMTM/TMTM , highlight the 'database_login' group, click on "Edit Advanced Properties' button (gear icon), this will show you the database type, database name, and database userid that BMTM uses to connect to the database and that userid and password are what we need to update the user schema when we upgrade BMTM.
9 - Backup entire BMTM install folder. Along with this, you should also backup any concrete event rules by using the mqsiexport command.
It is a good idea to back up the event rules before proceeding with upgrade, if you are not using the event templates and rather directly creating the event rules.
Following command can be used:
(Linux) ./mqsexport -p BMCSOFTWARE --event-rule ".*" eventRulesBackup.zip SA
(Windows) mqsexport.bat -p BMCSOFTWARE --event-rule ".*" eventRulesBackup.zip SA
10 - Backup BMTM database schema
11 - Verify that you have enough free disk space on your BMTM server. An estimated free space of 25~30 GB is recommended.
12 - Verify CPU/RAM is sufficient and coincides with the minimum requirements as per the product documentation.
Refer this article for details: https://docs.bmc.com/docs/TMTM/81/minimum-hardware-and-software-requirements-642528325.html
13 - If you are planning to use MVMA/TSMA - Monitor Edition, make sure that TSMA Admin user exists in AD and LDAP (AD) Admin info is correct.
14 - If MVMA/TSMA -Monitor Edition is to be used, verify what MQ serverconn channels you want to use to connect to TSMA?
You can further check the connectivity to the queue manager using the channel and the MQ client installed on the server by using the following method.
14.1 Set the environment to use the server connection channel:
14.2 Run the IBM dmpmqcfg tool:
dmpmqcfg -a -x object -o mqsc -m <QMGR_Name> -t all -c default
Once you are ready with the above mentioned details, you can reach out to BMC Customer Support and start your discussions around the upgrade path.
The attached spreadsheet can then be filled and shared with the BMC Customer Support Engineers to discuss the approach and readiness.
This document talks about the granular details with respect to the hardware software requirements of the BMTM product and the Database that is to be used in conjunction.