XCT data in IBM WebSphere

XCT context data is written to the HPEL log.

For the ECI resource adapter, the log is annotated with the target CICS® server, the CICS program name and, on exit, the CICS return code.

An example of XCT context data written to the HPEL repository viewed through the IBM® WebSphere® Application Server Log Viewer:

Screen image showing XCT context data in in the HPEL log.

The XCT context data can also be seen in the IBM WebSphere Application Server log file:

[9/3/12 12:45:10:016 GMT] 00000046  I UOW= source=com.ibm.websphere.XCT class= method= org=null prod=null component=null 
          thread=[WebSphere WLM Dispatch Thread t=007c40b8] requestID=[BKwWqX+HPuK-AAAAAAAAAAG]
          BEGIN BKwWqz2kOGV-AAAAAAAAAAE BKwWqz2kOGV-AAAAAAAAAAD ECIRA(Server(24TGNSIP) Program(EC01))
[9/3/12 12:45:31:106 GMT] 00000046  I UOW= source=com.ibm.websphere.XCT class= method= org=null prod=null component=null 
          thread=[WebSphere WLM Dispatch Thread t=007c40b8] requestID=[BKwWqX+HPuK-AAAAAAAAAAG]
          END   BKwWqz2kOGV-AAAAAAAAAAE BKwWqz2kOGV-AAAAAAAAAAD ECIRA(Server(24TGNSIP) Program(EC01) RC(ECI_NO_ERROR))

Additional information can be viewed using the IBM WebSphere Application Server Cross Component Trace.

For more information about configuring Cross Component Trace, see the IBM WebSphere Application Server V8.5 documentation.