You can remove nodes from a deployment
environment definition
using the wsadmin command.
Before you begin
This command to remove a node from the deployment
environment
will fail if the topology is already configured.
The admin client
must connect to the deployment manager from which you are removing
the node.
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 uses the wsadmin command
to remove a node
from a deployment environment definition.
You might want to use
the command line to remove a federated node from a deployment environment
when you are making a large number of changes to a deployment environment.
There is less overhead using the
wsadmin command than there would
be using the administrative console.
Procedure
- Open a command window.
The wsadmin command can be found at
either the <WPS>/profiles/<dmgr profile>/bin directory,
or the <WPS>/bin directory.
- At the command prompt, enter the wsadmin command
to enter the command environment.
Note: Make sure wsadmin connects
to the correct deployment manager, when running in connected
mode.
- Use the removeNodeFromDeploymentEnvDef command
to remove the node from 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 removes a node (
MyNode)
from a Messaging
cluster (
Messaging) for the deployment environment definition
(
myDepEnv) with administrative security enabled.
Note: If you
are running the admin client from the deployment manager bin folder,
you do not need to include the -host and -port parameters
in the command.
wsadmin -connType SOAP -host myDmgr -port 8879 -user dmgrAdmin -password -dmgrPass
> $AdminTask removeNodeFromDeploymentEnvDef -topologyName myDepEnv
-topologyRole Messaging -nodeName MyNode
The
-conntype parameter
specifies the type of connection to
be used; the default argument is
SOAP.
Note: As the
default is SOAP, you do not need to give explicitly
if SOAP is the connection type that is being used.
The
-host parameter
specifies the host used for the SOAP or
RMI connection. The default value for
-host is the
local host.
Note: If the node is running on the local host, you don
not need to specify -host
Note: If you
do not specify a value for topologyRole, the node
is removed from every role (cluster) in the environment definition.
Note: If
you disable administrative security, you do not need to
provide a user ID and password.
To save this change to the
master configuration issue the command: $AdminConfig Save