Network Deployment (Distributed operating systems), v8.0 > Set up the application serving environment > Administer nodes and resources > Administer nodes remotely using the job manager > Submit jobs > Submit jobs to manage applications

Update applications using the job manager

In a flexible management environment, you can submit the Update application job to upgrade all or part of an enterprise application that is deployed on managed targets of the job manager.

Before running the job, do the following:

1. Start the job manager and the targets. Each server on which you are updating an application must be running. If a target is a stand-alone application server, also start the admin agent.
2. Run the Distribute file job for the application file that replaces or upgrades the currently installed application file. You might specify a different destination value for this job than the value for the currently installed file. Remember any destination value specified when distributing the file.
3. Run the Stop application job to stop the currently installed application file to update.

We can use the administrative console of the job manager or the dmgr to submit a job that updates a deployed application file on selected targets. From the console, choose the Update application job, specify the file to upgrade, specify job options, schedule the job, review the summary, and submit the job.

Instead of using a console, you can run the updateApplication job script in the AdministrativeJobs command group to deploy the application file to targets. See the Administrative job types topic.

Procedure

1. Click Jobs > Submit from the navigation tree of the administrative console.

2. Choose a job to update an application file.

   1. Select the Update application job type from the list.

   2. Optionally specify a description of the job.

   3. Click Next.

3. Choose the job targets on which to deploy the application file.

   1. Select a group of targets from the list, or select Target names.

      Only groups of targets that are valid for the job type that you selected are displayed in the list of target groups.

   2. If you selected Target names, then specify a target name and click Add, or click Find and specify the chosen targets on the Find targets page.

   3. If user authentication is required, specify a user name, password, or any other authentication values as needed.

   4. Click Next.

4. Specify parameters for the update application job.

   1. For Application name, specify the base file name of the application file.

      By default, the job appends the .ear file extension to the application name.

      Click Find. On the Find target resources page, select the application resource that upgrades the currently installed application file.

      Suppose to upgrade the DynaCacheEsi.ear file used as an example in the topics on distributing files and installing applications.

      To continue with the DynaCacheEsi.ear example, specify the name of the application file without the .ear extension:

      DynaCacheEsi
      

   2. If you specified a Destination value other than the EAR file name when distributing the application, specify that destination value for Application location.

      By default, the job searches for the application in the default destination location. If you do not specify a Application location value, then the location defaults to downloadedContent/application_name.ear of the managed target. Thus, if you specified DynaCacheEsi for Application name, the application location defaults to downloadedContent/DynaCacheEsi.ear.

      To continue with the DynaCacheEsi.ear example, suppose that the destination value for the upgraded file is dynacache_esi_updated_sample. Specify the new destination value:

      dynacache_esi_updated_sample
      

   3. If you are updating the application on a federated node of a dmgr, specify the target server, node, or cluster names.

      For Server name, click Find and specify the target server. Based on your selection, the product fills in values for the server and node names.

      If the target is a cluster, for Cluster name, click Find and specify the target cluster.

   4. Click Next.

5. Schedule the job.

   The times and dates that you specify are relative to the job manager.

   1. Optionally specify one or more email addresses where notifications are sent when the job finishes.

      If you specify multiple email addresses, separate them with commas.

   2. Select when the job is available for submission.

   3. Select the job expiration.

   4. Optionally specify a recurring interval for the job, a start date and time for the interval, and an end date and time for the interval.

   5. Click Next.

6. Review the summary, and click Finish to submit the job.

Results

The targets run the job and attempt to install the application.

What to do next

On the Job status page, click the job ID and view the job status. Click the status refresh icon to refresh the displayed 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, the status on the Target resources page of the application is UPDATED. Click Jobs > Target resources > resource_name to see the resource status.

After updating an application, you can run other jobs that administer the application, such as the start application job.
Start and stop the job manager
Start and stop the admin agent
Distribute files from the job manager to targets
Install applications using the job manager
Check job status

Related

Administrative job types using wsadmin.sh
Find targets
Find target resources

+

Search Tips   |   Advanced Search