5-2 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
■
Section 5.15, Configuring Oracle HTTP Server for the WLS_SOAn Managed Servers
■
Section 5.16, Validating Access Through Oracle HTTP Server
■
Section 5.17, Setting the Frontend HTTP Host and Port
■
Section 5.18, Setting the WLS Cluster address for Direct BindingRMI invocations to composites
■
Section 5.19, Configuring a Shared JMS Persistence Store
■
Section 5.20, Configuring a Default Persistence Store for Transaction Recovery
■
Section 5.21, Enabling High Availability for Oracle File and FTP Adapters
■
Section 5.22, Scaling the Oracle Database Adapter
■
Section 5.23, Backing Up the Installation
5.1 Installing Oracle Fusion Middleware for SOA Home
You must install Oracle Fusion Middleware for SOA on both SOAHOST1 and SOAHOST2. These nodes will run managed servers configured with SOA
components.
1.
Start the installer for Oracle Fusion Middleware for SOA.
SOAHOST1 runInstaller
When the installer prompts you for a JREJDK location enter the Oracle SDK location created in the Oracle WebLogic Server installation, for example, MW_
HOMEjrockit_160_version .
2. In the Welcome screen, click Next.
3.
In the Prerequisite Check screen, verify that the checks complete successfully, and click Next.
4.
Specify the installation location. Select the previously installed Middleware Home from the drop-down list. For the Oracle Home directory, enter the directory name
soa.
Click Next. 5.
In the Installation Summary screen, click Install. 6.
In the Installation Complete screen, click Finish.
5.2 Enabling VIP2 on SOAHOST1 and VIP3 on SOAHOST2
The SOA domain uses virtual hostnames as the listen addresses for the SOA managed servers. You must enable A VIP mapping each of these hostnames on the two SOA
Machines, VIP2 on SOAHOST1 and VIP3 on SOAHOST2, and must be correctly resolve the virtual hostnames in the network system used by the topology either by
DNS Server, hosts resolution.
To enable the VIP, follow the steps described in Section 4.3, Enabling VIP1 in
SOAHOST1. These VIPs and VHNs are required to enable server migration for the
SOA Servers. Server migration must be configured for the SOA System for high availability purposes. Refer to Chapter 9, Server Migration of the Oracle Fusion
Middleware Enterprise Deployment Guide for Oracle SOA Suite for more details on configuring server migration for the SOA servers.
Extending the Domain for SOA Components 5-3
5.3 Extending the Domain for SOA Components
In this step, you extend the domain created in Chapter 4, Creating a Domain
to contain SOA components. In this section we are assuming that the SOA deployment
uses the same database service wcedg.mycompany.com as the WebCenter deployment. However, a deployment may choose to use a different database service
specifically for SOA such as soaedg.mycompany.com.
1.
Change directory to the location of the Configuration Wizard. This is within the SOA home directory. It is recommended that all database instances should be up.
SOAHOST1 cd ORACLE_HOMEcommonbin 2.
Start the Configuration Wizard.
SOAHOST1 .config.sh 3.
In the Welcome screen, select Extend an existing WebLogic domain, and click Next
.
4.
In the WebLogic Domain Directory screen, select the WebLogic domain directory ORACLE_BASEadmindomain_nameaserverdomain_name, and
click Next.
5.
In the Select Extension Source screen, do the following:
■
Select Extend my domain automatically to support the following added products
.
■
Select the following products:
– Oracle SOA Suite 11.1.1.0
The following products should already be selected, and grayed out. They were selected when you created in domain in
Section 4.4, Running the Configuration Wizard on SOAHOST1 to Create a Domain.
– Basic WebLogic Server Domain
– Oracle Enterprise Manager
– Oracle WSM Policy Manager
– Oracle JRF
Click Next. 6.
If you get a Conflict Detected message that Oracle JRF is already defined in the domain, select the Keep Existing Component option and click OK.
7.
In the Configure JDBC Component Schema screen Figure 5–1
, do the following:
Note: You must back up the current domain before extending the
domain. You may use the backup to recover in case any errors were made in the domain extension. See Oracle Fusion Middleware
Administrators Guide.
Note: Oracle SOA uses Quartz to maintain its jobs and schedules in
the database. The system clocks for the SOA WebLogic cluster must be synchronized to enable Quartz jobs to run correctly across the cluster.
5-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
a. Select the SOA Infrastructure, User Messaging Service, and SOA MDS
