Moving core group members

When moving members to a different core group, remember that: each process can be a member of only one core group, all members of a given cluster must belong to the same core group, each core group must contain at least one deployment manager or node agent process, and the high availability manager must be enabled on the deployment manager or at least one node agent in every core group. The high availability manager can be enabled on the deployment manager, and on multiple node agents in the same core group.

Before you begin

About this task

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

Depending on the whether you are moving an application server, a deployment manager, or a node agent, perform one of the following steps.

Procedure

  1. Move one or more application servers to another core group.
    1. Stop the application servers that you want to move.
    2. In the administrative console, click Servers > Core groups > Core group settings to display a list of the core groups in the topology.
    3. Click the name of the core group that contains the application servers that you want to move.
    4. On the configuration page for this core group, under Additional Properties, click Core group servers to display the list of members of this core group. This list includes all of the application servers, node agents, and deployment managers that are members of this core group.
    5. In the Select column, select the application servers that you want to move to a new core group.

      You can only designate one target core group to which to move the selected application servers. If you need to move some of the application servers on this list to two or more other core groups, you have to repeat this step and the following step for each core group.

    6. Click Move. The Core groups > core_group_name > Core group servers > Move administrative console page is displayed. This page lists the application servers that you selected to move and the core group to which they currently belong.
    7. Select the core group to which you want these application servers moved. The pull-down, under To core group, lists the core groups that are available on your system.
    8. Click Apply, and then click Save.
    9. Click System administration > Nodes, select all running nodes, and then click Synchronize to synchronize your configuration changes to all of the running nodes.
    10. Restart the application servers that you moved.
  2. Move one or more node agents to another core group.
    1. Stop the node agents that you want to move.
    2. In the administrative console, click Servers > Core groups > Core group settings to display a list of the core groups in the topology.
    3. Click the name of the core group that contains the node agents that you want to move.
    4. On the configuration page for this core group, under Additional Properties, click Core group servers to display the list of members of this core group. This list includes all of the application servers, node agents, and deployment managers that are members of this core group.
    5. In the Select column, select the node agents that you want to move to a new core group.

      You can only designate one target core group to which to move the selected node agents. If you need to move some of the node agents on this list to two or more other core groups, you have to repeat this step and the following step for each core group.

    6. Click Move. The Core groups > core_group_name > Core group servers > Move administrative console page is displayed. This page lists the node agents that you selected to move and the core group to which they currently belong.
    7. Select the core group to which you want these node agents moved. The pull-down, under To core group, lists the core groups that are available on your system.
    8. Click Apply, and then click Save.
    9. Issue the syncNode command from the profile_root/node_agent_profile/bin directory to manually synchronize the updated configuration to the node.
      Important: This synchronization must be performed before you restart the moved node agent.
    10. Restart the node agent that you moved.
  3. Move a deployment manager to another core group.
    1. Stop all members of the core group that contains the deployment manager, including the deployment manager.
    2. Issue the wsadmin –conntype NONE –lang jython command from the profile_root/deployment_manager_profile/bin directory to start a local mode scripting session under the deployment manager profile.
    3. In the local mode scripting session, move the deployment manager using the following command.
      AdminTask.moveServerToCoreGroup("-source <source_Core_Group> - target <target_Core_Group> -nodeName <node_name> -serverName <server_name>")
    4. Issue the AdminConfig.save() command to save the configuration changes.
    5. Restart the deployment managers that you moved.
    6. Restart the other core group members that you had to stop before moving the deployment manager.
    7. Click System administration > Nodes, select all running nodes, and then click Synchronize to synchronize your configuration changes to all of the running nodes.

Results

After all of the restarts complete, all moved application servers, node agents, and deployment managers belong to their new core groups.

What to do next




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 7:21:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=trun_ha_addcgmems
File name: trun_ha_addcgmems.html