You can unregister application server nodes so that they are no longer registered to an administrative agent. Unregister nodes if you no longer need the node in the administrative agent environment or if you intend to delete the application server node profile. After you unregister a node from an administrative agent, you can use the node stand-alone, register the node with another administrative agent, or delete the application server node profile.
The application server node that you want to remove from the administration agent environment must be registered with the administrative agent. Start the administrative agent if it is not running already.
For Port, if security is not enabled, specify 9960 for an unsecure job manager administrative console port. If no port number is specified, the default secure port number 9943 is used.
When you run the unregisterWithJobManager command, specify the name of the stand-alone application server node that is managed by the job manager for the required -managedNodeName parameter. Other parameters are optional.
AdminTask.unregisterWithJobManager('[-host myJobMgrHostname -port 8989 -managedNodeName myAppServerNodeName]')
The default value for the -host parameter is localhost.
The default value for the -port parameter is 9943, the job manager administrative console secure port number. If security is disabled, specify 9960, the default unsecure port number.
For more information about the unregisterWithJobManager command and parameters, see the topic on the ManagedNodeAgent command group for the AdminTask object.
If the system fails when unregistering a stand-alone application server from a job manager, run the cleanupManagedNode command in the JobManagerNode group to clean up job manager registration information. See the topic on the JobManagerNode command group for the AdminTask object.
To unregister a node, run the deregisterNode command from the bin directory of the administrative agent. Step 1 describes how to run the deregisterNode command.
When you unregister a node, the node configuration is retained, but is marked as not registered with the administrative agent. If the node that you unregister had the administrative console or management Enterprise JavaBeans (EJB) applications installed before registering the node, they are re-enabled.
Running the deregisterNode command might result in a null pointer exception if the application server node profile is corrupted or unusable. If you receive the null pointer exception, the process to unregister the application server from the administrative agent failed. You receive ADMU0116I, ADMU0128I, ADMU0211I, ADMU0113E, and ADMU1211I messages in the error log. Step 2 describes how to remove a node and related end points if there is a null pointer exception.
If the application server node profile is deleted before the node is unregistered, running the deregisterNode command is ineffective. Because the profile no longer exists, the administrative agent does not recognize the profile. Complete Step 2 to remove the node and related end points from the administrative agent environment.
The application server node is no longer registered with the administrative agent.
You can use the unregistered node stand-alone or register the node with another administrative agent. Optionally, use the manageprofiles command to delete the application server profile.
In this information ...Related concepts
Related tasks
| IBM Redbooks, demos, education, and more(Index) |