|
•
|
Oracle TSAM Plus Framework: The framework is the data collection engine. It is an independent layer working between Tuxedo infrastructure and other TSAM Plus components. This module is responsible for run time metrics collection, alert evaluation and monitoring policy enforcement.
|
|
•
|
Oracle TSAM Plus Plug-in: An extensible mechanism invoked by the Oracle TSAM Plus Framework. The Oracle TSAM Plus Agent provides default plug-ins to send data to the LMS (Local Monitor Server), and then to the Oracle TSAM Plus Manager. The plug-in allows custom plug-in to be hooked to intercept the metrics. The default plug-in communicates with LMS with share memory. Application will not be blocked at metrics collection point.
|
|
•
|
accrpt: An utility to analyze accounting and chargeback information generated by -a option in servopts(5).
|
|
•
|
JMX agent, which works in conjunction with the Enterprise Manager for Oracle Tuxedo to enable you to monitor and manage Oracle Tuxedo applications through the JMX interface and furthermore, through the Oracle Enterprise Manger cloud control 12c.
|
The “-l” option specifies the Oracle TSAM Plus Data Server address which is configured in the Oracle TSAM Plus Manager. For more information, see the
Oracle TSAM Plus Reference Guide. The Oracle TSAM Plus Data Server uses the same port number as the Oracle TSAM Plus Manager Console.
You can use a tmadmin command to turn on or turn off Oracle TSAM Plus. The command format is:
The -m parameter specifies the logic machine name where the Oracle TSAM Plus 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.
|
Note:
|
The KIXCONFIG environment variable is required for all ART applications.
|
Listing 1‑2 shows a
Region-Group.mapping file format example.
LMS SRVGRP=LMSGRP SRVID=101
Table 1‑1 lists the key words for the configuration file.
Listing 1‑4 shows an example of configuration file for TuxJES.
Listing 1‑5 shows an example of TSAM user mapping file.
Before starting tlisten, you must set the
tlisten environment variable
SHLIB_PATH/LIBPATH/LD_LIBRARY_PATH and include the
libjvm library path. For windows platforms, you only need to set
JAVA_HOME. For HP platforms, you need to set
LD_PRELOAD to include the
libjvm.so directory.
Listing 1‑6 shows examples of environment variable settings on different platforms:
|
Note:
|
LD_PRELOAD is only used for tlisten to start embedded JMX agent. It should not be set when building Tuxedo applications.
|
To start tlisten, use the following command:
When the tlisten process is started correctly, you can view the message “
RMI connector server successfully started and
Started the embedded JMX agent successfully” in ULOG.
|
•
|
tlisten acts as the Tuxedo-side monitoring and management agent . It receives monitoring and management requests from Enterprise Manager and dispatches these requests to corresponding Tuxedo services.
|
|
•
|
tlisten creates a Tuxedo context for each JMX connection. If a monitored Tuxedo domain enables authentication and authorization, tlisten provides the credentials attained from Enterprise Repository when it attaches a Tuxedo domain.
|
|
•
|
tlisten also forwards job requests from Enterprise Repository agent to MIB service. Enterprise Repository agent creates a new JMX connection for every job request, and releases the connection after the job finishes. Accordingly, tlisten creates a Tuxedo context for each job request.
|
Listing 1‑7 shows an SHM mode
UBBCONFIG file example supporting Enterprise Manager monitoring.
When this option is specified, GWTDOMIAN starts an embedded JVM and runs a BTM delegate observer to monitor bidirectional calls between WTC and itself.
