Set up a high availability environment

 

+

Search Tips   |   Advanced Search

 

Overview

The appserver infrastructure that is managed by a high availability manager includes cells and clusters. These components relate closely to core groups, high availability groups, and the policy that controls the high availability infrastructure.

The high availability manager is designed to function in all of the supported WAS topologies. However, a high availability-managed environment must comply to the following rules:

• A cell in a high availability infrastructure is partitioned into one or more core groups. WAS provides a default core group as part of the high availability manager function. Additional core groups can be created using the console.

• A core group cannot extend beyond the boundaries of a cell, and it cannot overlap with any other core groups.

• A cluster must be a member of only one core group. All of the individual members of that cluster must be members of the same core group.

• Individual appservers are also members of a core group.

• All running members of a core group must be able to communicate with all of the other running members of that same core group.

While administering your core groups, you might need to perform one or more of the following tasks. These tasks can be performed in any order.

 

Procedure

1. Set up preferred coordinators
2. Change the number of core group coordinators.
3. Configure a core group transport.
4. Configure the discovery protocol for a core group.
5. Configure the failure detection protocol for a core group.
6. Configure a core group for replication
7. Configure core group IP caching.
8. Set up IP addresses for high availability manager communications for V6.0.2 and higher.
9. Configure core group socket buffers.
10. Specify a core group when adding a node
11. Specify a core group when creating an appserver
12. View the core groups in a cell
13. View core group members
14. Create a new core group (high availability domain)
15. Move core group members
16. Disable or enabling a high availability manager
17. View high availability group information
18. Create a policy for a high availability group
19. Select the policy for a high availability group
20. Specify a preferred server for messaging requests
21. Configure the core group bridge service
22. High availability environment troubleshooting tips

 

What to do next

After you set up your WAS environment to comply with all of the high availability-managed environment rules, use the default core group to control this environment. DO NOT add additional core groups unless your environment absolutely requires them. Also, do not change the default configurations unless you are doing so to solve a specific problem or situation. When you do make configuration changes, such as changing the policy for a high availability group or moving core group members between core groups in a multi-core group environment, make sure you fully understand the effect such changes will have on your entire environment.

Troubleshoot high availability environment problems.

---