Installing the Version 8.0 product using the job manager and command line

In a flexible management environment, you can use the job manager to install, update, and uninstall IBM WebSphere® Application Server using the command line with a response file.

Before you begin

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

Before you install WebSphere Application Server using the job manager, ensure that you have WebSphere Application Server Version 8.0 installed on your primary machine.

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

About this task

To install WebSphere Application Server, use wsadmin to run the manageOfferings command. The manageOfferings command uses a response file and a security keyring. In the response file, you 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 your security setup, you 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 that you specify 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, you can safely delete the files.

Supported configurations Supported configurations: IBM Installation Manager 1.4.3 or above is required.sptcfg

Procedure

  1. Start the job manager. For detailed instructions, see starting the job manager.
  2. Register a host with the job manager. Before you can install the product on a target machine, you must register it with the job manager. Use the wsadmin tool to run the registerHost command.
    • You can register the host with a private key; for example:
      • Using Jacl:
        $AdminTask registerHost  {-host hostname -hostProps 
        {{privateKeyFile filename} {username root }{saveSecurity true}}}
      • Using Jython:
        AdminTask.registerHost('[-host hostname -hostProps 
        [[username user][privateKeyFile filename][saveSecurity true]]]')
    • You can register the host with a user name and password; for example:
      • Using Jacl:
        $AdminTask registerHost {-host hostname -hostProps { {password xxxxx} 
        { username root } {saveSecurity true}}}
      • Using Jython:
        AdminTask.registerHost('[-host hostname -hostProps [[password xxxxx][username user]
        [saveSecurity true]]]')
  3. Optional: Test the connection to the targets on which you want to install the product. Before you install the product on a target machine, you can test the connection.
    • If you test the connection without specifying credentials, the test will use default to existing credentials; for example:
      • Using Jacl:
        $AdminTask submitJob {-jobType testConnection -targetList {hostname}}
      • Using Jython:
        AdminTask.submitJob('-jobType testConnection -targetList [hostname]')
    • You can submit the Test connection job with a username and password; for example:
      • Using Jacl:
        $AdminTask submitJob {-jobType testConnection -targetList 
        {hostname} -username username -password password}
      • Using Jython:
        AdminTask.submitJob('-jobType testConnection -targetList 
        [hostname]  -username username -password password')
    • You can submit the Test connection job with a user name and private key file; for example:
      • Using Jacl:
        $AdminTask submitJob {-jobType testConnection -targetList 
        {hostname} -username username -privateKeyFile private_key_filename}
      • Using Jython:
        AdminTask.submitJob('-jobType testConnection -targetList 
        [hostname] -username username -privateKeyFile C:\temp\private_key_filename')
  4. Optionally run an Inventory job to see what is installed on your target machine.
    1. Submit an Inventory job with a user name and password.
      • Using Jacl:
        $AdminTask submitJob {-jobType inventory -targetList {hostname} 
        -username username -password password}
      • Using Jython:
        AdminTask.submitJob('-jobType inventory -targetList [hostname] 
        -username username -password password')
    2. Submit an Inventory job without a user name and password.
      • Using Jacl:
        $AdminTask submitJob {-jobType inventory -targetList {hostname}}
      • Using Jython:
        AdminTask.submitJob('-jobType inventory -targetList [hostname]')
  5. Optional: Install or update Installation Manager on your target machine.

    If you already have the correct version of Installation Manager on your target machine, you can proceed to the next step. For more information, see managing Installation Manager using the job manager.

  6. If you use SSH security, install your public key file.

    You can install the public key file using the same credentials as the job manager. This step does not apply to IBM i targets.

    1. Run the installSSHPublicKey admin task; for example:
      • Using Jacl:
        $AdminTask submitJob {-jobType installSSHPublicKey -targetList {target} 
        -jobParams { {publicKeyFile keyfilepath} } -description "test installSSHPublicKey"}
      • Using Jython:
        AdminTask.submitJob ('-jobType installSSHPublicKey -targetList [target] 
        -jobParams [[publicKeyFile keyfilepath]] -description "test installSSHPublicKey"')
  7. Set up a response file for the manageOfferings command.
    1. Create a response file. You can create a response file using the Installation Manager. For more information, see creating a response file with Installation Manager.
    2. You can edit the response file to include information about your target machine.
    3. You can use the response file to install any offering that is compatible with Installation Manager. For more information, see the Installation Manager information center.
    1. Save the response file as filename.txt.
  8. Run the manageOfferings command. For the job to run successfully, you must specify acceptLicense TRUE.
    1. Open wsadmin from the job manager profile bin directory.
    2. Enter the manageOfferings command in wsadmin. For example:
      • Using Jacl:
        $AdminTask submitJob {-jobType manageOfferings -targetList hostname -username user -password ******* 
        -jobParams 
        {{responseFile <RESPONSE FILE LOCATION>} {acceptLicense TRUE} {IMPath <IM install location>} 
        {keyringFile <key ring file location>} {keyringPassword pwd} }}
      • Using Jython:
        AdminTask.submitJob ('-jobType manageOfferings -targetList hostname -username user -password ******* 
        -jobParams
        [[responseFile <RESPONSE FILE LOCATION>] [acceptLicense TRUE][IMPath <IM install location>] 
        [keyringFile <key ring file location>] [keyringPassword pwd]]')
      The manageOfferings command pulls the response file that you created in this task and begins the product installation.
    The following parameter for this job is required:
    • responseFile: (Response file path name) This parameter contains the full path name to the offering response file on the job manager machine.
    The following parameters for this job are optional:
    1. IMPath: (IBM Installation Manager Path) This parameter contains the full path of the IBM installation manager on the remote machine. Use this parameter if you have more than one instance of Installation Manager on your remote machine. If you have only one instance of Installation Manager installed, you can leave this parameter empty because the job can find it. Specify whether the target machine has more than one instance of Installation Manager installed.
    2. keyringFile: (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.
    3. keyringPassword: (Key ring file password If the key ring file is password protected, specify the key ring password.
  9. Optional: Run the collectFile and distributeFile administrative tasks.

    Optionally transfer files to or from the target machine and delete files on 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. When using these administrative tasks, you can specify wildcards in the filename.

    Avoid trouble Avoid trouble: The destination must be a directory, it cannot be a file.gotcha
    • To collect a file from remote hosts:
      • Using Jacl:
        $AdminTask submitJob {-jobType collectFile -targetList hostname -jobParams 
        {{source D:\\WAS80\\logs\\manageprofiles\\response.log} {destination log}}}
      • Using Jython:
        AdminTask.submitJob('-jobType collectFile -targetList hostname -jobParams 
        [[source D:\\WAS80\\logs\\manageprofiles\\response.log] [destination log]')
    • To distribute a file to remote hosts:
      • Using Jacl:
        $AdminTask submitJob{-jobType distributeFile -targetList hostname 
        -jobParams {{source test.txt}{destination D:\\temp\\test.txt} }}
      • Using Jython:
        AdminTask.submitJob('-jobType distributeFile -targetList hostname 
        -jobParams [[source test.txt][destination D:\\temp\\test.txt] ]')
    • To delete a file on remote hosts:
      • Using Jacl:
        $AdminTask submitJob{-jobType removeFile -targetList hostname 
        -jobParams {{location D:\\temp\\test.txt}}}
      • Using Jython:
        AdminTask.submitJob('-jobType removeFile -targetList hostname 
        -jobParams [[location D:\\temp\\test.txt] ]')
  10. Create a profile for the newly installed product on the target machine.
    Restriction: This step does not apply to z/OS targets.
    Specify the following parameters:
    • targetList: The machine where you want to create a new profile
    • wasHome: The directory where you installed the product on the machine that is running job manager
    • responsefile: Enter the directory where you saved your response file. This text file provides the parameters and information of the profile to create.
    For example:
    • Using Jacl:
      $AdminTask submitJob {-jobType manageprofiles -targetList hostname 
      -jobParams {{wasHome D:\\WAS70GA} {responseFile D:\\temp\\mp1.txt}}}
    • Using Jython:
      $AdminTask submitJob {-jobType manageprofiles -targetList hostname 
      -jobParams {{wasHome D:\\WAS70GA} {responseFile D:\\temp\\mp1.txt}}}

Results

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

What to do next

Using the job manager, you can run any command or script on your target computer.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 3:08:41 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=tagt_job_install_was
File name: tagt_job_install_was.html