Use this page to specify the bridge interfaces that provide
access to the core group access point. A bridge interface is a server
that runs the core group bridge service. The core group bridge service
is the service that establishes communication between core groups.
Best practice:
- A server that you select as a core group bridge interface should
not be a server that handles production responsibilities, such as
filtering requests to cluster members, or WebSphere proxy servers.
Any server that is a core group bridge interface experiences extensive
memory and CPU usage during core group bridge startup, and failover
processing, which occurs when one of the bridges in a core group stops.
If you cannot dedicate a server as a core group bridge interface,
you should select a node agent as your core group bridge interface.
- You should typically specify ONLY two bridge
interfaces per core group. Having at least two bridge interfaces is
necessary for high availability. Having more than two bridge interfaces
adds unnecessary overhead in memory and CPU.
bprac
To access this administrative console page, click access_point_group_nameaccess_point_access_point_nameserver_node.
Select the servers, that are available in the appropriate core
group, that you want to use as the bridge interfaces for your core
group access point.