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 Installation Manager jobs

Install the WAS v8 using the job manager and command line

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

New feature: Supported configurations: This topic applies to WAS v8.0 only. For information about using centralized installation manager (CIM) for v6.1.x and 7.x, see Get started with the centralized installation manager (CIM) for previous versions.

Before you install WAS using the job manager, ensure that we have WAS v8.0 installed on your primary machine.

To install WAS, 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 the 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 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, you can safely delete the files.

IBM Installation Manager 1.4.3 or above is required.

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, register it with the job manager. Use wsadmin.sh to run the registerHost command.

   • We can register the host with a private key; for example:

     ### Jacl

     $AdminTask registerHost  {-host hostname -hostProps
     {{privateKeyFile filename} {username root }{saveSecurity true}}}
     

     ### Jython

     AdminTask.registerHost('[-host hostname -hostProps
     [[username user][privateKeyFile filename][saveSecurity true]]]')
     

   • We can register the host with a user name and password; for example:

     ### Jacl

     $AdminTask registerHost {-host hostname -hostProps { {password xxxxx}
     { username root } {saveSecurity true}}}
     

     ### Jython

     AdminTask.registerHost('[-host hostname -hostProps [[password xxxxx][username user]
     [saveSecurity true]]]')
     

3. Optional: Test the connection to the targets on which 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:

     ### Jacl

     $AdminTask submitJob {-jobType testConnection -targetList {hostname}}
     

     ### Jython

     AdminTask.submitJob('-jobType testConnection -targetList [hostname]')
     

   • We can submit the Test connection job with a username and password; for example:

     ### Jacl

     $AdminTask submitJob {-jobType testConnection -targetList
     {hostname} -username username -password password}
     

     ### Jython

     AdminTask.submitJob('-jobType testConnection -targetList
     [hostname]  -username username -password password')
     

   • We can submit the Test connection job with a user name and private key file; for example:

     ### Jacl

     $AdminTask submitJob {-jobType testConnection -targetList
     {hostname} -username username -privateKeyFile private_key_filename}
     

     ### 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.

      ### Jacl

      $AdminTask submitJob {-jobType inventory -targetList {hostname}
      -username username -password password}
      

      ### Jython

      AdminTask.submitJob('-jobType inventory -targetList [hostname]
      -username username -password password')
      

   2. Submit an Inventory job without a user name and password.

      ### Jacl

      $AdminTask submitJob {-jobType inventory -targetList {hostname}}
      

      ### Jython

      AdminTask.submitJob('-jobType inventory -targetList [hostname]')
      

   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. See managing Installation Manager using the job manager.

5. If you use SSH security, install your 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. Run the installSSHPublicKey admin task; for example:

      ### Jacl

      $AdminTask submitJob {-jobType installSSHPublicKey -targetList {target}
      -jobParams { {publicKeyFile keyfilepath} } -description "test installSSHPublicKey"}
      

      ### Jython

      AdminTask.submitJob ('-jobType installSSHPublicKey -targetList [target]
      -jobParams [[publicKeyFile keyfilepath]] -description "test installSSHPublicKey"')
      

6. Set up a response file for the manageOfferings command.

   1. Create a response file. We can create a response file using the Installation Manager. For more information, see creating a response file with Installation Manager.

   2. We can edit the response file to include information about your target machine.

   3. We can use the response file to install any offering that is compatible with Installation Manager. For more information, see the Installation Manager information center.

   (Windows) Create a response file that specifies the offering profile parameter as WAS ND on Windows; for example:

   <?xml version="1.0" encoding="UTF-8"?>
   <agent-input acceptLicense='true' clean='true' temporary='true'>
   <server>
   <repository location='
   <MY REPOSITORY LOCATION>'/>
   </server>
   <profile installLocation='
   <LOCATION TO INSTALL PRODUCT ON TARGET MACHINE>' id='IBM WAS - ND'>
   <data key='cic.selector.nl' value='en'/>
   <data key='eclipseLocation' value='
   <LOCATION TO INSTALL PRODUCT DATA ON TARGET MACHINE>'/>
   <data key='user.select.64bit.image,com.ibm.websphere.ND.v80' value='false'/>
   </profile>
   <install modify='false'>
   <offering profile='IBM WAS - ND' features='core.feature' id='com.ibm.websphere.ND.v80' />
   </install>
   <preference value='false' name='PassportAdvantageIsEnabled'/>
   <preference value='30' name='com.ibm.cic.common.core.preferences.connectTimeout'/>
   <preference value='0' name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount'/>
   <preference value='C:\IBM\WebSphere\AppServer-Shared' name='com.ibm.cic.common.core.preferences.eclipseCache'/>
   <preference value='false' name='com.ibm.cic.common.core.preferences.//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .disablePreemptiveAuthentication'/>
   <preference value='false' name='com.ibm.cic.common.core.preferences.keepFetchedFiles'/>
   <preference value='true' name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts'/>
   <preference value='30' name='com.ibm.cic.common.core.preferences.readTimeout'/>
   <preference value='false' name='com.ibm.cic.common.core.preferences.searchForUpdates'/>
   <preference value='false' name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode'/>
   <preference value='true' name='//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .ntlm.auth.enableIntegrated.win32'/>
   <preference value='NTLM' name='//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .ntlm.auth.kind'/>
   <preference value='true' name='offering.service.repositories.areUsed'/>
   </agent-input> 

   1. Save the response file as filename.txt.

7. Run the manageOfferings command. For the job to run successfully, specify acceptLicense TRUE.

   1. Open wsadmin from the job manager profile bin directory.

   2. Enter the manageOfferings command in wsadmin. For example:

      ### 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} }}
      

      ### 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 we have more than one instance of Installation Manager on your remote machine. If we 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.
   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. The destination must be a directory, it cannot be a file.

   • To collect a file from remote hosts:

     ### Jacl

     $AdminTask submitJob {-jobType collectFile -targetList hostname -jobParams
     {{source D:\\WAS80\\logs\\manageprofiles\\response.log} {destination log}}}
     

     ### Jython

     AdminTask.submitJob('-jobType collectFile -targetList hostname -jobParams
     [[source D:\\WAS80\\logs\\manageprofiles\\response.log] [destination log]')
     

   • To distribute a file to remote hosts:

     ### Jacl

     $AdminTask submitJob{-jobType distributeFile -targetList hostname
     -jobParams {{source test.txt}{destination D:\\temp\\test.txt} }}
     

     ### Jython

     AdminTask.submitJob('-jobType distributeFile -targetList hostname
     -jobParams [[source test.txt][destination D:\\temp\\test.txt] ]')
     

   • To delete a file on remote hosts:

     ### Jacl

     $AdminTask submitJob{-jobType removeFile -targetList hostname
     -jobParams {{location D:\\temp\\test.txt}}}
     

     ### Jython

     AdminTask.submitJob('-jobType removeFile -targetList hostname
     -jobParams [[location D:\\temp\\test.txt] ]')
     

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

   Specify the following parameters:

   • targetList: The machine where 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:

   ### Jacl

   $AdminTask submitJob {-jobType manageprofiles -targetList hostname
   -jobParams {{wasHome D:\\WAS70GA} {responseFile D:\\temp\\mp1.txt}}}
   

   ### 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

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

### Jacl

$AdminTask runCommand {-host hostname -jobParams
{{command command_to_run}{workingDir working_directory_on_remote_host}}}

### Jython

$AdminTask.runCommand ('-host hostname -jobParams
[[command command_to_run][workingDir working_directory_on_remote_host]]')

Manage Installation Manager using the job manager
Start and stop the job manager
Submit Installation Manager jobs

Related

Administrative job types using wsadmin.sh

+

Search Tips   |   Advanced Search