Use this task to avoid problems that can occur when a messaging engine that
is configured to use DB2 v8.2 with HADR for its data store terminates
if the DB2 database fails over.
Why and when to perform this task
If you configure a
messaging engine to
use DB2 v8.2 with HADR for its
data store and
a DB2 failover occurs, the application server on which the
messaging engine is
running might stop. The cause of this problem is that the messaging
engine does not treat the DB2 failover as a transient communications error.
When
you configure a messaging engine to
use DB2 v8.2 with HADR for its data store ensure
that the messaging engine can restart
automatically following an application server failure. Choose the option that
is appropriate for your configuration:
- If you are running a single server, WebSphere Application Server provides
no failover support. Consider other high availability provisions.
- If you are running the Network Deployment version without clustering,
the default configuration for the node agent ensures automatic restart.
- If you are running the Network Deployment version with clustering,
peer recovery restarts the messaging engine. Ensure that you have configured
the high availability policy to enable peer recovery.