Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

developerWorks Community:

  • Close [x]

Setup and considerations for double Remote Messaging and Remote Support topology usage

Andre Weiser (aweiser@de.ibm.com), Software Developer, IBM
Photo of Andre Weiser
Andre Weiser is a Software Developer and a member of the WebSphere Process Server SWAT team. He works in the Business Process Choreographer development team at the IBM Germany Development Lab, Boeblingen, Germany.
James Mallinson (jamesmal@us.ibm.com ), Software Developer, IBM
Photo of James Mallinson
James Mallinson is a Software Developer and a member of the WebSphere Process Server test team.
Vishnu Selvaraj (vishnu.selvaraj@us.ibm.com), Software Developer, IBM
Photo of Vishnu Selvaraj
Vishnu Selvaraj is a Software Developer and a member of the WebSphere Process Server SWAT team. He works at the IBM Bay Area Lab in Foster City, California.

Summary:  More and more users are moving to a double Remote Messaging and Remote Support topology, where there are two independent application deployment target clusters in WebSphere® Process Server. This tutorial describes how to move from a normal Remote Messaging and Remote Support topology (gold topology) to a double Remote Messaging and Remote Support topology. The tutorial helps you decide if a double Remote Messaging and Remote Support topology is the right way to go and explains the differences and implications compared to a normal Remote Messaging and Remote Support topology.

Date:  10 Jun 2009
Level:  Intermediate PDF:  A4 and Letter (2132 KB | 54 pages)Get Adobe® Reader®

Activity:  14470 views
Comments:  

Before you start

Clustering is a key technique that you can use to improve the availability and the scalability of a WebSphere® Process Server environment. With WebSphere Process Server (hereafter called Process Server), you can use clustering techniques in many different ways to address availability and scalability. Each pattern centers around the number of Process Server clusters and cluster members. The most used environment is the Remote Messaging and Remote Support topology. This topology provides three separate clusters: a remote messaging cluster, a support infrastructure cluster, and an application deployment target cluster. With this three-cluster pattern, resources are allocated to the cluster that handles the highest loads. This pattern is the most flexible and versatile, and is preferred by most users. The components are divided between the three clusters.

Objectives

  • Learn how to setup and configure a double remote messaging and remote support topology.
  • Understand the constraints and implications of a double Remote Messaging and Remote Support topology.

Prerequisites

You should be familiar with the WebSphere Process Server topologies and cluster setups.


System requirements

You need the following software:

  • WebSphere Process Server v6.1.2 or above with all current iFixes installed
  • A running WebSphere Process Server cell of the Remote Messaging and Remote Support topology
  • WebSphere Application Server v6.1.0.17
  • DB2® v8.1

Duration

2 hours

Note: The figures used in this tutorial are taken from a WebSphere Process Server v6.1.2 environment. However, the guidelines in this tutorial are also applicable for version 6.2 of WebSphere Process Server.

1 of 11 | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=395414
TutorialTitle=Setup and considerations for double Remote Messaging and Remote Support topology usage
publish-date=06102009
author1-email=aweiser@de.ibm.com
author1-email-cc=dwu@us.ibm.com
author2-email=jamesmal@us.ibm.com
author2-email-cc=dwu@us.ibm.com
author3-email=vishnu.selvaraj@us.ibm.com
author3-email-cc=dwu@us.ibm.com