WebSphere Application Server for Multiplatforms
Updates for Edge Components
Version 6.0.2
GI10-3353-01
Second edition (June 2005)
This edition applies to:
- WebSphere Application Server for Multiplatforms, Version 6.0.2
and to all subsequent releases and modifications until otherwise indicated
in new editions.
This softcopy version is based on the printed edition of this
book. Some formatting amendments have been made to make this information more
suitable for softcopy.
Order publications through your IBM representative or through the IBM branch
office serving your locality.
Copyright International Business Machines Corporation 2005. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Updating Edge Components 6.0
This section contains general instructions for obtaining and
installing updates to Edge Components version 6.0 for IBM(R) WebSphere(R) Application
Server.
For details on the content of the refresh pack see, Contents of Edge Components v6.0.2 (Refresh Pack 2).
The Edge Components documentation library is available from the
Information Center Web page, http://www.ibm.com/software/webservers/appserv/ecinfocenter.html.
Supported hardware and software requirements for Edge Components
are available from the following WebSphere Application Server Prerequisites
page, http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html.
Related information for WebSphere Application Server products is available
from the Library page, http://www.ibm.com/software/webservers/appserv/was/library/.
Self help information for Edge Components is available on the Technote database from the Support page of the WebSphere Application
Server Web site, http://www.ibm.com/software/webservers/appserv/was/support/.
- click Technote listed in the Self Help section of
the Support page,
- then select category Edge Component
Obtaining an update
You can obtain Edge Components v6.0.2 for the AIX(R), HP-UX, Linux,
Solaris Operating System, or Windows(R) systems in the form of --
- product CDs, for newly supported platforms
- refresh packs, as downloads for existing installations on currently supported
platforms
Newly supported platform installations (product CDs)
If you are installing Edge Components on newly supported platforms
for v6.0.2, you will need to install from the product CDs.
For installation instructions from the product CDs, see the Concepts, Planning, and Installation for Edge Components document, which
can be accessed from the Edge Components Information Center Web page, http://www.ibm.com/software/webservers/appserv/ecinfocenter.html.
For information about supported platforms, refer to http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html.
Currently supported platform installations (refresh packs)
Link to Edge Components refresh packs from the Download section of the WebSphere Application Server Web site Support page, http://www.ibm.com/software/webservers/appserv/was/support/
- From the Download section of the Support page, click the corrective
service release for the refresh pack (for example, Version 6.0 Refresh Pack
2) and follow the link to the download site.
- Follow the instructions on the site to download the Edge Components Refresh
Pack.
Use the following installation instructions to install the Edge Components
Refresh Pack on your system.
Installing a refresh pack
For AIX, HP-UX, Linux, Solaris, or Windows platform:
- Before installing the refresh
pack update, you must already have an earlier version of 6.0 Edge Components
installed on your system. See Prerequisite Edge Components version for the
required prerequisite Edge Components versions.
- If you do not already have v6.0
Edge Components installed on your system, install Edge Components v6.0. See
the Concepts, Planning, and Installation for Edge Components document for v6.0 installation instructions.
For installing Load Balancer, the only required v6.0 Edge Components
prerequisite is the v6.0 license file (nd60Full.LIC) because the refresh pack
does not provide the license. Obtain the license from installing just the
Load Balancer license package from Edge Components v6.0.
To install the Edge Components Refresh Pack:
- For UNIX(R) systems: Use the operating system's package
installation system (native installer). The Product Setup Program (common
installer) does not come with the refresh pack.
- For Windows systems: Use the InstallShield
installation program.
Installing an update on AIX, HP-UX, Linux, or Solaris
Install the packages necessary to update your system by using your operating
system's package installation system.
Before you begin
Consider the following items before proceeding with the installation of
the refresh pack.
- Any preexisting version of the product must be uninstalled from
your system.
- With the exception of Load Balancer, to install an
update package, the corresponding v6.0 package must already exist on your
machine. For example, if the v6.0 Caching Proxy package is not already installed
on a machine, then you cannot apply the v6.0.1 Components Refresh Pack for
the Caching Proxy package.
- For Load Balancer, you are only required to have the Load Balancer
v6.0 license package in order to install the v6.0.1 Edge Components Refresh
Pack for the Load Balancer package.
- For a list of package names and filesets in the Edge Components
Refresh Pack, see Edge Components Refresh Pack product notes.
Installing the packages for Caching Proxy (AIX, HP-UX, Linux, or Solaris)
Using your operating system's package installation tools, install the Caching
Proxy packages in the correct order. (See Table 1 for
a list of all Edge Components packages and the order in which to install them.)
The following procedure details the typical steps necessary to complete this
task.
IMPORTANT: Caching Proxy is available on all Edge Components installations, with the
following exceptions:
- Caching Proxy is not available for Edge Components installations that run on Itanium
2 or AMD Opteron 64-bit processors.
- Caching Proxy is not available for Edge Components installations of Load Balancer for IPv6.
- Become the local superuser root.
su - root
Password: password
- Stop the Caching Proxy process.
On AIX:
stopsrc -c -s ibmproxy
On HP-UX:
kill -9 proxy_PID
The term proxy_PID is the
process identifier for the Caching Proxy process. You can use the following
command to determine the PID for the Caching Proxy.
ps -e | grep ibmproxy
On Linux:
On Solaris:
kill -9 proxy_PID
The term proxy_PID is the process identifier for the Caching Proxy process.
You can use the following command to determine the PID for the Caching Proxy.
ps -e | grep ibmproxy
- Change to the directory containing the installation files.
cd download_package_directory/
- Install the packages.
The installation order of the packages for the
refresh pack are:
- gskit (Global security kit)
- icu (ICU Runtime)
- admin (Administrative Runtime)
- cp messages (Caching Proxy messages)
- cp (Caching Proxy)
- documentation (optional)
System-specific install directives --
- On AIX:
installp -acXd source package_name
where source is the
directory for the location of the package, and package_name is the name of the package.
For example, the
following installs the admin package (wses_admin.rte) when the packages reside
in the current directory.
installp -acXd . wses_admin.rte
And, the following installs the admin package when the packages reside in
the /tmp directory.
installp -acXd /tmp wses_admin.rte
When
using the System Management Interface Tool (SMIT), use the install_latest option. Be sure to set the value in the COMMIT software updates field to yes
.
- On HP-UX:
swinstall -s /source package_name
where source is the directory for the location of the package, and package_name is the name of the package.
For example,
Verify the installation of the packages
Issue swlist command to list all the packages that you have installed. For
example,
- If you install the packages for Caching Proxy, then issue the following
to list all installed packages:
swlist gsk*
swlist WSES*
- On Linux:
rpm -iv --replacefiles package_name
where package_name is the name
of the package.
For example,
rpm -iv --replacefiles WSES_Admin_Runtime-6.0.1-0.686.rpm
Do not use the -U option. Note that the --replacefiles option
is required for most packages. Using the option with packages that do not
require it does not affect their installation. After installation, the previously
installed versions of the new packages are still on the machine. Do not uninstall
them.
- On Solaris:
pkgadd -d source package_name
where source is the
directory for the location of the package, and package_name is the name of the package.
For example, the following
installs the admin package (WSESadmin) when the packages reside in the current
directory.
pkgadd -d . WSESadmin
And, the following
installs the admin package when the packages reside in the /tmp directory.
pkgadd -d /tmp WSESadmin
When installing gskit,
the following will install over a previous version of the gskit package
pkgadd -a ./admin -d . gsk7bas
To use the silent installation,
use the -a option and specify an administration file. An administration file
named instadm is provided with the packages that you are installing.
After installation, the previously installed versions of the new packages
are still on the machine. Do not uninstall them.
Installing the packages for Load Balancer (AIX, HP-UX, Linux,
or Solaris)
Uninstall any preexisting versions of Load Balancer
Before installing the refresh pack, stop and uninstall any preexisting version of Load Balancer. Perform the following as required.
Steps for uninstalling previous versions of Load Balancer
- Go to a command prompt with root authority.
- Copy to a backup directory any files that you created and placed in the
Load Balancer install directory. Also consider saving any Load Balancer configuration
scripts.
- Stop the Load Balancer Executor by using the command dscontrol executor
stop. The Executor can still be running even if dsserver is stopped.
If you receive a message that dsserver is not running, start dsserver and
then issue the command again.
- Stop dsserver by using the command dsserver stop.
- Uninstall all previous versions of Load Balancer packages using system-specific commands.
- On AIX:
To uninstall all of the Load Balancer
product packages, use the following command
installp -u ibmlb
- On HP-UX:
To uninstall all of the Load Balancer
product packages, use the following command
swremove ibmlb
- On Linux:
- To check for previously installed Load Balancer related packages, use
the following command
rpm -qa | grep ibmlb
- To uninstall each Load Balancer package, use the following command
rpm -e package_name
where package_name is the individual Load Balancer package name.
Note:
When uninstalling individual packages, they should be
removed in the reverse order they were installed.
- On Solaris:
- To check for previously installed Load Balancer related packages, use
the following command
pkginfo | grep ibmlb
- To uninstall each Load Balancer package, use the following command
pkgrm package_name
where package_name is the individual Load Balancer package name.
Note:
When uninstalling individual packages, they should be
removed in the reverse order they were installed.
Installing the Load Balancer v6.0 Refresh Pack
Note:
If you do not already
have a v6.0 Load Balancer component installed on your system, you are only
required to install the Load Balancer v6.0 license file (nd60Full.LIC) prior
to installing the refresh pack. The license can be obtained by installing
just the Load Balancer license package of the v6.0 product.
Installing the refresh pack
- Go to a command prompt with root authority.
- Obtain the Load Balancer Refresh Pack and place it in a temporary directory.
- Uncompress and untar the build package. This results in a number of separate
filesets.
- Install the software using system-specific commands, for example --
- On AIX:
- On HP-UX:
swinstall -s /source package_name
where source is the
directory for the location of the package, and package_name is the name of the package.
For example, the following installs the
base package for Load Balancer (ibmlb.base) when the packages reside in the
current directory:
swinstall -s /lb ibmlb.base
- On Linux:
rpm -iv --nodeps --replacefiles package_name
where package_name is the name
of the package.
For example, the following installs all the
packages (ibmlb*.rpm) for Load Balancer when the packages resides in the current
directory.
rpm -iv --nodeps --replacefiles ibmlb*.rpm
The "nodeps"
option allows you to successfully install the packages in any order.
- On Solaris:
pkgadd -d pathname package_name
where pathname is the directory for the location of the package, and package_name is the name of the package.
For example, the following
installs the Load Balancer admin package (ibmlbadm) when the package resides
in the current directory.
pkgadd -d . ibmlbadm
- Restore any configuration files and start scripts which you saved or modified
during a previous uninstall.
Edge Components packages
The following table lists all packages delivered with Edge Components
and the required order of installation. Install the packages included in the
refresh pack according to the order specified in this table.
Notes:
- Not all packages, listed here, are delivered with the refresh
pack. Update only the packages that are delivered with the refresh pack and
that were previously installed on your system.
- Refer to Edge Components Refresh Pack product notes for a list of the specific packages included
with the refresh pack and the AIX filesets and the Solaris and Linux file
names that correspond with the packages.
- On Linux, you can use the "nodeps" option to successfully install
all the packages in any order.
Table 1. Package installation details
Components installed |
Update the packages (listed generically)
in this order |
Load Balancer:
- Dispatcher
- Content Based Routing
- Site Selector
- Cisco CSS Controller
- Nortel Alteon Controller
- Metric Server
Load Balancer Documentation |
- Base
- Administation
- License
- Device Driver (AIX only)
- LB component(s)
- Metric Server
- Load Balancer Documentation (lang)
|
Caching Proxy |
- gskit7 -- Global security kit
- icu -- ICU Runtime
- admin -- Administrative Runtime
- msg-cp-lang -- Messages
- cp -- Caching Proxy
|
Edge Components Documentation |
doc-lang |
Installing an update on Windows platforms
Use the Edge Components Product Setup Program to upgrade Edge Components v6.0
on your Windows operating system as follows:
Note:
To prevent the currently installed Load Balancer from starting, be sure to
first edit any start scripts you have created to temporarily suppress any
commands that start the Load Balancer upon a reboot. Also, ensure that the
Load Balancer service is set as Manual. Then, restart
your Windows machine.
- Download the Edge Components Refresh Pack.
- Use the Add/Remove program to uninstall the current Load Balancer component,
if present.
- Run the setup program by doing one of the following:
- From a command prompt
- If installing Caching Proxy and Load Balancer, or if installing
only Caching Proxy
- Change to the directory containing the installation files for your platform
and enter setup
- If installing Load Balancer only
- Change to the lb directory and enter setup
- From the Start menu:
- Click Run.
- Click Browse.
- If installing Caching Proxy and Load Balancer, or if installing
only Caching Proxy, select the directory containing the installation files
for your platform and select setup.
- If installing only Load Balancer, select the lb directory and
select setup.
- Click Open.
- Click OK.
- Enter information as requested by the installation program.
Configuring your system after an update
After you install an Edge Components update, the previous Edge Components
configuration is maintained. However, when new functions (enhancements) are
delivered with a refresh pack, it is often necessary to add directives to
configuration files in order to enable the feature.
Note:
When updating
the Load Balancer component, you must manually save and restore configuration
files in order to maintain your previous Load Balancer configuration; see
Installing the packages for Load Balancer (AIX, HP-UX, Linux,
or Solaris) for more information.
Rejecting an update
- On Windows systems, use the Edge Components Product Setup
Program to remove components. Select Remove on
the Setup Program's Maintenance Options window. Then, use the Edge Components
Product Setup Program to reinstall the previous version.
- On UNIX systems, to remove a refresh pack and return to a prepatched state,
uninstall the product and reinstall the previous version.
The mechanism
that the AIX operating system provides for rejecting a patch requires that the
patch be produced in refresh pack format. The Edge Components Refresh Pack
is provided with product format packaging only, not refresh pack format packaging.
Therefore, you cannot use the AIX SMIT mechanisms for installing and removing
patches. In order to reject a patch on an AIX system, you must uninstall the filesets
and then reinstall the previous version.
For most components, when the refresh pack is removed, configuration files
are saved in the oldfiles/component directory
and can be used with the reinstalled version of the product in order to maintain
the patched configuration in the prepatched version. However for the Load
Balancer component, you must manually save configuration files in order to
maintain the patched configuration; see Installing the packages for Load Balancer (AIX, HP-UX, Linux,
or Solaris) for more
information.
Edge Components Refresh Pack product notes
This section contains information on the packages and components
updated and supported operating systems for the refresh pack.
List of package file names and filesets in the Refresh Pack
The Edge Components Refresh Pack includes updates for the following components:
- Caching Proxy
- Load Balancer
IMPORTANT: Caching Proxy is available on all Edge Components installations, with the
following exceptions:
- Caching Proxy is not available for Edge Components installations that run on Itanium
2 or AMD Opteron 64-bit processors.
- Caching Proxy is not available for Edge Components installations of Load Balancer for IPv6.
The following tables list the packages delivered with the refresh pack
and the corresponding package names --
Notes:
- See Installing a refresh pack for instructions on installing the refresh
pack.
- See Table 1 for the required order which the packages
must be installed.
- Not all packages, listed here, are delivered with the refresh pack. Update
only the packages that are delivered with the refresh pack and that were previously
installed on your system.
Table 2. AIX package names
Generic package name |
AIX fileset |
gskit7 (Caching Proxy) |
gskkm.rte |
icu (Caching Proxy) |
wses_icu.rte |
admin (Caching Proxy) |
wses_admin.rte |
msg-cp (Caching Proxy) |
wses_cp.msg.lang.base |
cp (Caching Proxy) |
wses_cp.base |
doc (Caching Proxy and Load Balancer) |
wses_doc.lang |
Notes:
- On AIX the variable lang refers to the substitution
of one of the following language-specific codes: de_DE, en_US, es_ES, fr_CA,
fr_CH, fr_FR, it_IT, it_CH, ja_JP, Ja_JP, ko_KR, pt_BR, zh_CN, ZH_CN, zh_TW,
Zh_TW.
|
Base (Load Balancer) |
ibmlb.base.rte |
Admin (Load Balancer) |
ibmlb.admin.rte ibmlb.msg.lang.admin |
License (Load Balancer) |
ibmlb.lb.license |
Device Driver (Load Balancer) |
ibmlb.lb.driver |
Load Balancer component(s) |
ibmlb.component.rte ibmlb.msg.lang.lb |
Metric Server (Load Balancer) |
ibmlb.ms.rte |
Load Balancer Documentation |
ibmlb.doc.rte ibmlb.msg.lang.doc |
Notes:
- On AIX, the variable lang refers to the substitution
of one of the following language-specific codes: de_DE, en_US, es_ES, fr_CA,
fr_CH, fr_FR, it_IT, it_CH, ja_JP, Ja_JP, ko_KR, pt_BR, zh_CN, ZH_CN, zh_TW,
Zh_TW.
- The variable component refers to the substitution
of one of the following: disp (dispatcher), cbr (CBR), ss (Site Selector),
cco (Cisco CSS Controller) or nal (Nortel Alteon Controller).
|
Table 3. Linux package file names
Generic package name |
Linux file name |
gskit7 (Caching Proxy) |
gsk7bas.rpm |
icu (Caching Proxy) |
WSES_ICU_Runtime-6.0.2-0.hardw.rpm |
admin (Caching Proxy) |
WSES_Admin_Runtime-6.0.2-0.hardw.rpm |
msg-cp (Caching Proxy) |
WSES_CachingProxy_msg_lang-6.0.2-0.hardw.rpm |
cp (Caching Proxy) |
WSES_CachingProxy-6.0.2-0.hardw.rpm |
doc (Caching Proxy and Load Balancer) |
WSES_Doc_lang-6.0.2-0.hardw.rpm |
Notes:
- The variable hardw refers to the substitution
of one of the following: i686 (IA-32 Linux), s390 (s390 Linux), ppc64 (Linux/PPC64),
ia64 (Itanium 2), x86_64 (AMD Opteron).
- The variable lang refers to the substitution of
one of the following language-specific codes: en_US, pt_BR, zh_CN, zh_TW,
fr_FR, de_DE, it_IT, ja_JP, ko_KR, es_ES.
|
Base (Load Balancer) |
ibmlb-base-6.0.2-0.hardw.rpm |
Admin (Load Balancer) |
ibmlb-admin-6.0.2-0.hardw.rpm |
License (Load Balancer) |
ibmlb-lic-6.0.2-0.hardw.rpm |
Load Balancer component |
ibmlb-component-6.0.2-0.hardw.rpm |
Metric Server (Load Balancer) |
ibmlb-ms-6.0.2-0.hardw.rpm |
Load Balancer Documentation |
ibmlb-lang-6.0.2-0.hardw.rpm |
Notes:
- The variable hardw refers to the substitution
of one of the following: i386 (IA-32 Linux), s390 (s390 Linux), ppc64 (Linux/PPC64),
ia64 (Itanium 2), x86_64 (AMD Opteron).
- The variable lang refers to the substitution
of one of the following language-specific codes: nlv-de_DE, nlv-es_ES, nlv-fr_FR,
nlv-it_IT, nlv-ja_JP, nlv-ko_KR, nlv-pt_BR, nlv-zh_CN, nlv-zh_TW. For English,
substitute the variable lang for doc.
- The variable component refers to the substitution
of one of the following: disp (dispatcher), cbr (CBR), ss (Site Selector),
cco (Cisco CSS Controller), or nal (Nortel Alteon Controller).
|
Table 4. HP-UX and Solaris package names
Generic package name |
HP-UX fileset |
Solaris file name |
gskit7 (Caching Proxy) |
gsk7bas |
gsk7bas |
icu (Caching Proxy) |
WSES-ICU |
WSESicu |
admin (Caching Proxy) |
WSES-ADMIN |
WSESadmin |
msg-cp (Caching Proxy) |
WSES-cpmlang |
WSEScpmlang |
cp (Caching Proxy) |
WSES-CP |
WSEScp |
doc (Caching Proxy and Load Balancer) |
WSES-DOC-lang |
WSESdoclang |
Notes:
- HP-UX, the variable lang refers to the substitution
of one of the following language-specific codes: de_DE, en_US, es_ES, fr_FR,
it_IT, ja_JP, ko_KR, pt_BR, zh_CN, zh_TW.
- On Solaris, the variable lang refers to the
substitution of one of the following language-specific codes: br, cn, cw,
de, en, es, fr, it, ja, kr.
|
Base (Load Balancer) |
ibmlb.base |
ibmlbbase |
Admin (Load Balancer) |
ibmlb.admin |
ibmlbadm |
License (Load Balancer) |
ibmlb.lic |
ibmlblic |
Load Balancer component(s) |
ibmlb.component |
ibmlbcomponent |
Metric Server (Load Balancer) |
ibmlb.ms |
ibmlbms |
Load Balancer Documentation |
ibmlb.lang |
ibmlblang |
Notes:
- On HP-UX, the variable lang refers to the
substitution of one of the following language-specific codes: nlv-deDE, nlv-esES,
nlv-frFR, nlv-itIT, nlv-jaJP, nlv-koKR, nlv-ptBR, nlv-zhCN, nlv-zhTW. For English, the variable lang refers
to the substitution of doc.
- On Solaris, the variable lang refers to the
substitution of one of the following language-specific codes: deDE, esES,
frFR, itIT, jaJP, koKR, ptBR, zhCN, zhTW. For English,
the variable lang refers to the substitution of doc.
- The variable component refers to the substitution
of one of the following: disp (dispatcher), cbr (CBR), ss (Site Selector),
cco (Cisco CSS Controller) or nal (Nortel Alteon Controller).
|
Prerequisite Edge Components version
Upgrade Edge Components to Refresh Pack 2 from the following previous
version:
- Edge Components v6.0
- Edge Components v6.0.1
Supported systems
AIX, HP-UX, Linux, Solaris, and Windows:
Supported hardware and software system requirements for this Edge Components
refresh pack are available from the following WebSphere Application Server Prerequisites
Web page, http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html.
Contents of Edge Components v6.0.2 (Refresh Pack 2)
Edge Components can be updated by applying refresh packs. Edge Components
Refresh Pack 2 (v6.0.2) includes all the most recent enhancements and fixes.
Enhancements in v6.0.2
Load Balancer enhancements
Support for IPv6 addressing
Load Balancer for IPv6 is now available. The Load Balancer for IPv6 installation contains
only the Dispatcher component but can support both IPv4 and the extended IP
addressing scheme of IPv6.
The original Load Balancer (which supports IPv4 only) is still available
for v6.0.2 with full functionality of all components.
For information on limitations and configuration differences, refer to
the chapter for deploying Dispatcher on Load Balancer for IPv6 in the WebSphere Application Server Load Balancer Administration Guide.
Additional 64-bit platform support for Load Balancer
For Edge Components v6.0.2, Load Balancer is available on additional platforms
running a 64-bit JVM.
For information on supported hardware and software for Edge Components
v6.0.2, access the following WebSphere Application Server Prerequisites
Web page, http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html.
Caching Proxy enhancements
FIPS enable directive
This new directive (FIPSenable) enables FIPS approved ciphers for SSLV3
and TLS protocol in SSL connections.
For more information, refer to WebSphere Application Server Caching Proxy Administration Guide
Directives to cache multiple variants of a resource (URI)
There are two new directives (SupportVaryHeader, RegisterCacheIdTransformer)
that enable Caching Proxy to cache and retrieve multiple variants of a URI
based on the HTTP Vary header and Cookie header.
For more information, refer to WebSphere Application Server Caching Proxy Administration Guide
Defects fixed in v6.0.2
To obtain a complete list of Edge Components defects fixed for this refresh
pack, refer to the WebSphere Application Server Web site Support page, http://www.ibm.com/software/webservers/appserv/was/support/
- From the Support page, follow the link to the corrective service
download site.
- From the download site for the refresh pack, link to the file
containing the list of defects fixed.
Contents of Edge Components v6.0.1 (Refresh Pack 1)
This section contains a list of enhancements introduced with Edge Components
Refresh Pack 1.
Enhancements in v6.0.1
64-bit platform support for Load Balancer
Load Balancer will now be available on the following platforms running a 64-bit
JVM:
- Linux for PowerPC 64-bit
- Linux for AMD Opteron 64-bit
- HP UX Itanium 2 64-bit
For information on supported software requirements for Edge Components
v6.0.1, access the following WebSphere Application Server Prerequisites
Web page, http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html.
Java 2 SDK provided on the installation
The Java 2 SDK automatically installs with Load Balancer on all platforms.
Mozilla browser requirement on UNIX and Linux systems
On UNIX and Linux systems: For viewing Edge Components
helps, the default browser is now Mozilla 1.4 or 1.7.
On Windows systems: For viewing Edge Components helps,
the default is the system browser. (This remains unchanged from the earlier
v6.0 release.) For detailed information on recommended browsers on Windows
systems, refer to the "Using browsers ..." section in the Concepts, Planning, and Installation for Edge Components document for
v6.0.1, which can be accessed from the Edge Components Information Center
Web page, http://www.ibm.com/software/webservers/appserv/ecinfocenter.html
Default adapter type for Solaris
The default adapter type for Solaris will now be eri as specified
in the ibmlb.conf file. It was previously specified as hme.
Defects fixed in Edge Components v6.0.1
To obtain a complete list of Edge Components defects fixed for this refresh
pack, refer to the WebSphere Application Server Web site Support page, http://www.ibm.com/software/webservers/appserv/was/support/
- From the Support page, follow the link to the corrective service
download site.
- From the download site for the refresh pack, link to the file
containing the list of defects fixed.