You can remove a messaging engine from a cluster so servers
that are members of the cluster cannot send and receive messages.
Before you begin
When you remove messaging engines from a cluster you should remove them in numerical order from highest to lowest, so as to avoid a situation where (for example) there are messaging engines numbered 001 and 002 and not 000. The reason for this is to provide additional surety when using WS-Notification, because WS-Notification attaches special significance to the "first" messaging engine in the cluster. For
more information, see the WS-Notification troubleshooting tip Deleting administered subscribers and messaging engines.
When
you remove a messaging engine from a cluster, all message points and
their messages are deleted, so if the cluster has a queue destination
configured, some of the messages stored for that queue might be lost.
About this task
To remove a messaging engine from a cluster:
Procedure
- In the navigation pane, click .
- In the content pane, click the name of the bus.
- In the content pane, under Additional properties,
click Bus members. A list
of members in the bus is displayed.
- In the content pane, select the cluster from which you
want to remove a messaging engine. A list of messaging
engines for the server is displayed.
- In the content pane, select the messaging engine that you
want to remove.
- Click Remove messaging engine.
- Save your changes to the master configuration.
Results
The messaging engine is removed from the cluster.
Remember: When you remove a messaging engine, WebSphere® Application Server does not delete
the data store tables automatically. If you want to recreate the same
messaging engine, you must first delete the previous set of tables.
But if you create a messaging engine with existing tables, they must
be empty, so that the messaging engine can function correctly. Refer
to the documentation for your chosen relational database management
system (RDBMS) for information about how to delete tables. However,
if you have created a data store with default settings, you do not
need to delete previous tables.
What to do next
You can also use the deleteSIBEngine command to remove
a messaging engine from a cluster.