Use the administrative console to add, remove, and
list the members of a bus.
Subtopics:
Adding a server as a new bus member
The members of a service integration bus are the application
servers and clusters within which messaging engines for that bus can
run. When you add a new bus member, you configure its message store,
which is either a file store or a data store.
Adding a cluster as a member of a bus
You can add a server cluster as a member of a service integration
bus so that it can use the bus to communicate. When a cluster is added
to the bus, all servers in the cluster are added to it, and at least
one messaging engine is created. The members of a service integration
bus are the application servers and clusters within which messaging
engines for that bus can run.
Modifying the messaging engine policy for a cluster bus member
You can change the messaging engine policy for a cluster bus member
that is already configured, and change the number of messaging engines and
their behavior so that they conform with the new messaging engine policy.
Adding a WebSphere MQ server as a member of a bus A WebSphere® MQ server represents a WebSphere MQ queue manager or (for WebSphere MQ for z/OS®) queue-sharing group.A WebSphere MQ server bus member is used as a bus member for assigning queue points and mediation points to WebSphere MQ queues.
Listing the members of a bus
You can display a list of servers, server clusters,
and WebSphere MQ
servers that have been added as members of a bus.
Removing a member from a bus
You can remove an application server, or a
server cluster, from a bus so that it is no longer used to process messages.
Disabling the service integration service
The SIB Service, which provides messaging capability, is
enabled automatically when you add a server to a service integration
bus. If required, you can disable service integration bus functions
when the application server starts.
Subtopics:
Adding a server as a new bus member
The members of a service integration bus are the application
servers and clusters within which messaging engines for that bus can
run. When you add a new bus member, you configure its message store,
which is either a file store or a data store.
Adding a cluster as a member of a bus
You can add a server cluster as a member of a service integration
bus so that it can use the bus to communicate. When a cluster is added
to the bus, all servers in the cluster are added to it, and at least
one messaging engine is created. The members of a service integration
bus are the application servers and clusters within which messaging
engines for that bus can run.
Modifying the messaging engine policy for a cluster bus member
You can change the messaging engine policy for a cluster bus member
that is already configured, and change the number of messaging engines and
their behavior so that they conform with the new messaging engine policy.
Adding a WebSphere MQ server as a member of a bus A WebSphere® MQ server represents a WebSphere MQ queue manager or (for WebSphere MQ for z/OS®) queue-sharing group.A WebSphere MQ server bus member is used as a bus member for assigning queue points and mediation points to WebSphere MQ queues.
Listing the members of a bus
You can display a list of servers, server clusters,
and WebSphere MQ
servers that have been added as members of a bus.
Removing a member from a bus
You can remove an application server, or a
server cluster, from a bus so that it is no longer used to process messages.
Disabling the service integration service
The SIB Service, which provides messaging capability, is
enabled automatically when you add a server to a service integration
bus. If required, you can disable service integration bus functions
when the application server starts.