IBM WebSphere Adapters Network Card User Manual


 
"getRecordForEvent()", "test");
return null;
}
}
Example of trace message for the outbound scenario with confidential tracing
property enabled
public HelloWorldConnectionFactory(ConnectionManager connMgr, WBIManagedConnectionFactory mcf) {
super(connMgr, mcf);
getLogUtils().traceConfidential(Level.FINE,
"com.ibm.helloworld.outbound.HelloWorldConnectionFactory",
"HelloWorldConnectionFactory()", "test",
new Object[] { "str" });
}
Example of trace message for the inbound scenario with confidential tracing
property enabled
public javax.resource.cci.Record getRecordForEvent(com.ibm.j2ca.extension.eventmanagement.Event event)
throws javax.resource.ResourceException,
javax.resource.spi.CommException {
logger.traceConfidential(Level.FINE,
"com.ibm.helloworld.inbound.HelloWorldEventStoreWithXid",
"getRecordForEvent()", "test", new Object[] { "str" });
return null;
}
Note: In the previous code snippets, getLogUtils() and logger are instances of the
LogUtils class.
Trace levels
Three trace levels allow users to adjust the level of detail. Consult the guidelines
shown in the following table to determine which trace level to assign to a trace
message.
Table 5. Trace level indicators
Level Indicator Significance
Fine 1 This trace features the lowest level of detail. It includes
broad actions taken by the adapter such as establishing a
connection to the EIS, converting an event in the EIS to a
business object (key values only), processing a business
object (key values only).
Finer 2 This trace provides more detailed information on adapter
logic, including API calls to the EIS and any parameters
or return values.
Finest 3 This is the most detailed level and includes method entry,
exit, and return values. Include complete business object
dumps and all detail needed to debug problems.
Configuring log and trace detail level
Set the trace level on the package that you want to trace to all in the Change Log
Detail Levels field: For example, if the adapter package name is
com.ibm.myadapter, modify the Change Log Detail Levels pane and add
com.ibm.myadapter.* = all.
Performance considerations
WebSphere Adapter development overview 177