IBM WebSphere Adapters User Manual page 181

– They provide information on the state of the adapter for use by monitor
tooling
– Represented as common base event data at run time, event messages can be
included in the extended LogUtils.log method signatures
Support for protecting sensitive user data in log and trace files
WebSphere Adapter Toolkit provides support for confidential tracing of properties.
This means that when you decide whether a property might contain potentially
sensitive data and the use a special interface when you record that information in a
log or trace message. Data recorded with the special interface is displayed in the
logs by a "XXXX". This functionality is most useful to customers who mainly deal
with a lot of confidential information such as banks, healthcare companies and
defense. This property is a part of the Adapter Foundation Classes, and so it can
be used by any adapters.
When a property is marked as confidential and if it needs to be logged or traced,
then you record the information using a special confidential log and trace
method provided in the logUtils will be invoked.
The following types of information are considered potentially sensitive data and
will be hidden:
v The contents of a business object
v The contents of the object key of the event record
v User names , Password, Environment and Role
v The URL used to connect to the
The following types of information are not considered potentially sensitive data
and will not be hidden:
v The contents of the event record that are not part of the event record object key.
For example, the transactionID ( XID), event ID, business object name, and
event status
v Business object schemas
v Call sequences
Inserting log and trace messages
The WebSphere Adapter Toolkit automatically provides entry and exit tracing
statements to the generated code, excluding constructors and assessor methods.
The WebSphere Adapter Toolkit does not add logging and tracing statements to the
generated code for a JCA resource adapter. You will not be able to manually add
logging and tracing to the generated JCA adapter code.
You can insert log and/or trace statements into your generated IBM WebSphere
adapter code using a dialog box that collects information about the log or trace
statement to be generated and insert the appropriate code at the cursor position.
Trace messages:
Trace messages convey information that is intended for support teams and
developers. Such information includes stack dumps for exceptions and operation
logic for debugging purposes. Because trace messages are directed at the teams
that wrote or support the adapter rather than customers, trace messages need not
be translated and can, in fact, be hard-coded in the adapter.
WebSphere Adapter development overview
175