You use IBM® Installation
Manager to install this version of Websphere Load Balancer for IPv4 and IPv6.
Before you begin

New feature:
Installation Manager is a single
installation program that can use remote or local software flat-file
repositories to install, modify, or update new WebSphere® Application Server products.
It determines and shows available packages—including products, fix
packs, interim fixes, and so on—checks prerequisites and interdependencies,
and installs the selected packages. You also use Installation Manager
to easily uninstall the packages that it installed. newfeat
Important: Do not transfer the content of
a repository in non-binary mode and do not convert any content on
extraction.
Tip: Although almost all of the instructions
in this section of the information center will work with earlier versions
of IBM Installation Manager,
the information here is optimized for users who have installed or
upgraded to Installation Manager Version 1.5 or later.
Important: Installation Manager can install any fix-pack level
of the product directly without installing the interim fix packs;
in fact, Installation Manager installs the latest level by default.
For example, you can skip fix-pack levels and go from Version 8.5.0.1
directly to Version 8.5.0.5. Keep in mind, however, that later you
can not roll back to any level that was skipped. If you directly install
to Version 8.5.0.5, for example, you cannot roll back to Version 8.5.0.4.
If you skip from Version 8.5.0.1 to Version 8.5.0.5, you can only
roll back to Version 8.5.0.1. You should plan your installations accordingly.
About this task
Perform one of these procedures to install or uninstall
the product using Installation Manager.
Procedure
Results
Notes on logging and tracing:
Notes on troubleshooting:
When you attempt to launch Installation Manager
from a DVD that was mounted using the CD-ROM file system (CDFS) on
an HP-UX operating system, it might fail to launch and point to a
log file that contains an exceptions similar to one of the following:java.util.zip.ZipException: Exception in opening zip file:
org.osgi.framework.BundleException: Exception in
org.eclipse.update.internal.configurator.ConfigurationActivator.start()
or bundle org.eclipse.update.configurator.
This issue
might be caused by Installation Manager reaching the upper limit of
number of descriptors that can be opened on a CDFS-mounted device.
This upper limit is determined by the value for the tunable kernel
parameter ncdnode, which specifies the maximum number of CDFS nodes
that can be in memory at any given time. To resolve the problem, change
the ncdnode system kernel setting to 250. If the problem persists,
increase the setting.
By default, some HP-UX systems are configured
to not use DNS to resolve host names. This could result in Installation
Manager not being able to connect to an external repository. You
can ping the repository, but nslookup does not return anything.
Work
with your system administrator to configure your machine to use DNS,
or use the IP address of the repository.
- In some cases, you might need to bypass existing checking mechanisms
in Installation Manager.
- On some network file systems, disk space might not be reported
correctly at times; and you might need to bypass disk-space checking
and proceed with your installation.
To disable disk-space checking,
specify the following system property in the
config.ini file
in
IM_install_root/eclipse/configuration and
restart Installation Manager:
cic.override.disk.space=sizeunit
where
size is
a positive integer and
unit is blank for bytes,
k for kilo, m for megabytes, or g for gigabytes. For example:
cic.override.disk.space=120 (120 bytes)
cic.override.disk.space=130k (130 kilobytes)
cic.override.disk.space=140m (140 megabytes)
cic.override.disk.space=150g (150 gigabytes)
cic.override.disk.space=true
Installation Manager will
report a disk-space size of Long.MAX_VALUE. Instead of displaying
a very large amount of available disk space, N/A is displayed.
- To bypass operating-system prerequisite checking, add disableOSPrereqChecking=true to
the config.ini file in IM_install_root/eclipse/configuration and
restart Installation Manager.
If you need to use any of these bypass methods, contact IBM Support for assistance in developing
a solution that does not involve bypassing the Installation Manager
checking mechanisms.
- For more information on using Installation Manager, read the IBM Installation
Manager Information Center.
- If a fatal error occurs when you try to install the product, take
the following steps:
- Make a backup copy of your current product installation directory
in case IBM support needs to
review it later.
- Use Installation Manager to uninstall everything that you have
installed under the product installation location (package group).
You might run into errors, but they can be safely ignored.
- Delete everything that remains in the product installation directory.
- Use Installation Manager to reinstall the product to the same
location or to a new one.