Clustering SOA Suite for HA – BPEL, ESB, OWSM ..
Key Points in configuring High Availability or Clustering SOA Suite Components (BPEL, ESB, OWSM, BAM)
— If you wish to configure SOA Suite for High Availability (Active-Active) deployment, don’t use Oracle SOA Suite Advanced Install Option (J2EE, Web Server and SOA Suite). You have to install it in two phases
a) First install J2EE and Web Server from SOA Suite (10.1.3) CD (Select Advanced Install and then select J2EE Server and Web Server 662 MB)
b) Then install SOA Suite components from component CD-ROM (BPEL, ESB, OWSM..) on OC4J installed on above component. To download individual product (BPEL, ESB..) software click here
— You configure load balancer in front of Web Server installed in HA (High Availability) Active-Active configuration, load balancer will forward request to Web Server which in turn will forward requests to applications (BPELConsole, esb, ccore..) deployed on OC4J
— While installing ESB (Enterprise Service Bus) from ESB CD-ROM you have to install ESB Repository Server and ESB Runtime Server in different ORACLE_HOME (These two servers of ESB in HA deployment can’t share oracle_home as only one ESB Repository Server will be up at any given time)
— While installing ESB in HA you have to repeat installation twice, once for ESB Repository Server and another time for ESB Runtime Server component of ESB
— You can cluster OC4J’s but this is optional configuration
Changes for BPELConsole Application
— Set soapServerUrl and soapCallbackURL properties of BPEL to load balancer URL using BPEL Console
— Change JNDI lookups to use list of JNDI Providers (returned by opmn)
— All the BPEL servers in cluster should have same domain
— If you are using RAC database as dehydration store then change data-sources.xml to include RAC details
— If BPEL Servers part of cluster are in different subnet then modify jgroups-protocol.xml
Changes for ESB
— ESB Repository Server and ESB Runtime Server in HA deployment should be installed in different ORACLE_HOME
— ESB Cluster name for ESB Runtime server should be changed after deployment (To ensure ESB cluster include only ESB Runtime Server and not ESB Repository Server)
— ESB Runtime Server should use one name for ESB Cluster where as for ESB Repository Server cluster should use different cluster name
Changes for BAM (Windows only)
— BAM consists of following components Active Data Cache (need hardware cluster), Enterprise Link, Plan Monitor, Web Applications, Report Cache (need hardware cluster), Event Engine (need hardware cluster)
Business Rules
There is no server or service running as Business Rule but it is an libabry to which an application can use.
Web Services Manager (OWSM)
— Install OWSM on cluster nodes configured by load balancer in front. Various components of OWSM are Gateway, Policy Manager, Monitor and Web Services Manager Control
Related
Install SOA Suite
Integrate SSO with SOA Suite
Step by Step deployment of SOA Suite (BPEL, ESB, OWSM) in cluster / HA (High Availability) coming soon …