Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX 

Chapter 17
Monitoring Console

This chapter describes how to upgrade Monitoring Console to Java ES 5 Update 1 (Release 5U1): Monitoring Console 1.0 Update 1. It covers only upgrade from Java ES 5.

The chapter provides an overview of upgrade considerations for the different upgrade paths supported by Release 5U1. The chapter covers upgrades on both the Solaris and Linux operating systems:

Overview of Monitoring Console Upgrades

This section describes the following general aspects of Monitoring Console that impact upgrading to Java ES 5 Update 1 (Release 5U1):

About Release 5U1 Monitoring Console

Release 5U1 Monitoring Console is a maintenance release that fixes bugs in Release 5 Monitoring Console and adds a few new features. See the Monitoring Console Release Notes for details. Monitoring Console was first introduced into Java ES with Release 5.

Release 5U1 Upgrade Roadmap

Table 17-2 shows the supported Monitoring Console upgrade paths to Release 5U1. The table applies to both Solaris and Linux operating systems.

Table 17-2 Upgrade Paths to Java ES 5 Update 1 (Release 5U1): Monitoring Console 1.0 Update 1

Java ES Release

Java DB Version

General Approach

Reconfiguration Required

Release 5

Monitoring Console 1.0

Maintenance upgrade. Apply patches.

None

Monitoring Console Data

The following table shows the type of data that could be impacted by an upgrade of Monitoring Console software.

Table 17-3 Monitoring Console Data Usage

Type of Data

Location

Usage

Master agent Configuration data

MonitoringConsoleConfig-base/masteragent.properties

Configuration of Monitoring Framework Master Agent

Console node list

MonitoringConsoleConfig-base/nodelist

List of the hosts displayed in the console

Console user preferences

MonitoringConsoleData-base/userPrefs/master_agent

User preferences

Monitoring rules

MonitoringConsoleData-base/persistence/threshold/ma

Monitoring rules

Monitoring Console Upgrade Strategy

Your strategy for upgrading Monitoring Console 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 Monitoring Console by presenting issues that might influence your Monitoring Console upgrade plan.

Compatibility Issues

Release 5U1 Monitoring Console is backwardly compatible with the Release 5 version.

Dependencies

Monitoring Console has a dependency on a number of shared components (see Table 1-10).

Dual Upgrade

Dual upgrades, in which both Monitoring Console and operating system are upgraded (as described in Dual Upgrades: Java ES and Operating System Software) do not apply to Release 5U1 Monitoring Console.

Upgrading Monitoring Console from Java ES 5

This section includes information about upgrading Monitoring Console from Java ES 5 (Release 5) to Java ES 5 Update 1 (Release 5U1). The section covers the following topics:

Introduction

When upgrading Release 5 Monitoring Console to Release 5U1, consider the following aspects of the upgrade process:

Release 5 Monitoring Console Upgrade

This section describes how to perform an upgrade of Monitoring Console from Java ES Release 5 to Release 5U1 on both the Solaris and Linux platform. Where a topic depends on platform-specific procedures, the topic will indicate the operating system to which it applies. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Monitoring Console software you should perform the following tasks:

Verify Current Version Information

You can verify the current version of Monitoring Console using the following steps:

  1. Open the Monitoring Console URL in a web browser:

    2. https://MonitoringConsole_Host:6789

  2. Log in as root.
  3. Click the Sun Java System Monitoring Console link.
  4. Click the Version button.

The version information is shown in the following table:

Table 17-4 Monitoring Console Version Verification Outputs

Java ES Release

Java DB Version Number

Release 5

1.0

Release 5U1

1.0U1

Upgrade Monitoring Console Dependencies

It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. Release 5U1 Monitoring Console has a hard upgrade dependency on the SJWC and MFWK shared components, which therefore need to be upgraded before upgrading Monitoring Console.

Back Up Monitoring Console Data
Upgrade of Monitoring Console to Release 5U1 does not require the reconfiguration of Monitoring Console software. Therefore backup of Monitoring Console data is optional.
Obtain Required Configuration Information and Passwords

No configuration information or password is required to upgrade Monitoring Console.

Upgrading Release 5 Monitoring Console (Solaris)

This section discusses considerations that impact the upgrade procedure for Monitoring Console, followed by a description of the procedure itself.

Upgrade Considerations (Solaris)

The upgrade of Monitoring Console software to Java ES Release 5U1 takes into account the following considerations:

Upgrade Procedure (Solaris)

The procedure documented below applies to Monitoring Console instances residing locally on the computer where the upgrade is taking place.

  1. Log in as root or become superuser.

    2. su -

  2. Make sure you have upgraded any Java ES components upon which Monitoring Console has hard upgrade dependencies (see Upgrade Monitoring Console Dependencies).
  3. Obtain the latest Monitoring Console upgrade patches, based on Table 17-5.

    4. To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to /workingDirectory.

  4. Apply the appropriate Monitoring Console core and, if needed, localization patches in Table 17-5, in that order.

    5. patchadd /workingDirectory/patch_ID

    Be sure to consult the README.patch_ID file for additional patch installation instructions.

  5. Confirm that the patch upgrades were successful:

    6. showrev -p | grep patch_ID

    The output should return the versions of patch IDs applied in Step 4.

  6. Undeploy the Release 5 Monitoring Console web application.

    7. /usr/sbin/wcadmin undeploy -a jesmc -x /jesmc

  7. Deploy the Release 5U1 Monitoring Console web application

    8. /usr/sbin/wcadmin deploy -a jesmc -x /jesmc MonitoringConsole-base

  8. Restart Release 5U1 Monitoring Console.

    9. /usr/sbin/smcwebserver restart

Upgrading Release 5 Monitoring Console (Linux)

This section discusses considerations that impact the upgrade procedure for Monitoring Console, followed by a description of the procedure itself.

Upgrade Considerations (Linux)

The upgrade of Monitoring Console software to Java ES Release 5U1 on the Linux platform takes into account the same considerations as on the Solaris platform (see Upgrade Considerations (Solaris)), except that the Linux Release 5U1 upgrade patches differ from the Solaris patches.

The Release 5U1 Monitoring Console upgrade patches for Linux OS are shown in the following table:

Table 17-6 Patches1 to Upgrade Monitoring Console on Linux 

Description

Patch ID and RPM names

Monitoring Console core

125452-06

  • sun-jesmc-1.0-108.i386.rpm
  • sun-jesmcr-1.0-108.i386.rpm
  • sun-mfwk-ma-2.0-108.i386.rpm

Monitoring Console localization

126291-05

  • sun-jesmc-1.0-13.i386.rpm

1Patch revision numbers are the minimum required for upgrade to Release 5U1. If newer revisions become available, use the newer ones instead of those shown in the table.

Upgrade Procedure (Linux)

The procedure documented below applies to Monitoring Console instances residing locally on the computer where the upgrade is taking place.

Caution

An upgrade from Release 5 to Release 5U1 on Linux cannot easily be rolled back.

  1. Log in as root or become superuser.

    2. su -

  2. Make sure you have upgraded any Java ES components upon which Monitoring Console has hard upgrade dependencies (see Upgrade Monitoring Console Dependencies).
  3. Obtain the latest Monitoring Console upgrade patches, based on Table 17-6.

    4. To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to /workingDirectory.

  4. Apply the core and, if needed, localization patch for Monitoring Console in Table 17-6, in that order.

    5. cd /workingDirectory/patch_ID
    ./installpatch

    If installpatch reports any errors, you will need to resolve the reported errors and run installpatch again.

    Be sure to consult the README.patch_ID file for additional patch installation instructions.

  5. Confirm that the patch upgrades were successful.

    6. rpm -qa | grep sun-jesmc

    The new version numbers of the RPMs should be returned.

  6. Undeploy the Release 5 Monitoring Console web application.

    7. /usr/sbin/wcadmin undeploy -a jesmc -x /jesmc

  7. Deploy the Release 5U1 Monitoring Console web application

    8. /usr/sbin/wcadmin deploy -a jesmc -x /jesmc MonitoringConsole-base

  8. Restart Release 5U1 Monitoring Console.

    9. /usr/sbin/smcwebserver restart

Verifying the Upgrade

You can verify successful upgrade of Monitoring Console using the following steps:

  1. Open the Monitoring Console URL in a web browser:

    2. https://MonitoringConsole_Host:6789

  2. Log in as root.
  3. Click the Sun Java System Monitoring Console link.
  4. Click the Version button.

See Table 17-4 for output values.

Post-Upgrade Tasks

No post-upgrade tasks are required when upgrading Release 5 Monitoring Console to Release 5U1.

Rolling Back the Upgrade (Solaris)

This section describes the Release 5U1 upgrade rollback procedure for Monitoring Console on the Solaris platform.

  1. Log in as root or become superuser.

    2. su -

  2. Remove the patches in Table 17-5.

    3. patchrm patch_ID

  3. Undeploy the Release 5U1 Monitoring Console web application.

    4. /usr/sbin/wcadmin undeploy -a jesmc -x /jesmc

  4. Deploy the Release 5 Monitoring Console web application

    5. /usr/sbin/wcadmin deploy -a jesmc -x /jesmc MonitoringConsole-base

  5. Restart Release 5 Monitoring Console.

    6. /usr/sbin/smcwebserver restart

Rolling Back the Upgrade (Linux)

This section describes the Release 5U1 upgrade rollback procedure for Monitoring Console on the Linux platform. There is no automated rollback procedure for Linux patches, so the recommended approach is to manually overwrite the Release 5U1 RPMs with the Release 5 RPMs, as described below.

  1. Log in as root or become superuser.

    2. su -

  2. Check the revision numbers of Monitoring Console RPMs.

    3. rpm -qa | grep sun-jesmc

    The updated RPMs should be those listed in Table 17-6.

  3. Check to see if the RPMs have been relocated from their default location.

    4. rpm -q --queryformat '%{INSTALLPREFIX}' rpmName

    where rpmName is the unique name of the RPM (for example, the values sun-jesmc-* shown in Table 17-6). The command returns a prefixValue as a path to the installed RPM.

  4. Reinstall Release 5 RPMs from the Java ES 5 distribution.

    5. (If you are rolling back to a post-Release 5 sustaining patch, rather than to Release 5, reinstall the RPMs from that patch.)

    rpm -Uvh --force [--prefix prefixValue] *.rpm

    The --force option will allow the command to overwrite later packages of the same name. The --prefix option is not required unless the RPMs have been relocated. (If only a subset of the RPMs had been relocated, use individual file names as command arguments rather than *.rpm.)

  5. Undeploy the Release 5U1 Monitoring Console web application.

    6. /usr/sbin/wcadmin undeploy -a jesmc -x /jesmc

  6. Deploy the Release 5 Monitoring Console web application

    7. /usr/sbin/wcadmin deploy -a jesmc -x /jesmc MonitoringConsole-base

  7. Restart Release 5 Monitoring Console.

    8. /usr/sbin/smcwebserver restart



Previous      Contents      Index      Next     

Part No: 820-2510-10
November 2007.   Copyright 2004 Sun Microsystems, Inc. All rights reserved.