Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System Upgrade Guide for Microsoft Windows 

Chapter 7
High Availability Session Store

This 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.

Note

File locations in this chapter are specified with respect to a directory path referred to as HADB-base. At least part of this path might have been specified as an installation directory when HADB was initially installed. If not, the Java ES installer assigned a default value.

The value of HADB-base is in relation to the Application Server directory structure, as follows:

ApplicationServer-base/hadb/version_number

The default value of HADB-base depends on the default value of ApplicationServer-base:

<windows_drive>\Sun\Hadb

Overview of HADB Upgrades

This 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.

Table 7-1  Upgrade Paths to Java ES Release 4: HADB 4.4.2 (2005Q4)

Java ES Release

HADB Version

General Approach

Re-configuration Required

Release 3

HADB 4.4.1 (2005Q1)

Direct upgrade: <apply patches>

None

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

<Hadb\4.4.1-7\lib\mgt.cfg

<Hadb\4.4.1-7\dbdef

<Hadb\4.4.1-7\repository

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 3

This 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:

HADB Upgrade

This section describes how to perform an upgrade of HADB from Java ES Release 3 to Java ES Release 4. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade HADB you should perform the tasks described below.

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.

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 configuration files oc*.cfg files from <Hadb>\Version\lib directory for safety and rollback.

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. Follow the steps:

  1. Stop the HADB service from SCM
  2. Take the backup of *.cfg files from location <HADB-HOME>\4.4.1.7\lib for safety.
  3. Execute the <patch_id>.exe, which installs the patch.
  4. Check the *.cfg files of whose backup has been taken. If the data has been changed, then revert the *.cfg files to their proper locations.
  5. Start the HADB service from SCM.

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.

  1. For all HADB services running, issue either of the following commands:

    2. HADB-base/bin/ma -V

    HADB-base/bin/hadbm -V

    For example, on the Windows 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] \(Win-2000-ix86)

  2. Check whether the database is running by issuing the commands in the following example for a database named ExampleDB:

    3. 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.

  3. Verify that the following registry entry is created in the Windows Registry

    4. <HKEY-LOCAL-MACHINE>\Software\SunMicrosystems\Entsys\installer\patches\<patch id>

Post-Upgrade Tasks

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, execute the uninstall_<patchid>.bat.file.



Previous      Contents      Index      Next     

Part No: 819-4461-10.   Copyright 2006 Sun Microsystems, Inc. All rights reserved.