SOA 11g: Cluster installation

This article is a summary of the document you can download that describes in detail how to install and configure an Oracle SOA Suite11g installation. A previous article was written that was based on SOA 10g. This installation is a straight forward cluster installation that assumes the following components.
on the in a clustered environment.

• Load balancer
• Server node #1
• Server node #2
• Database

I assume that the database is high available, using Oracle RAC for example. This is shown in the next diagram.




The goal is to install the Oracle SOA Suite 11g software in a cluster on a such way that it is easy to configure, maintain and efficient in usage. We will install the following components based on release 11g, patch set 1 (ps1):

• Oracle Weblogic Server
  
• Oracle SOA Suite 11g

A few assumptions have been made:

The software is already installed:

• Oracle Weblogic Server 11g
• Oracle SOA Suite 11g
• Oracle HTTP Server (Linux)
  
• Oracle Repository Creation Utility (RCU) (Linux)
  

A database is available and configured with the SOA 11g repository schema's; such as DEV_SOAINSTA; DEV_MDS; etc.

We will install this software on each node. On each node we create a cluster and within that cluster two managed servers; soa_server and bam_server. On one of each server, node #1, we configure the admin server. On each server we install the Oracle HTTP Server that will route the requests to the two servers.

The approach of the installation is as follows.

1. Configure Weblogic Server cluster domain definition.
   
2. Pack and unpack cluster domain.
   
3. Apply Java Object Cache
   
4. Apply Oracle Coherence for cluster deployment
   
5. Start environment
   
6. Configure Oracle HTTP Server on each node

This article and the document could not be created without the following documents.

• Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite, 11g Release 1, E12036-02
• Chapter 4: Creating a domain
  
• Chapter 5: Extending the Domain for SOA Components

The document can be download here.

Post config, based on best practise:

• Enabled production mode in console and in domains/soadomain/bin/setDomainEnv.sh
• Set logging levels to Warn everywhere (servers, domain broadcaster) and enabled logs rotation.
• Checked Protocols->Enable Tunneling for all servers so SOA solution could handle t3 and iiop protocols
• Changed File Stores location to filestore/* subdirectories (to make cleanup easy).
• Specified valid listen address for AdminServer.
• Specifiedhostname for all managed servers

Have fun.

Marc