Business Transaction Management (BTM) Integration

This chapter contains the following topics:

•

Overview

•	Prerequisite

•	Enable BTM Monitoring from Tuxedo

•	BTM Discovery

•	Tuxedo Container in BTM

•	Dependency

•	BTM Transaction for Tuxedo Operation

•	Call Path in TSAM Console

•	Tuxedo Service in BTM

Overview

By integrating TSAM Plus and BTM, users are able to:

•	Discover and track transactions across Tuxedo and more products monitored by BTM.

•	Drill down into TSAM Plus call path detailed information for a transaction coming from WTC side using the transaction ECID from BTM console.

Figure 4‑1 describes a typical scenario of a BTM transaction across the JEE server and Tuxedo domains.

Figure 4‑1 Delegate Container

In this scenario, a Tuxedo BTM delegate observer runs in a JVM started in the /T domain gateway by JNI technology. When the /T domain gateway receives inbound/outbound messages, it sends BTM inbound/outbound requests to BTM delegate observer.

Prerequisite

The following prerequisites must be met before monitoring Tuxedo by BTM.

•	BTM 12.1.0.6 is installed. For more information, see Oracle® Business Transaction Management Installation Guide.

•	The WTC and BTM JavaEE observer (12.1.0.6 or higher) are configured in Weblogic 12.1.3.0 or later.

•	TSAM 12.1.3.0.0 or later is required for BTM monitoring.

•	TSAM 12.1.3.0.0 agent is installed by enabling TSAM Plus during Tuxedo 12.1.3.0.0 installation.

Enable BTM Monitoring from Tuxedo

BTM Discovery

BTM discovery is entirely traffic-based. If messages are not flowing through the observed endpoints, Business Transaction Management cannot discover any application components nor can it discover the dependencies between these components.

Before discovery is performed, following steps must be done.

1.	Install the observers in the environment you want to observe.

A delegate observer is included in $TUXDIR/udataobj after TSAM Plus installation. You do not need to install any observer for Tuxedo observe. For the WTC monitoring, you must install the JavaEE observer in Weblogic side. For more information, see Installing Observers Overview.

2.	From the Observer Communication Policy page in BTM Console, check the DELEGATE probe is enabled.

3.	From the Observer Communication Policy page in BTM Console, choose Use fully qualified name (FQN) for Observer Behavior -> Mapping Algorithm.

Discovery involves the following steps:

1.	Send traffic through your system.

2.	Check the containers being observed. (Restarting the containers after installing Business Transaction Management is not enough to make them visible, you must send traffic to have them be seen.)

3.	View services to see that all the services you are interested in observing have been discovered.

4.

Check that measurements are being taken by looking at the Summary or Analysis tab for a service. Throughput, traffic, maximum response time, and average response time should be available for all the services involved in message traffic. If measurements are inaccurate or missing, it's possible that not enough time has elapsed for Business Transaction Management to calculate traffic measurements or perhaps monitoring was disabled.

Note:

Make sure you have created “BTM transaction for Tuxedo operation” before viewing measurements.

5.	Look at dependencies in the Service Map to see how traffic is flowing in your system.

6.

Adjust as necessary. Generally speaking if the discovered picture does not meet your expectations, the first thing to do is run more traffic to make sure Business Transaction Management has had time to see all pieces of your system. If that does not resolve your problem, you might need to do one or more of the following:

•	Check the -m option for GWTDOMAIN is configured correctly, and "The BTM monitoring is enabled." is printed in ULOG.

•	Check the "DELEGATE" probe for the "Observer Communication Policy" is enabled.

•	Check if the Weblogic and Tuxedo version is supported by BTM Tuxedo monitoring.

•	Resolve discovery problems due to versioning policy or replication problem.

Tuxedo Container in BTM

When BTM monitoring is enabled, GWTDOMIAN starts an embedded JVM and runs a BTM delegate observer to monitor bidirectional calls between WTC and itself. The Type for this container is "DELEGATE" and the address for this container is always "delegate://<Tuxedo host address>:11/"

Figure 4‑2 Delegate Container

All Tuxedo endpoints with the same base address belong to a same Tuxedo container. The address for this container is the endpoint's base address and the Type for this container is "TUXEDO/<Tuxedo version number>".

Figure 4‑3 Tuxedo Container

Dependency

For a service call through WTC and Tuxedo, no matter it is inbound or outbound call from Tuxedo, two services are defined in a BTM transaction to represent Tuxedo and WTC respectively.

The dependency between Tuxedo service and WTC service can be viewed in BTM console.

Figure 4‑4 Service Map

BTM Transaction for Tuxedo Operation

By use of the ECID (Execution Context ID) propagation feature introduced in Weblogic and Tuxedo, you can create the transaction in BTM console using ECID as Instance's message key. With the ECID, you can query the call path inner Tuxedo domain in the TSAM management console when the policy is configured.

All measurements based on the transaction can be shown in BTM console.

Note:

All BTM observers or BTM delegate observers (including the one embedded in GWTDOMAIN) must be located at machines with the same system time.

Following is the steps for creating a BTM Transaction based on Tuxedo operation.

1.	From BTM console, click Create -> Transaction in the up-left corner.

2.	In the popup window, choose the operations invoked in the transaction.

3.

Click OK.

If the dependency is already discovered by BTM, the related operations are automatically added in the transaction. Otherwise, you need to manually add the operations you want to monitor in this transaction.

4.	Select Start message and End message.

5.	Click the Logging tab. Enable the instance and message logging. This step is required only if you want record every transaction instance.

Figure 4‑5 Enable the Instance and Message Logging

6.	Click the Message Keys tab.

7.	Select requestECID as Start key and End key for all operations.

8.	Type a transaction name.

9.

Click OK.

Note:

For the transaction initiated by Tuxedo, you must configure ECID_CREATE as OPTIONS in UBBCONFIG.

Call Path in TSAM Console

When TSAM Plus is registered correctly and LMS server is configured in the Tuxedo domain, each call from the remote WTC monitored by BTM automatically initializes a TSAM call path from GWTDOMAIN. You can get the call path information from TSAM Plus console.

Tuxedo Service in BTM

Table 4‑1 lists the BTM property definitions for the Tuxedo service.

 

Table 4‑1 BTM Property Definitions for Tuxedo Service

BTM Property	Tuxedo Property
	Remote Service	Local Service
Service Namespace	http://oracle.tuxedo
ServiceName	The Remote Name of WTC exported service	The Remote Name of WTC imported service
OperationName	processWTCCall	callWTC
Request Url	tuxedo://<remote NWADDR>/ServiceName	tuxedo://<The network address for WTC remote access point>/ServiceName
EndpointType	urn:com.amberpoint.servicegenres:TUXEDO
ServiceType	urn:com.amberpoint.servicegenres:TUXEDO_SERVICE
Protocol	ATMI
ApplicationProtocol	SOAP

Table 4‑2 lists the BTM property definitions for the WTC services.

 

Table 4‑2 BTM Property Definitions for WTC Service

BTM Property	WTC Property
	Exported Service	Imported Service
Service Namespace	http://oracle.weblogic.wtc
ServiceName	Remote Name in WTC Exported Services	Remote Name in WTC Imported Services
OperationName	processTuxedoCall	callTuxedo
Request Url	apwtc://weblogic address: LocalAccessPointPort/WTC_EXPORT/ServiceName", for example, "apwtc://localhost:10086/WTC_EXPORT/TOLOWER	apwtc://weblogic address:port/WTC_IMPORT/LocalAccessPointId_RemoteAccessPointId/ServiceName
EndpointType	urn:com.amberpoint.servicegenres:WTC_EXPORT	urn:com.amberpoint.servicegenres:WTC_IMPORT
ServiceType	urn:com.amberpoint.servicegenres:WTC_SERVICE
Protocol	ATMI	AmberPointObservedMessage
ApplicationProtocol	SOAP