In a flexible management environment, you can submit jobs to remote nodes to manage applications, modify the product configuration on remote machines, or do a general purpose task such as run a script. You can specify when the jobs start, whether they are recurring, and when they expire.
Before you can submit a job, you must have registered at least one node with the job manager. A node can be an application server node that was first registered with an administrative agent or a deployment manager node.
Start the job manager and the target nodes. If a target node is a stand-alone application server, also start the administrative agent.
Your ID for the job manager must be authorized for the administrator role or the operator role to submit jobs. When you submit a job, you can specify a user name and password for authentication and authorization at the target node or nodes. If you do not provide a user name and password in the job parameters, the credentials for the job submitter at the job manager are used for this purpose. When you submit a job to multiple target nodes, the user name and password or the credentials for the submitter must apply to all the job targets.
You can simplify administration of multiple nodes by submitting jobs against groups of nodes. Each group of nodes represents a group of nodes. Before you can submit a job for a group of nodes, you must have created the group of nodes.
You can use the administrative console of the job manager to submit jobs to do tasks such as manage applications, modify the product configuration on remote workstations, or do general-purpose tasks such as run a script. To complete the job submission, choose the type of job, choose the nodes on which you want the job to run, specify the job parameters that are specific to the job type, schedule the job, review the summary, and submit the job.
The topics in this section describe how to submit jobs using the job manager console. Instead of using the job manager console, you can submit jobs from the command line using the wsadmin submitJob command in AdministrativeJobs command group. See the topic on administrative job types.
After you submit a job, the job might not be run immediately. The job manager queues submitted jobs. The administrative agents and deployment managers poll the job manager for jobs when they are online, based on their configured polling intervals. The default polling interval is 30 seconds. It takes at least two polling cycles for administrative agents and deployment managers to retrieve jobs and then return results to the job manager. Depending on how long it takes for the node to process the job, it might take more cycles to complete the job.
After you submit a job, the Job status page shows a unique
job ID; for example, 122763380912576341. You can use the job ID to
query, suspend, resume, or delete the job. When you click a job ID,
you see the specific properties of that job, including activation
and expiration time of the job and its status. If you click the job
status link, you see the job history for each job target. Click the
status refresh icon to
refresh the displayed status.
You can check the state and status of a job using the job manager console or a wsadmin command.
The job state shows where the job is in the execution process from the job manager perspective. Table 1 lists the job states.
Job states | Description |
---|---|
Pending | You submitted the job, but the job is not available yet to be run on the targets. |
Active | One or more targets have started running the job. |
Expired | The job has expired. If a target started to run the job before it expired, the job continues running. After a job expires, a target cannot start running the job. |
Suspended | The job suspended operation. If a target started to run the job before it is suspended, the job continues running. After a job is suspended, a target cannot start running the job. |
The job status shows a history of the job processing on a managed node. A typical job history is for the status to progress from Distributed to In progress to Succeeded. Table 2 shows the job status values.
Job status | Description |
---|---|
Not attempted | The node has not received the job. The status is NOT_ATTEMPTED. |
Distributed | The node has received the job. The status is DISTRIBUTED. |
In progress | The node is running the job concurrently with other jobs. The status is ASYNC_IN_PROGRESS. |
Failed | The job failed and is no longer running. The status is FAILED. |
Rejected | The node rejected the job because, for example, the node does not support the job type. The status is REJECTED. |
Succeeded | Job completed successfully. The status is SUCCEEDED. |
Partially succeeded | Applies only to startCluster and stopCluster jobs where the cluster has multiple cluster members and to startApplication and stopApplication jobs where the application is installed on multiple targets. If only some cluster members are started or stopped or the application does not start on all application targets, the status of the job is PARTIALLY_SUCCEEDED. |
By default, submitted jobs remain active for one day (24 hours). An active job is a running Java process that consumes machine resources. Delete jobs that you no longer need. You can use the job manager console Job status page. Click Delete.
, select the jobs, and clickIn this information ...Subtopics
Related concepts
Related tasks
| IBM Redbooks, demos, education, and more(Index) |