![]() |
![]() |
![]() |
![]() |
![]() |
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 Plus manager periodically.
• host is the host DNS name or IP address of the box where TSAM Plus manager is installed.
• port is the TCP port number.
• tsam is the Oracle TSAM Plus manager reserved path name.Optional parameter. It specifies the time interval LMS sends a warning message to ULOG if performance metrics data is dropped due to shared memory size limit. Its range is [1-65535]. The default value is equal the -t value. The warning message reports how many messages have been lost during the past interval.Listing 1‑1 shows the LMS in UBBCONFIG.Listing 1‑1 LMS in UBBCONFIGThe following tlisten options serve for JMX monitoring:jmxaddr specifies the address of RMI connector of embedded JMX agent. If the address has been occupied by another process, an error message is printed into ULOG and JMX agent fails to start up. Table 1 lists the jmxaddr adress formats.
Table 1 IPv4 and IPv6 Address Formats
Note: Specifies the maximum memory size (in MB) that can be allocated for the JVM used by JMX agent. The value of jvm_max_mem cannot be set smaller than the value of jvm_min_mem, otherwise the JVM are not created and JMX agent fails to start up. The default value is 500MB.Specifies the keyStore absolute path.Specifies the environment variable in which the password for the key store is stored. This variable is only usefully when no tty is attached.A new CLOPT option is introduced for GWTDOMAIN.The BTM monitor URL. The format is http://<HOST>:<PORT>/btmmonitor/agent/agent/.When this option is specified, GWTDOMIAN starts an embedded JVM and runs a BTM delegate observer to monitor bidirectional calls between WTC and itself.Oracle TSAM Plus Agent provides a tmadmin command to turn on/off. If you want to turn off Oracle TSAM Plus temporally, this command can be used. The format is as follows: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.tpgetcallinfo is used for call path monitoring. Using tpgetcallinfo allows applications to make dynamic decisions based on application performance metrics. When call path monitoring is enabled, tpgetcallinfo allows applications to get the corresponding call path information, for example, correlation ID and various timestamps.tsambegin()- Used in pair with tsamend() for users to manually add a segment to the current call path.If succeeded, TSAM Plus returns a positive description in long type denoting a sequence ID. The sequence ID is transferred to tsamend(), by which TSAM Plus can correlate the two APIs.Its error codes are defined in the file tsam_ext.h.
Table 1‑1 tsambegin Error Codes argc or argv value is invalid type value is invalid subtype value is invalidtsamend()- Used in pair with tsambegin() for users to manually add a segment to the current call path. It must be used with tsambegin() in the same thread.Specifies the sequence ID returned by tsambegin().Specifies the number of string pointed by argv. It must not less than 0.Its error codes are defined in the file tsam_ext.h.
Table 1‑2 tsamend Error Codes argc or argv value is invalid cd value is invalid