The first article in this series, WebSphere® Process Server and WebSphere Enterprise Service Bus deployment patterns, Part 1: Selecting your deployment pattern, provides knowledge and guidance for planning deployment environments. The article includes a design patterns section that contains general descriptions and diagrams of example patterns (step-by-step instructions are not included). A design guide section explains what the elements of the patterns actually are, and the alternatives and trade-offs associated with these elements.
This article, the second in the series, focuses on selecting a correct deployment pattern to meet the requirements of a given customer application or project. It provides focused, step-by-step guidance for creating "My First WPS Cluster", which is one of the design patterns discussed in the design guide. You can consider this article a final solution document, which details the steps for creating this specific deployment pattern. This article and future articles in this series are supporting documents for the design guide included in the first article of this series.
This article is best read by someone with a general understanding of WebSphere Enterprise Service Bus or WebSphere Process Server, the clustering technologies provided by WebSphere Application Server (WAS), the clustering concepts of the System Integration Bus (SIB), and the deployment environment of WebSphere Application Server Network Deployment (WAS ND).
You should read the first article in this series before attempting to work on this article and future articles in this series.
The contents of this article are based on WebSphere Process Server Version 126.96.36.199.
This article introduces you to the My First Process Server Cluster design pattern, which is one of the deployment patterns described in the design guide for IBM® WebSphere® Process Server and WebSphere Enterprise Service Bus deployment patterns. The goal of this very basic pattern is to provide a deployment environment for simple process server modules and mediation modules. The simple modules contain synchronous interactions. An additional goal of this pattern is to provide a starting point for you in planning and setting up WebSphere Process Server or WebSphere Enterprise Services Bus clustered environments. Setting up this topology and getting a business module deployed is a very good exercise for getting started in the world of clustering.
This article is focused on the actual steps that a user will perform to create this pattern. In order to keep the focus on the steps themselves, not every action will be explained, and not every decision will be weighed. For a discussion of the decisions that must be addressed, please refer back to the first article in this series.
|Article in PDF format1||0701_carlson_neumann.pdf||2MB||HTTP|
|Part 1 reference guide2||0611_redlin-deploypatterns.pdf||800KB||HTTP|
- This is the PDF file for this article.
- Reference guide for Part 1 of this series
WebSphere Process Server and WebSphere Enterprise Service Bus deployment patterns, Part 1: Selecting your deployment pattern
WAS ND v6 InfoCenter: Installing IBM HTTP server
Browse the technology bookstore for books on these and other technical topics.
Redbook: WebSphere Application Server Network Deployment V6: High Availability Solutions
Redbook: WebSphere Application Server V6 Scalability and Performance Handbook
WebSphere Business Integration zone
Get products and technologies
Download IBM product evaluation versions and get your hands on application development tools and middleware products from DB2® and WebSphere®.
Check out developerWorks
blogs and get involved in the developerWorks WebSphere forums and community.
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.
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.