WebSphere Application Server Version 6.1.x Feature Pack for Web Services
Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS
Learning about high availability and workload sharing
Use these topics to learn about high availability and workload
sharing.
Subtopics
WebSphere Application Server high availability
The WebSphere Application Server high availability framework
eliminates single points of failure and provides peer to peer failover for
applications and processes running within WebSphere. The WebSphere Application
Server high availability framework also allows
integration of WebSphere Application Server into an environment that may be
using other high availability frameworks,
such as HACMP, to manage non WebSphere resources.
Workload sharing
You can share workload between multiple messaging engines in
the service integration environment.
Service integration error types
There are four types of error that can occur in service integration:
errors that a messaging engine can
recover from while it is running, errors that can be resolved by an automatic
restart of the messaging engine,
errors that require the user's intervention and errors that are not detectable
in the messaging engine.
External high availability frameworks and service integration
You can configure an external high availability framework,
such as IBM HACMP, to manage a messaging engine as
if it were a resource in the external high availability framework's
resource group.
High availability of messaging engines that are connected to WebSphere MQ
You can connect a messaging engine to
a WebSphere MQ queue manager so that, to WebSphere MQ, the messaging engine appears
to be another queue manager. If you connect a messaging engine in
this way, there are some high availability considerations that you need to
take into account.