Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

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


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:

  • 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: mycomputer loghost

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

For example: 


getent host-name

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