Oracle TSAM Agent

This topic contains the following sections:

•	Prerequisites

•	Oracle TSAM Agent APIs

•	Local Monitor Server (LMS)

•	Oracle Tuxedo Application Runtime for CICS Configuration

•	Turning Oracle TSAM On and Off

Prerequisites

To effectively and correctly use the Oracle TSAM Agent, please note the following prerequisites:

•	The system clocks for all monitored Tuxedo machines and the Oracle TSAM Manager are synchronized. A uniform time server is recommended.

•	Set each Tuxedo domain to a unique DOMAINID in the UBBCONFIG file.

Oracle TSAM Agent APIs

The following APIs are used in conjunction with Oracle TSAM:

•	tpgetcallinfo

tpgetcallinfo

User applications can take advantage of the monitoring attributes by using tpgetcallinfo. tpgetcallinfo is designed for call path monitoring. Using tpgetcallinfo, allows applications to make dynamic decisions based on application performance metrics.

For more information, see tpgetcallinfo() in the Oracle TSAM Reference Guide.

Local Monitor Server (LMS)

Local Monitor Server (LMS) is a component of Oracle TSAM Agent. It performs the following tasks:

•	Act as a data proxy server between Oracle TSAM agent framework and Oracle TSAM Manager

•	Accept policy and alert configuration request from Oracle TSAM Manager and apply to Tuxedo domain

•	Send Tuxedo domain configuration to Oracle TSAM Manager

•	Other help functionality

For more information, see LMS in the Oracle TSAM Reference Guide.

Oracle Tuxedo Application Runtime for CICS Configuration

If you require Oracle Tuxedo Application Runtime for CICS monitoring, an additional configuration file (Region-Group.mapping)is required. The file must be put to the directory specified by the KIXCONFIG environment variable. For more information, see Oracle Tuxedo Application Runtime for CICS Users Guide.

Note:

The KIXCONFIG environment variable is required for all ART applications.

Listing 2‑1 shows a Region-Group.mapping file format example.

Listing 2‑1 Region-Group.mapping File Format Example

[region]
name= REG1
tuxgroups=APPGRP1,APPGRP2
resources_group=resgroup1,resgroup2

[region]
name= REG2
tuxgroups=APPGRP3,APPGRP4
resources_group=resgroup3,resgroup4

 

Each region will have a section in this file. The "name" is the name of the CICS region. The "tuxgroups" parameter is followed by the Oracle Tuxedo group names which The "resources_group" parameter is the CICS resource group in this region.

For more information, see the Oracle Tuxedo Application Runtime for CICS Reference Guide.

Turning Oracle TSAM On and Off

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

The -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.

See Also

•	Oracle TSAM Deployment Guide

•	Oracle TSAM Console User Guide

•	Oracle Tuxedo Application Runtime for CICS and Batch documentation