IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced for z/OS: Process Server > Configure IBM BPM Advanced for z/OS: Process Server > Completing the ND configuration > Create the deployment environment > Configure servers, server clusters, and product components > Set up deployment environments > Create deployment environments > Create deployment environments using the command line

Adding nodes to a deployment environment definition using the command line

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

The task assumes that the node has been federated to the dmgr.

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

You must be on the dmgr to add nodes.

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

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

Procedure

1. Open a command window. The wsadmin.sh 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 wsadmin.sh to enter the wsadmin.sh environment.

3. Enter the addNodeToDeploymentEnvDef command to add the node to the deployment environment definition.

   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.sh -connType SOAP -host myDmgr -port 8879 -user dmgrAdmin -password dmgrPass
> $AdminTask addNodeToDeploymentEnvDef {-topologyName myDepEnv 
-topologyRole Messaging -nodeName MyNode}

If you disable administrative security, you do not need to provide a user ID and password.

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 used by the new server.

Create deployment environments using the command line