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.