Recovering or moving nodes with the addNode -asExistingNode command

Use the -asExistingNode option of the addNode command to recover and move nodes of a deployment manager. Using the -asExistingNode option, federate a new custom node to a deployment manager as an existing node. During federation, the product uses information in the deployment manager master configuration to transform the custom node into the existing node.

This topic assumes that a WAS Network Deployment product has a deployment manager with one or more managed nodes.

Use the -asExistingNode option of the addNode command to quickly recover a damaged node, to move a node to a product installation on a different computer but at the same path, to move a node to a product installation on a different operating system or with a different path, or to create cells from a template cell.

The following procedures describe how to use the -asExistingNode option:

Avoid trouble: Other addNode options for node configuration are incompatible with this -asExistingNode option. Do not use -asExistingNode with the following incompatible options:

gotcha

When the addNode command is run with the -asExistingNode option, the product does not check for or resolve conflicts among ports. We must verify that the ports associated with a node do not conflict with ports that are already in use on the target host.


What to do next

Examine the nodes in the target installation to ensure that the node configuration operates properly. If necessary, delete profiles of the source installation.


Related concepts

  • Managed and unmanaged nodes


    Related tasks

  • Adding, managing, and removing nodes
  • Get started with wsadmin scripting
  • Create a new SSL certificate to replace an existing one in a node
  • Create new SSL certificates to replace existing ones in a cell

  • addNode command
  • Recover managed node settings
  • Node collection
  • Add managed node settings