Verifying Installation Prerequisites

1. Plan your JavaES installation. 

Refer to the Sun Java Enterprise System 5 Installation Planning Guide.

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

If installing Monitoring Console, see Sun Java Enterprise System 5 Monitoring Guide

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

Before performing any of the procedures described in the Installation Guide, you should read the Sun Java Enterprise System 5 Release Notes for UNIX. These notes address installation issues that might affect your deployment.

3. Survey your hosts for existing software. 

Refer to Surveying Existing Hosts.

If you need to upgrade, refer to the Sun Java Enterprise System 5 Upgrade Guide for UNIX

4. Upgrade any existing components that are incompatible with the Java ES 5 release. 

Note: On Solaris OS, existing versions of Application Server and Message Queue can usually be upgraded by the Java ES installer. 

Refer to When Incompatible Components Are Installed.

Refer to the Sun Java Enterprise System 5 Upgrade Guide for UNIX.

For information on using the platform package commands, refer to their respective man pages. 

5. Verify that system requirements are met. 

Refer to Determining If Your Hosts Are Ready.

Refer to Platform Requirements and Issues in Sun Java Enterprise System 5 Release Notes for UNIX,

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 product components. 

Chapter 3, Configuration Information, in Sun Java Enterprise System 5 Installation Reference for UNIX provides product component configuration information.

Chapter 4, Configuration Worksheets, in Sun Java Enterprise System 5 Installation Reference for UNIX provides worksheets for gathering your data.

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

Solaris OS: /var/sadm/install/productregistry

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

HP-UX: /var/adm/sw/productregistry

9. To run as a non-root user for Directory Server, create system accounts before configuring. 

Create the necessary system accounts required for non-root. 

10. If installing product 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, Secure Remote Access Core must be running and accessible. 

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

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

Linux: /usr/bin/perl

HP-UX: /opt/perl/bin/perl

Perl must be present before installation. If Perl is not present, use pkgadd, rpm -i, or swinstall to add the packages.

12. Verify that the second column returned by getent hosts for your target system contains the FQDN rather than the simple hostname.

Run this command: 

getent hosts ip-address

13. If installing the Load Balancing Plugin with Apache Web Server, Apache Web Server must be installed and configured before beginning Java ES installation.  

On Linux only, you must first install Application Server, then install Apache Web Server, and finally install the Load Balancing Plugin. 

HP-UX does not support Apache Web Server. 

If not already done, install and configure Apache Web Server. For more information, see Configuring Web Servers for HTTP Load Balancing in the Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.

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

Note: HP-UX does not support third-party web containers. For Config Now, Linux only supports BEA WebLogic as a third-party web container. 

For more information, see the Sun Java System Access Manager 7.1 Postinstallation Guide.

15. 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: 

Solaris OS: /opt/SUNWwbsvr7

Linux and HP-UX: /opt/sun/webserver7

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

For further information, refer to the Sun Java Enterprise System 5 Upgrade Guide for UNIX.

17. If your host does not have direct connectivity to the Internet, an HTTP proxy needs to be specified. 

An Application Server example can be found in the Sun Java System Application Server Enterprise Edition 8.2 Administration Guide

. 

18. On Linux, remove the /usr/share/bdb/db.jar link if it exists.

19. On Linux, verify that Ant 1.5.2 is not on the host: rpm –qa | grep ant

To remove it:  

rpm –e ant-1.5.2-23 ant—libs-1.5.2-23

20. On Linux, verify that Korn shell is installed. 

If Korn shell is not installed , go to the RPM directory and run the rpm –i pdksh command.

21. On HP-UX, verify that version 5.0 Update 3 of Java is installed before starting the installer. 

To verify the version of the JDK that is installed on your host: 

“swlist Jdk15”

If needed, download and install the correct version of Java from this location: http://www.hp.com/products1/unix/java/

22. On HP-UX, if Web Proxy Server is installed with default settings, verify that user nobody is a valid user.

User ID and group ID of nobody should be a positive value in the /etc/passwd and /etc/group files.

23. Follow any installation sequence guidelines that apply to your installation. 

Refer to Table 2–1