Remove a messaging engine from a bus
We can remove a messaging engine from a service integration bus if you no longer require it to send and receive messages on the bus.
You should be wary of deleting and recreating messaging engines on bus members for which WS-Notification administered subscribers have been configured, because in some cases this can leave the remote web service subscription active, and passing notification messages to the local server, even though there is no longer any record of it.
- Stop the messaging engine. We can stop either in Immediate or Force mode, as described in Stopping a messaging engine.
- Use wsadmin deleteSIBEngine to delete the messaging engine. All service integration bus links, MQ links, and custom properties that are owned by the engine are deleted.
When you remove a messaging engine, WAS does not delete the data store tables automatically. We must remove them manually, or delete all the rows in all the tables. If we do not do this, a new messaging engine might fail to start if it attempts to use an orphaned data store. Refer to the documentation for the chosen relational database management system for information about deleting tables.
Alternatively, for Apache Derby, we can delete the database directory, which is located in profile_root/databases/com.ibm.ws.sib, where profile_root is the directory in which profile-specific information is stored. However, do this only if the messaging engine is the sole user of the database.
For more information, see Data store life cycle.
Similarly, the file store files are not automatically deleted when we delete the messaging engine. We might want to delete the file store files to reclaim disk space.
Related concepts
Messaging engines
Related tasks
Emptying the data store for a messaging engine Delete files following removal of a messaging engine
deleteSIBEngine command
Related information:
Messaging engine troubleshooting tips