+

Search Tips   |   Advanced Search

Register nodes with the job manager

Configure a flexible management environment by registering application servers and deployment managers as nodes on the job manager. After registering nodes with the job manager, we can submit and manage jobs.

Before starting, start job manager and the administrative agent processes

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

Ensure that the administrative agent or deployment manager version number is not higher than the version number of any job manager with which the administrative agent or deployment manager is registered. A job manager can manage a node at an equal or lesser version number than the job manager. For example, a v8 job manager can manage v8 and 7 nodes. A v7 job manager can manage v7 nodes. The fix pack portion of the version number does not matter; for example, a v7.0.0.3 job manager can manage a node at v7.0.0.9, which is v7 with fix pack 9 installed.

A job manager can manage a v8 or v7 deployment manager that has a v6 federated node. A deployment manager registered with a job manager can manage a mixed version cell. Using the job manager, we can submit jobs that manage any resources in the mixed version cell, including resources on a v6 federated node.

We can administer multiple application servers that run customer applications from a management profile containing an administrative agent. The administrative agent provides a single administrative console to administer the application servers.

We can coordinate management actions among multiple deployment managers, asynchronously administer multiple unfederated application servers, and submit jobs to start servers from a management profile containing a job manager. To begin using the job manager to run jobs, register the application server and deployment manager nodes as managed nodes of the job manager.


Register profiles containing administrative agents as nodes on the job manager

  1. Register the application server with the administrative agent.

    Run the registerNode command from the bin directory for the administrative agent server to convert a stand-alone node 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 administrative console or the management EJB applications of the application server being registered are enabled, the node registration process disables them.

    Use the registerNode command utility to register the application server profile with the administrative agent.:

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

  2. Launch the wsadmin tool and connect to the administrative agent process:

      cd profile_root/profiles/myAdminAgent/bin
      wsadmin -profileName myAdminAgent -lang jython

  3. Register the node as a node on the job manager.

    Use the registerWithJobManager command and the following parameters...

    Parameter Description Data type
    -managedNodeName Name of the node registered with the administrative agent. If the node is a deployment manager profile, specify the node name of the deployment manager. (Required) String
    -host Optional. The hostname of the job manager. String
    -port Optional. The administrative port number to use. The default secure port number is 9943. The default unsecure port number is 9960.
    -user Optional. The connector login user name. String
    -password Optional. 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 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 AppSvr01]')

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

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

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

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.


Related:

  • Administrative agent
  • Job manager
  • Create management profiles with administrative agents
  • Create management profiles for job managers
  • ManagedNodeAgent
  • AdministrativeJobs