|
| |
| Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX | |
Chapter 9
High Availability Session StoreThis chapter describes how to upgrade High Availability Session Store to Java ES 5 Update 1 (Release 5U1): High Availability Session Store (HADB) 4.4.3.
The version of HADB included in Java ES 5 Update 1 is the same as that included in Java ES 5. Therefore, this chapter covers feature upgrades from previous Java ES release families to Release 5U1, but there is no maintenance upgrade from Java ES 5.
The chapter provides a general overview of upgrade issues before covering the different upgrade paths supported by Release 5U1. The chapter covers upgrades on both the Solaris and Linux operating systems:
Overview of HADB UpgradesThis section describes the following general aspects of HADB that impact upgrading to Java ES 5 Update 1 (Release 5U1):
About Release 5U1 HADB
Release 5U1 HADB is the same as Release 5 HADB and represents minor user enhancements with respect to Release 4 HADB.
HADB Upgrade Roadmap
Table 9-2 shows the supported HADB upgrade paths to Release 5U1. The table applies to both Solaris and Linux operating systems.
HADB Data
The following table shows the type of data that could be impacted by an upgrade of HADB software.
HADB Upgrade Strategy
Your strategy for upgrading HADB generally depends on the many considerations discussed in Chapter 1, "Planning for Upgrades": upgrade path, dependencies between Java ES components, selective upgrade versus upgrade all, multi-instance deployments, and so forth.
This section is to particularize that general discussion to HADB by presenting issues that might influence your HADB upgrade plan.
Compatibility Issues
Release 5U1 HADB is backwardly compatible with HADB provided with Java ES Release 4.
HADB Dependencies
Release 5U1 HADB has dependencies only on the J2SE shared component: Java™ 2 Platform, Standard Edition (J2SE™) Version 1.4 or later.
Dual Upgrade
Dual upgrades, in which both HADB software and operating system are upgraded (as described in Dual Upgrades: Java ES and Operating System Software) are performed in the context of Application Server dual upgrades. See Dual Upgrade for information about Application Server dual upgrades.
Upgrading HADB from Java ES Release 4This section includes information about upgrading HADB from Java ES 2005Q4 (Release 4) to Java ES 5 Update 1 (Release 5U1). The section covers the following topics:
Introduction
When upgrading Java ES Release 4 HADB to Release 5U1, consider the following aspects of the upgrade process:
- General Upgrade Approach. Upgrades consist of removing the Java ES Release 4 HADB packages and adding the Release 5U1 packages. There are two upgrades approaches available:
- Upgrade Dependencies. HADB has no hard upgrade dependencies. HADB requires J2SE Version 1.4 or later, meaning that it has a soft upgrade dependency on J2SE.
- Backward Compatibility. HADB provided with Java ES 5 Update 1 is backwardly compatible with HADB provided with Java ES Release 4.
- Upgrade Rollback. Rollback from the Release 5U1 upgrade to Release 4 is achieved by restoring Release 4 version packages.
- Platform Issues. The general approach for upgrading HADB is the same on both Solaris and Linux operating systems.
Release 4 HADB Upgrade
This section describes how to perform an upgrade of HADB from Java ES Release 4 to Release 5U1 on both the Solaris and Linux platform. The section covers the following topics:
Pre-Upgrade Tasks
Before you upgrade HADB software you should perform the following tasks:
Verify Current Version Information
You can verify the current version of HADB using standard version checking utilities. For example:
On Solaris:
pkgparam -v SUNWhadbaOn Linux:
rpm -qi sun-hadb-a
Upgrade HADB Dependencies
It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. However, all shared components required by HADB (namely J2SE) are upgraded automatically by the Java ES installer when you perform an upgrade of HADB to Release 5U1.
Back Up Directory Data and Configuration Files
The HADB upgrade from Java ES Release 4 to Release 5U1 does not modify HADB dynamic data. However, you can back up the Java ES Release 4 packages in case you need to roll back the upgrade.
Also, back up the following files if you have made any modifications to them since the previous HADB installation.
Obtain Required Configuration Information and Passwords
HADB upgrade requires you to know the superuser password.
Upgrading Release 4 HADB
This section discusses considerations that impact the upgrade procedure for HADB followed by a description of the procedure itself.
Upgrade Considerations
The upgrade of HADB software to Release 5U1 takes into account the following considerations:
- Based on your production requirements, you need to determine whether an online or offline upgrade is more appropriate.
- The Release 5U1 upgrade packages for Solaris and Linux platforms are shown in the following table. Solaris packages are listed in their installation sequence.
Online Upgrades of HADB
When you perform an online upgrade of HADB, you first install, start up, and verify Release 5U1 HADB on each server in the cluster being upgraded. Each server then un-registers from the earlier installation of HADB and registers with the newly installed version of HADB.
For details on performing an online upgrade, refer to the following section in Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide, http://docs.sun.com/doc/819-4740/6n4r9qo7n?a=view
Offline Upgrades of HADB
An offline upgrade of HADB is available when upgrading from either Java ES Release 3 or Release 4.
To perform an offline upgrade, shut down your HADB services and replace the existing HADB packages with the newer versions available from your Java ES 5 Update 1 (Release 5U1) distribution, shown in Table 9-5.
- Log in as root or become superuser.
su -
- Shut down all HADB services.
- List all databases that are running.
HADB-base/bin/hadbm list
- Shut down each of the listed databases.
HADB-base/bin/hadbm stop databaseName
Ignore the message if a database is already in the stopped state.
- Shut down the HADB management agent on every host running a management agent:
/etc/init.d/ma-initd stop
(The ma-initd script is located in HADB-base/bin if you have installed HADB using the standalone Application Server installer instead of the Java ES installer.)
- Launch the Java ES installer.
cd Java ES Release 5U1 distribution/os_arch
./installerwhere os_arch matches your platform, such as Solaris_sparc. (Use the installer -nodisplay option for the command line interface.)
After the Welcome and License Agreement pages are displayed, you will be presented with a component selection page. (When installed components are detected that can be directly upgraded by the Java ES installer, they are shown with a status of "upgradable.")
- Select High Availability Session Store 4.4 in the component selection page.
If you have already selected Application Server Enterprise Edition 8.2, then HADB is automatically selected.
- Confirm your upgrade choice.
HADB packages will be upgraded and an upgrade summary displayed.
- Exit the Java ES installer.
- Restore the files backed up in Back Up Directory Data and Configuration Files.
- Update the symbolic link /opt/SUNWhadb/4 to point to HADB-base.
cd HADB-base/
rm 4
ln -s 4.4.3-5 4For example, for the default HADB-base:
ls -l /opt/SUNWhadb/4
lrwxrwxrwx 1 root other 7 Jul 7 23:18 /opt/SUNWhadb/4 ->
4.4.3-5/- Restart the HADB management agents that were shut down in Step 2:
/etc/init.d/ma-initd start
(The ma-initd script is located in HADB-base/bin if you have installed HADB using the standalone Application Server installer instead of the Java ES installer.)
Verifying the Upgrade
After completing the online upgrade, verify the upgrade by using the following procedure. After verifying that the upgrade is successful, the old installation packages can be deleted.
To verify that running processes are using the upgraded HADB services, you can perform the following steps.
- For all HADB services running, issue either of the following commands:
HADB-base/bin/ma -V
HADB-base/bin/hadbm -VFor example,
HADB-base/bin/ma -V
Sun Java System High Availability Database 4.4 Database Management Agent
Version : 4.4.3.5 [V4-5-3-5 2006-03-31 13:59:50 pakker@astra07] (SunOS_5.9_sparc)- Check whether the database is running.
HADB-base/bin/hadbm status -n databaseName
For example, for a database named Example DB, enter the following commands.
HADB-basebin/hadbm list
Database
ExampleDBHADB-base/bin/hadbm status ExampleDB
Database Status
ExampleDB FaultTolerantHADB-base/bin/hadbm status -n ExampleDB
NodeNo HostName Port NodeRole NodeState MirrorNode
0 sungod012 15000 active running 1
1 sungod012 15020 active running 0All HADB services for listed nodes should in the "running" state.
- Verify that all products using HADB are using the new HADB path.
HADB-base/bin/hadbm get PackageName databaseName
For example, for a database named Example DB, enter the following commands.
HADB-base/bin/hadbm get PackageName ExampleDB
Attribute Value
PackageName V4.4.3.5The above command displays the current version of HADB. For a detailed listing, issue the following command:
HADB-base/bin/hadbm get --all ExampleDB
Post-Upgrade Tasks
There are no post-upgrade tasks beyond the steps described in Upgrading HADB from Java ES Release 4.
Rolling Back the Upgrade
To roll back the upgrade to HADB, replace the newer versions of the HADB packages you installed with the versions you had previously backed up, as described in Back Up Directory Data and Configuration Files.
Upgrading HADB from Java ES Release 3The procedure for upgrading Java ES 2005Q1 (Release 3) HADB to Release 5U1 is the same as that for upgrading Release 4 HADB to Release 5U1.
To upgrade Release 3 HADB to Release 5U1, use the instructions in Upgrading HADB from Java ES Release 4, except substitute Release 3 wherever Release 4 is referenced.