Chapter 4. Runtime environment 83
Figure 4-19 Staff Plugin Provider scope at the node level
4.5 Configuring for high availability
A high availability configuration builds on the scalable topologies discussed in
the previous section, adding protection from outages. In some cases, this could
be as simple as adding a number of nodes to the WebSphere Business
Integration Server Foundation cluster to allow the application to continue
executing if one of the nodes fails.
It is also important to consider the supporting components such as the JMS
provider, database server and LDAP server. These will need to be protected from
availability. If WebSphere MQ is the JMS provider, it will probably require a
clustered environment using persistent queues, with some form of takeover of
transitional data. An RDBMS is likely to be either hot standby or a parallel server
environment. LDAP will also need to be configured in a highly available mode.
Important: While configuring the Staff plug-in at the node level, make sure to
use the appropriate J2C authentication aliases that are specific to the node
the Staff plug-in is being configured for.
84 WebSphere Business Integrator Server Foundation V5.1 Handbook
A possible high availability topology is shown in Figure 4-20.
Figure 4-20 High availability environment
Some of the features of this environment are listed below:
򐂰 High availability for the WebSphere Business Integration Server Foundation
is provided by the WebSphere Application Server cluster mechanism. This,
however, depends on the other components in the infrastructure.
򐂰 The WebSphere Application Server Network Deployment server has a hot
standby, since there can be only one active Network Deployment server in the
environment.
򐂰 The WebSphere MQ JMS provider is configured in a clustered environment.
򐂰 The Data stores, DB2 Enterprise Server Edition and Tivoli Directory Server
have a redundant node topology, configured with data replication so that
operation can transfer to the hot standby in the event of an outage.
DB2
Database
F
i
r
e
w
a
l
l
Tivoli
Directory
Server
WebSphere
MQ Server
IBM HTTP
Server
DB2
Client
MQ
Client
WBISF Node 1
WBISF Node 2
Node Agent
App Server
WBI SF v5.1
DB2
Client
MQ
Client
Node Agent
App Server
WBI SF v5.1
WAS
Plugin
IBM HTTP
Server
WAS
Plugin
WAS
v5.1 ND
WebSphere
MQ Server
DB2
Database
Tivoli
Directory
Server
MQ Cluster
DB2 HACMP
OS or Hardware Cluster: Hot Standby
OS or Hardware Cluster: Hot Standby
Edge
Server
Edge
Server
Edge Cluster
WAS Cluster
DB2
Client
MQ
Client
WAS
v5.1 ND
DB2
Client
MQ
Client
Internet

Get WebSphere Business Integration Server Foundation V5.1 Handbook now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.