This chapter contains the following sections:
To effectively and correctly use the Oracle TSAM Agent, please note the following prerequisites:
The following APIs are used in conjunction with Oracle TSAM:
User applications can take advantage of the monitoring attributes by using
tpgetcallinfo is designed for call path monitoring. Using
tpgetcallinfo, allows applications to make dynamic decisions based on application performance metrics.
For more information, see
) in the Oracle TSAM Reference Guide.
Local Monitor Server (LMS) is a component of Oracle TSAM Agent. It performs the following tasks:
For more information, see Reference Guide.in the Oracle TSAM
To use Oracle Tuxedo Application Runtime for CICS monitoring, an additional configuration file (
Region-Group.mapping)is required. The file must be put in the directory specified by the
KIXCONFIG environment variable. For more information, see .
Listing 2-1 shows a
Region-Group.mapping file format example.
Each region has a section in this file. The CICS region is called "name". The
tuxgroups parameter is followed by the Oracle Tuxedo group name. The
resources_group parameter is the CICS resource group in this region.
For more information, see the
|Note:||For Oracle Tuxedo Application Runtime for CICS 126.96.36.199.2 running on Linux, the ARTMON server must be configured in order to enable TSAM monitoring.|
If you need to monitor Oracle Tuxedo Application Runtime for Batch ARTJES component, set the JESMONITOR environment variable to yes before you start the LMS server.
Oracle TSAM Agent provides a
tmadmin command to turn on/off. If you want to turn off Oracle TSAM temporally, this command can be used. The format is as follows:
changemonitor (chmo) [-m machine] on|off
-m parameter specifies the logic machine name where the Oracle TSAM collection is disabled. Without this option, monitoring on all machines is disabled. By default, monitoring is turned on. If monitoring is turned off, all data collection is stopped even if there is a monitoring policy defined.