Use the registerNode command to register a standalone node with an administrative agent so that the administrative agent can manage the node.
Run the registerNode command from the bin directory of the administrative agent server to register a node with the administrative agent. When you run the command, the standalone node is converted into a node that the administrative agent manages. The administrative agent and the node being registered must be on the same system. You can only run the command on an unfederated node. If the command is run on a federated node, the command exits with an error.
When you run the registerNode command, the command stops all running application servers on the node. You can optionally stop application servers on the node that you are registering prior to running the registerNode command.
If you were previously
running on Version 7.0.0.11 or earlier, and have an administrative
agent with a managed node that has mismatched products or versions,
when you apply Version 7.0.0.13 or later to the administrative agent,
that administrative agent will not be able to start the subsystem
for any mismatched nodes. You must update these nodes to have the
same products and versions as the administrative agents, restart
the servers on the node and then restart the administrative agent,
before the administrative agent can resume managing these registered
nodes
If the administrative console or the management Enterprise JavaBeans™ (EJB) applications of the application server being registered are enabled, the node registration process disables them.
The registerNode command syntax is as follows:
registerNode [options]
The following options are available for the registerNode 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.
During node registration, the registerNode command uses an automatically generated set of recommended ports if you do not specify the -portsFile parameter. The recommended port values can be different than the default port values based on the availability of the default ports.
The format of the ports_file file that you specify is the same as the portdef.props file, except that only the following ports are used: SOAP_CONNECTOR_ADDRESS, RMI_CONNECTOR_ADDRESS, JSR160RMI_CONNECTOR_ADDRESS, and IPC_CONNECTOR_ADDRESS.
registerNode.sh -conntype SOAP -port 8878
-profilePath app_server_root/profiles/default
registerNode.sh -conntype SOAP -port 8878
-profilePath app_server_root/profiles/AppSrv01
registerNode.bat -conntype SOAP -port 8878
-profilePath app_server_root\profiles\AppSrv01
registerNode -conntype SOAP -port 8878
-profilePath user_data_root/profiles/AppSrv01