Date Added: Jun 2009
It is no mean task to configure a cluster. When it comes to an SOA Suite Cluster, it might seem easy at large. But there are still some things that might leave one befuddled. This blog looks at how one can configure a cluster in a manner that is more involved than when it comes to configuring a single instance. The paper suggests that this is not very complicated because it offers both scalability and high availability. This paper looks at the functioning of an SOA Suite cluster and the blog discusses some ideas around clustering and SOA Suite. This paper delves on clustering of BPEL Process Manager and the Oracle Service Bus. The BPEL and SOA Suites are very easily manageable when it comes to implementation of clustering. There is one more similarity that parallels the two suites?their linear scaling with increased nodes. The limitation on BPEL is the load on the backend dehydration store. The paper takes the example of an Oracle Real Application Cluster database that runs on 3-nodes to eventually provide for a high availability database environment. In such a case two clusters are available?a cluster of 5 BPEL Process Manager instances (all of them pointing to the same RAC database), and a cluster of 5 OSB instances. Both of the clusters are fronted by two hardware load balancers. The BPEL and OSB clusters can therefore provide load balancing through a front end web server. Even so, this paper suggests that a hardware load balancer is the best way to go about it.