Skip to main content


developerWorks  >  WebSphere  >

Expanding clustered topologies for WebSphere Process Server and WebSphere Enterprise Service Bus

Configuration patterns and design decisions

developerWorks

Level: Intermediate

Eric Herness (herness@us.ibm.com), Chief Architect, WebSphere Business Integration, IBM
Graham Wallis (graham_wallis@uk.ibm.com), Senior Technical Staff Member, IBM
Charlie Redlin (redlin@us.ibm.com), WebSphere Process Server Architect, IBM
Karri Carlson-Neumann (karricar@us.ibm.com), Advisory Software Engineer, IBM

07 Jan 2009
Updated 07 Jan 2009

Get the download

Learn how and when to grow clustered topologies that use IBM® WebSphere® Process Server and WebSphere Enterprise Service Bus. When new BPM and ESB applications are deployed, you may need to expand the initial topology to take advantage of increased IT resources (such as memory) or to isolate applications. This article describes a standard "golden topology" widely used in production deployments, and then examines how to grow the topology from within the cluster, and by adding new clusters. It describes good and bad design patterns, what to consider, and the costs and limitations of each approach. The article also describes how to plan for Service Integration Bus connectivity and desired messaging engine behavior.



Download

DescriptionNameSizeDownload method
Article in PDF formateherness.pdf848KBHTTP
Information about download methodsGet Adobe® Reader®


About the authors

Eric Herness photo

Eric Herness is currently the Chief Architect for Websphere Business Integration and is from the Rochester, Minnesota development lab. He is senior member of the WebSphere Foundation Architecture Board and a core member of the Software Group Architecture Board. Eric has been involved in product architecture and product development in object technology and distributed computing for over 15 years.


Graham Wallis photo

Graham Wallis is a Senior Technical Staff Member at Hursley, UK and is responsible for the messaging componentry in WeSphere Application Server and the products built on it. Graham has been with IBM for 22 years and has worked on a variety of technologies, including data communications, parallel processing, asynchronous messaging, and high availability.


Charlie Redlin is an architect on the WebSphere Process Server development team in Rochester, Minnesota. He has worked in the development of WebSphere clusters and network deployment environments for many years. He currently works in a bring-up lab and is focused on the deployment and integration of WebSphere Process Server.


Karri Carlson-Neumann is an Advisory Software Engineer on the WebSphere Process Server development team in Rochester, Minnesota. She has been involved with the development of WebSphere Business Integration Server Foundation and WebSphere Process Server for many years. She currently works in a bring-up lab and is focused on the deployment and integration of WebSphere Process Server.




Rate this content


Please take a moment to complete this form to help us better serve you.



 


 


Not
useful
Extremely
useful
 


Back to top


Document options

Document options requiring JavaScript are not displayed

Discuss


My developerWorks needs you!

Connect to your technical community


Rate this content

Help us improve this content