Search Tips   |   Advanced Search

Submit centralized installation manager jobs

In a flexible management environment, we can submit jobs to install Installation Manager instances, update Installation Manager with a repository (not supported on z/OS targets), manage Installation Manager offerings, and install WebSphere Application Server products.

This topic applies to centralized installation manager (CIM) for WAS v8.0 and later. Although this version of CIM can be used to manage v9.0 and previous versions of WAS, CIM v8.0 and later functions are not compatible with CIM v6.x or 7.x, which is not included in this release.

IBM Installation Manager Version 1.8.5 or later is required to install the product.

CIM functions are accessed through the job manager. Using the job manager, we can perform the following functions:

Start the job manager and make a remote host a target of the job manager. In the job manager console or deployment manager console, click Jobs > Targets > New Host and complete the fields on the New targets page.

A remote host typically is a different computer than the one on which the job manager is installed.

To submit jobs, your ID at the job manager must be authorized for the administrator role or the operator role. When submitting a job, we can specify a user name and password for authentication and authorization at the target or targets. When submitting a job to multiple targets, the user name and password or the credentials for the submitter must be applicable to all of the job targets.

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

(ZOS) SSH code is not automatically included with z/OS operating systems. We must ensure SSH is installed and enabled on any target we want to access using CIM.

Use the Installation Manager to install and manage installations on remote hosts. Using the job manager, we can run jobs that create and update Installation Manager instances and install the product on remote hosts.

The topics in this section describe how to use the Installation Manager by running jobs in the job manager console or the deployment manager console. Instead of using a console, we can run wsadmin commands in the AdministrativeJobs command group. See the Administrative job types topic.


If our remote target is running a Tectia SSH server and it does not support the use of SCP file transfer protocol, some CIM jobs may fail during file transfer. To avoid this problem, we can force the file transfer to use SFTP instead of SCP. To use the SFTP mode, set the java system property "com.ibm.ws.admin.cim.rxa.force.sftp" to "true." If this property is not set, or set to "false", then the file transfer default is SCP. For CIM v7.0 and 8.0, we can use the following wsadmin command to set the java property:

We then restart the server.

Use CIM v8.0, we can also specify to use SFTP for each target individually. When registering the target host, set the host property "com.ibm.ws.admin.cim.rxa.force.sftp" to "true." Use the following wsadmin command:

The host property value takes precedence.

What to do next

On the Job status page, click the ID of the job and view the job status. If the job is not successful, view any error messages that result from running the job, correct the error condition, and submit the job again.

To review the Installation Manager license...