Configuring the Common SOA Infrastructure Properties in Oracle 11g

In Oracle SOA Enterprise Manager Console, there are few common SOA Infrastructure properties that helps us during development.

• Audit Level
• Composite Instance State
• Payload Validation

In the EM console go to the SOA->soa-infra  and right click the soa-infra to see the Common Properties

By default the Audit Level is set to Production and others are unchecked.

• Audit Level

               "Production" (default): Composite instance tracking is collected, but Mediator engine will not collect payload details and BPEL engine will not collect payload details for assign activities (payload details for other BPEL activities are collected). This level is optimal for most normal production operations.

"Development": Allows both the composite instance tracking and payload detail tracking. However it may impact the performance. This level is useful mostly for testing and debugging purposes.

"Off": No logging is performed. Composite instance tracking and payload details are not collected. 

• Capture Composite Instance State 

                 Turning this feature on will allow for separate tracking for "running" instances. However, this may impact the performance. 

• Payload Validation 

                Select to enable validation of incoming and outgoing messages.

 Choose the values accordingly as required and save the properties (no server restart required).

Configuring XA Support for Data Sources in Oracle 11g

Changing the Driver Name to Support XA Drivers
           If your data sources require support for XA drivers, you must change the driver name on Oracle WebLogic Server. This is particularly true for environments in which BPEL processes assume XA is present when calling database adapters and JMS adapters.


Change the driver name through one of the following methods.

• Edit in Oracle WebLogic Server Administration Console.

1. Log into Oracle WebLogic Server Administration Console.
2. In the left pane, select Domain Structure.
3. Select Services > JDBC > Data Source > SOADataSource > Connection Pool.
4. For the Driver Class Name, change the value to oracle.jdbc.xa.client.OracleXADataSource. This provides support for the XA driver.
5. Restart the server.

• Edit the SOADataSource-jdbc.xml file.

1. Open the soaDataSource-jdbc.xml file on Oracle WebLogic Server.
2. Change the SOADataSource driver name from

          oracle.jdbc.OracleDriver to
          oracle.jdbc.xa.client.OracleXADataSource.
          <?xml version="1.0" encoding="UTF-8"?>
          <jdbc-data-source
          /. . .
          . . .
         / <name>SOADataSource</name>
        <jdbc-driver-params>
        <url>jdbc:oracle:thin:@adc60086fems.us.oracle.com:1537:co0yd570</url>
        <driver-name>*oracle.jdbc.xa.client.OracleXADataSource*</driver-name>
        <properties>
        <property>
        <name>user</name>
        <value>fusion_soainfra</value>
        </property>
        </properties>
        / . . .
        . . ./
       </jdbc-driver-params>
       /. . .
      . . ./
      </jdbc-data-source>

 Source:  Administrator’s Guide for Oracle SOA Suite and Oracle Business Process Management Suite 11g Release 1 (11.1.1)