|
| |
| Sun Java Enterprise System Upgrade Guide for HP-UX | |
Chapter 7
High Availability Session StoreThis chapter describes how to upgrade High Availability Session Store to Java ES 2005Q4 (Release 4): High Availability Session Store (HADB) 4.4.2.
The chapter provides a general overview of upgrade issues before covering the different upgrade paths supported by Java ES Release 4 on Solaris.
Overview of HADB UpgradesThis section describes the following general aspects of HADB that impact upgrading to Java ES 2005Q4 (Release 4):
About Java ES Release 4 HADB
Java ES Release 4 versions of HADB represents bug fixes to the Java ES 2005Q1 (Release 3) version.
HADB Upgrade Roadmap
Table 7-1 shows the supported HADB upgrade paths to Java ES Release 4. 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.
Table 7-2 HADB Data Usage
Type of Data
Location
Usage
Dynamic application data
/var/opt/SUNWhadb and /etc/opt/SUNWhadb
High availability session store and configuration information.
Compatibility Issues
HADB provided with Java ES Release 4 is backwardly compatible with HADB provided with Java ES Release 3.
HADB Dependencies
HADB provided with Java ES Release 4 requires Java™ 2 Platform, Standard Edition (J2SE™ ) Version 5.0 or later.
Upgrading HADB from Java ES Release 3This section includes information about upgrading HADB from Java ES 2005Q1 (Release 3) to Java ES 2005Q4 (Release 4). The section covers the following topics:
Introduction
When upgrading Java ES Release 3 HADB to Java ES Release 4, consider the following aspects of the upgrade process:
General Upgrade Approach. Upgrades consist of removing the Java ES Release 3 HADB packages and adding the Java ES Release 4 packages. There are two upgrades approaches available:
- Upgrade Dependencies. HADB requires J2SE Version 5.0 or later.
- Backward Compatibility. HADB provided with Java ES Release 4 is backwardly compatible with HADB provided with Java ES Release 3.
- Upgrade Rollback. Rollback from the Java ES Release 4 upgrade to Java ES Release 3 is achieved by restoring the Release 3 version, which is left undisturbed in a separate directory by the upgrade to Release 4.
- Platform Issues. The general approach for upgrading HADB is the same on both Solaris and Linux operating systems.
HADB Upgrade
This section describes how to perform an upgrade of HADB from Java ES Release 3 to Java ES Release 4 on both the Solaris and Linux platform. The section covers the following topics:
Pre-Upgrade Tasks
Before you upgrade HADB you should perform the tasks described below.
Verify Current Version Information
You can verify the current version of HADB using standard version checking utilities. For example:
Solaris:
pkgparam -v SUNWhadba
Linux:
rpm -qi sun-hadb-a-4.4.2-7.i386.rpm
Upgrade HADB Dependencies
It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Java ES Release 4. The upgrade of HADB to Release 4 depends on J2SE 5.0 or later.
Back Up Directory Data
The HADB upgrade from Java ES Release 3 to Java ES Release 4 does not in itself modify HADB dynamic data. However, you can back up the Java ES Release 3 packages in case you need to roll back the upgrade.
Obtain Required Configuration Information and Passwords
HADB upgrade requires you to know the superuser password.
Upgrading 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 Java ES Release 4 takes into account the following considerations:
Online Upgrades of HADB
Online upgrades of HADB are only available when upgrading from Java ES Release 3.
When you perform an online upgrade of HADB, you first install HADB on each server in the cluster being upgraded. Each server first unregisters from an earlier installation of HADB and then 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.1 2005Q2 High Availability Administration Guide (http://docs.sun.com/doc/819-2555/6n4r9qo7n?a=view).
Offline Upgrades of HADB
An offline upgrade of HADB is available when upgrading from either Java ES Release 3.
To perform an offline upgrade, shut down your HADB services and replace the existing HADB packages with the newer versions available from your Java Enterprise System Release 4 distribution, shown in Table 7-4.
Use the below procedures.
To upgrade packages for shared components on Solaris platforms
- Log in as superuser or become superuser by using the su - command.
Note
Become superuser with su -, not su, to make sure you obtain the complete superuser environment.
- Navigate to the location of the packages in your Java ES Release 4 distribution.
The packages are found under one of the following directories, depending on your platform:
Solaris_sparc/Product/shared_components/Packages/
Solaris_x86/Product/shared_components/Packages/
Note
If you have a subset distribution of Java Enterprise System, this subset distribution contains all the necessary shared components at the location indicated above.
- Remove the current versions of the packages that you are upgrading by using the pkgrm command.
For example, to remove packages for HADB:
pkgrm SUNWhadba SUNWhadbc SUNWhadbe SUNWhadbi SUNWhadbj SUNWhadbm SUNWhadbo SUNWhadbs SUNWhadbv SUNWhadbx
For detailed information on removing packages, refer to the pkgrm(1m) man page.
- Install the packages from your distribution using the pkgadd command.
For example, to install packages for HADB:
pkgadd SUNWhadba SUNWhadbc SUNWhadbe SUNWhadbi SUNWhadbj SUNWhadbm SUNWhadbo SUNWhadbs SUNWhadbv SUNWhadbx
For detailed information on removing packages, refer to the pkgadd(1m) man page.
- Verify that the package is correctly installed using the pkgparam and pkginfo commands.
Use pkgparam with the -v option to verify the version. pkginfo provides provides additional information about the package.
For detailed information on these commands refer to the pkgparam(1) and pkginfo(1) man pages.
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 -V
For example, on the Solaris 8 platform:
HADB-base/bin/ma -V
Sun Java System High Availability Database 4.4 Database Management Agent Version : 4.4.2.7 [V4-4-2-7 2005-05-26 13:49:01 server@domain] \(SunOS_5.8_sparc)
- Check whether the database is running by issuing the commands in the following example for a database named ExampleDB:
HADB-base/bin/hadbm status -n databaseName
HADB-base/bin/hadbm list
Database
ExampleDB
HADB-base/bin/hadbm status ExampleDB
Database Status
ExampleDB FaultTolerant
HADB-base/bin/hadbm status -n ExampleDB
NodeNo HostName Port NodeRole NodeState MirrorNode
0 sungod012 15000 active running 1
1 sungod012 15020 active running 0
All HADB services for listed nodes should in the “running” state.
- Verify that all products using HADB are using the new HADB path by issuing the command in following example for a database named ExampleDB:
HADB-base/bin/hadbm get PackageName ExampleDB
Attribute Value
PackageName V4.4.2.7
The above command displays the current version of HADB. For a detailed listing, issue the following command:
hadbm get --all ExampleDB
Post-UpgradeTasks
There are no post-upgrade tasks beyond the steps described in Upgrading HADB from Java ES Release 3.
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 previously had installed. Use the same procedure described in Rolling Back the Upgrade. There is no data or configuration files that need to be changed.