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 at the deployment manager to which you are adding 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
- Open a command window.
The wsadmin command can be found at either the <ESB>/profiles/<dmgr
profile>/bin directory, or the <ESB>/bin directory.
- At the command prompt, enter the wsadmin command
to enter the wsadmin environment.
- 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.
wsadmin -connType SOAP -host myDmgr -port 8879 -user dmgrAdmin -password dmgrPass
> $AdminTask addNodeToDeploymentEnvDef { -topologyName myDepEnv -nodeRuntime WESB
-topologyRole Messaging -nodeName MyNode -serverCount 3}
Note: If
you disable administrative security, you do not need to provide a
user ID and password.