Install a customized installation package (CIP) for WebSphere Application Server Network
Deployment.
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 installation procedure requires the
installer ID to have the following advanced user rights, Act as part
of the operating system and Log on as a service to
install Windows services.
The installer ID can be
a non-root user ID. However, some installation procedures might require the
installer ID to be the root user. For detailed information on non-root limitations
see, Limitations of non-root installers.
About this task
This topic describes how to install the product using a CIP. A
CIP installation runs the installation wizard in graphical interface mode
or in silent mode.
The installation wizard performs the following actions:
- Automatically checks system prerequisites
- Looks
for a previous WebSphere Application Server Version 6.1 installation to determine
whether you can add features to the existing product or to install a new application
server product.
- Installs the necessary product binaries
- Prompts you to create a
cell profile,a deployment manager profile, a standalone application server
profile, or a custom profile; or prompts you to start the Profile Management tool to
create a profile
You
can install the product by running the installation wizard remotely from a
Windows workstation, however you cannot install interim fixes remotely. To
install the product with interim fixes, you must run the CIP locally on an
iSeries machine.
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
Procedure
- Plan your installation.
See Planning the installation.
See Task overview: installing.
- Prepare your operating platform for installation.
See Preparing the operating system for product installation.
See Preparing the operating system for installation.
Review the roadmap for
installing the Network Deployment product as described in Roadmap: Installing the Network Deployment product.
- Install the Network Deployment product.
If you cannot use a graphical user interface on your operating system
for some reason, use the wizard in silent mode.
Choose an installation
scenario to continue the installation:
- Graphical user interface: Perform a custom installation with the
wizard.
The custom installation lets you select features to install.
See Installing a CIP for Network Deployment.
You can perform a scratch installation remotely from a
Windows workstation using a CIP. You cannot install interim fixes remotely
using a CIP. The scratch installation of a CIP has no interim fixes. To install
the product and interim fixes using a CIP, you must run the CIP locally on
your iSeries machine using the command-line interface. For information on
installing the product, without any fixes, remotely from a Windows workstation,
see Installing a CIP using a Windows workstation graphical interface.
Installation using a CIP is similar to installation using the product media.
- Graphical user interface: Install additional features to an existing
installation.
After installing the product, you can install it again to
update the system files by installing previously uninstalled features.
See Installing CIP features on an existing Network Deployment product.
- Command-line interface: Perform a silent installation as described
in Installing a CIP silently.
A silent
installation requires you to edit the response file that contains all of your
installation choices. After creating a valid response file, issue the install command
with the -silent parameter and the -options parameter from a command window.
The installer program does not support the ISMP-console installation
method at this time.
If you encounter a problem such as needing more
disk space or temporary space or missing prerequisite packages on your system,
cancel the installation, make the required changes, and restart the installation.
Results
You can install a CIP for
WebSphere Application Server Network Deployment Version 6.x by following this
procedure.