Updating applications using the job manager

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

Before running the job, do the following:

1. Start the job manager and the target nodes. Each server on which we are updating an application must be running. If a target node is a stand-alone appserver, also start the administrative agent.

2. Run the Distribute file job for the application file that replaces or upgrades the currently installed application file. We 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.

Use the admin console of the job manager to submit a job that updates a deployed application file on selected nodes. From the job manager 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 the job manager console, we can run the updateApplication job script in the AdministrativeJobs command group to deploy the application file to target nodes. See the Administrative job types topic.

 

1. Click Jobs > Submit from the navigation tree of the job manager 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 you want to deploy the application file.

   1. Select a group of nodes from the list, or select Node names.

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

   2. If you selected Node names, then specify a node name and click Add, or click Find and specify the chosen nodes on the Find nodes page.

   3. If user authentication is required, specify the user name and password.

   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 node 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 target managed node. 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 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 the selection, WAS 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 e-mail addresses where notifications are sent when the job finishes.

      If you specify multiple e-mail 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 target nodes run the job and attempt to install the application.

 

Next steps

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 Node resources page of the application is UPDATED. Click Jobs > Node resources > resource_name to see the resource status.

After updating an application, we can run other jobs that administer the application, such as the start application job.

---

Related tasks Starting and stopping the job manager Starting and stopping the admin agent Distributing files from the job manager to nodes Install applications using the job manager Check job status Related reference Administrative job types using wsadmin scripting Find nodes Find node resources

   

---

Last updated Nov 10, 2010 8:23:07 PM CST