Install WebSphere Application Server v8.5 using the job manager and administrative console

In a flexible management environment, we can use the job manager to install, update, and uninstall IBM WebSphere Application Server using the GUI.

Supported configurations: This topic applies to WebSphere Application Server v8.5. For information about using centralized installation manager (CIM) for Version 6.1.x and 7.x, see the topic about getting started with the centralized installation manager (CIM) for previous versions..

Ensure that you have the administrative console installed on the primary machine.

(iseries) The user profile must have *JOBCTL authorization in order to use centralized installation manager (CIM) on IBM i targets.

(zos) Note: CIM jobs to install, uninstall, and update Installation Manager are not supported on z/OS targets. We must first install Installation Manager on z/OS targets before using CIM manage offerings jobs.

To install WebSphere Application Server, use the administrative console to register the target machine, install IBM Installation manager, and install WebSphere Application Server or other product offerings that are compatible with Installation Manager. Using the administrative console, we can set parameters for the directory in which to install the product on the target machine, specify where to store product data on the target machine, and specify the URL of the repository to download the product from. Depending on the security setup, we can also specify keyring credentials to log in to the product repository.

After the centralized installation manager successfully completes the installation process on a remote node, it then deletes the installation image files that are located in the temporary location specified during the installation process. If the installation is unsuccessful, the files remain in the temporary location for you to use to determine what caused the installation error. However, we can safely delete the files.

Supported configurations: IBM Installation Manager 1.5.2 or later is required.

  1. Start the job manager. See Starting the job manager.

  2. Register a host with the job manager. Before we can install the product on a target machine, you must register it with the job manager. For more information, see Register or unregister with job manager settings.

  3. Launch the administrative console. For more information, read about the administrative console.

  4. Test the connection to the targets on which to install the product. This step is optional. Before you install the product on a target machine, we can test the connection.

    1. In the administrative console, select Job > Submit.

    2. In the Job type menu list, select Test connection. Click Next.

    3. Specify the target names and target authentication.

      • If we test the connection without specifying credentials, the test will use default to existing credentials.

      • We can submit the Test connection job with a user name and password.

      • We can submit the Test connection job with a user name and private key file.

  5. Optionally run an inventory job. To see what is installed on the target machine, we can run an inventory job.

    1. In the administrative console, select Job > Submit.

    2. In the job type menu list, select Inventory. Click Next.

    3. Specify the target names and target authentication.

      • We can submit an inventory job with a user name and password.

      • We can submit an inventory job without a user name and password.

  6. Install or update Installation Manager on the target machine. This step is optional. If we already have the correct version of Installation Manager on the target machine, we can proceed to the next step. For more information, see Managing Installation Manager using the job manager. This step does not apply to z/OS targets.

  7. If we use secure shell (SSH) security, install the public key file. We can install the public key file using the same credentials as the job manager. This step does not apply to IBM i targets.

    1. In the administrative console, select Job > Submit.

    2. In the job type drop down menu, select Install SSH Public Key. Click Next.

    3. Specify the job parameters.

  8. Install the product. Use the manageOfferings job to install the product.

    1. In the administrative console, select Job > Submit.

    2. In the job type drop down menu, select Manage offerings. Click Next.

    3. Specify the following optional or required job parameters.

      Required parameter:

      • Response file path name: The full path name to the response file on the job manager machine.

      Optional...

      • IBM Installation Manager Path: Specify the path to install Installation Manager on the remote machine. If this parameter is blank, then Installation Manager is installed to the default location.

      • IBM Installation Manager key ring file: If the package repository requires a key ring file for authentication, specify the full path name of the key ring file on the job manager machine.

      • Key ring file password: If the key ring file is password protected, specify the key ring password.

      • (v8550) Secure storage file: For a secure file to store user credentials, specify the full path name of the secure storage file.

      • (v8550) Master password file: For a master password file containing a master passphrase, such as "This text is the passphrase for a master password file, specify the full path name of the master password file.

      • IBM Installation Manager agent data location: Specify an IBM Installation Manager data location that is not the default location for the manageOfferings job.

        Avoid trouble: Do not use a non-default data location unless you are familiar with IBM Installation Manager.gotcha

    4. Select I accept the terms in the license agreements.

  9. Optionally transfer files to or from the target machine. For example, if the installation fails, you might want to transfer the log files from the target machine to understand why the job failed.

    • To collect a file from remote hosts:

      1. In the administrative console, select Job > Submit.

      2. In the job type menu list, select Collect file. Click Next.

      3. Specify the job parameters.

        • The destination location is <profile home>/config/temp/JobManager/<task id>/host.

    • To distribute a file to remote hosts:

      1. In the administrative console, select Job > Submit.

      2. In the job type menu list, select Distribute file. Click Next.

      3. Specify the job parameters.

        • The source location must be <profile home>/config/temp/JobManager.

    • To delete a file on remote hosts:

      1. In the administrative console, select Job > Submit.

      2. In the job type menu list, select Remove file. Click Next.

      3. Specify the job parameters.

  10. Create a profile for the newly installed product on the target machine.

    1. In the administrative console, select Job > Submit.

    2. In the job type menu list, optionally select Manage Profiles. Click Next.

    3. Choose the job targets.

    4. Specify the job parameters.

      • wasHome: The directory where you installed the product on the target machine

      • responseFile: The response file used to create an IBM WebSphere Application Server profile


Results

You have installed WAS on a target machine and created a profile using the job manager.


What to do next

Use the job manager, we can run any command or script on the target machine.

  1. In the administrative console, select Job > Submit.

  2. In the job type drop down menu, select runCommand. Click Next.

  3. Specify the job parameters.

We can uninstall Installation Manager using the administrative console. For more information, see Managing Installation Manager using the job manager.


Related tasks

  • Submitting Installation Manager jobs
  • Manage Installation Manager using the job manager