CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

322 CICS Transaction Gateway V5
J2EE resource adapter trace
Resource adapter tracing can either be set programmatically, or by using the
WebSphere administrative console to change properties in the connection
factory.
Programmatic trace control
Resource adapter tracing is set programmatically using the
ECIManagedConnectionFactory object. Two steps must be taken to enable
tracing:
1. Turn logging on through the setLogWriter() method.
2. Specify the level of tracing using the setTraceLevel() method as shown:
ECIManagedConnectionFactory mcf = new ECIManagedConnectionFactory();
mcf.setLogWriter(new java.io.PrintWriter(System.out));
mcf.setTraceLevel(new Integer(mcf.RAS_TRACE_INTERNAL));
Valid levels of tracing are as follows, with each level of trace building upon the
previous level. Therefore, ENTRY_EXIT includes everything in
ERROR_EXCEPTION, and INTERNAL includes all trace levels:
RAS_TRACE_OFF Disable all tracing
RAS_TRACE_ERROR_EXCEPTION Output exception trace stacks
RAS_TRACE_ENTRY_EXIT Output method entry and exit stack traces
RAS_TRACE_INTERNAL Output debug trace entries
.
Tip: We found that the CICS resource adapter trace traced the execution of
methods only within the resource adapter itself. The resource adapter acts as
a client to the CICS TG classes, so enabling CICS TG Java client tracing will
provide extra information. We suggest that you combine J2EE resource
adapter trace with the use of the com.ibm.ctg.client.T class, since this will
provide end-to-end debug information.
Managed connections
Tracing on a connection factory is set using the TraceLevel property of the
connection factory resource. To modify tracing, from the WebSphere
administrative console expand WebSphere Administrative Domain ->
Resources -> J2C Resource Adapters -> CICS ECI and click J2C Connection
Factories. Click the connection factory instance and then click the Connections
tab. The TraceLevel property controls the tracing (Figure 11-32 on page 323).