Sun Java Enterprise System 2005Q4 Installation Planning Guide

Other Installation Issues

This section lists a number of specific issues that occur in some solutions with references to detailed information.

Table 3–3 Installation Issues to Consider

Solution Requires 

Guidelines or Instructions 

Using Solaris 10 zones 

If you will be installing into Solaris 10 zones, refer to Solaris 10 Zones in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.

Using Directory Server encryption 

Configuring LDAPS (SSL over LDAP) on the Directory Server instance 

Note: If Directory Server encryption is a requirement, Administration Server must be installed when Directory Server is installed. 

Using a third-party web container with Access Manager

Third-party web containers (BEA WebLogic Server or IBM WebSphere Application Server) can be used with Portal Server and Access Manager. These containers must be installed and running before installing any Java ES components that depend on them.

To use a third-party web container for Access Manager SDK, you must configure Access Manager SDK manually after installation. See Access Manager SDK With Container Configuration Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

Note: Portal Server can only use third-party web containers on Solaris OS. 

Note: Access Manager and Portal Server should use the same type of web container. 

Using Apache Web Server for load balancing plugin

The Apache Web Server can be used with the Application Server load balancing plugin. In this case, the Apache Web Server must be installed and running before installing any Java ES components that depend on it. For additional information, refer to Installation Prerequisites in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.

Using Schema 1 LDAP

An installation example based on LDAP Schema 1 is described in Calendar-Messaging Schema 1 Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX. For a Schema 1 deployment, you cannot use Access Manager.

Configuring single user entry and single sign-on

Procedures for setting up single sign-on, can be found in the Chapter 8, Configuring and Using Single Sign-On, in Sun Java Enterprise System 2005Q1 Deployment Example Series: Evaluation Scenario. Access Manager is required for single sign-on.

Configuring High availability using HADB 

An example of setting up HADB for high availability is contained in Web and Application Services Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.

Application Serverload balancing 

An example that includes using the Application Server load balancing plugin is contained inWeb and Application Services Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.

Non-root ownership 

If non-root ownership will be required for Application Server or Web Server, refer to one of the following examples:

Access Manager Configured to Run as a Non-root User Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX, or

Portal Server on a Non-root Owned Web Server or Application Server Instance Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.