WAS v8.5 > WebSphere applications > Service integration > Service integration configurationsBootstrap members
An application inside a client container or application server outside the cell, cannot connect directly a bus inside the cell. This is because the client container or application server outside the cell, does not have access to cell configuration information. Therefore, to connect to a bus, the application must bootstrap to an application server inside the cell. That application server identifies a server inside the cell that is a bus member. Then, the client or application server outside the cell, will be able to connect to the bus inside the cell. A bootstrap member is an application server that is configured to accept requests to bootstrap into the service integration bus. The bootstrap member authenticates a connection request, and directs the request to a suitable bus member. The administrator configures the bootstrap member policy for the bus to determine which types of server can service requests to bootstrap.
The following bootstrap member policies are available:
- All members of the cell with the SIB Service enabled
- This the default policy. Any server in the cell that has the SIB service enabled can service bootstrap requests.
- Bus members and nominated bootstrap members
- Only bus members or nominated bootstrap members can service bootstrap requests.
- Bus members only
- Only bus members can service bootstrap requests.
Unlike a bus member, a bootstrap member does not host a messaging engine and therefore does not provide messaging services. However, an application server can be both a bootstrap member and a bus member.
The administrator can use the dmgr console to list bootstrap members. This information is helpful in managing bus topologies, developing applications, and diagnosing problems.
If a server is a member of one bus only, the administrator can choose the bootstrap member policy Bus members and nominated bootstrap members to prevent the members of one bus from bootstrapping into another bus.
If a bus topology uses multiple security domains, we can isolate buses and the applications that use them by configuring the bootstrap members so that only a subset of servers can access a bus.
Related concepts:
Messaging security and multiple security domains
Bus configurations
Related
Configure a bootstrap member policy for a bus
Administer bootstrap members for a bus
Nominating bootstrap members for a bus
Delete nominated bootstrap members from a bus
List the bootstrap members for a bus
Reference:
addSIBBootstrapMember command
removeSIBBootstrapMember command
listSIBNominatedBootstrapMembers command
listAllSIBBootstrapMembers command