Verifying General Installation Prerequisites

1. Plan your 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 Installation Guide for UNIX.

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 Communications Suite 5 Release Notes and the Sun Java Enterprise System 5 Release Notes for UNIX. These notes contain installation issues that might pertain to your deployment.

3. Survey your hosts for existing software. 

Refer to Surveying Existing Hosts.

If you need to upgrade Communications Suite product components, refer to the Sun Java Communications Suite 5 Upgrade Guide. If you need to upgrade Java ES product components, refer to the Sun Java Enterprise System 2006Q3 Upgrade Guide.

4. Upgrade any existing components that are incompatible with the Communications Suite 5 release. 

When Incompatible Components Are Installed

Sun Java Communications Suite 5 Upgrade Guide

Sun Java Enterprise System 2006Q3 Upgrade Guide

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.

Sun Java Communications Suite 5 Release Notes and 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

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. 

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, rpm -i, or swinstall to add the packages.

12. If you are installing a communications product 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: domain mycomputer.company.com

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

  # domainname fully_qualified_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 the second column returned by getent hosts for your target system contains the FQDN rather than the simple hostname.

For example: 

getent hosts ip-address

15. When installing the Load Balancing Plugin with Apache Web Server, Apache Web Server must be installed and configured before beginning installation.  

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

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

16. 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. 

For more information, see the Sun Java System Access Manager 7.1 Postinstallation 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: 

Solaris OS: /opt/SUNWwbsvr7

Linux: /opt/sun/webserver7

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 2006Q3 Upgrade Guide.

19. If you are implementing Messaging Server, verify that sendmail is disabled.

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

/etc/init.d/sendmail stop

If needed, disable sendmail on Solaris 10 as follows: 

svcadm disable sendmail

20. 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

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

22. 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

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

To install Korn shell, go to the RPM directory and run the rpm –i pdksh command.