Removing a member from a bus
We can remove an application server, or a server cluster, from a bus so that it is no longer used to process messages.
- When we remove a member from a bus, all messaging engines on that bus member are also deleted and their associated messages are discarded. If we add the same bus member again, first we must manually delete the old data source for the messaging engines to ensure that once the new messaging engines are created, they can restart.
- If we remove a member from a bus, and it is the only member for that server, we must also disable the SIB Service at server start up.
(ZOS) On z/OS, disabling the SIB Service prevents an adjunct address space from starting when the server starts up.
To remove a member from a bus, use the administrative console to complete the following steps:
Tasks
- In the navigation pane, click Service integration -> Buses. A list of buses is displayed in the content pane.
- In the content pane, select the bus from which we want to remove the member.
- In the content pane, under Topology, click Bus members. A list of members in the bus is displayed.
- Select the bus member to remove.
- Click Remove.
- Save changes to the master configuration.
The member is removed from the bus. All the messaging engines on that bus member and the core group policies associated with those messaging engines are deleted.
What to do next
If we have removed the only bus member for a server, we must now disable the SIB Service at server start up.
Related:
Bus members Disable the service integration service (ZOS) JMS provider settings