Add managed nodes

Add managed nodes

A managed node is a node with an appserver and a node agent that belongs to a dmgr cell. To add an appserver node to a dmgr cell.
To view this dmgr admin console page, click System Administration > Nodes > Add node > Next .

Node connection

Specifies connection information for WAS.

Host
Specifies the host name or IP address of the node to add to the cell. A WAS instance must be running on this machine.

Data type String
Default None

JMX connector type
Java™ Management Extensions (JMX) connectors that communicate with the WAS when you invoke a scripting process.
Select from one of these JMX connector types:

SOAP
Use when the appserver connects to a SOAP server.
RMI
Use when the appserver connects to an RMI server.

JMX connector port
Port number of the JMX connector on the instance to add to the cell. The default SOAP connector port is 8880.

Date type Integer
Default 8880

Application server user name
Administration user name that connects to the remote Application Server whose node is being added to the cell. The Application Server user name and password are used to connect to the appserver and start the add node process at the appserver. The Application Server user name and password settings always display. Specify values for them if security is enabled at the appserver. Otherwise, leave them blank.
Application server password
for the appserver user name that you supply.
Deployment manager user name
Deployment manager administration user name that the appserver uses when connecting to the dmgr to add its node to the cell. The dmgr user name and password settings display only if security is enabled at the dmgr. The dmgr user name and password are required if their settings display.
Deployment manager password
for the dmgr user name that you supply.

Options

Select from the following settings to further specify characteristics when adding a managed node to a cell.

Include Applications
Copies the applications installed on the remote instance into a cell. If the applications to copy have the same name as the applications that currently exist in the cell, the appserver does not copy the applications.
Include buses
Whether to move the bus configuration at the node to the dmgr.
Starting portPort numbers for the node agent process.

Use default
Whether to use the default node agent port numbers. The topic Port number settings in WAS versions provides a list of all of the default port numbers.
Specify
Allows you to specify the starting port number in the Port number field. WAS administration assigns the port numbers in order from the starting port number. For example, if we specify 9950, the administration program configures the node agent ports as 9950, 9951, 9952, and so on.

Core Group
Group to which we can add a cluster or node agent. By default, clusters or node agents are added to the DefaultCoreGroup group.
Select from one of the core groups if a list is displayed. The list displays if a core group in addition to the default core group exists.
Node group
Group to which we can add the node. By default, nodes are added to the DefaultNodeGroup group.
Select from one of the node groups if a list is displayed. The list displays if a node group in addition to the default node group exists.

Related concepts
Node

Related tasks
Manage nodes

Related
Custom property collection

Use default	Whether to use the default node agent port numbers. The topic Port number settings in WAS versions provides a list of all of the default port numbers.
Specify	Allows you to specify the starting port number in the Port number field. WAS administration assigns the port numbers in order from the starting port number. For example, if we specify 9950, the administration program configures the node agent ports as 9950, 9951, 9952, and so on.