Registering nodes with the job manager using scripting


Set the flexible management environment by...

After we register nodes with the job manager, we can submit and manage jobs.

We must configure a flexible management environment, consisting of a job manager, and optionally an administrative agent for the application server node to register. Start the job manager and the administrative agent processes before registering nodes or dmgrs with the job manager.

The identity under which the administrative agent server is running must have at least the monitor role for the profile of the managed appserver node. Otherwise, when we attempt to register the node with the job manager, registration fails with the ADMN0022E message.

We can administer multiple appservers that run customer applications from a management profile that contains an administrative agent. The administrative agent provides a single admin console to administer the appservers.

We can coordinate management actions among multiple deployment managers, asynchronously administer multiple unfederated appservers, and submit jobs to start servers from a management profile that contains a job manager. In order to begin using the job manager to run jobs, register the appserver and dmgr nodes as managed nodes of the job manager.

Use the following steps to register profiles that contain administrative agents as nodes on the job manager.

 

  1. Register the appserver with the administrative agent if it is not yet registered.

    Run the registerNode command from the bin directory for the administrative agent server to register a node with the administrative agent. When we 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. We can only run the command on an unfederated node. If the command is run on a federated node, the command exits with an error.

    If the admin console or the management Enterprise Java Beans™ (EJB) applications of the appserver being registered are enabled, the node registration process disables them.

    Use the registerNode command utility to register the appserver profile with the administrative agent, as the following command demonstrates:

    bin>registerNode -profilePath $WP_PROFILE/profiles/AppSrv01 -host localhost -conntype SOAP -port 8878

  2. Launch wsadmin. Navigate to the $WP_PROFILE/profiles/myAdminAgent/bin directory and use the following command to connect wsadmin to the administrative agent process:

    wsadmin -profileName myAdminAgent -lang jython

  3. Register the node as a node on the job manager. If the node to register contains an administrative agent, use the registerWithJobManager command and the following parameters to register a node as a node on the job manager.


    Table 1. registerWithJobManager parameter descriptions

    Parameter Description Data type
    -managedNodeName Name of the node that is registered with the administrative agent. If the node is a dmgr profile, specify the node name of the dmgr. (Required) String
    -host Optionally specifies the hostname of the job manager. String
    -port Optionally specifies the admin port number to use. The default secure port number is 9943. The default unsecure port number is 9960.  
    -user Optionally specifies the connector login user name. String
    -password Optionally specifies the password for the connector login user name. String
    -alias Optionally specifies an alias for the node. The job manager uses this name instead of the value of the managedNodeName parameter to register the node. Use this parameter if the new node has the same name of a node that is registered with the job manager. String
    -startPolling Optionally specifies whether to start polling after registering the node. Specify false to disable polling. The default value is true. Boolean
    -autoAcceptSigner Optionally specifies whether to automatically accept the signer provided by the server. Specify false to disable this option. The default value is true. Boolean

    The following sample command registers the AppSvr01 application server profile with the job manager:

    AdminTask.registerWithJobManager('[-host jobMgrHost -managedNodeName Node01]')

    The following sample command registers the DMGR01 dmgr profile with the job manager:

    AdminTask.registerWithJobManager('[-host jobMgrHost -managedNodeName DMGR01]')

  4. Repeat the registerWithJobManager command to register additional profiles as nodes on the job manager.

 

Results

The node of interest is registered with the job manager when the system successfully runs the registerWithJobManager command.

 

What to do next

Submit, monitor, and manage jobs for the nodes that are registered with the job manager.


Administrative agent
Job manager

 

Related tasks


Create a management profile with an administrative agent
Create a management profile with a job manager

 

Related


ManagedNodeAgent
AdministrativeJobs