Install the v9.0 product using the job manager and administrative console
In a flexible management environment, we can use the job manager to install, update, and uninstall IBM WAS using the graphical user interface.
Ensure that we have the administrative console installed on our 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.
After the centralized installation manager successfully completes the installation process on a remote node, it then deletes the installation image files 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.
IBM Installation Manager 1.8.5 or later is required.
Install the WAS ND v9.0
- Start the job manager.
- Register target host with the job manager.
- Launch the administrative console.
- Test the connection to the targets on which we want to install the product.
- Click...
Job > Submit Test connection > Next
- 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.
- Optionally run an inventory job.
To see what is installed on the target machine, we can run an inventory job.
- In the administrative console, select...
Job > Submit > Inventory > Next
- 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.
- Install or update Installation Manager on the target machine.
If we already have the correct version of Installation Manager on the target machine, we can proceed to the next step. This step does not apply to zOS targets.
- If we use secure shell (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.
- In the administrative console, select Job > Submit.
- In the job type drop down menu, select Install SSH Public Key. Click Next.
- Specify the job parameters.
- Install the product. Use the manageOfferings job to install the product.
- In the administrative console, select Job > Submit.
- In the job type drop down menu, select Manage offerings. Click Next.
- 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 parameters:
IBM Installation Manager Path 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. Secure storage file If we are using a secure file to store user credentials, specify the full path name of the secure storage file. Master password file If we are using 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. Do not use a non-default data location unless we are familiar with IBM Installation Manager. - Select I accept the terms in the license agreements.
- Optionally transfer files to or from the target machine. For example, if the installation fails, we might want to transfer the log files from the target machine to understand why the job failed.
- To collect a file from remote hosts:
- In the administrative console, select Job > Submit.
- In the job type menu list, select Collect file. Click Next.
- Specify the job parameters.
- The destination location is <profile home>/config/temp/JobManager/<task id>/<host name>.
- To distribute a file to remote hosts:
- In the administrative console, select Job > Submit.
- In the job type menu list, select Distribute file. Click Next.
- Specify the job parameters.
- The source location must be <profile home>/config/temp/JobManager.
- To delete a file on remote hosts:
- In the administrative console, select Job > Submit.
- In the job type menu list, select Remove file. Click Next.
- Specify the job parameters.
- Create a profile for the newly installed product on the target machine.
- In the administrative console, select Job > Submit.
- In the job type menu list, optionally select Manage Profiles. Click Next.
- Choose the job targets.
- Specify the job parameters.
- wasHome: The directory where we installed the product on the target machine
- responseFile: The response file used to create an IBM WAS profile
We 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.
- In the administrative console, select Job > Submit.
- In the job type drop down menu, select runCommand. Click Next.
- Specify the job parameters.
We can uninstall Installation Manager using the administrative console. See Managing Installation Manager using the job manager.
Submitting centralized installation manager jobs Manage Installation Manager using the job manager