In a flexible management environment, you can use the job manager to install, update, and
uninstall IBM WebSphere Application Server using the graphical user interface.
Before you begin
Deprecated feature: The job manager and
centralized installation manager (CIM) are deprecated. Instead of job manager or CIM, use Urban Code
Deploy to install the product, to deploy applications, and to manage remote hosts. To manage
WebSphere® Application Server, you also can use swinging profiles. See
Swinging
profiles between product installations.
Ensure that you have the administrative console installed on your primary machine.
The user profile must have *JOBCTL authorization in order to use centralized
installation manager (CIM) on IBM i targets.
About this task
To install WebSphere Application Server, use the administrative console to register your 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, 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: IBM Installation Manager 1.8.5 or later is required.
Procedure
-
Start the job manager.
See Starting the job manager.
-
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. For more information, see Register or unregister with job manager settings.
-
Launch the administrative console.
For more information, read about the administrative console.
-
Test the connection to the targets on which you want to install the product.
This step is optional. Before you install the product on a target machine, you can test the
connection.
-
In the administrative console, select .
-
In the Job type menu list, select Test connection. Click
Next.
-
Specify the target names and target authentication.
- If you test the connection without specifying credentials, the test will use default to existing
credentials.
- You can submit the Test connection job with a user name and
password.
- You 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 your target machine, you can run an inventory job.
-
In the administrative console, select .
-
In the job type menu list, select Inventory. Click
Next.
-
Specify the target names and target authentication.
- You can submit an inventory job with a user name and password.
- You can submit an inventory job without a user name and password.
-
Install or update Installation Manager on your target machine.
This step is optional. 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. This step does not apply to zOS targets.
-
If you use secure shell (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.
-
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.
-
Select I accept the terms in the license agreements.
-
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:
- In the administrative console, select .
- 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 .
- 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 .
- 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 .
-
In the job type menu list, optionally select Manage Profiles. Click
Next.
-
Choose the job targets.
-
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 WebSphere Application Server 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 machine.
- In the administrative console, select .
- In the job type drop down menu, select runCommand. Click
Next.
- Specify the job parameters.
You can uninstall Installation Manager using the administrative console. For more
information, see Managing Installation Manager using the job manager.