It is important to understand what happens to dependencies and protected services when a WebSphere hierarchy is deleted.
- Dependencies: Before removing a resource hierarchy, you may wish to remove the dependencies. Dependent file systems will be removed. Dependent non-file system resources like IP or Generic Application will not be removed as long as the delete is done via the LifeKeeper GUI or the WebSphere MQ delete script. For LifeKeeper to not delete the dependent file systems of the WebSphere MQ queue manager, manually remove the dependencies prior to deleting the WebSphere MQ hierarchy.
- Protected Services: If the WebSphere resource hierarchy is taken out of service before being deleted, the WebSphere daemons for this queue manager will be stopped. If a hierarchy is deleted while it is in service, the WebSphere MQ daemons will continue running and offering services (without LifeKeeper protection) after the hierarchy is deleted.
To delete a resource hierarchy from all the servers in your LifeKeeper environment, complete the following steps:
- On the Edit menu, select Resource, then Delete Resource Hierarchy.
- Select the Target Server where you will be deleting your WebSphere MQ resource hierarchy and click Next. (This dialog will not appear if you selected the Delete Resource task by right-clicking on a resource instance in either pane.)
- Select the Hierarchy to Delete. (This dialog will not appear if you selected the Delete Resource task by right-clicking on a resource instance in the left or right pane.) Click Next.
- An information box appears confirming your selection of the target server and the hierarchy you have selected to delete. Click Delete.
- Another information box appears confirming that the WebSphere resource was deleted successfully.
- Click Done to exit.
Thanks for your feedback.
Post your comment on this topic.