Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

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. Access Manager and Portal Server must use the same type of web container.

Note –

To use this sequence example, also refer to known issue 6284663 in the Sun Java Enterprise System 2005Q4 Release Notes.


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

Note –

You must use Access Manager Legacy (6.x) installation type if you are installing Access Manager with Portal Server, Messaging Server, Calendar Server, Delegated Administrator, or Instant Messaging. Access Manager Realm (7.x) installation type can only be used if you are not installing any of these components.

ProcedureTo Develop a Sequence for Host A

The following high-level tasks are required:


    Verifying that Access Manager and Directory Server are installed and running

    Because Administration Server provides a graphical interface for Directory Server, you might also want to select Administration Server.

    Identity Management Example

ProcedureTo Develop a Sequence for Host B

The following high-level tasks are required:

  1. Running the Java ES installer

  2. At component selection, selecting Portal Server

    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

    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

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

  5. Selecting the Configure Now option

    The configuration pages are displayed.

  6. In the Access Manager: Administration (1 of 4) page, supplying the following values for the remote Access Manager:

    • Administrator (amAdmin) Password (retyped)

    • LDAP user (amldapuser) Password (retyped)

    • Password Encryption Key

  7. In the Access Manager: Directory Server Information page, specifying the information for the Directory Server on Host A.

    • Directory Server Information

    • Directory Manager Password

    • Suffix

  8. In the Access Manager: Web container for running Sun Java System Access Manager Services, specifying the information about the remote Access Manager on Host A

    Host name should be the fully qualified name on Host A.

  9. In the Portal Server: webcontainer page, specifying the web container (and any configuration parameters) that Portal Server is running within

  10. Running the installation

  11. Viewing the Installation Summary and Log

  12. Completing any required post-install configuration: