IBM® Installation
Manager is a common installer for many IBM software
products that you use to install, update, roll back, and uninstall
the DMZ Secure Proxy Server for IBM WebSphere Application Server.
Before you begin
Restriction: Installation Manager console mode,
which is included in Installation Manager Version 1.4.3 and later,
does not work with WebSphere Application Server Version 8.5 offerings
on systems other than z/OS.
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.6 or later.
About this task
Perform one of these procedures to install, update, roll
back, or uninstall the DMZ Secure Proxy Server.
Note: For information
on installing and removing fix packs for WebSphere Application Server
offerings on distributed operating systems using the Installation
Manager command line, read the following articles in this information
center:
- Installing fix packs on distributed operating systems using the
command line
- Uninstalling fix packs from distributed operating systems using
the command line
Procedure
Results
Notes on logging and tracing:
Notes on troubleshooting:
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 Version 1.6 Information Center or the IBM Installation
Manager Version 1.5 Information Center.