|
| |
| Sun Java Enterprise System Upgrade Guide for HP-UX | |
Chapter 2
Upgrading Java ES Shared ComponentsThis provides information on upgrading shared components for Sun Java™ Enterprise System (Java ES) 2005Q4 release. This chapter contains the following sections:
Shared Component Upgrade OverviewUpgrading shared components for Java ES 2005Q4 (Release 4) should be done as part of a larger upgrade plan, as discussed in Chapter 1, "Planning for Upgrades". To ensure that you have a successful upgrade, read Chapter 1 carefully and prepare an upgrade plan that meets your needs.
About Your Upgrade Plan
Your upgrade plan should cover the following areas:
- Operating System Issues. Perform any operating system upgrades, as described in Operating System Issues before you upgrade shared components.
- Upgrade Path. Determine which version of Java Enterprise System you currently have and make sure you understand the supported path to upgrade to Java ES Release 4. Procedures that depend on a specific upgrade path are noted in this chapter. For more information on upgrade path, refer to Upgrade Paths.
- Upgrade Dependencies. Understand the interdependencies of the components you are upgrading. Typically, you sequence the upgrade of product components according to their dependencies. For example, before you upgrade a component you upgrade any component upon which it depends. There are various other factors to consider, such as hard and soft dependencies, as explained in Upgrade Dependencies.
Use Table 1-6 to determine which shared components need to be upgraded before you upgrade product components.
- Upgrade All or Selective Upgrade. If you are upgrading all product components on a computer, then you should upgrade all shared components upon which the product components depend. However, when upgrading from Release 3 to Release 4, you can selectively upgrade some product components on a computer without upgrading others. In this scenario, best practice is to upgrade all shared components upon which all product components on the computer depend.Nevertheless, best practice is to upgrade all shared components upon which all product components on the computer depend. Release 4 shared components are certified to support Release 3 product components. For more information, refer to Shared Component Upgrade Guidelines.
- Sequencing Guidelines. Review the sequencing guidelines listed in General Sequencing Guidelines. Typically, shared components are upgraded first. However, you should understand the entire sequence of your upgrade to Java ES Release 4 before beginning your upgrade process.
Technologies for Upgrading Shared Components
There are three technologies for upgrading shared components to Java ES Release 4. The technologies you use depend on the number and type of shared components you are upgrading, according to your upgrade plan.
If your upgrade plan calls for upgrading a few shared components, then you might consider applying individual patches to those components for which upgrade patches are available.
Table 2-1 shows the upgrade patches that are available for each shared component. Upgrading Shared Components by Applying Patches provides instructions for downloading and applying patches.
Table 2-1 shows the shared components that use replacement of packages when upgrading to Java ES Release 4. Upgrading Components by Replacing Packages provides details on replacement of packages.
General Upgrade Procedure
The general steps you take to upgrade shared components are listed below:
- From your upgrade plan, determine your upgrade path, the shared components you wish to upgrade, and the sequence for upgrading them. Review the earlier sections in this overview for information on developing an upgrade plan. You can also refer to Upgrade Planning for additional information.
- Determine the upgrade technologies available to upgrade the shared components listed in your upgrade plan.
You can find this information in the following section:
Upgrading Shared Components from Java ES Release 3
- Depending on your specific needs, follow the procedures in the following section:
Upgrading Shared Components from Java ES Release 3
Table 2-1 below shows the upgrade technologies to use when upgrading shared components from Java ES (Release 3). Please note the following different upgrade options that are available:
- In many cases, you apply specific patches to upgrade shared components to Java ES Release 4.
- In some cases, you replace packages Release 3 packages with Release 4 packages provided with the Java ES distribution.
- For shared components that have not changed since Release 3, no upgrade is necessary.
Note
In Table 2-1, the trailing two digits in the patch ID specify the revision number for the patch. A higher revision number indicates a newer version.
Release 4 Shared Components specifies the full name of shared components listed in Table 2-1.
Upgrading Shared Components by Applying PatchesOn HP-UX platforms, many packages for shared components can be upgraded from Java ES 2005Q1 (Release 3) by application of patches that modify the installed packages.
The advantage of patch technology over replacement of packages is that revisions applied by a patch can later be backed out, if needed. Typically, the size of a patch is smaller than the size of an updated package, so it is easier to download and install. Patches are generally more current than the latest available package. The most current revision of a patch is readily available for download from SunSolve, as described in this section.
Table 2-1 shows the patch IDs for all shared component patches used to upgrade to Java ES 2005Q4 (Release 4) from Java ES Release 3.
If your upgrade plan calls for upgrading only a few shared components, you probably want to apply individual patches as described in the following procedure. You can later back out patches you apply, as described following the procedure.
To apply a patch to upgrade to Java ES 2005Q4
- Retrieve the patch from the following location:
Table 2-1 lists the available patch IDs to upgrade each shared component.
- Log in as superuser or become superuser by using the su - command.
- Before applying the patch, read any special instructions in the README supplied with the patch.
- Apply the patch using the swinstall command, as indicated in the following example, which applies the patch to the NSPR shared component:
swinstall 121502-01
For information on the swinstall command, refer to the swinstall man page.
To back out a patch you previously applied
- Log in as superuser or become superuser by using the su - command.
- Back out the patch using the swremove command, as indicated in the following example, which backs out the patch to the NSPR shared component:
swremove 121502-01
- For information on the swremove command, refer to the swremove man page.
Upgrading Components by Replacing PackagesMany shared components do not use patch technology to upgrade to Java ES 2005Q4 (Release 4). Instead, you upgrade these components by installing new packages or replacing existing packages with newer versions of the packages. In a few cases, you run special procedures to properly upgrade a shared component.
Upgrade Strategy for Replacement of Packages
The number of shared components you upgrade depends on your upgrade plan and the Java ES components installed on your computer.
For upgrades from Java ES Release 3, you might be either upgrading all components or doing a selective upgrade of product components to Release 4. While you can choose to upgrade only those Java ES shared components needed to support the product components you select to upgrade, it is advisable to upgrade all shared components on your computer. For more information, refer to Shared Component Upgrade Guidelines.
Note
The sequence of upgrading shared components is determined by component interdependencies, which should be reflected in your upgrade plan.
Upgrade Path
The procedures for upgrading shared components by replacement of packages generally do not depend on your upgrade path.
However, the section Packages for HP-UX Platforms contain tables that specify the few instances where the upgrade path determines the procedures you use.
Package Versions
When replacing packages, you should only replace packages with newer versions of those packages. The section Packages for HP-UX Platforms provides information on how to compare package versions before upgrading.
Package Locations
The packages for upgrading most shared components are provided with your Java ES distribution under one of the following directories, depending on your platform:
HPUX_PA-RISC/Product/shared_components/Packages
Localized versions of shared component packages can be found in the following directory:
HPUX_PA-RISC/Product/shared_components/Packages/locale/
Procedures for Replacement of Packages
With few exceptions, packages can be replaced following general procedures. Refer to Upgrading Packages for HP-UX Platforms for procedure.
Special Instructions
Some packages have special instructions for preserving configuration information or other data. Links to special instructions are contained in the package tables listed in the section Packages for HP-UX Platforms.
Packages for HP-UX Platforms
Table 2-2 below lists the HP-UX depot names for shared components that can be upgraded by replacement of packages. The table also lists the versions of the packages available in Java ES Release 4 and special instructions for upgrading the component.
For each shared component, the packages are listed in the sequence you would install them.
You should only replace packages with newer versions. Before you replace a package, compare the version of the package on your system with the version of the package you intend to use to replace it.
To determine the version of an installed package use the swlist command. The output of this command provides the package version.
swlist -a revision <depot name>
Note
The versioning system for different packages varies, but generally a higher number indicates a newer version of the package.
Release 4 Shared Components specifies the full name of shared components listed in Table 2-2.
Upgrading Packages for HP-UX Platforms
The following procedure shows the general instructions for upgrading packages on HP-UX platforms by replacement of depots.
A few shared components require special instructions in addition to these general instructions. Table 2-2 provides special instructions for components that require them.
To upgrade packages for shared components on HP-UX platforms by replacement of depots
- 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.
- Check Table 2-2 for special instructions that might apply to the component you are upgrading.
Follow any special instructions before upgrading the package. If no special instructions are indicated, proceed to the next step.
- Navigate to the location of the packages in your Java ES Release 4 distribution. The packages are found under one of the following directories:
HPUX_PA-RISC/Product/shared_components/Packages
HPUX_PA-RISC/Product/shared_components/Packages/locale
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 swremove command.
For example, to remove packages for webconsole:
swremove sun-mcon sun-mconr sun-mcos sun-mcosx sun-mctag
For detailed information on removing packages, refer to the swremove man page.
- Install the packages from your distribution using the swinstall command.
swinstall sun-mcon sun-mconr sun-mcos sun-mcosx sun-mctag
For detailed information on installing packages, refer to the swinstall man page.
- Verify the version of an installed package use the swlist command. The output of this command provides the package version.
swlist -a revision <depot name>
For detailed information on these commands refer to the swlist man pages.
Upgrading J2SE for Java ES Release 4
Java ES 2005Q4 (Release 4) is certified for Java 2 Platform, Standard Edition (J2SE) Version 5.0.01, identified here as J2SE 5.0. (J2SE 5.0 is sometimes referred to as developer version 1.5.0.01).
Upgrading J2SE on HP-UX Platform
Before proceeding with upgrading J2SE on HP-UX platform, you should determine the version of J2SE currently used by your Java ES installation. For Java ES 2005Q1 (Release 3), the default is J2SE Version 1.5.0. For various reasons, you might have upgraded J2SE from the default versions.
Use the following procedure to determine which version of J2SE your Java ES installation is using.
To display the J2SE version used by your Java ES installation
- Run the following command:
/usr/jdk/entsys-j2se/bin/java -version
- Here is an example of the version string displayed for J2SE 1.4.2.03:
java version "1.4.2.03"
You can upgrade J2SE to 5.0.01 by downloading J2SE 5.0 from the HP-UX Java at:
http://www.hp.com/products1/unix/java/java2/jdkjre5_0/index.html.
Java Enterprise System does not use the default J2SE installed on your computer, but instead maintains a symbolic link to the supported version of J2SE. After installing J2SE you might need to update the Java ES symbolic link so it points to the newly installed J2SE.
The procedures you use to upgrade J2SE depends on whether you are upgrading from J2SE 1.4 or an earlier version of J2SE 5.0. The general steps for HP-UX platforms follow. Details of these steps are in procedures that appear later in this section.
Follow these steps if you are upgrading from J2SE 1.4.2_03
Follow these steps if you are upgrading from an earlier version of J2SE 5.0
Starting and Stopping Services
When upgrading J2SE you might want to shut down any services that depend on the currently installed J2SE before proceeding. This is to avoid any problems that might arise with services that are using the current J2SE. If you do not shut down the services that depend on J2SE, after installing J2SE and setting the Java ES symbolic link to it, you should reboot your system.
Installing J2SE 5.0 on HP-UX Platform
You can install J2SE 5.0.01 on HP-UX platform by using the bits available from the HP website.
To install J2SE 5.0 on HP-UX platform using the HP packages
- Navigate to the following location in the HP website to retrieve the current version of JDK 5.0 and the installation instructions:
http://www.hp.com/products1/unix/java/java2/jdkjre5_0/index.html.
- Follow the instructions for installation available with the download. Before installing J2SE, you might want to stop services that depend on J2SE, as described in Starting and Stopping Services.
- After installation is complete, proceed to the section Setting the J2SE Symlink for Java Enterprise System on HP-UX Platform.
Setting the J2SE Symlink for Java Enterprise System on HP-UX Platform
Java Enterprise System maintains a symbolic link that points to the supported version of J2SE platform. Java Enterprise System maintains this link to ensure that Java ES services can find the correct J2SE runtime to use.
If you upgraded to J2SE 5.0.01 from J2SE 1.4.2_03, then you need to set the symbolic link so it points to the newly installed J2SE 5.0.01. If you upgraded to J2SE 5.0.01 from an earlier version of J2SE 5.0, then you just need to verify that your Java Enterprise System installation is using the updated version.
The following procedures show how to set the Java Enterprise System symbolic link and verify the version of your upgraded J2SE installation.
To Set the J2SE symbolic link for Java Enterprise System on HP-UX
- Reset the /usr/jdk/entsys-j2se symbolic link to point to the newly installed or updated J2SE installation as indicated below:
If you installed J2SE 5.0.01 in the default location, reset the symbolic link as follows:
rm /usr/jdk/entsys-j2se
ln -s /opt/java1.5 /usr/jdk/entsys-j2se
If you installed J2SE 5.0.01 in a non-default location, replace the default path (path /opt/java1.5) with the path to your non-default location.
- If you previously stopped services prior to upgrading or installing J2SE 5.0 Update 4, restart the services.
If you did not stop services prior to upgrading or installing J2SE 5.0 you might want to reboot your system so services that depend on J2SE 5.0 use the new symbolic link.