You can reduce the number of messaging engines configured for a cluster bus member by removing a messaging engine.
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.
You can also use the deleteSIBEngine command to remove a messaging engine from a cluster.
In this information ...Related concepts
Related tasks
Related reference
Related information
| IBM Redbooks, demos, education, and more(Index) |