Use the deleteSIBEngine command to delete a messaging engine from a service integration bus member.
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. For more information, see the WS-Notification troubleshooting tip Problems can occur when deleting administered subscribers and messaging engines.
If you promote a server bus member to a cluster that is not a member of the bus, do not delete then recreate the messaging engine. Use the migrateServerMEtoCluster command instead.
To run the command, use the AdminTask object of the wsadmin scripting client.
The wsadmin scripting client is run from Qshell. For more information, see Configuring Qshell to run WebSphere® Application Server scripts.
print AdminTask.help('SIBAdminCommands')
print AdminTask.help('command_name')
AdminConfig.save()
This command deletes a messaging engine from a bus member. Any associated configurations of the messaging engine, such as core group policies or destinations, are also deleted. If the messaging engine uses a data store for the message store, objects in the data stores remain so that you can still access them. If you recreate the same messaging engine, you must remove any old data store tables before you start the new messaging engine.
This command also cleans up any mediation execution points that are on the messaging engine as the result of mediating a destination to a WebSphere MQ server bus member. The command unmediates the destination to which the mediation execution point corresponds.
A messaging engine.
None.
Delete the messaging engine from server1 on node1 that is a member of a bus1.
AdminTask.deleteSIBEngine ('[-bus bus1 -node node1 -server server1]')