Search Tips   |   Advanced Search

Administer nodes remotely using the job manager

In a flexible management environment, we can asynchronously submit and administer jobs for large numbers of stand-alone application servers, deployment managers, and host computers over a geographically dispersed area. At the remote machines, we can use jobs to manage applications, modify the product configuration, or do general purpose tasks such as run a script.

A job manager is a single management server from which we can remotely manage multiple administrative agents, deployment managers, stand-alone (unfederated) application servers, and host computers.

In contrast to a deployment manager, the job manager does not exclusively inherit the administrative functions of its registered targets. Targets that register with a job manager maintain their own administrative capabilities. Additionally, the targets periodically poll the job managers to determine whether there are jobs posted there that require action. We can administer all registered targets separately from the job manager. The advantage to a job manager is that we can administer targets in multiple varied environments.

To administer targets, we submit jobs using the job manager. We can submit jobs for individual targets or for groups of targets defined. After we submit a job, we can check the job status, check the status of targets, and check the status of target resources. The status of managed resources is not necessarily up-to-date. Status in the job manager administrative console is updated only when a status job or an inventory job for the target containing the resource completes successfully. We can view target resources for targets and groups of targets that we administer. We can configure the job manager and view its properties.


What to do next

If we no longer need a target, unregister the target. We can unregister targets from a job manager in the following ways:

Use a deployment manager to unregister the deployment manager from a job manager. Use an administrative agent to unregister a stand-alone application server. To fully remove a stand-alone application server from the flexible management environment, first unregister the stand-alone application server from a job manager and then unregister it from an administrative agent.

Unregister a node before deleting its profile. For example, AppSrv02 is a stand-alone application server registered as nodeB. Use the administrative agent to unregister nodeB before deleting profile AppSrv02. For more information, see the topic on unregistering nodes of the administrative agent.

If the system fails when unregistering a target from a job manager, run the cleanupTarget command in the JobManagerNode group to clean up job manager registration information. The command does not remove the job history of the node that we are unregistering. Jobs in progress continue to run, but new jobs do not start for the node.



  • Create management profiles for job managers
  • Administer jobs in a flexible management environment
  • manageprofiles command
  • Unregistering nodes of the administrative agent
  • Register or unregister with job manager settings
  • Enable security
  • startServer command
  • (ZOS) START command
  • ManagedNodeAgent .
  • registerNode command
  • deregisterNode command
  • stopServer command
  • (ZOS) STOP command
  • JobManagerUpkeep
  • restoreJobManager command
  • JobManagerNode
  • System administration for WAS V7: Part 3: Administering a flexible management topology