Use the centralized installation manager (CIM) to install
one or more packages to the specified target workstations.
Before you begin
To successfully install a package, you must first define
an installation target, which is the remote workstation
on which selected software packages might be installed. By default,
all of the workstations that contain nodes that are defined in the
cell are displayed as installation targets.
Avoid trouble: The
CIM does not install maintenance on the deployment manager. Instead,
use the IBM Update Installer for WebSphere Software to apply maintenance
to the deployment manager. For more information on downloading and
installing the tool, read the “Downloading the IBM Update Installer
for WebSphere Software" topic.
gotcha
During the installation process,
the wizard prompts you to select an authentication method which is
either user name and password or Secure Shell (SSH) public/private
key. If you choose to use the SSH public/private key method, you must
first create a pair of public/private keys and install the public
key on all the installation targets. Read the “Managing installation
targets" topic for details.
You must first create the repository
to use the features of the CIM. If you did not create the repository
during the product installation, you can still set up the CIM repository
and add the binary installation images to the repository using the
Installation Factory. Ensure that the CIM repository is populated
with the installation image for the components that you want to install
on the remote workstations. For more information on the steps to populate
the CIM repository, refer to the "Getting started with the centralized
installation manager" topic for more information.
About this task
The number of steps to complete this task can vary depending
on the type of installation package that you choose to install.
Procedure
- Access the wizard from the administrative console.
- Click .
- Select a package type, which is the type of installation
you want to perform. For example, you can choose to complete a product
installation, or an installation that applies various types of maintenance
files.
- Next, select an installation package. If you choose
a package that includes available features, select each feature from
the feature list. This list is not displayed if you choose an installation
package that does not include available features.
Note: To
deselect any selected feature from the feature list, press Ctrl while
you click the selected feature.
- Click Show installation targets to
populate the table with a list of applicable target workstations on
which to install the selected software package.
- Select one or more installation targets from the list,
and click Install or Install Using
Response File to start the Installation wizard.
Not all installation packages support response files. The Install
Using Response File button is disabled if that installation
package does not support response files.
- Accept the license agreement. Click View License
Agreement to read the agreement and accept the terms.
Click Next to continue.
- Select an authentication method to access the installation
target, and click Next. You can choose to use
either the Secure Shell (SSH) public/private key method, or the user
name and password method to authenticate.
- Provide the authentication settings, and click Next.
Depending on the authentication method that you choose in
step 3, provide the appropriate user name and password for one or
more installation targets, or provide the location of the SSH private
key file and password on the deployment manager.
If you choose
to authenticate using the user name and password method, you can provide
a common user name and password to access all of the installation
targets, or you can configure unique user names and passwords for
each target.
Avoid trouble: Do not use the browser to
save the user name and password. The browser might offer the same
user name and password on different target names.
gotcha
- Optional: If you choose to install using a
response file, you can click Browse to locate
the response file in the deployment manager. For security reasons
the browse function is restricted to browse response files in the app_server_root/cim/responsefiles directory
and any subdirectories below it.
Password encoding
utility program for response files
The passwords specified
in the response file may optionally be encoded using the ResponseFilePasswordEncoder utility.
The following script files for running the utility are located in
the app_server_root /bin directory:
- ResponseFilePasswordEncoder.sh
file_name password_keys_list [-Backup | -noBackup]
- ResponseFilePasswordEncoder.bat file_name
password_keys_list [-Backup | -noBackup]
The password_keys_list element is a list
of password keys (delimited by comma) for which the password values
are to be encoded.
The -Backup option is an
optional argument for making a backup copy of the response file to
be encoded. The default option is -noBackup.
Examples
- To encode the password values
in the response file, responsefile.nd.txt, identified by the keys PROF_importSigningCertKSPassword and PROF_importPersonalCertKSPassword,
enter:
./ResponseFilePasswordEncoder.sh responsefile.nd.txt PROF_importSigningCertKSPassword,PROF_importPersonalCertKSPassword
- To encode the password values in the response
file, responsefile.nd.txt, identified by the keys PROF_importSigningCertKSPassword and PROF_importPersonalCertKSPassword and
to keep a back-up copy of the original response file, enter:
ResponseFilePasswordEncoder.bat responsefile.nd.txt PROF_importSigningCertKSPassword,PROF_importPersonalCertKSPassword -Backup
Invalid arguments in the command line cause the utility to
display the command usage information.
- Specify the installation location and the working location
of each installation target, and click Next.
The installation location is the remote location of the installation
target where the package will be installed.
The working location
specifies the directory on the remote target where the CIM will transfer
the binary installation files from its repository to the target for
subsequent installation on the target.
Make sure you have enough
disk space on both the installation location and the working location.
The space required in the installation and working location varies
by installation packages. CIM transfers the binary files for the selected
installation package from the repository and extracts the content
of the binary files into the working location.
- Specify other command parameters.
The Installation
wizard is a generic wizard for all installation packages that the
CIM supports. In addition to the standard installation location parameter,
a particular installation package might have zero or more command
parameters that require user input. Specify values for these parameters
as needed or take the default values.
- Read the installation summary, and click Finish to
submit the installation request to the CIM for processing.
Results
You completed the steps to install one or more packages
to the specified target workstations. The CIM receives your installation
request, processes the information that you provided, and then installs
the package to the workstations.
Avoid trouble:
- The CIM only works on nodes that are part of a deployment manager
cell. If you use a response file to install WebSphere Application
Server Version 7.0, whether a profile is created and federated to
the cell is entirely controlled by the response file. After you have
installed a target node, you must federate the target node to the
deployment manager in order for the CIM to perform operations against
it.
-
If you use the CIM to install WebSphere Application Server
Version 7.0 on a machine that is not yet part of the cell and do not
use a response file, the CIM automatically creates a custom profile
after completing the installation. The CIM then federates the newly
defined node to the cell.
gotcha
What to do next
In the administrative console, check the status of your
pending requests on the Installations in Progress page, and
review the log files of your submitted installation requests from
the Installation History page. Read the details about the options
that you can use to further monitor the progress of each request.
From
the Installation History panel you can click View Details to
display a panel with additional details on the results. Links to log
files on the remote targets are included. However, those logs might
be moved, replaced, or deleted if they are not viewed immediately
after an installation operation.