In a flexible management environment, you 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 Version 8.0 products.
Before you begin
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 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 you submit a job, you can specify a user name and password
for authentication and authorization at the target or targets. When
you submit 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.
The user profile must have *JOBCTL
authorization in order to use centralized installation manager (CIM)
on IBM i targets.
New feature: For Version 8.0, centralized installation manager
(CIM) functions are accessed through the job manager. Using the job
manager, you can perform the following functions:
- Install, update, and uninstall WebSphere Application Server offerings on remote
machines
- Install, update, and uninstall IBM® Installation
Manager on remote machines. Not supported on z/OS targets. For z/OS
targets, you must install Installation Manager prior to working with
CIM.
- Collect, distribute, and delete files on remote hosts
- Run scripts on remote hosts
newfeat
For Version 8.0, CIM functions are
not compatible with CIM Version 6.x or 7.x.
Supported configurations: IBM
Installation Manager 1.4.3 or above is required.
sptcfg
About this task
You can use the Installation Manager to install and manage
installations on remote hosts. Using the job manager, you 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,
you can run wsadmin commands in the AdministrativeJobs command group.
See the Administrative job types topic.
Procedure
- Run the install
Installation Manager job.
- Run the update
Installation Manager job.
- Run the uninstall
Installation Manager job.
- Run the install
SSH public key job.
Avoid trouble: If
your 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, you can force the file
transfer to use SFTP instead of SCP. In order 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 Version 7.0 and 8.0, you
can use the following wsadmin command to set the java property:
AdminTask.setJVMSystemProperties('[-propertyName com.ibm.ws.admin.cim.rxa.force.sftp -propertyValue true]')
AdminConfig.save()
You must then restart the server.
Using CIM Version 8.0, you 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:
AdminTask.registerHost('[-host thinkblue -hostProps [ [com.ibm.ws.admin.cim.rxa.force.sftp true][osType os_type] [password password] [saveSecurity true] [username user_name] ]]')
The host property value takes precedence.
gotcha
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,
perform the following steps:
- If you are using the graphical user interface (GUI), run the following
command and follow the instructions:
- If you are using the command line, run the following command and
follow the instructions: