Monday Feb 27, 2012

Enable Trace level logging for Oracle B2B 11g

Enable Trace level logging to debug Oracle B2B 11g
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.

Log 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.


Set Log Level to Trace1

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
/oracle/mwhome/user_projects/domains/hcfptrng_domain/servers/AdminServer/logs/AdminServer-diagnostic.log

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]
   [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService]
   [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:
   findBusinessMessageByB2BMessageId:
   Got 1messages for field messageId with value 7F000001135BFCABBE20000035016E70


Oracle B2B 11g Proxy Configuration

Oracle B2B 11g Proxy Configuration Various B2B Transports can be configured to use a proxy for sending and receiving.

For a complete list of transports that support a proxy on an outbound channel refer to the "Use Proxy" row in the following table.
http://docs.oracle.com/cd/E21764_01/integration.1111/e10229/b2b_tps.htm#BABJIJJF

For a complete list of transports that support a proxy on a listening channel refer to the "Use Proxy" row in the following table.
http://docs.oracle.com/cd/E21764_01/integration.1111/e10229/bb_listen_chan.htm#BAJDGEID

Proxy configuration is a two step process

1) Add the following options to the JVM that hosts WebLogic and the B2B transport
     -Dhttp.proxySet=true
     -Dhttp.proxyHost=192.168.1.115
     -Dhttp.proxyPort=8888

     -When adding the entries, change the Host and Port values above to match the location of your proxy.
     -Restart WLS

2) In the B2B Console select the "Use Proxy" checkbox on the transport that will use the proxy.
    For example, the image below shows the "Use Proxy" field on a HTTP Transport.
    The Url field value points to the endpoint the channel will call, not the proxy endpoint.

Use Proxy Transport checkbox

About

Picture of Bob

I am an Oracle Architect specializing in Service Oriented Architecture and Business Process Management.


Any code presented is for educational purposes only, no warranty or support is implied.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today