Configuring the MQS_HOME system environment variable for the Default layout

The TMTM Extensible Agent, TMTM Configuration Agent and most performance and availability monitoring extensions have all the required files located in the directory where they are executed. However, if you wish to consolidate where logging is controlled and where log files reside you can place QPLog.ini in a directory specified by the system environment variable. This is recommended for supportability.

The directory specified by the system environment variable is used as a well-known location for packages and BTM deployments which are distributed.

Some TrueSight Middleware and Transaction Monitor extensions and applications which are monitored by a BTM Extension need the MQS_HOME environment variable pointing to a directory with the QPTTAB.DAT and QPLog.ini file. If not set up properly, monitoring of that application can fail due to translation issues and the btm log files can be written to the tmp directory.

The following procedures describe how to define the system environment variable and copy the required files.

Related topics

Installing-extension-agent-in-the-default-layout

Creating-environment-directories-on-the-agent-system-for-the-default-layout

Configuring-the-JRE 

To configure the MQS_HOME system environment variable on Windows

  1. Right-click My Computer and select Properties > Advanced > Environment Variables.
  2. In the System variables section, click New.
  3. In the Variable name field, enter MQS_HOME.
  4. In the Variable Value field, enter the full path to the directory.
  5. Click OK.
  6. Reboot the computer to set the system environment variable.

To configure the MQS_HOME system environment variable on UNIX and z/OS USS

The following approaches can be used for defining the MQS_HOME variable:

  • /home/$username/.profile or shell equivalent in the users home directory, but this works only for this user when they have a login shell
  • /etc/profile works globally for all users who have a shell logon
  • /etc/environment works for all users without a shell login. If you do an "su - username" the variable is gone, then /etc/profile is used
  • define it for a service in, for example, xinet.d. In /etc/xinetd.d/service_name add env = MQS_HOME=/directory_path
  1. Set and export the system environment variable to a directory of your choice where all logs and other BTM files are to be saved. This should be done from a logon script such as .profile or whatever is applicable for your default shell. This should be the same directory and set for all users which run an extension.
  2. Reinitiate your profile to ensure the system environment variable is set. Under Linux it might help to identify if a running process has an environment variable by looking in /proc/PID/env or /proc/PID/environment.

To configure the MQS_HOME system environment variable on i5/OS

  1. Using WRKENVVAR, create a new system wide environment variable (*SYS) and name it MQS_HOME. It must be located in the IFS. In the Variable Value field, enter the full path to the directory.
  2. Establish a new command environment to ensure the system environment variable is set.

 

 

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