|
Problem(Abstract) |
Load Balancer is part of WebSphere® Application Server
Edge Components. This technote provides instructions for installing Load
Balancer service releases on multiple platforms. |
|
|
|
Cause |
You require installation instructions for service releases
and interim fixes. |
|
|
Resolving the
problem |
The following installation procedures are for Load
Balancer (formally known as Network Dispatcher) service releases on these
platforms:
Files that might need to be saved during an upgrade include:
- License filesets (ndxxFull.LIC or
ndxxTry.LIC)
- Server startup scripts that have been customized, such as
dsserver and default.cfg, if modified.
For AIX® systems
Before installing a new Load Balancer service release on AIX systems,
stop and uninstall any presently-installed release. Perform the following
steps as required.
- Uninstalling Load Balancer on AIX systems
- Go to a command prompt with root authority.
- Copy to a backup directory any files that you created and placed in
the Load Balancer installation directory chain. Also consider saving any
Load Balancer configuration scripts.
- Use the following command to stop the Executor:
dscontrol executor stop
Note: The Executor can still be running even if dsserver is
stopped. If you receive a message that dsserver is not running, start
dsserver, then issue the command again.
- Stop dsserver with the following command:
dsserver stop
- Uninstall the product:
- Copy the .LIC file from the /conf directory to a temporary
place.
- Enter the following command:
installp -u ibmlb
- Copy the license file back to the /conf directory, because it
is deleted if the license fileset is installed.
- Installing Load Balancer on AIX systems
- If any version of Load Balancer is installed, use the preceding
instructions to uninstall it.
- Go to a command prompt with root authority.
- Obtain the new Load Balancer Service Release and place it in a
temporary directory. Perform all FTP transfers in binary mode.
- Uncompress and untar the build package. This results in a number of
separate filesets.
- Install the software.
- Use the following command to generate a .toc file if it is not already
there:
inutoc
- Enter the following command:
installp -acXd . ibmlb
- (Optional) Restore any configuration files and start scripts that you
saved or modified during a previous uninstallation. Verify that any start
scripts you created reflect the correct Load Balancer installation
directory chain.
For Solaris systems
Before installing a new Load Balancer service release on Solaris, stop
and uninstall any presently installed Load Balancer. Perform the following
steps as required.
- Uninstalling Load Balancer on Solaris systems
- Go to a command prompt with root authority.
- (Optional) Copy to a backup directory any files that you created and
placed in the Load Balancer installation directory chain. Also consider
saving any Load Balancer configuration scripts.
- Stop the Executor:
dscontrol executor stop
Note: The Load Balancer 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:
dsserver stop
- Uninstall the product:
- Copy the .LIC file from the /conf directory to a temporary
place.
- Run pkgrm on all of the Load Balancer related packages.
- Installing Load Balancer on Solaris systems
- If any version of Load Balancer is installed on the box, use the
preceding instructions to uninstall it.
- Go to a command prompt with root authority.
- Obtain the new Load Balancer service release and place it in a
temporary directory. Perform all FTP transfers in binary mode.
- Uncompress the .Z file:
uncompress filename
where:
filename is the name of the new Service Release.
For example:
To uncompress Load Balancer 5.0.1.0:
uncompress eLBSUN-5.0.1.0.tar.Z
A file without the .Z extension is created.
- Untar the service release file:
tar -xf filename
where:
filename is the name of the new service release (without
the .Z)
For example:
To untar Load Balancer 5.0.1.0:
tar -xf eLBSUN-5.0.1.0.tar
Several files are created in the temporary directory.
- From the same temporary directory, install the product:
pkgadd -d pathname
- (Optional) Restore any configuration files and start scripts that you
saved or modified during a previous uninstall. Verify any start scripts
that you created reflect the correct Load Balancer installation directory
chain.
For Microsoft® Windows® 2000
systems
- Uninstalling Load Balancer on Windows 2000 systems
Note: Installation of a new Load Balancer service release on
Windows automatically uninstalls a previous version.
Copy the .LIC file from the /conf directory to a temporary
place.
- Installing Load Balancer on Windows 2000 systems
- (Optional) Copy to a backup directory any files that you created and
placed in the Load Balancer installation directory chain. Also consider
saving any Load Balancer configuration scripts.
- Sign on with administrator authority.
- Edit any start scripts you might have created that automatically start
Load Balancer upon reboot. Temporarily suppress the commands that start
Load Balancer.
- Prevent the presently installed Load Balancer from starting as a
service on the next reboot. Click Start > Settings > Control
Panel > Services.
- Select IBM Dispatcher, then click Startup.
- Select Manual > OK. Close the windows.
- Reboot.
- Obtain the new Load Balancer service release and place it in a
temporary directory. Perform all FTP transfers in binary mode.
- Start Windows Explorer, double-click the service release executable
file to begin the installation. Follow the instructions.
- (Optional) Restore any configuration files and start scripts that you
saved or modified before the installation. Verify that any start scripts
that you created reflect the correct Load Balancer installation directory
chain.
For Linux® systems
Before installing a new Load Balancer service release on Linux, any
presently-installed Load Balancer must be stopped and uninstalled. Perform
the following steps as required.
- Uninstalling Load Balancer on Linux systems
- Go to a command prompt with root authority.
- (Optional) Copy to a backup directory any files that you created and
placed in the Load Balancer installation directory chain. Also consider
saving any Load Balancer configuration scripts.
- Stop the Executor:
dscontrol executor stop
Note: The Load Balancer Executor can still be running even if
dsserver is stopped. If you receive a message that dsserver is not
running, start dsserver, then issue the command again.
- Stop dsserver:
dsserver stop
- Uninstall the product:
- Copy the .LIC file from the conf directory to a temporary place.
- Run rpm -e on all of the Load Balancer related packages.
- Installing Load Balancer on Linux systems
- If any version of Load Balancer is installed on the box, use the
preceding instructions to uninstall it.
- Go to a command prompt with root authority.
- Obtain the new Load Balancer service release and place it in a temp
directory. Perform all FTP transfers in binary mode.
- Uncompress the .Z file:
uncompress filename
where:
filename is the name of the new service release.
For example:
To uncompress Load Balancer 5.0.2.0:
uncompress eLBLX-5.0.2.0.tar.Z
A file without the .Z extension is created.
- Untar the service release file:
tar -xf filename
where:
filename is the name of the new service release (without
the .Z)
For example:
To untar Load Balancer 5.0.2.0:
tar -xf eLBLX-5.0.2.0.tar
Several files are created in the temp directory.
- From the same temp directory, install the product:
rpm -i --nodeps ibmlb*.rpm
The product is installed in its directory chain.
- (Optional) Restore any configuration files and start scripts that you
saved or modified during a previous uninstall. Verify that any start
scripts that you created reflect the correct Load Balancer installation
directory chain.
For HP-UX systems
Before installing a new Load Balancer service release on HP-UX, stop and
uninstall any presently-installed release. Perform the following steps as
required.
- Uninstalling Load Balancer on HP-UX systems
- Go to a command prompt with root authority.
- Copy to a backup directory any files which you created and placed in
the Load Balancer installation directory chain. Also consider saving any
Load Balancer configuration scripts.
- Stop the Executor with the following command:
dscontrol executor stop
Note: The Executor can still be running even if dsserver is
stopped. If you receive a message that dsserver is not running, start
dsserver, then issue the command again.
- Stop dsserver with the following command:
dsserver stop
- Uninstall the product:
- Copy the .LIC file from the /conf directory to a temporary
place.
- Enter the following command:
swremove ibmlb
- Copy the license file back to the /conf directory, because it
is deleted if the license fileset is installed.
- Installing Load Balancer on HP-UX systems
- If any version of Load Balancer is installed on the box, use the
preceding instructions to uninstall it.
- Go to a command prompt with root authority.
- Obtain the new Load Balancer Service Release and place it in a
temporary directory. Make sure you perform all FTP transfers in binary
mode.
- Uncompress and untar the build package. This results in a number of
separate filesets.
- Install the software using the following command,
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 command installs the base package for
Load Balancer (ibmlb.base) when the packages reside in the lb directory:
swinstall -s /lb ibmlb.base
- (Optional) Restore any configuration files and start scripts that you
saved or modified during a previous uninstallation. Verify that any start
scripts you created reflect the correct Load Balancer installation
directory chain.
|
|
|
|
|
|
|