Database Prerequisites VIP and IP Prerequisites Shared Storage Prerequisites

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-95 For information about configuring virtual IPs for the Administration Server and configuring the Administration Server for high availability, see Section 12.2.2.3, Transforming the Administration Server for Cold Failover Cluster. 5.13.1 Preparing the Environment: Prerequisite Steps Before Setting up a SOA High Availability Configuration The following sections provide prerequisite steps before setting up an Oracle SOA Service Infrastructure high availability configuration. For information about platform-specific commands, see the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite. ■ Section 5.13.1.1, Database Prerequisites ■ Section 5.13.1.2, VIP and IP Prerequisites ■ Section 5.13.1.3, Shared Storage Prerequisites ■ Section 5.13.1.4, Installing and Configuring an LDAP Provider ■ Section 5.13.1.5, Synchronizing System Clocks ■ Section 5.13.1.6, Terminology for Directories and Directory Environment Variables ■ Section 5.13.1.7, Installing and Configuring the Database Repository ■ Section 5.13.1.8, Using Oracle Fusion Middleware Repository Creation Utility to Load the Fusion Middleware Schemas in the Database ■ Section 5.13.1.9, Configuring Virtual Server Names and Ports for the Load Balancer ■ Section 5.13.1.10, Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2

5.13.1.1 Database Prerequisites

Oracle SOA Suite requires the presence of a supported database and schemas. To check if your database is certified or to see all certified databases, refer to the Certified Databases section in the Certification Document: http:www.oracle.comtechnologysoftwareproductsiasfilesfus ion_certification.html To determine the database version, execute this query: SQLselect version from sys.product_component_version where product like Oracle;

5.13.1.2 VIP and IP Prerequisites

As shown in Table 5–2 , you configure the Administration Server and the SOA managed servers to listen on different virtual IPs. This requires the provisioning of the corresponding VIP in the node and related host names in the DNS system in your network. Ensure that the different VIPS are available and are reachable from SOAHOST1, SOAHOST2, and the client systems before running the installation. 5-96 Oracle Fusion Middleware High Availability Guide

5.13.1.3 Shared Storage Prerequisites

For proper recovery in case of failure, store both JMS and transaction logs in a location that is accessible to all the nodes that can resume the operations after a failure in a managed server. This requires a shared storage location that can be referenced by multiple nodes. Table 5–3 lists the contents of shared storage. The shared storage can be a NAS or SAN device. Specifically for NFS mounted systems, different issues related to file locking and abrupt node failures have been detected. Check the Oracle Fusion Middleware Release Notes and with your storage vendor for the main recommended parameters to be used as mount options. The following is an example command based on a NAS device. Your options may be different from the ones specified in this section: SOAHOST1 mount nasfiler:volvolXFMWshared MW_HOME -t nfs -o rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768 Table 5–2 Virtual Hosts Virtual IP VIP Maps to... Description VIP0 SOAHOST1VHN0 SOAHOST1VHN0 is the virtual host name that is the listen address for the Administration Server and fails over with manual failover of the Administration Server. It is enabled on the node where the Administration Server process is running SOAHOST1 by default. VIP1 SOAHOST1VHN1 SOAHOST1VHN1 is the virtual host name that maps to the listen address for WLS_SOA1 and fails over with server migration of this managed server. It is enabled on the node where WLS_SOA1 process is running SOAHOST1 by default. VIP2 SOAHOST2VHN1 SOAHOST2VHN1 is the virtual host name that maps to the listen address for WLS_SOA2 and fails over with server migration of this managed server. It is enabled on the node where WLS_SOA2 process is running SOAHOST2 by default. Table 5–3 Contents of Shared Storage Server Type of Data Vol in Shared Storage Directory Files WLS_SOA1 Tx Logs VOL1 ORACLE_ BASEadmindomain _namesoa_cluster_ nametlogs Common location stores decided by WebLogic Server WLS_SOA2 Tx Logs VOL1 ORACLE_ BASEadmindomain _namesoa_cluster_ nametlogs Common location stores decided by WebLogic Server WLS_SOA1 JMS Stores VOL1 ORACLE_ BASEadmindomain _namesoa_cluster_ namejms Common location but Individual store per server for example: SOAJMSStore1, UMSJMSStore1 WLS_SOA2 JMS Stores VOL1 ORACLE_ BASEadmindomain _namesoa_cluster_ namejms Common location but Individual store per server for example: SOAJMSStore2, UMSJMSStore2 Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-97

5.13.1.4 Installing and Configuring an LDAP Provider