Adding nodes to a deployment environment definition using the command line

You can add nodes to a deployment environment definition using the wsadmin command.

Before you begin

The task assumes that the node has been federated to the deployment manager.

This command to add a node to the deployment environment definition will fail if the topology is already configured.

You must be on the deployment manager to add nodes.

Required security role for this task: When security and role-based authorization are enabled, you must use a userid and password with administrator or operator authority to perform this task.

About this task

This task adds a federated node to a deployment environment definition and uses the wsadmin command.

Procedure

  1. Open a command window. The wsadmin command can be found in either of the following directories:
    install_root/profiles/dmgr profile/bin
    install_root/bin
  2. At the command prompt, enter the wsadmin command to enter the wsadmin environment.
  3. Enter the addNodeToDeploymentEnvDef command to add the node to the deployment environment definition.
    Note: If administrative security is on, you will be prompted for a user ID and password, if you do not supply it in the command.

Example

This example adds a node (MyNode) to deployment environment definition (myDepEnv) with administrative security enabled:
Attention: If you are adding a node to a single cluster topology pattern, the value for -toplogyRole must be set to ADT. Deployment environment topology patterns are specified when you create the deployment environment using either the createDeploymentEnvDef command or the Deployment Environment Configuration wizard.
Note: If you disable administrative security, you do not need to provide a user ID and password.
Important: If you use additional servers with unique ports, WebSphere® Application Server does not automatically configure the virtual host for the server. Specifically, WebSphere Application Server does not automatically add the host alias ports to a virtual host. However, you can use the administrative console to add a new host alias for each of the ports that are used by the new server. For more information, see the WebSphere Application Server documentation about configuring virtual hosts.