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.

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.

To Provide Access to Your Local Display for the Graphical
Installer

Steps

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

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:

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.

To Use the Installer for Identifying Upgrade Issues

Steps

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

Proceed to component selection.

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.

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.

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.

For shared components, most upgrading can be done during installation.

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.

If the memory found on the host does not satisfy Java ES recommendations,
the installer displays a warning. Installation can proceed.

If the disk space found on the host is insufficient, the installer
cannot proceed. You must resolve the problem before you can resume the installation.

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: