WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Managing nodes

In WebSphere Extended Deployment, the default node that is created during installation is based on the host name. When you create a node, the name can be the IP host address of that computer. The relationship between applications and the nodes on which they can run is expressed in terms of an intermediate construct called a node group. A node can only be a member of a single node group at any time.

Before you begin

WebSphere Extended Deployment must be installed and you need access to the administrative console.
Depending on your administrative role, you are allowed specific privileges when managing nodes. The following list shows the administrative roles and privileges for managing nodes:
Monitor
Can view the information.
Operator
Can set and unset maintenance nodes.
Can synchronize nodes.
Can stop nodes.
Configurator
Can view the configuration.
Can add and remove nodes.
Administrator
Has all privileges.

Procedure

  1. From the administrative console, click System Administration > Nodes. Select an existing node for editing.
  2. Click Add Node to add a node to a cell.
    1. Type the network name of the node to add to the cell. A WebSphere Application Server instance must be running on this machine.
    2. Complete the required fields and click Save.
  3. To edit the node, you can select from the following:
    • Remove node: Select a node to remove and click Remove node. You cannot remove a node from a node group if it has a running instance of a dynamic cluster. Stop the instances of the dynamic cluster first.
    • Force delete: Select a node to delete and click Force delete.
    • Synchronize: Verifies that all the nodes in a cell are in synchronization and that the same configuration and settings for servers, node groups, dynamic clusters, and so forth are the same. When you make a change through the administrative console, the change is saved only to the deployment manager unless you select the box to synchronize to all the nodes.
    • Full synchronize: Recompares the node and deployment manager configurations, instead of a comparison of just the configuration folders the system knows about. Synchronization operations only know about configuration changes that occur through the administrative tools, like the administrative console or the wsadmin scripting utility. If you directly edit or add new files into the configuration tree, use console operation to make these changes known to the system.
    • Stop: Stops a node. You cannot restart the node from the administrative console. Instead, use the reStart command on the node.
    • Set maintenance, immediate stop: Takes a node offline, while stopping all the node processes, for maintaining, troubleshooting, or setting up a backup node.
    • Set maintenance: Takes a node offline, without stopping all the node processes, for maintaining, troubleshooting, or setting up a backup node.
    • Unset maintenance: Select this operation to bring a node online. If the node agent is stopped, manually restart the node agent.

Results

You have a configured node.



Related tasks
Configuring health management
Preparing the hosting environment for dynamic operations
Related reference
Administrative roles and privileges
Task topic    

Terms of Use | Feedback

Last updated: Oct 16, 2009 11:06:12 AM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/odoe_task/todrcreatenode.html