How to Use This Chapter

The example installation sequences in this chapter are intended to provide basic guidelines for doing some common Java ES installations. These are not literal procedures, but instead provide the high-level sequential steps required to implement particular deployment scenarios.

The single-session examples describe typical steps for installing one or a number of Java ES components on a single host in a single installation session. An evaluation example is included.

The remaining examples describe situations where multiple installation sessions are performed on multiple hosts, for a variety of solutions.

For the most part, the sequences in this chapter are based on the relationships among the components as shown in Table 2-2.

At component selection, the Java ES installer identifies incompatible versions of components as well as unmet requirements. You receive warning messages that identify the problem and tell you what you need to do. Many of these messages tell you about requirements that are not yet met. Other messages tell you that incompatible versions of some or all of the components you are trying to install are already on the local host.

Tip

Installation goes smoothly if any incompatible versions of Java ES components are identified and removed or upgraded before starting the installer.

Evaluation Example

This example installs all the Java ES components except Sun Cluster software on a single host in a single installation session.

An evaluation installation is generally considered a trial deployment, a quick installation to see how things go. This example uses the graphical interface and the Configure Now option. When you are presented with configuration pages, you accept defaults wherever possible.

The general steps for this type of installation include the following:

If you are using a remote component to fulfill dependencies, the remote component must be installed and running before installing any components that depend on it.

Access Manager and Portal Server Example

This example installs Portal Server with Access Manager on a single host, with Web Server as the web container.

Requirements

Portal Server requires a local copy of Access Manager or Access Manager SDK. Access Manager can be remote, but Access Manager SDK must be local. Access Manager requires Directory Server, but not necessarily a local copy. Portal Server requires a local web container which in this example is Web Server. Delegated Administrator is automatically installed with Access Manager.

To use a remote copy of Directory Server, deselect Directory Server and specify a remote copy when prompted.

Note

The remote Directory Server must be running before installing any other components. For instructions on installing Directory Server, refer to Directory Server Only Example.

To use a remote copy of Access Manager, deselect Access Manager and specify a remote copy during postinstallation configuration.

Note

The remote Access Manager must be running before installing any other components. For instructions on installing Access Manager, refer toIdentity Management Example.

Resolving incompatibilities

The installer verifies software on your host and provides guidance if incompatibilities are identified.

Selecting the Configure Now or Configure Later option

For the Configure Now option, configuration pages are displayed for those components that allow installation-time configuration. Do not accept defaults for components that are remote; use the remote information.

(Optional) If you are using a remote copy of Directory Server, deselect Directory Server and specify a remote copy when prompted.

Note

The remote Directory Server must be running before installing any other components. For instructions on installing Directory Server, refer to Directory Server Only Example.

Resolving incompatibilities

The installer verifies software on your host and provides guidance if incompatibilities are identified.

Verifying installation directories

Selecting the Configure Now or Configure Later option

For the Configure Now option, configuration pages are displayed for the local components that can be configured during installation. Do not accept defaults for components that are remote; use the remote information.

Message Queue Only Example

This example installs Message Queue by itself.

Requirements

Message Queue has no dependencies on other Java ES components.

Note

If you are using this component with Sun Cluster software, you must perform a precise series of tasks before installing any components. Refer to Sun Cluster Software Example to see Sun Cluster guidelines.

The general steps for this type of installation include the following:

The installer verifies software on your host and provides guidance if incompatibilities are identified.

Solaris OS:

If a previous copy of Message Queue, Platform Edition is detected on the host, the installer will automatically update the installation with Message Queue, Enterprise Edition.

If a previous copy of Message Queue, Enterprise Edition is detected on the host, you must exit the installer and follow the instructions for upgrading to Message Queue, Enterprise Edition in the Java Enterprise System Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062).

Linux:

If a previous copy of Message Queue, (Platform or Enterprise Editions) is detected on the host, you must exit the installer and follow the instructions for upgrading and migrating to Message Queue, Enterprise Edition in the Java Enterprise System Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062).

Portal Server Secure Remote Access Example

This example installs Portal Server Secure Remote Access with Access Manager on a single host, with Web Server as the web container.

Requirements

Portal Server Secure Remote Access requires a local copy of Access Manager or Access Manager SDK. Portal Server Secure Remote Access Core requires a local copy of Portal Server except in case of Gateway, where Portal Server Secure Remote Access does not require a local copy of Portal Server and can be installed on a separate host. Directory Server is required by Portal Server, but not necessarily a local copy. Access Manager requires a local web container.

To use a remote copy of Directory Server, deselect Directory Server and specify a remote copy when prompted.

Note

The remote Directory Server must be running before installing any other components. For instructions on installing Directory Server, refer to Directory Server Only Example.

To use a remote copy of Access Manager, deselect Access Manager and specify a remote copy during postinstallation configuration.

Note

The remote Access Manager must be running before installing any other components. For instructions on installing Access Manager, refer to Identity Management Example.

Resolving incompatibilities

The installer verifies software on your host and provides guidance if incompatibilities are identified.

Selecting the Configure Now or Configure Later option

For the Configure Now option, configuration pages are displayed for those components that allow installation time configuration. Do not accept defaults for components that are remote; use the remote information.

Web Server Only Example

This example installs Web Server by itself.

Requirements

Web Server has no dependencies on other components.

Note

If you are using this component with Sun Cluster software, you must perform a precise series of tasks before installing any components. Refer to Sun Cluster Software Example to see Sun Cluster guidelines.

The general steps for this type of installation include the following:

Solaris 10 Zones

This section describes Solaris 10 zones support for the current release of Java ES. An installation example is included.

Overview of Solaris Zones

The Solaris 10 zones (also known as Solaris containers) feature provides a means of creating virtualized operating system environments within an instance of Solaris OS. This allows one or more processes to run in isolation from other activities on the host. For example, a process running in a zone will only be able to send signals to other processes in the same zone, regardless of user ID and other credential information.

Every Solaris 10 host contains a single global zone. The global zone is both the default zone for the host and the zone used for system-wide administrative control. All processes run in the global zone if no non-global zones are created by the global administrator.

A non-global zone can be thought of as a box. One or more applications can run in this box without interacting with the rest of the host. Each non-global zone has what appears to be its own instance of an installed Solaris 10 operating system with configuration and other information unique to that non-global zone. The default configuration for a non-global zone is to share portions of its file system with the global zone (as a read-only loopback file system mount).

Zones Scenarios Supported in this Release of Java ES

The following Java ES and zones scenarios are supported in this release of Java ES:

Installing Java ES in a non-global zone that uses the whole root file system (Using the default sparse root file system is not supported.)

Installing Java ES in the global zone with no non-global zones

Java ES Limitations in Global Zones

Installing and configuring Java ES for use in the global zone is supported, but this configuration has some limitations in this release of Java ES. These limitations are due to the nature of some of the Java ES packages and how those packages are automatically propagated by the zones infrastructure to both existing and newly created non-global zones.

Limitation: If non-global zones already exist, the Java ES installer will not allow installation to proceed.

Solution: Either plan to install Java ES in a non-global zone, or remove the existing non-global zones and install Java ES in the global zone.

Limitation: Creating a non-global zone after you have installed Java ES software into the global zone is not supported. If a non-global zone is created after Java ES has been installed in the global zone, package propagation errors will result when the non-global zone is created. It is unlikely that the newly created non-global zone will function correctly.

Solution: Remove the newly created non-global zone. Determine whether it is more important to retain the Java ES installation in the global zone or to create non-global zones. If you must create non-global zones, then uninstall Java ES from the global zone, create the required non-global zones and consider installing Java ES in one or more of the non-global zones.

Solaris 10 Zones Example

Verifying that all the non-global zones specified in your implementation plan have been created by the global zone administrator as “whole root” zones with no inherited file systems

For information on creating non-global zones, refer to the “Planning and Configuring Non-Global Zones (Tasks)” chapter in the System Administration Guide: Solaris Containers-Resource Management and Solaris Zones (http://docs.sun.com/doc/817-1592).

Some components, such as SRS Net Connect, cannot be installed in a non-global zone because they require access to global zone capabilities. Other components are not supported for Solaris 10. These components are unavailable at component selection.

Sun Cluster Software Example

Components that can be configured to run in a cluster instead of on a single server include Administration Server, Calendar Server, Directory Server, Message Queue, Messaging Server, and Web Server.

Requirements

Messaging Server requires Directory Server, but not necessarily a local copy. In addition, Messaging Server requires a local copy of Administration Server. You will need the Sun Cluster Core component as well as the Sun Cluster Agents for Directory Server, Administration Server, and Messaging Server.

Sequencing Issues

Installing, configuring, and starting the components in the correct order is crucial for a successful Sun Cluster implementation. The general tasks include the following:

Installing the Java ES Sun Cluster component

Configuring the Sun Cluster framework

Installing the additional Java ES components that are required for Messaging Server to operate in the cluster

Configuring the Sun Cluster data services using the agents for the relevant Java ES components

At least two installation sessions are performed on each node in the cluster.

The installer verifies software on your node and provides guidance if incompatibilities are identified.

Tip

During a Configure Now installation (usually where you have chosen to install all Java ES components), you are prompted whether to enable support for remote Sun Cluster configuration. If you select Yes, postinstallation configuration for Sun Cluster will be easier.

Verifying installation directories

Selecting the Configure Now or Configure Later option

Messaging Server and Sun Cluster cannot be configured during installation.

Access Manager SDK With Container Configuration Example

This example installs Access Manager SDK, using a copy of Access Manager that is already installed on a remote host.

Requirements

Before you install Access Manager SDK, the Access Manager core services must be installed and running on a remote host. The web container information and Directory Server configuration information that you provide in this installation example must match the web container and Directory Server configuration information that you provided during installation of Access Manager core services.

Note

When the installer asks for information about the remote web container and Directory Server, default values are displayed based on the local host.

Do not accept the default values; use them only as examples of format. Instead, you must supply the correct information from the remote host.

The Java ES installer does not allow you to configure the web container when you are installing only the Access Manager SDK.

The general steps for this type of installation include the following:

Requirements

Access Manager is required if you are implementing single sign-on or Access Manager managed policies. In this case, either Access Manager or a local copy of the Access Manager SDK is required. Access Manager SDK requires Access Manager, but not necessarily a local copy. Calendar Server and Messaging Server both require Directory Server, but not necessarily a local copy. Messaging Server requires a local copy of Administration Server.

In this example, remote copies of Directory Server and Access Manager are used. Access Manager requires a local web container.

Sequence Issues

If you are using this component with Sun Cluster software, you must perform a precise series of tasks before installing any components. Refer to Sun Cluster Software Example to see Sun Cluster guidelines.

The remote Directory Server must be installed and running before installing any components that depend on it.

The remote Access Manager must be running before installing Access Manager SDK. For instructions on installing Access Manager, refer to Identity Management Example.

The general steps for this type of installation include the following:

Deselecting Directory Server and specifying a remote copy when prompted

Resolving incompatibilities

The installer verifies software on your host and provides guidance if incompatibilities are identified.

Verifying installation directories

Selecting the Configure Now option

Calendar Server and Messaging Server cannot be configured during installation.

Configuration pages are displayed for the local components that can be configured during installation. Do not accept defaults for components that are remote; use the remote information. Gather your configuration information from the tables in Chapter 4, "Configuration Information".

Communications Express and Messaging Server Example

This example installs Communications Express for messaging services in a 2-host Schema 2 environment. A remote copy of Directory Server is used.

Requirements

Communications Express requires either Access Manager or the Access Manager SDK for Schema 2. (A local copy of Access Manager SDK is always required, but you can use a remote copy of Access Manager.) Directory Server is required for Access Manager and Communications Express, but Directory Server does not need to be on the local host. Communications Express requires a local web container which can be either Application Server or Web Server.

To use messaging services, Communications Express requires a local copy of Messaging Server, which requires a local copy of Administration Server. To use calendar services, Communications Express requires Calendar Server, but Calendar Server does not need to be on the local host. This example uses messaging services.

Sequence Issues

If you are using Messaging Server or Web Server with Sun Cluster software, you must perform a precise series of tasks before installing any components. Refer to Sun Cluster Software Example to see Sun Cluster guidelines.

The remote Directory Server must be installed and running before installing any components that depend on it.

The general steps for this type of installation include the following:

Using the following URL to access the default Communications Express login page:

http://web-container-host:web-container-port/URI-path-CommsExpress

Using the following URL to access the default Access Manager Login page:

http://web-container-host:web-container-port/amserver/UI/Login

Instant Messaging and Access Manager Example

This example installs Instant Messaging with Access Manager, using a remote Directory Server, and Web Server as the web container.

Requirements

For the Instant Messaging Core subcomponent, Access Manager is required, but not necessarily a local copy. For the Instant Messaging Resources subcomponent, the Access Manager SDK must be local to Instant Messaging. Access Manager requires a web container, which can be remote. If you use Access Manager, Directory Server is required, but not necessarily a local copy. If you are using Access Manager with Instant Messaging, you must also use the Access Manager SDK.

Sequence Issues

The installer does not automatically select components that Instant Messaging depends on. You are responsible for selecting these components.

If you are deploying other components with Instant Messaging, the other components must be configured before configuring Instant Messaging.

Deselecting Directory Server and specifying the remote copy when prompted

Resolving incompatibilities

The installer verifies software on your host and provides guidance if incompatibilities are identified.

Verifying installation directories

Selecting the Configure Now or Configure Later option

Instant Messaging cannot be configured during installation.

For the Configure Now option, configuration pages are displayed for the local components that can be configured during installation. Do not accept defaults for components that are remote; use the remote information.

Communication and Collaboration Services Example

This example installs most of the Java ES components to implement communication and collaboration services across four hosts.

Note

If you are using any of these components with Sun Cluster software, you must perform a precise series of tasks before installing any Java ES components. Refer to Sun Cluster Software Example to see Sun Cluster guidelines.

Requirements

Directory Server is required for all the communications components, but not necessarily a local copy. A local copy of Administration Server is required by Messaging Server. Access Manager or the Access Manager SDK is required, but Access Manager can be remote. In this example, Web Server fulfills the Access Manager requirement for a web container. Although Calendar Server and Messaging Server do not require a local web container, Communications Express does. Communications Express can use a remote copy of Calendar Server, but Messaging Server must be local.

To implement single sign-on, Instant Messaging requires Access Manager and a local or remote web container. Portal Server Secure Remote Access requires Access Manager and a local web container. Portal Server Secure Remote Access also requires Portal Server, but not necessarily a local copy.

Sequencing Issues

For large deployments, you might deploy each component on a separate server, in approximately the same order shown in this example. For small deployments, components are installed in separate installation sessions on fewer servers.

On Host D

Installing and starting Communications Express, Messaging Server, Access Manager SDK, and Web Server, specifying the remote Access Manager and Directory Server that are installed on Host A and the remote Calendar Server that is installed on Host C

Access Manager SDK must be local to Messaging Server and Communications Express. A web container must be local to Communications Express.

Identity Management Example

In this example, identity management is implemented by installing Access Manager and Directory Server, with Directory Server on a remote host.

Requirements

Access Manager requires Directory Server, but not necessarily a local copy. Access Manager requires a web container, which in this example is Web Server. Delegated Administrator is automatically installed with Access Manager. The remote Directory Server must be running before installing any other components.

Note

To use a third-party web container for Access Manager, you must configure Access Manager manually after doing a Configure Later installation.

On Host B

Directory Server and the Directory Preparation Script are automatically selected.

Deselect Directory Server and specify a remote copy when prompted.

Resolving incompatibilities

The installer verifies software on your host and provides guidance if incompatibilities are identified.

Selecting the Configure Now or Configure Later option

For the Configure Now option, configuration pages are displayed for those components that allow installation-time configuration. Do not accept defaults for components that are remote; use the remote information.

For a full scenario showing how to establish an initial user and implementing single sign-on, refer to the Java Enterprise System Deployment Example Series: Small Scale Communications Scenario(http://docs.sun.com/doc/819-0060).]]

Web and Application Services Example

This example provides guidelines for implementing a two-node HADB cluster with load balancing.

Sequencing Issues

HADB (used for high availability session storage) works with Application Server to provide failover capabilities that include session persistence.

The general tasks include:

Installing the Java ES components

Starting the servers

Configuring HADB

Configuring load balancing

All tasks are performed on each node in the cluster, which means a minimum of two installation sessions are required (for a two-host cluster).

Requirements

Application Server requires a local copy of Message Queue. Application Server and HADB must be on the same host so you can use the integrated management tools provided by Application Server. The Load Balancing Plugin subcomponent of Application Server requires a web server. This example uses the Java ES Web Server as the container.

Refer to the “HTTP Load Balancing and Failover” section in the “Application Server High Availability Features” chapter of the Sun Java System Application Server Enterprise Edition High Availability Administration Guide (http://docs.sun.com/doc/819-0216).

Portal Server Using a Remote Access Manager Example

This example installs Portal Server and its required components on one host, using a copy of Access Manager that is already installed with Directory Server on another host.

Requirements

Portal Server requires Access Manager. Access Manager requires a local or remote copy of Directory Server and a local web container. You can run Portal Server on a separate host from Access Manager, in which case Portal Server requires a local copy of the Access Manager SDK and a local web container. When you install Portal Server and the Access Manager SDK, you need to deselect the unneeded subcomponents of Access Manager. (The installer automatically selects all Access Manager subcomponents when you select Portal Server.)

The general steps for this type of installation include:

On Host A

Verifying that Access Manager and Directory Server are installed and running

Access Manager Configured to Run as a Non-root User Example

This example provides an installation sequence and configuration procedures for allowing Access Manager to run in a web container that is not owned by root.

Requirements

If your installation plan calls for deploying Access Manager in an instance of Web Server or Application Server that is not owned by the superuser (root), you must install Access Manager in a separate installation session from Directory Server and Web Server or Application Server.

Note

If you have already deployed Web Server in a root-owned instance of Web Server or Application Server, uninstall any copy of Access Manager before following the procedure in this section.

This example provides an installation sequence and configuration procedures for allowing Portal Server to run in a web container that is not owned by root.

Requirements

If your installation plan calls for deploying Portal Server in an instance of Web Server or Application Server not owned by the superuser (root), you must install Portal Server in a separate installation session from Web Server or Application Server.

Caution

If you have configured your Portal Server host to run as non-root user, and subsequently apply a patch, some directories will have their ownership reset to root ownership because the patch is applied as root user.

After successfully applying the patch, reconfigure your host to run as non-root user.

On Host A

Skip this step if Portal Server will be using a copy of Access Manager that is already running on a remote host.

On Host B

Making sure that the non-root instance of Web Server or Application Server is installed and configured on the same host where you are installing Portal Server

For Web Server:

If Web Server is not yet installed, use the installer to install Web Server, selecting the Configure Now option. Specify the non-root owner in the Runtime user and Runtime group configuration parameters.