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

11.4.2 Tracing
Example 11-2 Output from dumpnamespace
=============================================================================
Beginning of Name Space Dump
=============================================================================
1 (top)
...
8 (top)/eis javax.naming.Context
9 (top)/eis/SCSCPJA1 SCSCPJA1
...
57 (top)/ejbs javax.naming.Context
58 (top)/ejbs/CTGTesterCCI itso.cics.eci.j2ee.testercci._CTGTesterCCIHome_Stub
...
Recall that we defined each connection factory’s JNDI binding path as being
eis/. Example 11-2 shows our connection factory
SCSCPJA1 bound with the JNDI path eis/SCSCPJA1 as specified in “Configure
a connection factory” on page 297.
Also recall that when we deployed the CTGTesterCCI enterprise application, we
used the value of ejbs/CTGTesterCCI for the JNDI Name of our CTGTesterCCI
session bean. Example 11-2 also shows the JNDI entry for our session bean.
Various levels of CICS TG tracing can be enabled from WebSphere. They are:
► Java application trace
► Resource adapter trace
► JNI trace
Java client trace
CICS TG Java client tracing can be set programmatically by adding the following
statements to the Java application:
com.ibm.ctg.client.T.setDebugOn(true);
com.ibm.ctg.client.T.setTimingOn(true);
Both of these traces go to the stderr output stream, so they will appear in the
standard error log file.
Note: Enabling CICS TG Java client tracing in an application will enable it for
all applications running in the application server, as a consequence of the
static nature of the T class.
Chapter 11. CICS TG and WebSphere Application Server for Windows 321