Scaling the Oracle Database Adapter Configuring Node Manager for the WLS_SOA Managed Servers Configuring Server Migration for the WLS_SOA Managed Servers

Extending the Domain with SOA Components 6-23

6.18 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 Oracle FMW 11gR1 PS1, that approach has now been superseded. If you were using this approach previously, you can simply remove in db.jca or clear on the Logical Delete wizard page the MarkReservedValue, and you will 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 non-recoverable situations in high-availability environments is minimized. ■ No unique MarkReservedValue needs to be specified. Previously, for this to work, you had 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.

6.19 Configuring Node Manager for the WLS_SOA Managed Servers

Oracle recommends using host name verification for the communication between Node Manager and the servers in the domain. This requires the use of certificates for the different addresses communicating with the Administration Server and other servers. See Chapter 9, Setting Up Node Manager for further details. The procedures in that chapter must be performed twice using the following information:

6.20 Configuring Server Migration for the WLS_SOA Managed Servers

Server migration is required for proper failover of the SOA components in the event of failure in any of the SOAHOST1 and SOAHOST2 nodes. See Chapter 10, Configuring Server Migration for further details. For SOA, use the following values for the variables in that chapter: ■ Server names: – WLS_SERVER1: WLS_SOA1 – WLS_SERVER2: WLS_SOA2 Note: this step is optional and applies only to those deployments that require adapter support for the BPEL processes that are invoked by IPM. Run Host Name HOST Virtual IP VIP Server Name WLS_SERVER Run 1: SOAHOST1 SOAHOST1VHN1 WLS_SOA1 Run 2: SOAHOST2 SOAHOST2VHN1 WLS_SOA2 6-24 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite ■ Host names: – HOST1: SOAHOST1 – HOST2: SOAHOST2 ■ Cluster name: – CLUSTER: SOA_Cluster

6.21 Backing Up the Installation