IBM E02HRLL-G - WebSphere Partner Gateway Express, Administration Manual

Page: 151 / 268

components. Components are represented by the Java package names for the
classes that can provide trace information when they are issued by the application
server.
Note: The Java package names for WebSphere Partner Gateway classes all begin
with the prefix
com.ibm.bcg
so you can locate the individual components by
looking for packages that use this prefix.
There are three ways to set log detail levels:
v
To set log details at the component level using the component tree:
1.
Select the item.
2. Choose the level of tracing you require.
3.
Click
OK
on the page to make the change
v
To set log details at the group level using the group tree:
1.
Select the group name.
2. Choose the level of tracing you require.
3. Click OK to make the change
Note: There are groups of components that represent WebSphere Partner
Gateway subsystems like the receiver or the document manager state engine.
You can view the subsystems by clicking the
Groups link. The WebSphere
Partner Gateway group names can be identified because they all start with the
prefix
BCG
. Each of the group names describes the purpose of the classes and
packages that are in the group.
v
To Set log details by directly entering package and class names. The names that
are in the tree views are only a fraction of all the packages and classes that make
up WebSphere Partner Gateway applications. You might be asked to obtain
tracing for classes that are not in these lists.
If you change the configuration page, be sure to save the configuration to the
master configuration according to the message that displays at the top of the page.
Identifying WebSphere Partner Gateway trace messages
If you configured tracing with the Advanced format, each trace message includes
the class name, method name, originator, thread id, thread name, and other
information for the message. The Basic log format contains necessary information
like timestamp, thread id, source class, source method, severity level and log
message.
Note: WebSphere Partner Gateway does not use the First Failure Data Capture
(FFDC) functionality of WebSphere Application Server. Do not refer to the FFDC
logs unless directed to by product support or specific troubleshooting instructions.
EDI, XML, ROD subcomponent tracing
There might be times to enable tracing for some EDI, XML and ROD (flat file)
components that are used in relation to validation maps and transformation maps
created by the DIS Client. These are enabled from the
WebSphere Partner Gateway
Console > System Administration > Feature Administration > EDI Properties
.
For the trace level settings and purpose of each property, see Table 54 on page 232
Chapter 14. Using logging and tracing features
145