Moving core group members

 

When moving members to a different core group, remember that: each WebSphere process is a member of exactly one core group, all members of a given cluster must belong to the same core group, and each core group must contain at least one deployment manager or node agent process.

• Review core group concepts.

• Determine which core group members you want to move, and to which core group you want to move them

• Stop affected processes using the following guidelines:

  • Case 1: You are not moving the deployment manager. Stop all of the processes you are moving.

  • Case 2: You are moving the deployment manager. Because the deployment manager has to be moved separately, stop all of the other processes you are moving, but leave the deployment manager running until after you have moved all of these other processes.

    In general, you should not move a deployment manager.

 

Overview

You might need to move one or more core group members:

• To populate a newly created core group.

• To rebalance existing core groups.

To move members between core groups:

 

Procedure

1. In the console, click Servers > Core groups > Core group settings > core_group_name > Core group servers.

2. Select the core group containing the processes to move to another core group.

3. In the Select column, select the servers to move. If you are populating a new core group, at least one node agent or deployment manager must be moved to the new core group.

4. Click Move. The Core groups > DefaultCoreGroup > Core group servers > Move console panel is displayed showing the servers you want to move and the core group to which these servers currently belong.

5. Indicate in the To core group field the core group to which you want these servers moved.

6. Click Apply and then Save.

7. Click System administration > Nodes, and then click Synchronize to synchronize your changes on all running nodes.

8. Manually synchronize all stopped nodes by running the syncNode command from the profile_root/node_agent_profile/bin directory.

9. If the deployment manager is moved, restart the deployment manager process.

10. Restart all of the other moved processes.

 

Results

After the servers complete their restart, all moved servers should belong to their new core group.

 

What to do next

• You can verify that the servers are in the correct core groups. For each core group, in the console, click Servers > Core groups > Core group settings > core_group_name > Core group servers and look at the list of core group servers that displays.

• You can set up core group bridges if any of the core groups need to communicate with each other. See Core group communications using the core group bridge service for more information.

---

Core group server move options

 

Related concepts

Core groups (high availability domains)

 

Related tasks

Setting up a high availability environment