Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System Installation Guide for Microsoft Windows 

Chapter 4
Installation Scenarios

This chapter provides guidelines for some common Sun Java™ Enterprise System (Java ES) installation scenarios. These are not literal procedures, but instead provide the high-level steps required to implement the installation examples presented here.

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

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

Note

The Schema 1 example is the only scenario based on LDAP Schema 1. The other examples in this chapter are based on Schema 2.

This chapter contains the following sections:

Single-Session Installation Examples

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

Evaluation Example

An evaluation installation is generally considered a trial deployment, a quick installation to see how things go. The Java ES components are installed on a single host in a single installation session. This example uses the graphical interface and the Quick Configure option.

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

  1. Starting the Java ES graphical installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

  2. At component selection, selecting ‘Sun Java Enterprise System’

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

  3. Verifying the installation directories
  4. Selecting the appropriate configuration option
  5. Accepting the configuration defaults when they are offered

    6. To use non-default information, review the appropriate configuration tables in Chapter 6, "Gathering Configuration Information for Configure Later Option".

  6. Viewing the Installation Summary and Log
  7. Complete the post-installation configuration

    8. Chapter 7, "Post-installation Configuration for Configure Later Option".

  8. Starting the components

    9. Refer Chapter 9, "Starting and Stopping Components" to view the Startup procedures.

For a detailed example of performing this type of deployment, including establishing an initial user and setting up single sign-on, refer to the Java Enterprise System Deployment Example Series: Evaluation Scenario (http://docs.sun.com/doc/819-0059).

Access Manager Only Example

Access Manager requires Directory Server, but not necessarily a local copy. Access Manager also requires a web container, which can be an Application Server or a Web Server. Delegated Administrator is automatically installed with Access Manager.

In this example, Access Manager uses Web Server as a web container.

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

  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

    3. Directory Server is 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 system and provides guidance if incompatibilities are identified.

  4. Verifying the installation directories
  5. Selecting the appropriate configuration options
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option"

  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing any post-install configuration
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:
    3. Configuring Directory Server After a Configure Later Installation
    4. Configuring Access Manager After a Configure Later Installation
    5. Configuring Web Server After a Configure Later Installation
  9. Starting the components in this order
    1. Starting Directory Server
    2. Starting and Stopping Web Server (automatically starts Access Manager)
  10. Accessing the default Access Manager login page

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

The following table contains additional Access Manager information.

Table 4-1  Installation Information for Access Manager 

Task

Relevant Information

Post-installation configuration

Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

Configuring Access Manager After a Configure Later Installation

Starting/stopping

Starting and Stopping Access Manager

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Access Manager Troubleshooting Tools

Upgrading

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

Access Manager and Directory Server Example

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 general steps for this installation example include:

  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

    3. Directory Server is 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 system and provides guidance if incompatibilities are identified.

  4. Selecting the appropriate configuration options
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option"

  5. Running the installation
  6. Viewing the Installation Summary and Log
  7. Completing any post-install configuration
    1. For Quick Configure, refer to:
    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"
    3. For Configure Later, refer to:
    4. Configuring Directory Server After a Configure Later Installation
    5. Configuring Access Manager After a Configure Later Installation
    6. Configuring Web Server After a Configure Later Installation
  8. Starting the components
    1. Starting Directory Server
    2. Starting and Stopping Web Server (automatically starts Access Manager)
  9. Accessing the default Access Manager login page

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

Access Manager and Portal Server Example

This example installs both Access Manager and Portal Server on the same host. Access Manager requires Directory Server, but not necessarily a local copy. Access Manager also requires a web container, which in this example is Application 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 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

    3. Access Manager, Directory Server, and Message Queue 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 the software on your system and provides guidance if incompatibilities are identified.

  4. Selecting the appropriate configuration options
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option".

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

    8. For Quick Configure, refer to:

  8. Starting the components

    9. Starting and Stopping Application Server (Access Manager, Portal Server, and Message Queue start automatically.)

  9. Accessing the default Access Manager login page

    10. http://hostname:port/amconsole

Application Server Only Example

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

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

  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

  2. At component selection, choosing Application Server

    3. Message Queue is automatically selected. The Load Balancing plug-in subcomponent is not selected.

    (Optional) If you are going to implement load balancing, expand Application Server and select the Load Balancing plug-in subcomponent. Web Server is automatically selected and must be installed on the same host as Application Server.

  3. Resolving incompatibilities

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

  4. Verifying installation directories
  5. Selecting the appropriate configuration options
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later. refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option"

  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing post-install configuration
  9. Starting Application Server (automatically starts Message Queue)

    10. Starting and Stopping Application Server
    (Optional) Starting and Stopping Web Server

The following table contains additional Application Server information.

Table 4-2  Installation Information for Application Server 

Task

Relevant Information

Post-installation configuration

Configuring Application Server After a Configure Later Installation

Starting/stopping

Starting and Stopping Application Server

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Application Server Troubleshooting Tools

Communications Express and Messaging Server Example

Communications Express requires a local copy of either Access Manager or Access Manager SDK. Directory Server is required for Access Manager, 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.

If you are using messaging services, Communications Express requires a local copy of Messaging Server, which requires a local copy of Administration Server. If you are using calendar services, Communications Express requires Calendar Server, but Calendar Server does not need to be on the local host.

In this example, Messaging Server is installed on the local host. Web Server is used as the web container.

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

  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

    3. Administration Server and Directory Server 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 post-installation configuration.

      • Note

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

  3. Resolving incompatibilities

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

  4. Selecting the appropriate configuration options
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option"

  5. Reviewing the configuration pages
  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing post-install configuration
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Configuring Access Manager After a Configure Later Installation

      Configuring Communications Express After a Configure Later Installation

      Configuring Messaging Server After a Configure Later Installation

  9. Starting the components

    10. Starting and Stopping Web Server (Access Manager automatically starts)
    Starting and Stopping Messaging Server

  10. Using the following URL to access the default Access Manager login page:

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

Directory Server Only Example

Because Directory Server has no dependencies on other Java ES components, an installation of Directory Server alone is relatively simple.

Sequence Issues

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

  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

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

  4. Verifying installation directories
  5. Selecting the appropriate configuration options
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option"

  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing post-install configuration
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later:

      3. Configuring Directory Server After a Configure Later Installation

      (Optional) Configuring Administration Server After a Configure Later Installation

  9. Starting the components in this order:
    1. Starting Directory Server
    2. (Optional) Starting and Stopping Administration Server

The following table contains additional Directory Server information.

Table 4-3  Installation Information for Directory Server 

Task

Relevant Information

Post-installation configuration

Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

Configuring Directory Server After a Configure Later Installation

Starting/stopping

Starting and Stopping Directory Server

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Directory Server Troubleshooting Tools

Directory Proxy Server Only Example

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 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

  2. At component selection, selecting Directory Proxy Server

    3. Directory Server 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 the software on your system and provides guidance if incompatibilities are identified.

  4. Verifying installation directories
  5. Selecting the appropriate configuration options
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option"

  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing post-install configuration
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Configuring Directory Server After a Configure Later Installation

      Configuring Administration Server After a Configure Later Installation

      Configuring Directory Proxy Server After a Configure Later Installation

  9. Starting the components in this order:
    1. Starting Directory Server
    2. Starting and Stopping Administration Server
    3. Starting and Stopping Directory Proxy Server

The following table contains additional Directory Proxy Server information.

Table 4-4  Installation Information for Directory Proxy Server 

Task

Relevant Information

Starting/stopping

Starting and Stopping Directory Proxy Server

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Directory Server Troubleshooting Tools

Instant Messaging Only Example

Instant Messaging requires Directory Server, but not necessarily a local copy. Instant Messaging also requires a web container which can be remote. In this example, the web container is Web Server.

Access Manager is required if you are implementing single sign-on or Access Manager managed policies. 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.

Sequence Issues

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

  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

    3. (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 the software on your system and provides guidance if incompatibilities are identified.

  4. Verifying installation directories
  5. Selecting the appropriate configuration options
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option".

  6. Running the installation
  7. Viewing the Installation Summary and Log
  8. Completing post-install configuration
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Configuring Directory Server After a Configure Later Installation

      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.

  9. Starting the components in this order:
    1. Starting Directory Server
    2. Starting and Stopping Web Server
    3. Starting and Stopping Instant Messaging

The following table contains additional Instant Messaging information.

Table 4-5  Installation Information for Instant Messaging 

Task

Relevant Information

Post-installation configuration

Configuring Instant Messaging After a Configure Later Installation

Starting/stopping

Starting and Stopping Instant Messaging

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Instant Messaging Troubleshooting Tools

Implementation scenarios

Sun Java System Communications Deployment Planning Guide

Message Queue Only Example

Because Message Queue has no dependencies on other Java ES components, installation of Message Queue alone is very simple.

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

  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

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

  4. Selecting the appropriate configuration options.

    Note

    The installer automatically configures Message Queue in both Quick Configure and Configure Later options.

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

    8. Starting and Stopping Message Queue

The following table contains additional Message Queue information.

Table 4-6  Installation Information for Message Queue 

Task

Relevant Information

Post-installation configuration

Configuring Message Queue After a Configure Later Installation

Starting/stopping

Starting and Stopping Message Queue

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Message Queue Troubleshooting Tools

Portal Server Only Example

Portal Server requires a local copy of Access Manager or Access Manager SDK. Access Manager can be remote, but 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 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

    3. Access Manager and Directory Server 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 post-installation configuration.

      • Note

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

  3. Resolving incompatibilities

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

  4. Selecting the appropriate configuration options
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option".

  5. Running the installation
  6. Viewing the Installation Summary and Log
  7. Completing any post-install configuration
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Configuring Directory Server After a Configure Later Installation

      Configuring Access Manager After a Configure Later Installation.

      Configuring Web Server After a Configure Later Installation

      Configuring Portal Server After a Configure Later Installation

  8. Starting the components

    9. Starting Directory Server
    Starting and Stopping Web Server (Access Manager and Portal Server start automatically.)

  9. Accessing the default Access Manager login page

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

The following table contains additional Portal Server information.

Table 4-7  Installation Information for Portal Server 

Task

Relevant Information

Post-installation configuration

Configuring Portal Server After a Configure Later Installation

Starting and Stopping Portal Server

Starting and Stopping Portal Server

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Portal Server Troubleshooting Tools

Portal Server Secure Remote Access Only Example

Portal Server Secure Remote Access requires a local copy of Access Manager or Access Manager SDK. Portal Server Secure Remote Access also requires Portal Server, but not necessarily a local copy. Directory Server is required, but not necessarily a local copy. Web Server is used to fulfill the Access Manager requirement for a web container.

The general steps for this installation example include:

  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

    3. Portal Server, Access Manager and Directory Server 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 post-installation configuration.

      • Note

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

  3. Resolving incompatibilities

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

  4. Selecting the appropriate configuration options:
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option"

  5. Running the installation
  6. Viewing the Installation Summary and Log
  7. Completing any post-install configuration
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Configuring Directory Server After a Configure Later Installation

      Configuring Access Manager After a Configure Later Installation.

      Configuring Web Server After a Configure Later Installation

      Configuring Portal Server SRA After a Configure Later Installation

  8. Starting the components

    9. Starting Directory Server
    Starting and Stopping Web Server(Access Manager and Portal Server start automatically.)

    Starting and Stopping Portal Server

  9. Accessing the default Access Manager login page

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

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

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

Task

Relevant Information

Starting/stopping

Starting and Stopping Portal Server

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Portal Server Secure Remote Access Troubleshooting Tools

Web Server Only Example

Because Web Server has no dependencies on other components, an installation of Web Server alone is relatively simple. If you are using the Load Balancer Plug-in subcomponent of Application Server, Web Server must be installed on the same host as Application Server.

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

  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

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

  4. Verifying installation directories
  5. Selecting the appropriate configuration option
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option"

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

    9. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    To Configure Web Server After a Configure Later Installation

  9. StartingWeb Server

    10. Starting and Stopping Web Server

The following table contains additional information for installing Web Server.

Table 4-9  Installation Information for Web Server 

Task

Relevant Information

Post-installation configuration

Configuring Web Server After a Configure Later Installation

Starting and Stopping Web Server

Starting and Stopping Web Server

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Web Server Troubleshooting Tools

Calendar Server and Messaging Server Example

Note

This example is based on Schema 2. For Schema 1, refer to Schema 1 Calendar-Messaging Example.

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. Web Server fulfills the Access Manager requirement for a 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

Access Manager Only Example

On Host C
  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

    3. Directory Server, 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 system and provides guidance if incompatibilities are identified.

  5. Verifying installation directories
  6. Selecting the appropriate configuration option
    1. For Quick Configure, refer to:

      2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

    2. For Configure Later, refer to:

      3. Chapter 6, "Gathering Configuration Information for Configure Later Option".

  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. Starting and Stopping Administration Server
    2. Starting and Stopping Messaging Server
    3. Starting and Stopping Calendar Server

The following table contains additional Calendar Server information.

Table 4-10  Installation Information for Calendar Server 

Task

Relevant Information

Post-installation configuration

Configuring Calendar Server After a Configure Later Installation

Starting and Stopping Calendar Server

Starting and Stopping Calendar Server

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Calendar Server Troubleshooting Tools

The following table contains additional Messaging Server information.

Table 4-11  Installation Information for Messaging Server 

Task

Relevant Information

Post-installation configuration

Configuring Messaging Server After a Configure Later Installation

Starting and Stopping Messaging Server

Starting and Stopping Messaging Server

Uninstalling

Chapter 10, "Uninstalling the Software"

Troubleshooting

Messaging Server Troubleshooting Tools

Schema 1 Calendar-Messaging Example

This example installs the communication components, Calendar Server, and Messaging Server in a Schema 1 environment. These components require Directory Server, but not necessarily a local copy. In addition, a local copy of Administration Server is required by Messaging Server.

In this example, two installation sessions are used. The first installs Directory Server on Host A, and the second installs the remaining components on Host B.

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 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

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

    3. Directory Server 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 the software on your system and provides guidance if incompatibilities are identified.

  5. Selecting the Quick Configure option
  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. Configuring Calendar Server After a Configure Later Installation

    Configuring Messaging Server After a Configure Later Installation.

  10. Starting the components in this order:
    1. Starting and Stopping Administration Server
    2. Starting and Stopping Messaging Server
    3. Starting and Stopping Calendar Server
  11. To set up single sign-on, use the component-specific utilities like commcli and modify the settings (like setting SSO parameters in config files) of respective products.

Identity Management Example

Java ES implements unified identity by having only a single user entry that all components use for authentication. This example provides guidelines for installing Directory Server and Access Manager to implement identity management.

Access Manager requires Directory Server, but not necessarily a local copy. Access Manager also requires a local web container.

On Host A
  1. Installing and starting Directory Server

    2. Directory Server Only Example

On Host B
  1. Installing and starting Access Manager and a web container

    2. Access Manager Only 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)

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

Communication and Collaboration Services Example

This example uses most of the Java ES components to implement communication and collaboration services. For large deployments, you might deploy each component on a separate server, in approximately the same order as shown in this example. For small deployments, components are installed in separate installation sessions on fewer servers.

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 serves as the web container, which is required by Access Manager. 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.

Instant Messaging and Portal Server Secure Remote Access are added to the front-end server (Host D) after the other components are installed and functioning. 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.

In this example, the following installation sessions are used:

By dividing the installation into a number of sessions, you can 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. Access Manager and Directory Server Example

On Host B
  1. Installing and starting Portal Server and Web Server, 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.

    Portal Server Only Example
    Portal Server Using a Remote Access Manager Example

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, 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 Only 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 Only 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).

For a full scenario showing how to perform this type of deployment, including establishing an initial user and setting up single sign-on, refer to the Java Enterprise System Deployment Example Series: Small Scale Communications Scenario (http://docs.sun.com/doc/819-0060).]

Portal Server Using a Remote Access Manager Example

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 and Directory Server Example

On Host B
  1. Running the Java ES installer

    2. Chapter 5, "Installing Sun Java Enterprise System Using the Installation Wizard"

  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 the software on your system and provides guidance if incompatibilities are identified.

  5. Selecting the Configure Later option

    6. Refer Chapter 7, "Post-installation Configuration for Configure Later Option".

  6. Specifying the host name of the web container for running the Access Manager SDK (same as for Portal Server)
  7. Specifying the web container (and any configuration parameters) that Portal Server is running within
  8. Running the installation
  9. Viewing the Installation Summary and Log
  10. Completing any required post-installation configuration:

    11. Configuring Portal Server After a Configure Later Installation.



Previous      Contents      Index      Next     

Part No: 819-1652-10.   Copyright 2005 Sun Microsystems, Inc. All rights reserved.