Fault Propagation Non-Retryable Errors for Outbound Interaction Handling

ADAPTER Life-Cycle Management 2-41 Figure 2–13 Fault Propagation

2.22.3.2.2 Two Cases When the Fault Policy Mechanism Does Not Work

There are two cases where the fault policy mechanism does not work: ■ Outbound Adapters in XA Mode ■ Outbound Adapters in Mediator Sequential Routing

2.22.3.2.3 Outbound Adapters in XA Mode

The fault policy mechanism does not work for outbound adapters in XA mode. For example, in XA mode, if you want the fault policy to retry when the outbound adapter fails, it will not retry and any outbound adapter that has been successful before this failure occurred does not rollback messages.

2.22.3.2.4 Outbound Adapter in Mediator Sequential Routing

Fault policies also do not work for the outbound adapter that is invoked in Mediator sequential routing, because the mediator fault policies are applicable to parallel routing rules only.

2.23 Testing Applications

You can run and test instances of deployed SOA composite applications from Oracle Enterprise Manager Grid Control Console. This enables you to: ■ Manage a composite application ■ Initiate an instance of a composite ■ Track an instance of a composite ■ View detailed component instance audit trails For more information about testing applications, see Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle Business Process Management Suite. Adapter Adapter Service Infrastructure BPEL Service Infrastructure Service Infrastructure Invocation Exception Service Infrastructure Invocation Exception 2-42 Oracle Fusion Middleware Users Guide for Technology Adapters

2.24 Setting the Trace Level of Oracle JCA Adapters

Set the trace level for the following types of adapters as follows: ■ Oracle JCA Adapters and Oracle Adapter for Oracle Applications: set the log level to, for example, TRACE:32 in the logger oracle.soa.adapter. For more information about setting trace levels for adapters, see Oracle Fusion Middleware Administrators Guide. ■ Packaged-application adapters: For outbound interactions, set the Loglevel property for packaged-application adapters in the weblogic-ra.xml file. ■ Legacy adapters: you can use Oracle Studio to set the trace level for Oracle Connect, and the mainframe server.

2.24.1 How to Set the Trace Level of Oracle JCA Adapters

To set the trace level by using the Fusion Middleware Control Console: 1. Navigate to http:servername:portnumberem. The Fusion Middleware Control Console home page is displayed. 2. Right-click soa-infra from the SOA Folder in the Navigator in the left pane. The console displays a menu. 3. Select Logs, and the Log Configuration, as shown in Figure 2–14 . Figure 2–14 Navigating to the Log Configuration Page The Log Configuration page is displayed.

4. Locate oracle.soa.adapter in the Logger Name list, and change the log level in the

Oracle Diagnostic Logging Level Java Level field. In this example, select Trace:32 FINEST from the list, as shown in Figure 2–15 .