Before you begin
Before you use the installation tools, read this topic
to prepare for installation and to learn about installation options.
Also read the hardware and software requirements on the Supported hardware and software Web site to
get started.
The installer ID can be a non-root
user ID. However, some installation procedures might require the installer
ID to be the root user.
About this task
This topic describes how to install a feature pack using
a CIP. A CIP installation runs the installation wizard in graphical
interface mode or in silent mode.
- Automatically checks prerequisites.
- Looks for a previous WebSphere Application Server
installation to determine installation options to display.
- Options include adding features and maintenance to the product
binaries, and installing a new set of product binaries at the updated
maintenance level that is included in the CIP.
- Prompts you to create a profile available to your application
server edition.
Image spanning
New feature: You
can split, or span, a customized installation package image into multiple
smaller images if the installation image contained in the CIP is also
spannable. For example, if you are creating a CIP that contains WebSphere Application Server Version 7.0,
you can split the resulting CIP into several images because the application
server product image itself is spannable. When you generate a spanned
CIP, the images are created in directories named DISC1, DISC2, and
so on.
newfeat
Different installation images might have different
minimum sizes for spanned images. The minimum size will be the larger
of the contribution's minimum specified image size and the largest
pak file in the CIP image. If you select a size which is too small
you are alerted with an error message that indicates the minimum spanned
size of that image.
During the installation of a spanned CIP,
some core files are copied to the temporary directory before the installer
is launched. There can be a case where you might not have enough space
in the temporary directory for this operation. If you are installing
with the GUI, a dialog box will come up prompting you for an alternate
temp location. In silent mode you can use the
tempSpace parameter
to provide another temporary directory location. For example:
./install -is:tempdir /temp1
Installing
fixes included with the CIP
If you have included any fixes
in the CIP whose prerequisites are not satisfied, then the CIP installer
will not install those fixes and will continue to run instead of failing.
The result of the installation will be a partial success, which allows
you to attempt to resolve fix problems individually. If you want the
CIP installation to fail if any of the included fixes fail, add the
following option to the command line when invoking the installer:
-W installIfixesAsListOfMaintenances.skipPrereqFailure=false
What to do next
See the migration documentation for
information about migrating from a previous version of WebSphere Application
Server.
See the "Fast Paths for WebSphere Application
Server" for information about getting started deploying applications.