test

Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

Chapter 1 Preparing for Installation

This chapter provides information that will help you install the Sun JavaTM Enterprise System (Java ES) software. Before starting the tasks documented in this guide, you should have already planned your installation according to the Sun Java Enterprise System 2005Q4 Installation Planning Guide

This chapter contains the following sections:

How the Java ES Installer Works

Sun JavaTM Enterprise System (Java ES) integrates a number of Sun server-side products into a system that provides the server software needed to support distributed enterprise applications. In this document, these products are referred to as the Java ES components. A single installer is provided for installing the Java ES components in various combinations. Because of the complex interrelationships of these components, installation requires much more preinstallation and postinstallation effort than is required to install a single component

This section contains the following subsections:

Java ES Components Used in This Release

The Java ES software associated with the 2005Q4 release includes the following selectable components. (The abbreviated names used in this guide follow the name and version.)

To see the full list of services and subcomponents as displayed in the Java ES installer, refer to Appendix A, Java ES Components for This Release. This appendix also lists the shared components that are provided with this release.

Installer Modes

The Java ES installer is an installation framework that uses the Solaris pkgadd or Linux rpm utility to transfer Java ES software to your system. You can install Java ES interactively or by means of a reusable script.

Tip –

You can run the Java ES installer without installing software. This is useful for creating state files for a silent installation or for surveying Java ES software on your existing hosts.

Language Selection

The interactive installer runs in the language specified by the operating system locale setting. The following languages are available:

If your operating system language is not listed, the installer runs in English.

The installer automatically installs English versions of all Java ES components. In addition, you can choose to install component packages in any of the languages listed. During an installation session, the language you choose applies to all the components you are installing. To install some components in one language and other components in another language, you must run the installer multiple times.

On Solaris OS, if your operating system language is on the list, that language is automatically selected for component installation. However, you can change this selection.

The Java ES installer cannot install additional language packages for previously-installed components. However, you can use the pkgadd or rpm utility to add language packages at any time.

Preexisting Component Check

During installation, the Java ES installer surveys the software that is already installed on the host where you are installing and identifies the following:

Dependency Check

Many components depend on the presence of other components to provide their core functions. The installer does extensive cross checking of components to verify that the components you select during installation will function properly together. For this reason, the installer might prompt you to include certain components as you make your component selections.

In general, the Java ES installer uses the following rules for handling dependencies among the Java ES components:

Configuration Options and Parameter Settings

Many Java ES component products require some degree of installation-time configuration. The extent of installation-time configuration you perform depends on which components you select and which installation option you choose.

The following configuration options are available in the installer:

Common server settings are parameters that multiple components use. For example, most components require that you specify an administrative ID and password. By setting these common values, you are setting default values for all component administrative IDs and passwords. Component settings are parameters that apply to a particular component. These settings are requested during installation only if you have selected the Configure Now option. Some of these settings are populated from the common server settings.

Uninstaller

Java ES provides an uninstallation program for removing component products that were installed on your local host using the Java ES installer. The Java ES uninstaller checks product dependencies for the host on which it is running, issuing warnings when it discovers a dependency.

The uninstaller can be run in graphical, text-based, or silent mode.

After Java ES installation is complete, the uninstaller is located here:

Surveying Existing Hosts

Before installation, it is important to know what resides on the hosts where you plan to install the Java ES software. If you have ordered a new Solaris system that has Java ES software preloaded, you do not need to survey your host. However, if your existing hosts have versions of Java ES components already installed, you might need to upgrade or remove some software before running the Java ES installer.

This section contains the following subsections:

When Java ES Software Is Preloaded on Solaris OS

If you ordered a Sun Solaris hardware system with preloaded software, the installation image for the Java ES software has already been copied to your system.

If Java ES software is preloaded on a host, the following directory exists:

/var/spool/stage/JES_05Q4_architecture/

The architecture variable indicates the system’s hardware architecture, such as, SPARC or x86.

You will need to expand the installation image and use the Java ES installer to install and configure the preloaded Java ES software as described in this manual. Although there are no preexisting Java ES components installed on the host, you will still need to plan your installation sequence.

Note –

If your preloaded Java ES software is on a Solaris 10 system, refer to Solaris 10 Zones before expanding the installation image.

When Incompatible Components Are Installed

During installation, the installer verifies that any Java ES components that are already installed on the host are compatible with the release of Java ES you are installing. If some components are not compatible, your installation is likely to be interrupted by incompatibility error messages. Therefore, it is important to survey installed software and do any upgrading before running the Java ES installer.

Note –

The Java ES installer does not upgrade selectable components during installation, with one exception: when Application Server and Message Queue have already been installed with the Solaris OS, the installer asks if you want to upgrade the components during installation.

The Java ES installer upgrades or installs any shared components that are required for the selectable components you are installing.

Using the Installer to Survey Installed Software

You can use Solaris commands such as prodreg and pkginfo or the Linux rpm command to examine installed software. You can also use the installer itself to examine package-based software installations as described in the procedures in this section.

Note –

Do not rely only on the Java ES installer for information about installed software. You must also perform an independent survey of the host to determine what software is currently installed.

ProcedureTo Provide Access to Your Local Display for the Graphical Installer

Steps

  1. Set your DISPLAY environment variable.

    If you are logging in to a remote host, make sure your DISPLAY environment variable is properly set to the local display. If the DISPLAY variable is not set properly, the installer runs in text-based mode.

    • Example for C Shell (host name myhost):


      setenv DISPLAY myhost:0.0

    • Example for Korn Shell (host name myhost):


      DISPLAY=myhost:0.0

  2. Grant display authorization.

    You might need to grant display authorization to run the installer on your local display. For example, you can use the following command to grant display authority from myhost to the root user on serverhost:


    myhost\> xauth extract - myhost:0.0|rsh -l root serverhost xauth merge -
    Note –

    For full instructions on granting such authorization safely, refer to the “Manipulating Access to the Server” chapter in the Solaris X Window System Developer's Guide.

ProcedureTo Use the Installer for Identifying Upgrade Issues

Steps

  1. On each host, start the installer using the -no option to indicate that this is not an active installation:

    For the graphical installer:


    ./installer -no

    For the text-based installer:


    ./installer -nodisplay -no

  2. Proceed to component selection.

  3. Select the components you are planning to install on this host.

    The Status column indicates products that are required for the components you have selected.

  4. If an incompatible version of a selectable component is detected by the installer, you are prompted to upgrade or remove the incompatible version.

    After resolving the problem, you can refresh the selection list, make your selection, and then ask the installer to proceed.

  5. If an incompatible version of a shared component is detected by the installer, the Shared Component Upgrades Required list is displayed.

    For each shared component listed, review the Installed Version against the Required Version to determine if any upgrading will need to be done. You must determine whether the newer Java ES versions of shared components are compatible with other installed applications on the host.

  6. Exit the installer and do any upgrading necessary.

  7. Repeat the procedure for each target host.

    Note –

    The installer detects the Directory Server version that is distributed with the Solaris OS and warns you that the Directory Server script belonging to the Solaris distribution will be renamed by the installer. No action is required.

Determining If Your Hosts Are Ready

Before you start the installer, review the issues in this section.

System Requirements

Before you install Java ES, ensure that the hosts in your system meet the minimum hardware and operating system requirements. For the latest information on the supported platforms and software and hardware requirements, refer to “Hardware and Software Requirements” in the Sun Java Enterprise System 2005Q4 Release Notes.

If the operating system found on the host does not satisfy Java ES recommendations, the installer cannot proceed. You must resolve this problem before installation.

Access Privileges

To install Java ES software, you must be logged in as root, or become superuser.

Memory and Disk Space Requirements

The installer runs a check to determine if your host has sufficient memory and disk space for the components you selected.

Note –

On Solaris 10, memory check is not performed if you are installing into a non-global zone.

Korn Shell Required for Portal Server on Linux

To install and configure Portal Server on Linux, the installer requires that the Korn shell be accessible at /bin/ksh. If your host does not have the Korn shell installed, you can get the Korn shell software by issuing the following command:

up2date pdksh

Determining If You Can Use an Installation Sequence Example

The order in which you install the Java ES components on the hosts of your system is crucial to installation success. You might be able to use one or more of the sequence examples provided in Chapter 2, Example Installation Sequences to guide you. These sequences include the high-level tasks that are required for some typical Java ES installations.

Full instructions for planning your installation are contained in the Sun Java Enterprise System 2005Q4 Installation Planning Guide.

Installation Prerequisites

The following table lists the tasks that you should perform before beginning any type of installation. The left column lists the order in which you should perform the tasks, the middle column describes the action, and the right column contains the location of instructions and other useful information. Not all tasks are required for all installations.

Table 1–1 Preinstallation Checklist

Task 

Instructions and Helpful Information 

1. Plan your Java ES installation. 

Refer to the Sun Java Enterprise System 2005Q4 Installation Planning Guide.

If installing Sun Cluster software, see Sun Cluster Software Example.

2. Determine if any release notes issues affect your installation. 

Before performing any of the procedures described in the Installation Guide, you should read the Sun Java Enterprise System 2005Q4 Release Notes. These notes contain installation issues that might pertain to your deployment.

3. Survey your hosts for existing software. 

Refer to Surveying Existing Hosts.

4. Upgrade any existing components that are incompatible with Java ES 2005Q4. 

When Incompatible Components Are Installed

prodreg, pkginfo, or rpm command. For usage information, refer to their man pages.

Sun Java Enterprise System 2005Q4 Upgrade Guide

5. Verify that system requirements are met. 

Refer to Determining If Your Hosts Are Ready.

Sun Java Enterprise System 2005Q4 Release Notes

6. Determine if an installation sequence example can be used. 

Refer to Chapter 2, Example Installation Sequences.

7. For a Configure Now installation, gather configuration information for components. 

Chapter 1, Configuration Information, in Sun Java Enterprise System 2005Q4 Installation Reference Provides component configuration information.

Chapter 2, Configuration Worksheets, in Sun Java Enterprise System 2005Q4 Installation Reference Provides worksheets for gathering your data.

8. Make a copy of the product registry file. The backup copy is helpful in recovering if installation a fails. 

On Solaris: /var/sadm/install/productregistry

On Linux: /var/opt/sun/install/productregistry

9. For non-root, create the necessary system accounts. 

To run as a non-root user for Directory Server, Directory Proxy Server, or Administration Server, you must create system accounts before configuring. 

10. If installing components that depend on servers or services that are already installed, ensure that the existing servers and services are accessible. 

For example, If you are installing a Portal Server Secure Remote Access subcomponent, the Secure Remote Access core must be running and accessible. 

11. If installing Directory Server, verify that Perl is installed. 

Solaris: Perl packages (SUNWperl5*) can be found on the Solaris media.

Linux: /usr/bin/perl must be present before installation.

If Perl is not present, use pkgadd or rpm -i to add the packages.

12. If you are installing a communications component, verify that the domain name of the host on which Access Manager will be installed is set. 

To set the domain name, do one of the following: 

  • If the file /etc/resolv.conf exists, enter the fully qualified domain name in the domain configuration entry. Example: mycomputer.company.com

  • If the file /etc/resolv.conf does not exist, enter the following command:

    # domainname fullyqualified_domain_name

13. Verify that the second column in the /etc/hosts file contains the fully-qualified domain name (FQDN) rather than a simple host name. For example:

192.18.99.999 mycomputer.company.com mycomputer loghost

14. Verify that a fully-qualified domain name query works on your system. 

For example: 


host-name install-target-server.sun.com
 

getent host-name install-target-server.sun.com

15. When installing the Load Balancing Plugin with Apache Web Server, install and configure Apache Web Server before beginning Java ES installation. (On Linux only, you must first install the Application Server, then install Apache Web Server, and finally install the Load Balancing Plugin.) 

For more information, see Configuring Web Servers for HTTP Load Balancing in the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide.

16. If installing Access Manager for deployment on a third-party web container, you must choose the Configure Later option and run a postinstallation configuration script. 

For more information, see Access Manager Sample Configuration Script Input File in Sun Java System Access Manager 7 2005Q4 Administration Guide.

17. If this is a reinstallation, verify that the Web Server installation directory does not exist. If it does, remove or rename the directory.

Default installation directory for Web Server: 

On Solaris/opt/SUNWwbsvr

On Linux: /opt/sun/webserver

18. If you are upgrading J2SE software, verify that you have stopped other products that depend on the J2SE component you are upgrading. 

Refer to the Sun Java Enterprise System 2005Q4 Upgrade Guide.

19. If Directory Proxy Server will use a preinstalled Configuration Directory Server, ensure that the Configuration Directory Server is running before installing Directory Proxy Server. 

If you are installing Directory Proxy Server and the Configuration Directory Server at the same time, you can skip this task. 

20. If you are implementing Messaging Server or Communications Express, verify that sendmail is disabled.

If needed, disable sendmail on Solaris 8/9 and Linux as follows:

/etc/init.d/sendmail stop

If needed, disable sendmail on Solaris 10 as follows: 

svcadm disable sendmail

Getting the Java ES Software

You can get the Java ES software in the following ways:

For a listing of the distribution bundles for this release, refer to Chapter 4, Java ES Distribution Bundles, in Sun Java Enterprise System 2005Q4 Installation Reference.

Making an Installation Image

The Java ES distribution is designed so that you can easily put the installation files in a shared location. The benefit of this is that the installation files can then be run from this shared location as often as needed.

ProcedureTo Create an Image on Your Network

This section provides instructions for making a Solaris SPARC installation image available on your site network.

Steps

  1. Log in as root or become superuser.

  2. Create a shared directory on your network. For example:


    mkdir shared-location/java_ent_sys_2005Q4

  3. Access your installation files from the web site, the CD, or the DVD, then prepare the installation files to be shared.

    1. Create an installation image from the mounted ISO image. For example:

      Note –

      Installation cannot be done directly from a mounted ISO image. Instead, the image must be copied onto your network.


      unzip java_es_05Q4-ga-solaris-sparc-1-iso.zip
lofiadm -a pathname/java_es_05Q4-ga-solaris-sparc-1.iso /dev/lofi/1

      If /dev/lofi/1 is already in use, refer to the lofiadm (1M) man page.


      mkdir mountpoint
mount -F hsfs /dev/lofi/1 mountpoint
cd mountpoint
find . -print | cpio -pdum shared-location/java_ent_sys_2005Q4

      After copying is done, unmount the ISO image:


      cd
umount mountpoint
lofiadm -d /dev/lofi/l

      Repeat this step for the remaining ISO images.

    2. Create an installation image from the CD or DVD. For example:


      cd /cdrom/cdrom0
find . -print | cpio -pdum shared-location/java_ent_sys_2005Q4

      Repeat this step for the remaining CDs.

    3. Create an installation image from the compressed archive. For example:


      cd shared-location/java_ent_sys_2005Q4
unzip pathname/java_sys_2005Q4-ga-solaris-sparc-1.zip

      Repeat this step for the remaining compressed archive files.

    Note –

    If you copy files for multiple platforms to the shared location, you will receive a query similar to the following in relation to the README file and the COPYRIGHT file:

    File already exists. OK to overwrite?

    Type Yes. These files are identical for all platforms.