Install applications using the job manager

In a flexible management environment, we can submit the Install application job to deploy an enterprise application on managed appserver nodes of the job manager. An enterprise application is an EAR file that conforms to Java™ Platform, Enterprise Edition (Java EE) specifications.

Before installing an enterprise application on an application server, do the following:

• Develop and assemble the EAR file. The Install application job does not change existing Java Naming and Directory (JNDI) and other application bindings. If set binding values during deployment, do not use the job manager to deploy the application. Instead, use a deployment tool such as the admin console application installation wizard or a wsadmin script and specify managed nodes of the job manager as deployment targets.

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

• Ensure that the target nodes are compatible with the application. Version 7.0 or later nodes support EAR files that have J2EE 1.3, J2EE 1.4, or Java EE 5 modules.

• Copy the EAR file to the /config/temp/JobManager directory of the job manager profile.

  If the JobManager directory does not exist, create the JobManager directory in the job manager profile /config/temp directory. To create and access the directory, have the appropriate authority.

  If the EAR file exists on a managed node, we can run the Collect file job to copy the EAR file from the managed node to the job_manager_profile/config/temp/JobManager/jobToken/nodeName directory. See the topic on the collect file job.

• Run the Distribute file job to copy the EAR file to managed nodes. Remember any destination value that is specified when distributing the file.

  Avoid trouble: You must distribute an EAR file to the target nodes before we can run the Install application job. The distribute file job copies the EAR file in the /config/temp/JobManager directory of the job manager profile to the target nodes. The name of the EAR file on the target nodes becomes whatever value that you specify for the destination when distributing the file. See the topic on the distribute file job.

Use the admin console of the job manager to submit a job that deploys an enterprise application file on selected nodes. From the job manager console, choose the Install application job, specify the file to install, specify job options, schedule the job, review the summary, and submit the job.

Instead of using the job manager console, we can run the installApplication 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 install an application file.

   1. Select the Install 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 install 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. Suppose that you distributed the DynaCacheEsi.ear file as described in the topic on distributing files from the job manager to nodes. To continue with the DynaCacheEsi.ear example in that topic, 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 an 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.

      When distributing the file, if you specified a value for Destination other than the EAR file name, specify the Destination value for Application location.

      For the DynaCacheEsi.ear example, you did not specify the EAR file name, DynaCacheEsi.ear, for the destination value when distributing the EAR file. You specified dynacache_esi_sample for the destination value. Thus, the application location is downloadedContent/dynacache_esi_sample. To enable the target nodes to find the application, specify the destination value:

      dynacache_esi_sample
      

   3. If installing 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 file.

 

Next steps

On the Job status page, click the ID of the install application job 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 installation is successful, the application name is shown in the list of node resources. Click Jobs > Node resources to see the list of resources.

After application installation, we can run jobs that administer the application or file:

• Start application

• Stop application

• Update application

• Uninstall application

• Remove file

---

Related concepts Application bindings Ways to install enterprise apps or modules Installable enterprise module versions Related tasks Set up a job manager environment Starting and stopping the job manager Starting and stopping the admin agent Starting and stopping the dmgr Starting and stopping a node Distributing files from the job manager to nodes Collecting files for the job manager Administer nodes remotely using the job manager Administer groups of nodes for 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