You can reduce the number of messaging engines configured for a
cluster bus member by removing a messaging engine.
Before you begin
Before you remove a messaging engine from a cluster, drain it of
messages and prevent further messages being sent to it. Otherwise, when a
messaging engine is removed, all messages currently stored on that messaging
engine are deleted. Any messages that are in transit to the removed messaging
engine might remain on the sending messaging engine on a remote queue point
and require manual cleanup.
When you remove messaging engines from a cluster, 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. This is to avoid problems if you use WS-Notification, which attaches special significance to the first-created messaging engine in a cluster. For
more information, see the WS-Notification troubleshooting tip Problems can occur when 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 cluster from which you want to remove
a messaging engine. The Bus member detail panel is displayed.
- In the content pane, under Additional properties,
click Messaging engines. A list of messaging
engines for the cluster 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.
You can also use
the deleteSIBEngine command to remove a messaging engine from a cluster.
What to do next
Remember: When you remove a messaging engine,
WebSphere® Application Server (base) does
not delete
the data store tables or the file store files automatically.
- For a data store, if you want to recreate the same messaging engine, you
must first delete the previous set of tables. If you create a messaging engine
and use existing tables, the tables 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 created a data store with default settings, you do not need
to delete previous tables.
- For a file store, you might want to delete the file store files to reclaim
disk space.