Running the Monitor Console

In previous releases of TrueSight Middleware and Transaction Monitor (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 Open link .

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 8.1.00 Server Fix Pack D, which addresses the ending of support for Java Web Start applications.

Before you begin

TMTM services must be running. See Starting and stopping services for more information.

To access the Monitor Console as a Java Web Start application (legacy)

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. If the port number has been changed from the default, then use the new port number.
Note

The default HTTPS configuration may not meet the security requirements of your browser. See Secure communication among product components for details.
Select Launch Monitor Console.
A warning may advise that a Java install or update is required. If you do not have Java installed, click Download Client JRE (the Client JRE is version 8, the last supported version by Oracle) and follow the instructions.
Note that in Google Chrome (from v42) Java integration is disabled. When clicking on Launch Monitor Console, a JNLP file is downloaded and you can run this file using Java (if you have it installed; if not, click Download Client JRE and follow the instructions).
A prompt may ask if you want to run the application. Allow the application to run only after reviewing the application details presented. These details let you confirm that it is the "Monitor Console" application, published by "BMC Software Inc", and that it was launched from the same location as the TMTM Application Service.
Log in:
1. Enter your user name and password. If this is a first-time login, use the supplied credentials:
  - User: SA
  - Password: BMCSOFTWARE
2. To change your password after logging in, check Change Password.
3. Select the host.
4. Click Login to open the Monitor Console.
  Note
  If it takes longer than 25 seconds to connect, you might get an error message. If this is a consistent problem, change the length of the log-on time out as follows:
  1. Click on Customize Settings.
  2. Enter the following in the JVM Arguments text field:
    -Dcom.mqsoftware.mercury.connection_timeout=50000
  3. Click Launch to start the Monitor Console. If this does not solve the connection problem, call BMC Support.

To access the Monitor Console as a standalone Java application

The standalone Monitor Console is delivered as an installable application, bundled with a private (to the application) OpenJDK based Java 11 JRE.

Accessing the Monitor Console Installer

From the product launch page, click Download Monitor Console Installer to access the Monitor Console Windows installer (both UI and silent mode (with response file) installer options are supported, as described below).

Note that the existing (Java Web Start) based launch is still available (and described in the section above).

To run the GUI Installer

After downloading the Monitor Console as an installer executable (see above), open it from your browser or double-click on the monitor_console_installer.exe file from File Explorer. Follow the installer onscreen instructions.

To run the Silent Installer

Silent installations will always overwrite a previous installation, if one already exists.

When running a silent install, you need to define a properties file (to indicate the install path). For example, save the following code to a file called install.props.
```
INSTALLER_UI=silent
USER_INSTALL_DIR=D:\\Path\\To\\Dir
```

Run the installer using the following command:

> monitor_console_installer.exe -f install.props

Uninstalling the Monitor Console

The standalone Monitor Console can be uninstalled as per standard applications from the Control Pamel (using the Uninstall or change a program option).

Launching the Monitor Console and Client configuration

After installation, the standalone Monitor Console can be started from the Start menu (select TMTM Monitor Console from the TrueSight Middleware and Transaction Monitor folder). A product version check will run; if the server is using a different version from the client a warning message is displayed.

The local client configuration is then compared with that on the server (based on the "default_client..." settings in the App_Service section of the services configuration). If the server based settings have changed, you can choose to restart with the new settings, or continue without using them.

Notes

Local configuration is stored in %LOCALAPPDATA%/BMC Software/TMTM/monitorconsole.ini.

A sample configuration is provided in monitorconsolesample.ini in the Monitor Console install directory.

Server configuration takes precedence over local configuration unless you choose to continue with the current settings. This is intended to provide functionality equivalent to the "Customize Settings ..." option used in the Java Web Start launcher (meaning server defaults prevail unless you explicitly launch with custom settings).

Logging

Most client logging is directed to the service tier, into qpas-webmc.log, after the client has connected; Java Web Start launches can still be debugged via the Java Console view.

Native launch logging can be enabled in monitorconsole.ini by adding a property to set the log file name and log level (info|warning|error|none - see the example below). This logging is off (none) by default. The log file will be in the install directory.

log=mc_launch.log
log.level=info

The native launcher logging covers the JRE bootstrap (reading the ini file, locating the JRE, building the classpath, initializing the JVM).

For the updated Monitor Console (Java Web Start and native), post-launch logging goes to %LOCALAPPDATA%/BMC Software/TMTM/qpmc.jvm.out.log. Post-launch logging covers initial JRE startup (environment variables, system properties, product version) and connecting to the service tier.