In this example, identity management is implemented by installing Access Manager and Directory Server, with Directory Server on a remote host.
Access Manager requires Directory Server, but not necessarily a local copy. Access Manager requires a web container, which in this example is Web Server. The remote Directory Server must be running before installing any other components.
The following high-level tasks are required:
Installing and starting Directory Server
Because Administration Server provides a graphical interface for Directory Server, you might also want to select Administration Server.
The following high-level tasks are required:
Running the Java ES installer
At component selection, choosing Access Manager and Web Server
Directory Server and the Directory Preparation Tool are automatically selected.
Deselect Directory Server and specify a remote copy when prompted.
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Selecting the Configure Now or Configure Later option
For the Configure Now option, configuration pages are displayed for those components that allow installation-time configuration. Do not accept defaults for components that are remote; use the remote information.
You will need to gather your configuration information from the tables in Chapter 1, Configuration Information, in Sun Java Enterprise System 2005Q4 Installation Reference.
For the Configure Later option, configuration pages are not displayed.
Running the installation
Viewing the Installation Summary and Log
Completing any post-install configuration
For Configure Now:
Configuring Access Manager After a Configure Now Installation
For Configure Later:
Starting the components
Starting and Stopping Web Server (Access Manager starts automatically.)
Accessing the default Access Manager login page
http://webserver-host:port/amserver |
Establishing an initial user and setting up single sign-on