Java 2 SDK 1.4.2 Installation Notes for Solaris 64-bit

   

  1. First, install the 32-bit Java 2 SDK. Refer to the 32-bit Java 2 SDK Installation Notes .
  2.  

  3. Second, install the supplemental files for 64-bit support using the following 64-bit installation instructions.

64-bit Installation Instructions

install the 32-bit Java 2 SDK

As with the installation of the 32-bit Java 2 SDK, the 64-bit supplemental support is available in two installation formats; use the same installation format as you used for the installation of the 32-bit Java 2 SDK.

Note: For any text on this page containing the following notation, you must substitute the appropriate Java 2 SDK update version number for the notation.
       
               <version>
            
For example, if you are downloading update 1.4.2_01, the following command:
       
               chmod +x j2sdk-1_4_2_<version>-solaris-sparcv9.sh
            
would become:
       
               chmod +x j2sdk-1_4_2_01-solaris-sparcv9.sh
            

Installation of Self-Extracting Binary

Follow these instructions to add 64-bit support to the Java 2 SDK which has already been installed using the self-extracting binary. If you want to install Solaris packages comprising the SDK, see Installation of Solaris Packages.

1. Download the self-extracting binary and check the download file size.

You can download to any directory you choose; it does not have to be the directory where you want to install the J2SE.

Before you download the file, notice its byte size provided on the download page on the web site. Once the download has completed, compare that file size to the size of the downloaded file to make sure they are equal.

2. Make sure that execute permissions are set on the self-extracting binary:

chmod +x j2sdk-1_4_2_<version>-solaris-sparcv9.sh

3. Change directory to the same directory from where you ran the self-extracting binary for the 32-bit install.

This is the directory that contains the j2sdk1.4.2_<version> directory of the 32-bit J2SE. The next step installs the J2SE into the current directory.
4. Run the self-extracting binary.
Execute the downloaded file, prepending the path to it. For example, if the downloaded file is in the current directory, prepend it with " ./":

./j2sdk-1_4_2_<version>-solaris-sparcv9.sh

The binary code license is displayed, and you are prompted to agree to its terms.

The supplemental files for 64-bit support are installed in directories named sparcv9 at several locations within the same j2sdk1.4.2_<version> directory where the 32-bit J2SE was installed.

Installation of Solaris Packages

Use these instructions if you want to use the pkgadd utility to install 64-bit support for the Java 2 SDK.

1. Check the download file size

Before you download a file, notice that its byte size is provided on the download page. Once the download has completed, check that you have downloaded the full, uncorrupted software file.

2. Extract the contents of the compressed tar file:

zcat j2sdk-1_4_2_<version>-solaris-sparcv9.tar.Z | tar -xf -

This will create the SUNWj3dvx, SUNWj3rtx, and SUNWj3dmx packages which contain 64-bit support for the Java 2 SDK.

3. Become root by running su and entering the super-user password.

4. Run the pkgadd command to install the packages.

 

pkgadd -d . SUNWj3rtx SUNWj3dvx SUNWj3dmx

This will install the files for 64-bit support into the Java 2 SDK 1.4.2_<version> installation at /usr/j2se.

5. Delete the tar files and extracted directories.

6. Exit the root shell.

Installation Notes for 64-bit Support

Java 2 SDK, Standard Edition
Version 1.4.2
Solaris (SPARC Platform Edition) Operating System

link

Oracle is reviewing the Sun product roadmap and will provide guidance to customers in accordance with Oracle's standard product communication policies. Any resulting features and timing of release of such features as determined by Oracle's review of roadmaps, are at the sole discretion of Oracle. All product roadmap information, whether communicated by Sun Microsystems or by Oracle, does not represent a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. It is intended for information purposes only, and may not be incorporated into any contract.