Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 2005Q1 Installation Guide 

Chapter 3
Example Installation Sequences

This chapter provides sequencing guidelines for some common Sun Java™ Enterprise System (Java ES) installation examples.

This chapter contains the following sections:

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.

Note

The Calendar-Messaging Schema 1 Example is the only example based on LDAP Schema 1. All other examples in this chapter are based on Schema 2.

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.

You can use the Java ES installer to identify components that are already on your local host. For instructions, refer to Are Incompatible Components Installed?.

To upgrade components that are already on your local host, refer to Java Enterprise System Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062).

Single-Session Installation Examples

The following examples apply to installing on a single host in a single session:

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:

  1. Starting the Java ES graphical installer

    2. Chapter 7, "Installing with the Graphical Interface"

  2. At component selection, selecting Install All, then deselecting the Application Server and Sun Cluster components

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

  3. Verifying installation directories
  4. Selecting the Configure Now option

    5. Messages indicate which components cannot be configured during installation.

  5. Accepting configuration defaults when they are offered

    6. If you want to use non-default information, review the appropriate configuration tables in Chapter 4, "Configuration Information".

  6. Viewing the Installation Summary and Log
  7. Completing post-install configuration

    8. Chapter 10, "Configuring Components After Installation"

  8. Starting the components

    9. Table 11-1 contains the preferred Java ES startup sequence. Startup procedures follow the table.

    Note

    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.

The general steps for this installation example include:

  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, choosing Portal Server and Web Server

    3. Access Manager, Directory Server, and Directory Preparation Script are automatically selected.

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

  3. Resolving incompatibilities

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

  4. Selecting the Configure Now or Configure Later option
    1. 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.

      2. You will need to gather your configuration information from the tables in Chapter 4, "Configuration Information".

    2. For the Configure Later option, configuration pages are not displayed.
  5. Running the installation
  6. Viewing the Installation Summary and Log
  7. Completing any post-install configuration

    8. For Configure Now:

  8. Starting the components
  9. Accessing the default Access Manager login page

    10. http://webserver-host:port/amconsole

The following table contains additional Access Manager information.

Table 3-1  Installation Information for Access Manager 

Task

Relevant Information

Configuration information for the installer

Access Manager Configuration Information
Access Manager SDK Configuration Information

Postinstallation configuration

Configuring Access Manager After a Configure Now Installation

Configuring Access Manager After a Configure Later Installation

Starting and stopping

Starting and Stopping Access Manager

Uninstalling

Access Manager-related Post-uninstallation
Access Manager Uninstallation Behavior

Troubleshooting

Access Manager Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

The following table contains additional Portal Server information.

Table 3-2  Installation Information for Portal Server 

Task

Relevant Information

Configuration information for the installer

Portal Server Configuration Information

Postinstallation configuration

Configuring Portal Server and Portal Server Secure Remote Access After a Configure Now Installation on a Sun Web Container

Configuring Portal Server After a Configure Later Installation on a Third-Party Web Container

Starting and stopping

Accessing the Portal Server Desktop

Uninstalling

Portal Server Uninstallation Behavior

Troubleshooting

Portal Server Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

Application Server Only Example

This example installs Application Server by itself.

Requirements

Application Server requires a local copy of Message Queue. If you are using load balancing, a local copy of Web Server is also required.

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

  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, choosing Application Server

    3. Message Queue is automatically selected. The Load Balancing Plugin subcomponent is not selected.

    (Optional) If you are going to implement load balancing, expand Application Server and select the Load Balancing Plugin subcomponent. Web Server is automatically selected.

  3. Resolving incompatibilities

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

  4. Verifying installation directories
  5. Selecting the Configure Now or Configure Later option
    1. For the Configure Now option, configuration pages are displayed for the local components that can be configured during installation.

      2. Gather your Application Server configuration information from the tables in Application Server Configuration Information.

    2. For the Configure Later option, configuration pages are not displayed.
  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing post-install configuration
  9. Starting Application Server (automatically starts Message Queue)

The following table contains additional Application Server information.

Table 3-3  Installation Information for Application Server 

Task

Relevant Information

Configuration information for the installer

Application Server Configuration Information

Postinstallation configuration

Configuring Application Server After a Configure Later Installation

Starting and stopping

Starting and Stopping Application Server

Uninstalling

Application Server Uninstallation Behavior

Troubleshooting

Application Server Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

Directory Server Only Example

This example installs Directory Server by itself.

Requirements

Directory Server has no dependencies on other Java ES components.

Note

If you are using replication for encryption for Directory Server, you should also select Administration Server at component selection.

Sequence Issues

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

  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, selecting Directory Server and (optionally) Administration Server

    3. The Directory Preparation Script is automatically selected.

  3. Resolving incompatibilities

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

  4. Verifying installation directories
  5. Selecting the Configure Now or Configure Later option
    1. For the Configure Now option, configuration pages are displayed for the local components that can be configured during installation.

      2. Gather your configuration information from the tables in Chapter 4, "Configuration Information".

    2. For the Configure Later option, configuration pages are not displayed.
  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing post-install configuration
  9. Starting the components in this order:
    1. To Start Directory Server
    2. (Optional) To Start Administration Server

The following table contains additional Directory Server information.

Table 3-4  Installation Information for Directory Server 

Task

Relevant Information

Configuration information for the installer

Directory Server Configuration Information

Postinstallation configuration

Configuring Directory Server After a Configure Later Installation

Starting and stopping

Starting and Stopping Directory Server

Uninstalling

Directory Server Uninstallation Behavior

Troubleshooting

Directory Server Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

Directory Proxy Server Example

This example installs Directory Proxy Server with Directory Server on a single host.

Requirements

Directory Proxy Server requires Directory Server, but not necessarily a local copy. In addition, Directory Proxy Server requires a local copy of Administration Server.

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

  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, selecting Directory Proxy Server

    3. Directory Server, Directory Preparation Script, and Administration Server are automatically selected.

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

  3. Resolving incompatibilities

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

  4. Verifying installation directories
  5. Selecting the Configure Now or Configure Later option
    1. 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.

      2. Gather your configuration information from the tables in Chapter 4, "Configuration Information".

    2. For the Configure Later option, configuration pages are not displayed.
  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing post-install configuration
  9. Starting the components in this order:
    1. To Start Directory Server
    2. To Start Administration Server
    3. To Start Directory Proxy Server

The following table contains additional Directory Proxy Server information.

Table 3-5  Installation Information for Directory Proxy Server 

Task

Relevant Information

Configuration information for the installer

Directory Proxy Server Configuration Information

Postinstallation configuration

Configuring Directory Proxy Server After a Configure Later Installation

Starting and stopping

Starting and Stopping Instant Messaging Server and Multiplexor

Uninstalling

Directory Proxy Server Uninstallation Behavior

Troubleshooting

Directory Proxy Server Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

Instant Messaging Only Example

This example installs Instant Messaging by itself.

It is not uncommon for Instant Messaging to be installed in a separate installation session after other components have been installed and configured.

Note

If you are using single sign-on or Access Manager managed policies, Access Manager is required. For guidelines, refer to Instant Messaging and Access Manager Example.

Sequence Issues

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

  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, choosing Instant Messaging
  3. Resolving incompatibilities

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

  4. Verifying installation directories
  5. Selecting the Configure Later option

    6. Instant Messaging cannot be configured during installation.

  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing post-install configuration

    9. Configuring Instant Messaging After a Configure Later Installation

  9. Starting Instant Messaging (after starting any other components that Instant Messaging might depend on)

    10. To Start Instant Messaging Server and Multiplexor

The following table contains additional Instant Messaging information.

Table 3-6  Installation Information for Instant Messaging 

Task

Relevant Information

Postinstallation configuration

Configuring Instant Messaging After a Configure Later Installation

Starting and stopping

Starting and Stopping Instant Messaging Server and Multiplexor

Uninstalling

Instant Messaging Uninstallation Behavior

Troubleshooting

Instant Messaging Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

Deployment scenarios

Sun Java System Communications Deployment Planning Guide

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:

  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, selecting Message Queue
  3. Resolving incompatibilities

    4. 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).

  4. Selecting the Configure Later option.

    5. Message Queue cannot be configured during installation

  5. Running the installation
  6. Viewing the Installation Summary and Log
  7. Starting Message Queue

    8. Starting Message Queue

The following table contains additional Message Queue information.

Table 3-7  Installation Information for Message Queue 

Task

Relevant Information

Postinstallation configuration

Configuring Message Queue After a Configure Now Installation

Starting and stopping

Starting Message Queue

Uninstalling

Message Queue Uninstallation Behavior

Troubleshooting

Message Queue Troubleshooting Tools

Upgrading

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.

The general steps for this installation example include:

  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, choosing Portal Server Secure Remote Access and Web Server

    3. Portal Server, Access Manager, Directory Server, and Directory Preparation Script, and are automatically selected.

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

  3. Resolving incompatibilities

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

  4. Selecting the Configure Now or Configure Later option
    1. 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.

      2. You will need to gather your configuration information from the tables in Chapter 4, "Configuration Information".

    2. For the Configure Later option, configuration pages are not displayed.
  5. Running the installation
  6. Viewing the Installation Summary and Log
  7. Completing any post-install configuration

    8. For Configure Now:

  8. Starting the components

    9. To Start Directory Server
    To Start Web Server Administration Server and Instance (Access Manager and Portal Server start automatically.)

    To Start Portal Server Secure Remote Access Gateway

  9. Accessing the default Access Manager login page

    10. http://webserver-host:port/amserver

  10. Accessing the portal

    11. http://webserver-host:port/portal/dt

  11. Accessing the Portal Gateway

    12. http://gateway-server:port/

The following table contains additional Portal Server Secure Remote Access information.

Table 3-8  Installation Information for Portal Server Secure Remote Access 

Task

Relevant Information

Configuration information for the installer

Portal Server Secure Remote Access Configuration Information

Starting and stopping

Starting and Stopping Portal Server Secure Remote Access

Uninstalling

Portal Server Secure Remote Access Uninstallation Behavior

Troubleshooting

Portal Server Secure Remote Access Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

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:

  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, selecting Web Server
  3. Resolving incompatibilities

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

  4. Verifying installation directories
  5. Selecting the Configure Now or Configure Later option
    1. For the Configure Now option, the Web Server configuration pages are displayed by the installer.

      2. Gather your configuration information from the tables in Chapter 4, "Configuration Information".

    2. For the Configure Later option, configuration pages are not displayed.
  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing any post-install configuration

    9. To Configure Web Server After a Configure Later Installation

  9. StartingWeb Server

    10. To Start Web Server Administration Server and Instance

The following table contains additional information for installing Web Server.

Table 3-9  Installation Information for Web Server 

Task

Relevant Information

Configuration information for the installer

Web Server Configuration Information

Postinstallation configuration

Configuring Web Server After a Configure Later Installation

Starting and stopping

Starting and Stopping Web Server

Uninstalling

Web Server Uninstallation Behavior

Troubleshooting

Web Server Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

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:

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.

Solaris 10 Zones Example

This example installs Java ES software in a Solaris 10 non-global zone.

  1. Verifying that Solaris 10 is installed on your host

    2. The global zone is automatically created.

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

    3. 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).

  3. Starting the Java ES installer in the desired non-global zone

    4. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  4. At component selection, choosing the components you want

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

  5. Running the installation
  6. Viewing the Installation Summary and Log
  7. Completing postinstallation configuration as needed

    8. Chapter 10, "Configuring Components After Installation"

  8. Starting components

    9. Chapter 11, "Starting and Stopping Components"

  9. Repeating Step 3 to Step 8 in additional non-global zones as needed

Sun Cluster Software Example

This example installs Messaging Server in a Sun Cluster framework.

Note

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:

  1. Installing the Java ES Sun Cluster component
  2. Configuring the Sun Cluster framework
  3. Installing the additional Java ES components that are required for Messaging Server to operate in the cluster
  4. 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.

Phase I. Installing and Configuring the Sun Cluster Framework

The following tasks must be performed on all nodes in the cluster:

  1. Verifying that the hardware is connected correctly for the cluster
  2. Running the Java ES installer

    3. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  3. At component selection, choosing only the Sun Cluster component
  4. Selecting the Configure Later option
  5. Following the instructions to configure the Sun Cluster Framework for each host in the cluster

    6. “Installing and Configuring Sun Cluster Software” chapter of the Sun Cluster Software Installation Guide for Solaris OS (http://docs.sun.com/doc/817-6543)

    For documentation on creating resource groups and configuring data services, refer to the Sun Cluster Data Services Planning and Administration Guide for Solaris OS (http://docs.sun.com/doc/817-6564).

Phase II. Installing and Configuring Components and Agents

The following tasks must be performed on all nodes in the cluster:

  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, choosing the following:
    1. Messaging Server

      2. Directory Server, the Directory Preparation Script, and Administration Server are automatically selected.

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

    2. Sun Cluster Agents for Sun Java System

      3. All agents are selected by default.

    3. Expanding the Sun Cluster Agents for Sun Java System component and deselecting all agents except Administration Server, Directory Server, and Messaging Server
  3. Resolving incompatibilities

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

  4. Verifying installation directories
  5. Selecting the Configure Now or Configure Later option

    6. Messaging Server and Sun Cluster cannot be configured during installation.

  6. Configuring all the selected components except Sun Cluster Agents
  7. Starting all the components except Sun Cluster Agents, in this order:
    1. To Start Directory Server
    2. To Start Administration Server
    3. To Start Messaging Server
  8. Configuring the data services for the components you have installed and configured

    9. Sun Cluster Data Services Configuration

The following table contains additional Sun Cluster information.

Table 3-10  Installation Information for Sun Cluster 

Task

Relevant Information

Postinstallation configuration information

Sun Cluster Framework Configuration
Sun Cluster Data Services Configuration

Starting and stopping

Stopping and Rebooting Sun Cluster Software

Uninstalling

Sun Cluster Uninstallation Behavior

Troubleshooting

Sun Cluster Software Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

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:

On Host A

Installing and starting Access Manager core services

Identity Management Example

On Host B
  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, choosing Access Manager SDK
  3. Resolving incompatibilities

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

  4. Selecting the Configure Later option
  5. Running the installation
  6. Viewing the Installation Summary and Log
  7. Verifying that your web container is installed and running
  8. Completing the configuration
    1. In the AccessManager-base/SUNWam/bin directory, make a copy the amsamplesilent file.
    2. Edit the copy of the amsamplesilent file.

      3. Note

      When you edit the amsamplesilent file for the Access Manager SDK, use the same encryption key for AM_ENC_PWD as the encryption key specified during the remote installation of Access Manager.

    3. Use the edited amsamplesilent file to deploy Access Manager.

      4. ./amconfig -s ./am.sdk_install

  9. Restarting your web container

Calendar Server and Messaging Server Example

This example installs Calendar Server and Messaging Server in a 3-host Schema 2 environment. Remote copies of Access Manager and Directory Server are used.

Note

For a Schema 1 example, refer to Calendar-Messaging Schema 1 Example.

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

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

On Host A

Installing and starting Directory Server

Directory Server Only Example

On Host B

Installing and starting the web container and Access Manager (deselecting Directory Server)

Identity Management Example

On Host C
  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, selecting Calendar Server, Messaging Server, and Access Manager SDK

    3. Directory Server, Directory Preparation Script, and Administration Server are automatically selected.

  3. Deselecting Directory Server and specifying a remote copy when prompted
  4. Resolving incompatibilities

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

  5. Verifying installation directories
  6. Selecting the Configure Now option

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

  7. Running the installation
  8. Viewing the Installation Summary and Log
  9. Completing post-install configuration, including specifying remote components

    10. Configuring Calendar Server After a Configure Later Installation

    Configuring Messaging Server After a Configure Later Installation

  10. Starting the components in this order:
    1. To Start Administration Server
    2. To Start Messaging Server
    3. To Start Calendar Server

The following table contains additional Calendar Server information.

Table 3-11  Installation Information for Calendar Server 

Task

Relevant Information

Postinstallation configuration

Configuring Calendar Server After a Configure Later Installation

Starting and stopping

Starting and Stopping Calendar Server

Uninstalling

Calendar Server Uninstallation Behavior

Troubleshooting

Calendar Server Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

The following table contains additional Messaging Server information.

Table 3-12  Installation Information for Messaging Server 

Task

Relevant Information

Postinstallation configuration

Configuring Messaging Server After a Configure Later Installation

Starting and stopping

Starting and Stopping Messaging Server

Uninstalling

Messaging Server Post-uninstallation
Messaging Server Uninstallation Behavior

Troubleshooting

Messaging Server Troubleshooting Tools

Upgrading

Java Enterprise System Upgrade and Migration Guide
http://docs.sun.com/doc/819-0062

Calendar-Messaging Schema 1 Example

This example installs Calendar Server and Messaging Server in an LDAP Schema 1 environment on two hosts. A remote version of Directory Server is used.

Requirements

Both Calendar Server and Messaging Server require Directory Server, but not necessarily a local copy. In addition, a local copy of Administration Server is required by Messaging Server.

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

On Host A

Installing and starting Directory Server

Directory Server Only Example

On Host B
  1. Running the Java ES installer.

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, choosing Calendar Server and Messaging Server

    3. Directory Server, the Directory Preparation Script, and Administration Server are automatically selected.

  3. Deselecting Directory Server

    4. When you are prompted to choose a local or remote Directory Server, choose remote (the Directory Server that is already installed and running on Host A).

  4. Resolving incompatibilities

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

  5. Selecting the Configure Now option

    6. You will receive a message that Calendar Server and Messaging Server cannot be configured during installation.

  6. Reviewing the configuration pages for Administration Server
  7. Running the installation
  8. Viewing the Installation Summary and Log
  9. Completing any post-install configuration:
  10. Starting the components in this order:
    1. To Start Administration Server
    2. To Start Messaging Server
    3. To Start Calendar Server
  11. If needed, setting up single sign-on

    12. Refer to the “Legacy SSO” chapter in the Sun Java System Messaging Server Administration Guide (http://docs.sun.com/doc/819-0105).

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

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

On Host A

Installing and starting Directory Server

Directory Server Only Example

On Host B
  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, choosing Communications Express, Access Manager, Messaging Server, and Web Server

    3. Administration Server, Directory Server, and the Directory Preparation Script are automatically selected.

  3. Deselecting Directory Server

    4. When you are prompted to choose a local or remote Directory Server, choose remote (the Directory Server that is already installed and running on Host A).

  4. Resolving incompatibilities

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

  5. Selecting the Configure Now option

    6. Communications Express cannot be configured during installation, and will require postinstallation configuration.

    Configuration pages are displayed for those components that can be configured during installation.

  6. Reviewing the configuration pages
  7. Running the installation
  8. Viewing the Installation Summary and Log
  9. Completing post-install configuration:
  10. Starting the components
  11. Using the following URL to access the default Communications Express login page:

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

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

    13. 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 general steps for this type of installation include the following:

On Host A

Installing and starting Directory Server

Directory Server Only Example

On Host B
  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, choosing Instant Messaging, Directory Server, and Web Server

    3. The Directory Preparation script is automatically selected.

  3. Deselecting Directory Server and specifying the remote copy when prompted

  4. Resolving incompatibilities

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

  5. Verifying installation directories
  6. Selecting the Configure Now or Configure Later option

    7. Instant Messaging cannot be configured during installation.

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

      2. Gather your configuration information from the tables in Chapter 4, "Configuration Information".

    2. For the Configure Later option, configuration pages are not displayed.
  7. Running the installation
  8. Viewing the Installation Summary and Log
  9. Completing post-install configuration

    10. Configuring Web Server After a Configure Later Installation

    Configuring Instant Messaging After a Configure Later Installation
    (Optional) For remote components: During Instant Messaging configuration, specify any remote locations for Directory Server, Access Manager, and Web Server.

  10. Starting the components in this order:
    1. To Start Web Server Administration Server and Instance
    2. To Start Instant Messaging Server and Multiplexor

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.

In this example, the following installation sessions are used:

By dividing the installation into a number of sessions, you are able to verify the components in each session before proceeding to the next session.

The general steps for this type of installation include:

On Host A
  1. Installing and starting Access Manager and Directory Server

    2. Identity Management Example

On Host B
  1. Installing and starting Portal Server and Web Server, specifying the remote Access Manager and Directory Server that are installed and running on Host A

    2. A web container and the Access Manager SDK must be local to Portal Server.

On Host C
  1. Installing and starting Messaging Server and Calendar Server, specifying the remote Access Manager and Directory Server that are installed on Host A

    2. Access Manager SDK must be local to Messaging Server and Calendar Server.

    Calendar Server and Messaging Server Example

On Host D
  1. 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

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

    Communications Express and Messaging Server Example

On Host D
  1. Installing Instant Messaging, specifying the remote Access Manager and Directory Server that are installed on Host A

    2. Access Manager SDK must be local to Instant Messaging.

    Instant Messaging and Access Manager Example

On Host D
  1. Installing Portal Server Secure Remote Access, specifying the remote Access Manager and Directory Server that are installed on Host A

    2. A web container and the Access Manager SDK must be local to Portal Server Secure Remote Access.

    Portal Server Secure Remote Access Example

  2. Establishing an initial user and setting up single sign-on

    3. Sun Java Enterprise System User Management Guide (http://docs.sun.com/doc/817-5761).

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.

The general steps for this installation example include:

On Host A

Installing and starting Directory Server

Directory Server Only Example

On Host B
  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, choosing Access Manager and Web Server

    3. Directory Server and the Directory Preparation Script are automatically selected.

  3. Deselect Directory Server and specify a remote copy when prompted.
  4. Resolving incompatibilities

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

  5. Selecting the Configure Now or Configure Later option
    1. 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.

      2. You will need to gather your configuration information from the tables in Chapter 4, "Configuration Information".

    2. For the Configure Later option, configuration pages are not displayed.
  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing any post-install configuration

    9. For Configure Now:

    Configuring Access Manager After a Configure Now Installation

    For Configure Later:

  9. Starting the components

    10. To Start Web Server Administration Server and Instance (Access Manager starts automatically.)

  10. Accessing the default Access Manager login page

    11. http://webserver-host:port/amserver

  11. Establishing an initial user and setting up single sign-on

    12. Sun Java Enterprise System User Management Guide (http://docs.sun.com/doc/817-5761)

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:

  1. Installing the Java ES components
  2. Starting the servers
  3. Configuring HADB
  4. 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.

The following tasks must be performed on all nodes in the cluster:

  1. Verifying that the hardware is connected correctly for your cluster
  2. Running the Java ES installer

    3. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  3. At component selection, choosing Application Server and High Availability Session Store

    4. Message Queue and all the subcomponents of Application Server except the Application Server Node Agent and Load Balancing Plugin are automatically selected.

  4. Expanding the Application Server component and selecting Load Balancing Plugin.

    5. Web Server is automatically selected.

    Note

    You must install Web Server and Load Balancing Plug-in using the same access permissions.

  5. Resolving incompatibilities

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

  6. Selecting the Configure Now option

    7. High Availability Session Store cannot be configured during installation. Message Queue requires no configuration.

    The configuration pages are displayed for components that can be configured during installation.

  7. Running the installation
  8. Viewing the Installation Summary and Log
  9. Starting the components:
  10. Completing HADB postinstallation configuration

    11. Refer to Configuring HADB After a Configure Later Installation.

  11. Completing load balancing configuration

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

Identity Management Example

On Host B
  1. Running the Java ES installer

    2. Chapter 7, "Installing with the Graphical Interface"
    Chapter 8, "Installing with the Text-Based Interface"

  2. At component selection, selecting Portal Server

    3. All Access Manager components are automatically selected as well as Directory Server and the Directory Preparation Tool.

    The web container is not selected. The Web Container Selection page prompts you to select a web container.

  3. Deselecting Directory Server and all subcomponents of Access Manager except Access Manager SDK

    4. Dependency messages guide you to do the following:

    1. Select Application Server, Web Server, or a previously installed local web container.
    2. Select a remote instance of Access Manager.
  4. Resolving incompatibilities

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

  5. Selecting the Configure Now option

    6. The configuration pages are displayed.

  6. In the Directory Server: Configuration Directory Server (3 of 5) page:
    1. Select Store this server's configuration data in the following instance of Directory Server
    2. Supply values for the following parameters for the remote Directory Server:
      • Directory Server Host
      • Directory Server Port (389 is the default)
      • Directory Manager DN (cn=Directory Manager is the default)
      • Directory Manager Password
  7. In the Directory Server: Data Storage Location (4 of 5) page:
    1. Select Store user data and group data in the following instance of Directory Server
    2. Supply values for the following parameters for the remote Directory Server:
      • Directory Server Host
      • Directory Server Port (389 is the default)
      • Directory Manager DN (cn=Directory Manager is the default)
      • Directory Manager Password
      • Suffix
  8. In the Access Manager: Administration (1of 6) page, supplying the following values for the remote Access Manager:
    • Administrator (amAdmin) Password (retyped)
    • LDAP user (amldapuser) Password (retyped)
    • Password Encryption Key
    • Directory Server Information (need to match step 9)
    • Directory Manager Password
    • Suffix
  9. Specifying the host name of the web container for running the Access Manager SDK (same as for Portal Server)
  10. Specifying the web container (and any configuration parameters) that Portal Server is running within
  11. Running the installation
  12. Viewing the Installation Summary and Log
  13. Completing any required post-install configuration:

Non-Root Examples

This section contains the following non-root examples:

For other non-root information, see Configuring Components with Non-root Identifiers.

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.

Sequence Issues

This example uses three installation sessions.

The general steps for this type of installation include:

On Host A
  1. Installing Directory Server and Administration Server using the Configure Now option
    • In the Common Server Settings page, enter the non-root user for System User and non-root group for System Group.
    • Select port numbers for Directory Server and Administration Server that are higher than 1024 (do not use 389 and 390).
  2. As the non-root user, starting Directory Server and Administration Server (all processes must be owned by the non-root user)
On Host B, Installation Session 1
  1. Installing Web Server using the Configure Now option
    • In the Common Server Settings page, enter the non-root user for System User and non-root group for System Group.
    • In the Web Server: Administration (1 of 2) page, change the Administration Runtime User ID to the non-root user.
    • In the Web Server: Default Web Server Instance page:
      1. Change the Runtime User ID to the non-root user.
      2. Change the Runtime Group to the non-root group.
      3. Select a value for HTTP Port that is higher than 1024.
  2. As the non-root user, starting the Web Server administration instance and Web Server instance (all processes should be owned by the non-root user)
On Host B, Installation Session 2
  1. Installing Access Manager using the Configure Later option
  2. Changing ownership of the following directories from root/other to the non-root user/non-root group:

    3. Solaris OS: /opt/SUNWma and /etc/opt/SUNWma
    Linux: /opt/sun/mobileaccess and /etc/opt/sun/mobileaccess

    chown -R non-root-user:non-root-group /opt/SUNWma /etc/opt/SUNWma

  3. Editing the amsamplesilent file
    1. Go to the Access Manager bin directory:

      2. Solaris OS: cd AccessManager-base/SUNWam/bin
      Linux: cd AccessManager-base/identity/bin

    2. Make a copy of the amsamplesilent file. For example:

      3. cp -p amsamplesilent am.non_root_install

    3. Edit the copy of the amsamplesilent file.
      • Set BASEDIR to the same value that you selected for the installation directory of Access Manager during installation
      • Update SERVER_HOST, SERVER_PORT, DS_HOST, DS_PORT, ROOT_SUFFIX, WS61_ADMINPORT and all related password fields (DS_DIRMGRPASSWD, ADMINPASSWD, AMLDAPUSERPASSWD).
  4. Using the edited amsamplesilent file to deploy Access Manager

    5. ./amconfig -s ./am.non_root_install

    1. Set NEW_OWNER to the non-root user.
    2. Set NEW_GROUP to the non-root group.
  5. As the non-root user, stopping the Web Server admin instance and Web Server instance
  6. As root, changing the ownership of the Web Server installation directory

    7. chown -R <non-root-user>:<non-root-group> WebServer-base

  7. As the non root-user, starting the Web Server admin instance and Web Server instance
  8. Accessing the Web Server admin console in a browser and logging in as the admin user
  9. Selecting the instance on which you deployed Access Manager
    1. Click Manage.
    2. Click Apply and click Apply Changes.

Portal Server on a Non-root Owned Web Server or Application Server Instance Example

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.

The general steps for this type of installation include:

On Host A

Installing and starting the web container and Access Manager (deselecting Directory Server)

Identity Management Example

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

      Web Server Only Example

      If Web Server is already installed, use the Web Server administrative utilities to create a new web server instance owned by the non-root user.

    • For Application Server:

      • If Application Server is not yet installed, use the installer to install Application Server.

      Application Server Only Example

      After Application Server is installed, use the Application Server administrative utilities to create a new Application Server instance owned by the non-root user.

  2. Making sure the non-root instance of Web Server or Application Server is running, as well as the administrative instance of Web Server or Application Server
  3. Installing Portal Server with the Configure Now option
  4. During Portal Server configuration, doing the following:
    • Enter the user and group information of the non-root instance owner in the System User and System Group parameters when specifying values on the Common Server Settings page.
    • Enter information about the non-root instance when specifying values on the Portal Server: Sun Java System Web Server page or the Portal Server Sun Java System Application Server page.
  5. After installation, changing the ownership of the Portal Server directories from root to Userid:UserGroup.

    6. Solaris OS:

    chown -R Userid:UserGroup /opt/SUNWps
    chown -R Userid:UserGroup /etc/opt/SUNWps
    chown -R Userid:UserGroup /var/opt/SUNWps

    Linux:

    chown -R Userid:UserGroup /opt/sun/portal
    chown -R Userid:UserGroup /etc/opt/sun/portal
    chown -R Userid:UserGroup /var/opt/sun/portal

  6. Setting the permissions for the Portal Server directories.

    7. Solaris OS:

    chmod 0755 /opt/SUNWps
    chmod 0755 /etc/opt/SUNWps
    chmod 0755 /var/opt/SUNWps

    Linux:

    chmod 0755 /opt/sun/portal
    chmod 0755 /etc/opt/sun/portal
    chmod 0755 /var/opt/sun/portal

  7. Stopping and then starting Web Server or Application Server.

    8. Starting and Stopping Application Server
    Starting and Stopping Web Server



Previous      Contents      Index      Next     

Part No: 819-0056-11.   Copyright 2005 Sun Microsystems, Inc. All rights reserved.