Getting started for users

1

Open a browser instance (see the supported list of browsers here) and enter the URL: http://hostname:15007 or https://hostname:15004

where:

hostname is the hostname or IP address of the computer running the TMTM Application Service.
15007 and 15004 are default ports used by the TMTM Application Service.

The TMTM Launch Page is displayed.

2

To access the Monitor Console, click Download Monitor Console Installer to install the standalone version of the Monitor Console, or click Launch Monitor Console to launch the legacy Java Web Start version of the Monitor Console. For further information about which version you should use, see Accessing-the-Monitor-Console.

If you do not have Java installed you will be prompted to download and install the correct version. Click Download Client JRE and follow the instructions.

After you are prompted to run the "Monitor Console" application, the Monitor Console login page is launched; enter your user name and password, which by default are:

• User name: SA
• Password: BMCSOFTWARE

For further information and troubleshooting, see Accessing-the-Monitor-Console.

3

To access TrueSight Middleware Administrator (TSMA) - via which you can manage queue managers, queues, and channels - from the Launch Page, click Administrator Console.

The TSMA window is launched in a new browser window/tab (note that in contrast to the Monitor Console, the TSMA User and Admin Consoles are web-based).

For further information on the functionality available in TSMA, see Working-with-queue-managers-queues-and-channels.

4

To download TMTM agents for distribution to the relevant computers, click Download Agents.

From the list of displayed environment options, select the relevant agent download package.

For further information about downloading and deploying agents, see Distributing-the-Agent-and-extensions-via-the-launch-page.

5

To download the Report Designer, via which you can import, design and preview TMTM History Reports before publishing them to TMTM, click Download Report Designer.

Download and run report_designer_install.exe when prompted. Follow the instructions to complete the installation.

For further information, see Working-with-the-Report-Designer.

6

To access the online documentation for TMTM, click Documentation.

1

In the Monitor Console, click the Policies tab and then click the Agent Policies sub-tab. In this tab, the supplied Agent policies are listed (with names like WMQ_Agents_Basic). The naming convention for the BMC supplied policies is TECHNOLOGY_Agents_LEVEL, where TECHNOLOGY is an abbreviation for the specific monitored product to which the policy applies. 

Once TMTM is installed, you will see the policies for IBM WebSphere MQ (prefixed with WMQ) and the self-monitoring policies for TMTM (prefixed with BMM). If you are only monitoring these technologies, you can proceed to Step 2.

If you are monitoring other technologies, you need to import the relevant Event Pack for the specific technology before proceeding.

2

Select the level of monitoring you require (click on the relevant policy in the Agent Policies tab). For each technology, the supplied policies come with a number of monitoring levels: 

• Minimal - This level ensures there is almost no automatic monitoring, although will automatically keep history on the TMTM Agent and the top level component of the technology (for example, the MQ Queue Manager, IIB Broker, or EMS Server), and provides Console alerts if the monitoring extension has lost contact with the underlying technology. Choose this level if you wish to control your monitoring mostly manually rather than automatically, but need to ensure the absolute core is monitored.
• Basic - This level does everything the Minimal level monitors, but also discovers and selects for monitoring the underlying objects (such as MQ queues and channels, Broker Message Flows, WAS EJBs, and DataPower Multi-Protocol Gateways). In addition, it stores history on the key metrics of those objects. Note that this level does not alert automatically, other than the minimal Console alerts. Choose this level if you want to ensure that objects are discovered and populated in the Operations tab of the Monitor Console automatically but wish to manage your events manually.
• Standard_NNN - This level is intended to implement TMTM best practices for monitoring. The monitored objects are discovered and populated in the Monitor Console Operations tab. Historical data is collected on all key metrics, and alerts are set up automatically to notify you of key conditions for all monitored objects. As this level includes alerting, there are several variants specified by the NNN to control where the event notifications go. Note that all of these eventing options will require some general configuration (see Getting-started-with-policies for more details).
• ALL_NNN - This level monitors and stores historical data on all objects and alerts on essentially every condition that TMTM believes could be of interest. As with the Standard_NNN level, there are variants. Choose this policy in an environment where you wish to explore the possible monitoring capabilities. It is generally not recommended that you select this policy level in a production environment because it may generate a large number of alerts.

3

After selecting the level of monitoring, click the Copy Agent Policy with all Sub-Components button  (also known as a Deep Copy), and specify a prefix for your copy (such as "MyCompany_"). Click OK to copy and enable the policy and all required underlying objects. 

Then apply the policy to your existing objects by clicking the Apply button . 

Note that policies will apply to new objects in the future, but this step is necessary to check all of the existing objects that were discovered before you applied your policy. Upon completion, you can exit the dialog box. 

4

If you have not deployed and started any agents, this would be the next step. The policy will pick up the new objects and configure the monitoring setup based on the policy.