By Bob Webster on Feb 27, 2012
The B2B 11g logging level can be changed at runtime to faciliate debugging of message interactions.
Perform the following steps:
1) Login to the EM Fusion Middlware Control
2) Under the Farm tree on the left side
Expand the SOA folder and right mouse click on the soa-infra node.
Select Logs -> Log configuration from the context menu.
3) The Log Configuration Page appears as shown below.
Under the "Log Levels" tab
Expand the "oracle.soa" node and locate the oracle.soa.b2b node.
Using the dropdown select box change the log level for the oreacle.soa.b2b.node to TRACE:1
Hit the Apply button in the upper right corner to save the configuration change.
Changes to the log level are immediate, no restart of the WLS server is required.
Trace level log entries will be written to the *-diagnostic.log of the server hosting SOA.
For example, on a development workstation where soa is running on a single admin server the log is located at
Trace level log entries similar to the entry below will be written to the log.
The following TRACE entry was output by the oracle.soa.b2b.engine
[2012-02-27T09:10:31.743-08:00] [AdminServer] [TRACE]  [oracle.soa.b2b.engine]
[tid: [ACTIVE].ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)']
[userId: <anonymous>] [ecid: 11d1def534ea1be0:4204a3be:135bf121efc:-8000-0000000000004d02,0:2]
[WEBSERVICE_PORT.name: execute_pt] [APP: soa-infra] [composite_name: Provider_270_271]
[component_name: Send270] [J2EE_MODULE.name: fabric]
[SRC_METHOD: synchedLog_J] [WEBSERVICE.name: EligibilityCompositeService]
[J2EE_APP.name: soa-infra] oracle.tip.b2b.msgproc.ToplinkHelper:
Got 1messages for field messageId with value 7F000001135BFCABBE20000035016E70