WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Removing a messaging engine through the command line

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

Before you begin

The command described in this topic is run using the AdminTask object of the wsadmin scripting client.

This command is only valid when run against WebSphere Application Server Version 6 application servers. Do not run it against earlier versions.

Command-line help is provided with each of the service integration technologies commands:
  • For a list of all the available service integration bus commands, plus a brief description of each command, type the following command:
    wsadmin> $AdminTask help SIBAdminCommands
  • For detailed help on a given command, enter the following command:
    wsadmin> $AdminTask help command_name

For additional details of the command properties, see the related reference topic.

Purpose

This command deletes a messaging engine from a bus member.

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

To save the changes made by the command, invoke the "save" command on the AdminConfig object.

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

install_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)

Reference topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\ref\rjk_cli_me_delete.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)