Creating the Production Site for the Oracle SOA Suite Topology Creating the Production Site for the Oracle Identity Management Topology

Setting Up and Managing Disaster Recovery Sites 4-55 ■ Creating the Production Site for the Oracle Portal, Forms, Reports, and Discoverer Topology ■ Validating the Production Site Setup

4.2.1 Creating the Production Site for the Oracle SOA Suite Topology

The production site should be installed and configured as described in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite with the following variations. The steps to install and configure the production site are listed below and should be followed in the sequence listed. 1. Create volumes and consistency groups on the shared storage device, as described in Section 4.1.1.1.1, Volume Design for Oracle SOA Suite. 2. Set up physical host names on the production site and physical host names and alias host names for the standby site. See Section 3.1.1, Planning Host Names for information on planning host names for the production and standby sites. 3. Install and configure Oracle SOA Suite as described in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite with the following modifications: a. Install the Oracle SOA Suite components into the volumes created on the shared storage device. b. Use the physical host names when installing and configuring WebLogic domain. c. Create a separate volume on each site for the JMS stores and transaction logs. d. After the installation and configuration of the production site, turn off host name verification. See the Disabling Host Name Verification for the Oracle WebLogic Administration Server and the WLS_WSM1 Managed Server section in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite for detailed instructions about turning off host name verification for an Administration Server and Managed Server. e. If you do not plan on turning host name verification off, follow the steps in Section 4.1.4, Node Manager to configure Node Manager communication. f. Create SSL certificates using the host name aliases on all of the Oracle Fusion Middleware hosts for proper Node Manager communication.

4.2.2 Creating the Production Site for the Oracle Identity Management Topology

The production site should be installed and configured as described in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management with the following variations. The steps to install and configure the production site are listed below and should be followed in the sequence listed. 1. Create volumes and consistency groups on the shared storage device, as described in Section 4.1.1.3.1, Volume Design for Oracle Identity Management. 2. Set up physical host names on the production site and physical host names and alias host names for the standby site. See Section 3.1.1, Planning Host Names for information on planning host names for the production and standby sites. 3. Install and configure Oracle Identity Management as described in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management with the following modifications: 4-56 Oracle Fusion Middleware Disaster Recovery Guide a. Install the Oracle Identity Management components into the volumes created on the shared storage device. b. Use the physical host names when installing and configuring the WebLogic domain. c. Create a separate volume on each site for the JMS stores and transaction logs. d. After the installation and configuration of the production site, turn off host name verification. See the Disabling Host Name Verification for the Oracle WebLogic Administration Server and the WLS_WSM1 Managed Server section in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite for detailed instructions about turning off host name verification for an Administration Server and Managed Server. e. If you do not plan on turning host name verification off, follow the steps in Section 4.1.4, Node Manager to configure Node Manager communication. f. Create SSL certificates using the host name aliases on all of the Oracle Fusion Middleware hosts for proper Node Manager communication.

4.2.3 Creating the Production Site for the Oracle WebCenter Topology