Removing a messaging engine using the wsadmin tool

Use this command to remove a messaging engine from a bus member.

You should be wary of deleting and re-creating 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 Deleting administered subscribers and messaging engines.

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 the topic "Configure Qshell to run WebSphere® Application Server scripts".

This command is only valid when used with WebSphere Application Server Version 6 and later application servers. Do not use it with earlier versions.

Command-line help is provided for service integration bus commands:

After using the command, save your changes to the master configuration; for example, by using the following command:
 $AdminConfig save

Purpose

This command deletes a messaging engine from a bus member. The command also cleans up any mediation execution points that reside 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.

Command name
deleteSIBEngine
Target
None.
Result
The messaging engine is deleted.

Required parameters

-bus busname
The name of the service integration bus on which the bus member is configured. You can use the listSIBuses command to list the names of existing buses.

Conditional parameters

-node nodename -server servername
To delete a messaging engine from an application server as a bus member, specify both the name of the node on which the server runs and the name of the server.
-cluster cluster
To delete a messaging engine from a server cluster as a bus member, specify the name of the cluster.

This option should be used only in WebSphere Application Server environments that support server clusters.

-engine enginename
If the bus member has only one messaging engine, you do not need to specify the engine name. If the bus member has several messaging engines, you must specify the name of the engine that you want to delete.

Optional parameters

None.

Example

app_server_root/bin>wsadmin -conntype SOAP -port 8879
WASX7209I: Connected to process "dmgr" on node 9994GKCCellManager01 using SOAP
 connector;  The type of process is: DeploymentManager
WASX7029I: For help, enter: "$Help help"
wsadmin>$AdminTask listSIBEngines {-bus abus -cluster cluster1}
cluster1.000-abus(cells/9994GKCCell01/clusters/cluster1|sib-engines.xml#SIBMessagingEngine_1098181503570)
cluster1.001-abus(cells/9994GKCCell01/clusters/cluster1|sib-engines.xml#SIBMessagingEngine_1098189151487)
wsadmin>$AdminTask deleteSIBEngine {-bus abus -cluster cluster1 -engine cluster1.001-abus}
wsadmin>$AdminTask listSIBEngines {-bus abus -cluster cluster1}
cluster1.000-abus(cells/9994GKCCell01/clusters/cluster1|sib-engines.xml#SIBMessagingEngine_1098181503570)



Related tasks
Unmediating a destination
Related reference
Messaging engine administrative commands
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 8:21:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-express-iseries&topic=rjk_cli_me_delete
File name: rjk_cli_me_delete.html