Use the deregisterNode command to unregister a node from an administrative agent so that you can use the node standalone, register the node with another administrative agent, or federate the node with the deployment manager.
Run the deregisterNode command from the bin directory of the administrative agent. The node must have been previously registered with the administrative agent. When you unregister a node, the node configuration is retained, but is marked as not registered with the administrative agent.
When you run the deregisterNode command, the command stops all running application servers on the node. You can optionally stop application servers on the node that you are unregistering prior to running the deregisterNode command.
If the node that you unregister had the administrative console or management Enterprise JavaBeans™ (EJB) applications installed prior to registering the node, they are re-enabled.
The deregisterNode command syntax is as follows:
deregisterNode [options]
The following options are available for the deregisterNode command:
The default port number is 8878 for the default SOAP port of the administrative agent. SOAP is the default Java™ Management Extensions (JMX) connector type for the command. If you have multiple product installations or multiple profiles, the SOAP port might be different than 8878. Examine the administrative agent SystemOut.log file to see the current ports in use.
deregisterNode.sh -conntype SOAP -port 8878
-profilePath app_server_root/profiles/AppSrv01
deregisterNode.bat -conntype SOAP -port 8878
-profilePath app_server_root\profiles\AppSrv01
deregisterNode -conntype SOAP -port 8878
-profilePath user_data_root/profiles/AppSrv01