This example provides guidelines for installing Portal Server and its required product 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 on a host.
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 following high-level tasks are required:
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
Verifying that Access Manager and Directory Server are installed and running
The following high-level tasks are required:
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
Running the Java ES installer
At component selection, selecting Portal Server
Access Manager SDK, Access Manager Core Services, Administration Console, and Federation Management are automatically selected as well as Directory Server Core Server, the Directory Preparation Tool, Java DB, and Service Registry. The web container is not selected. The Web Container Selection page prompts you to select a web container.
Deselecting Directory Server and all subcomponents of Access Manager except Access Manager SDK
Dependency messages guide you to do the following:
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Selecting the Configure Now type
The configuration pages are displayed.
In the Access Manager: Specify Configuration Information page, supplying the following values for the remote Access Manager:
Passwords must be different for amAdmin and amladpuser.
Administrator (amAdmin) Password (retyped)
LDAP user (amldapuser) Password (retyped)
Password Encryption Key (must match the encryption key entered for Host A)
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
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.
In the Portal Server: webcontainer page, specifying the web container (and any configuration parameters) that Portal Server is running within
Running the installation
Viewing the Installation Summary and Log
Completing any required postinstallation configuration:
Portal Server and Portal Server Secure Remote Access Postinstallation Configuration