1.2.2.4 XA Transaction

There are two ways to initiate XA Transaction queries: you can specify an XA Transaction identifier, or you can query using filtering parameters. These two ways are exclusive. The following table lists the XA Transaction Query by Scope filtering options.

Table 1-27 XA Transaction Query by Scope Panel Options

Options	Description
Initiator Type	There XA Transaction monitoring scenarios: If the monitoring policy is applied to an XA Transaction initiator, monitoring initiated with the XA Transaction path propagation (similar to Call Path). If monitoring is initiated for particular processes only (such as TMS without initiator involved), propagation does not take place and only the monitored XA Transaction calls are reported. The "Initiator Type" applies to the first situation, so that a specific XA Transaction can be retrieved. It has the following values: All Native Client Workstation Client Jolt Client Domain Gateway Application Server The default value is All and the second monitoring scenario must use the default setting.
Status	Allows you to select the following values: Any Succeeded Failed
Query for latest	Query under latest time (in seconds).
Query during	Query XA transactions during a specific time period.
Query by GTRID	Query an XA transaction by using an XA transaction identifier. For example x0 x46524a28 x1. For more information, see How the System Tracks Distributed Transaction Processing in the Oracle Tuxedo User Documentation. The Exact Match checkbox is under the text field. If checked, the whole identifier string must be matched, otherwise all the XA transaction IDs that contain the specified string are listed.

Click Submit; the XA Transaction results appears in the XA Transaction Result List panel.

The following table lists the XA Transaction Results List panel options.

Table 1-28 XA Transaction Results List Panel Options

Options	Description
GTRID	Global Transaction ID.
Initiator	The initiated process where the transaction starts.
Status	Successful transactions indicated by Failed transactions indicated by
Start Time	Time when the XA Transaction started.
Duration (microsecond)	Total transaction time span.
Execution Time (microsecond)	Total transaction time per Oracle Tuxedo service.
Parent GTRID	Displays the GTRID of the previous domain if the transaction was propagated from another Oracle Tuxedo domain.

When you click on a transaction item in the list, the transaction path, related call path ID and transaction details are displayed in the XA Transaction Path, Corresponding Call Path Correlation ID and XA Transaction Detail panels respectively.

The XA Transaction Path shows the XA Transaction network in a tree structure similar to the Component Tree. In the XA Transaction Path tree, each node represents one domain XA Transaction. If multiple /T domains are involved in the XA Transaction, the XA transaction spread path can be easily observed.

In the Corresponding Call Path Correlation ID panel, the call path(s) related to the XA transaction are listed. You can include multiple call path correlation IDs in an XA Transaction. To do so, you must define an XA Transaction policy element and a call boundary call path policy element. If the two elements are applied to one process, one XA Transaction monitoring process includes multiple call paths. Clicking on the call path ID displays the call path detail in the Call Path Metric.

The following lists the XA Transaction Detail panel options.

Table 1-29 XA Transaction Detail Panel Options

Options	Description
XA Routine	The transaction routine names are as follows: tpbegin tpcommit tprollback tpabort xa_commit xa_start xa_prepare xa_rollback xa_end tms_msg_xxx (for GWTDOMAIN XA Transaction activities) xa_msg_xxx (for GWTDOMAIN XA Transaction activities)
Return Code	The XA Routine return code.
Machine/Group/Process	The XA Routine process information. The process can be an Oracle Tuxedo server or a client.
Start Time	The time when the XA Routine started.
Execution Time (microsecond)	The elapse time used for the XA Routine.