Click Save after you update the properties. The Save Deployment Plan page Click Save and Activate. Scaling the Oracle Database Adapter

Extending the Domain for SOA Components 5-23 in-memory mutex to lock outbound write operations. You must choose from the following values for synchronizing write operations: memory: The Oracle File and FTP Adapters use an in-memory mutex to synchronize access to the file system. oracle: The adapter uses Oracle Database sequence. db: The adapter uses a pre-created database table FILEADAPTER_MUTEX as the locking mechanism. You must use this option only if you are using a schema other than the Oracle Database schema. user-defined: The adapter uses a user-defined mutex. To configure the user-defined mutex, you must implement the mutex interface: oracle.tip.adapter.file.Mutex and then configure a new binding-property with the name oracle.tip.adapter.file.mutex and value as the fully qualified class name for the mutex for the outbound reference.

h. Click Save after you update the properties. The Save Deployment Plan page

appears. i. Enter a shared storage location for the deployment plan. The directory structure is as follows: ORACLE_BASEadmindomain_namecluster_namedpPlan.xml

j. Click Save and Activate.

k. Configure BPEL Process or Mediator Scenario to use the connection factory as shown in the following example in the jca file included in the composite for the binding component: adapter-config name=FlatStructureOut adapter=File Adapter xmlns=http:platform.integration.oracleblocksadapterfwmetadata connection-factory location=eisHAFileAdapter adapterRef= endpoint-interaction portType=Write_ptt operation=Write interaction-spec className=oracle.tip.adapter.file.outbound.FileInteractionSpec property.. property.. interaction-spec endpoint-interaction adapter-config

5.22 Scaling the Oracle Database Adapter

If you are using Logical Delete polling, and you set MarkReservedValue, skip locking is not used. Formerly, the best practice for multiple Oracle Database Adapter process instances deployed to multiple Oracle BPEL Process Manager, or Oracle Mediator nodes was essentially using LogicalDeletePollingStrategy or DeletePollingStrategy with a unique MarkReservedValue on each polling node, and setting MaxTransactionSize. However, with the introduction of skip locking in this release that approach has now been superseded. If you were using this approach previously, you can simply remove Note: The location attribute is set to eisHAFileAdapter for the connection factory. 5-24 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter in db.jca or clear Logical Delete Page of wizard the MarkReservedValue, and you automatically get skip locking. The benefits of using skip locking over a reserved value include: ■ Skip locking scales better in a cluster and under load. ■ All work is in one transaction as opposed to updatereserve, then commit, then select in a new transaction, so the risk of facing a non-recoverable situation in a high availability environment is minimized. ■ No unique MarkReservedValue must be specified. Previously, for this to work you would have to configure a complex variable, such as R{weblogic.Name-2}-{IP-2}-{instance}. For more information, see Scalability and Polling Strategies in Oracle Fusion Middleware Users Guide for Technology Adapters.

5.23 Backing Up the Installation