In a flexible management environment, you can submit the Install
IBM Installation Manager job to install the Installation
Manager on registered hosts of the job manager.
Before you begin
Start the job manager and the targets. Ensure that the
targets for which you want to install Installation Manager are registered
with the job manager.
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 apply to all of the job targets.
To run the job against a large number of targets, optionally
create a group of targets and submit the job against the group.
For
instructions on updating an existing instance of Installation Manager,
see Submitting jobs to update Installation Manager on remote hosts.
Note: CIM jobs to install, uninstall,
and update Installation Manager are not supported on z/OS® targets. You must first install Installation
Manager on z/OS targets before using CIM manage offerings jobs.
About this task
You can use the administrative console of the job manager
or the deployment manager to submit the job. From the console, choose
the Install IBM Installation Manager job, specify
the targets, schedule the job, review the summary, and submit the
job.
Instead of using a console, you can run the installIM job
script in the AdministrativeJobs command group. See the Administrative
job types topic.
For Windows targets, CIM sends unzip.exe to
the target to unzip the Installation Manager zip file. If you do
not want to use unzip.exe from CIM, you can set the JVM parameter:
com.ibm.ws.admin.cimjm.unzipOnTheFly=true/TRUE"
If
this parameter is set to "true", CIM unzips the zip file from the
job manager and sends individual files to the target. You must restart
the server after changing this parameter.
For Linux/UNIX targets,
if CIM detects an instance of unzip, CIM sends the zip file to the
target and then unzips the zip file. If CIM does not detect an instance
of unzip, CIM unzips the zip file from the job manager and sends individual
files to the target. Sending the files individually usually requires
more time than unzipping on the target. For IBM i targets, CIM uses
the jar command found on the IBM i target to unzip the zip file.
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.4.3
or above is required.
sptcfg
Procedure
- Click from the navigation tree of the administrative console.
- Choose the Install IBM Installation Manager job
and click Next.
- Choose job targets.
- Select a group of targets from the list, or select Target
names.
- If you selected Target names,
then specify a target name and click Add, or
click Find and specify the chosen targets on
the Find targets page.
- If user authentication is required, specify a user name,
password, or any other authentication values as needed.
- Click Next.
- On the Specify the job parameters page,
specify the location of the Installation Manager instance that you
want to install.
Note: If you do not specify the IBM Installation
Manager installation kit path, the installIM job searches for the
most recent IBM Installation Manager installation kit that is suitable
for the target platform from the installation kit repository on the
Job Manager. By default, the installation kit repository is <profile_home>/IMKits.
You can change the location from the Job Manager. Click , then modify 'Installation Manager
installation kits location' to a different location. If you are using
the command line, you can check for the repository location at: <profile_home>/properties/cimjm/CIMJMMetadata.xml.
Optional
parameters:
- Installation Manager agent data location: specifies the location
of the Installation Manager agent data.
Avoid trouble: The
data location cannot be a subdirectory of the installation location.
gotcha
- Installation Manager installation directory: specifies the location
of the Installation Manager installation directory.
If you select the Skip prerequisite checking check
box, you specify that no prerequisite checking is performed when installing
Installation Manager and that Installation Manager disk space checking
is disabled.
For the job to run successfully, you must select I
accept the terms in the license agreements. Click NextTo
review the Installation Manager license, perform the following steps:
Avoid trouble: Run the install command from the Installation Manager
install kit.
gotcha
- 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:
New feature: You can
install Installation Manager so that it can be used by a group of
users. Specify the following optional parameter:
installTypeValues:
- single: perform a single user installation in non administrative
mode. This option is available for all CIM supported platforms.
- Auto: the command initiates a single user installation in non
administrative mode if your are a non administrative user. If you
are an administrator, this action performs an administrative installation.
newfeat
- Schedule the job, and click Next.
- Review the summary, and click Finish to
submit the job.
Results
The job runs and installs Installation Manager on the selected
targets.
What to do next
On the Job status page, click the
job ID and view the job status. Click the status refresh icon
to refresh the displayed 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.