|
|
The Oracle TSAM Reference Guide describes system processes and commands delivered with the Oracle TSAM software.
Table 1 lists the Oracle TSAM system processes and commands.
LMS—The Oracle TSAM Agent Local Monitor Server
LMS SRVGRP="identifier" SRVID="number" [other_parms]
CLOPT= "-A -- -l tsam-manager-dataserver-url [-t heartbeat-interval]
LMS is an Oracle TSAM Agent Tuxedo server. It provides the following functions:
The performance metrics collected by the Oracle TSAM framework are passed to the plug-in. Oracle TSAM default plug-in sends the data to the LMS using the Tuxedo service infrastructure.
The LMS must be configured in the UBBCONFIG file and set with the proper options. One Tuxedo machine must be configured with one LMS. Multiple LMS on one machine is not supported. LMS is recommended to be configured at the end of UBBCONFIG so that it can retrieve all server information when Tuxedo domain booted. LMS still can synchronize the configuration to TSAM manager periodically.
-l
-m
-t
Listing 1-1 shows the LMS in UBBCONFIG.
...
*SERVERS
LMS SRVGRP=LMSGRP SRVID=1
CLOPT=”-A -- -l tsamweb.abc.com:8080/tsam/-m 20M -t 180”
...
tpgetcallinfo()— Routine for retrieving call path message monitoring attributes.
int tpgetcallinfo(const char *msg, FBFR32 **obuf, long flags)
tpgetcallinfo() is used for call path monitoring only. It supports the following parameters:
msg
obuf
flags
For monitored calls, tpgetcallinfo()uses the following fields: following fields:
tpgetcallinfo()
tpgetcallinfo()
tpgetcallinfo() to check the requested message monitoring attributes. It can provide the following information:| Note: | - Correlation ID of the request. It is generated by the caller |
| Note: | - Begins time stamping when the monitoring initiator starts the call |
| Note: | - Last stop time stamp on the call path tree of the monitored request. Usually, it is used to measure the process requested message waiting time for a service |
| Note: | - Workstation client address if the request is from a Tuxedo workstation client |
tpgetcallinfo() to get the end to the monitored call end time. | Note: | Note: tpgetcallinfo() can be called at any time for a reply buffer after a reply is received. This is especially useful with tpacall/tpgetrply. |
Table 2 lists the FML monitor metrics field names.
Upon successfully getting a FML32 buffer containing the monitoring attributes, returns 0.
Upon failure, tpgetcallinfo() returns -1 and sets tperrno to indicate the error condition.
Upon failure, tpgetcallinfo() sets tperrno to one of the following values,
[TPEINVAL]
[TPESYSTEM]
[TPEOS]
Listing 1-1 provides a service-side tpgetcallinfo example.
#include <stdio.h>
#include <atmi.h>
#include <userlog.h>
#include <fml32.h>
#include <tpadm.h>
#if defined(__STDC__) || defined(__cplusplus)
tpsvrinit(int argc, char *argv[])
#else
tpsvrinit(argc, argv)
int argc;
char **argv;
#endif
{
/* tpsvrinit logic */
#ifdef __cplusplus
extern "C"
#endif
void
#if defined(__STDC__) || defined(__cplusplus)
APPSVC(TPSVCINFO *rqst)
#else
TOUPPER(rqst)
TPSVCINFO *rqst;
#endif
{
FBFR32 *metainfo;
int len = 0;
/* Allocate the metainfo space */
metainfo = tpalloc("FML32", NULL, 1024);
if (metainfo == NULL ) {
userlog("Memory allocation failed");
tpreturn(TPFAIE, 0, 0, 0);
}
/* Get the monitoring attributes*/
if ( tpgetcallinfo(rqst->data, &metainfo, 0) == 0 )
{
char *corrid;
long laststopsec, starttimesec;
if ((corrid = Ffind32(metainfo, TA_MONCORRID, 0, &len) ) {
userlog("Correlation ID = %s", corrid);
}
len = sizeof(starttimesec);
if (( Fget32(metainfo, TA_MONSTARTTIMESEC, &starttimesec, &len) == 0) {
userlog("Message beginning time = %ld", starttimesec);
}
}
len = sizeof(lasttimesec);
if (( Fget32(metainfo, TA_MONLASTTIMESEC, &lasttimesec, &len) == 0) {
userlog("Message entering my queue time = %ld", lasttimesec);
}
}
tpfree(metainfo);
/* rest of service processment */
......
}
|