Submitting jobs to manage servers

In a flexible management environment, we can submit jobs to create and administer servers on managed targets of the job manager. The servers can be a stand-alone server or a federated node of a deployment manager.

Before submitting a job, start the job manager and the targets. If a target is a stand-alone application server, also start the administrative agent.

Your ID at the job manager must be authorized for the administrator role or the operator role to submit jobs. When you submit a job, we can specify a user name and password for authentication and authorization at the target or targets. When you submit a job to multiple targets, the user name and password or the credentials for the submitter must be applicable to all the job targets.

The topics in this section describe how to create and administer servers by running jobs in the job manager console or the deployment manager console.

The jobs that we can run depend on the jobs supported by managed targets and the security credentials. To run jobs that administer clusters, a deployment manager target must be registered with the job manager. To run jobs that administer proxy servers, a target that supports proxy servers must be registered with the job manager.

Instead of using a console, we can run wsadmin commands in the AdministrativeJobs command group. See the Administrative job types topic.


What to do next

On the Job status page, click the ID of the job and view the job status. If the job is not successful, view any error messages that result from running the job, correct the error condition, and submit the job again.

If the job is successful, click Jobs > Target resources to see the server in the list of resources.


Subtopics


Related tasks

  • Start and stop the job manager
  • Start and stop the administrative agent
  • Checking job status

  • Administrative job types