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

Removing a messaging engine from a bus

Removing a messaging engine from a from a bus means that the messaging engine can no longer be used for communicating with that bus.

Why and when to perform this task

To remove a messaging engine from a bus, complete the following steps:

Steps for this task

  1. Stop the messaging engine. You can stop either in Immediate or Force mode as described in Stopping a messaging engine.
  2. Use the deleteSIBEngine command to delete the messaging engine. All service integration bus links, MQ links, and custom properties owned by the engine are deleted.
    Note: When you remove a messaging engine, WebSphere Application Server does not delete the data store tables automatically. You must remove them manually or delete all of the rows in all of the tables. Failure to do so can result in a new messaging engine failing to start if it attempts to use an orphaned data store. Refer to the documentation for your chosen relational database management system for information about deleting tables.

    For Cloudscape, you can alternatively delete the database's 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, only select this option if the messaging engine is the sole user of the database.

    For more information , see Data store life cycle.

Related concepts
Messaging engines
Related tasks
Emptying the data store for a messaging engine

Task topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjj0053_.html

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