Administer nodes using the job manager
Job manager can asynchronously submit jobs for large numbers of unfederated remote appservers and dmgrs.
- manage applications
- modify WAS configuration
- Run scripts
Before we can use the job manager...
- Install WAS.
- Create a management profile for the job manager.
If we have at least one administrative agent, create profiles for one or more nodes residing on the same computer as the administrative agent profile. If we have at least one dmgr profile, you would have profiles for one or more federated nodes.
- Ensure system clocks are synchronized.
If we plan to change the system clock, stop all the appservers, the node agent servers, the dmgr server, the administrative agent server, and the job manager server first. After you stop the servers, change the system clock, and then restart the servers. If we change the system clock on one system, ensure the clocks on all systems that communicate with each other and have WAS installed are synchronized. Otherwise, we might experience errors, such as security tokens no longer being valid.
- Verify the servers in the flexible management environment either all have security enabled or all have security disabled.
The servers include a job manager. Depending on the environment, the servers can include administrative agents, the nodes registered to the administrative agents, dmgrs, and the nodes federated with the dmgr.
- Use registerNode to register unfederated nodes with the administrative agent.
Nodes registered must be on the same computer as the administrative agent.
- Register unfederated nodes and dmgrs with the job manager. Use the following methods, depending on what we are registering:
- Use the job manager console to verify that the nodes have been registered to the job manager.
- Verify the servers in the flexible management environment are running.
New feature: In a flexible management environment, the job manager allows you to asynchronously submit and administer jobs for large numbers of unfederated appservers and dmgrs over a geographically dispersed area. Many of the management tasks that we can perform with the job manager are tasks that we can already perform with WAS ND, such as application management, server management, and node management. However, with the job manager, we can aggregate the tasks and perform the tasks across multiple appservers or dmgrs
We can submit jobs for groups of nodes that you define or for individual nodes. After you submit a job, we can check the job status, check the status of nodes, and check the status of node resources. The status of managed resources is not necessarily up-to-date. Status in the job manager admin console is updated only when a status job or an inventory job for the node containing the resource completes successfully. We can view node resources for nodes and groups of nodes that you administer. Configure the job manager and view its properties.
- Submit a job.
We can submit jobs to remote nodes to manage applications, modify WAS configuration on remote machines, or do general purpose tasks such as run a script. We can specify when the jobs start, whether they are recurring, and when they are no longer available for submission.
- Check the status of a job.
We can check the status of jobs, the status of jobs at their nodes, and the job history of nodes. We can suspend, resume, or delete jobs on the Job status collection panel.
- Administer nodes of the job manager.
We can view nodes with their version numbers based on the results of the Find option and view node resources for nodes that you select. We can also view the properties and property values for a particular node.
- Administer node resources of the job manager.
We can view server, application, node, and cluster resources that are associated with nodes and groups of nodes registered to the job manager. We can also view the status of specific resources at each node and view properties for a particular node resource as a name-value pair.
- Administer groups of nodes for the job manager.
We can create, modify, delete, and view groups of nodes. Groups of nodes make job submission simpler because we can submit a job for a group of nodes instead of entering multiple node names for a job submission.
- Set job managers.
We can specify settings such as the default job expiration, the job manager Web address, and the mail provider JNDI name for the job manager. We can view job manager properties such as the process ID and the state of the job manager.
Depending on the tasks that you completed, we might have submitted jobs, checked the status of jobs, viewed nodes and node resources, or administered groups of nodes.
We can continue to administer jobs as described in the procedure. We can register nodes using the wsadmin registerWithJobManager command, or unregister nodes using the wsadmin unregisterWithJobManager command. Both commands are in the ManagedNodeAgent command group. We can stop and restart the job manager.
Submitting a job
Check job status
Administer nodes of the job manager
Administer node resources of the job manager
Administer groups of nodes for the job manager
Set job managers
Related conceptsJob manager
Related tasksCreate a management profile with a job manager
Administer jobs in a flexible management environment using scripting
Register or unregister with job manager settings
Administrative console buttons