12.1.1 Installation Architecture
The following diagram illustrates how the Digital Airlines website is integrated with Access Manager.
Figure 12-2 Digital Airlines Architecture
This document explains how to use a browser machine and two other machines for this configuration.
Table 12-1 Access Manager Components
|
Administration Console |
Identity Server |
Access Gateway |
Application Web Server |
LDAP User Store |
Browser |
|---|---|---|---|---|---|---|
|
Machine 1 |
X |
X |
|
X |
X |
|
|
Machine 2 |
|
|
X |
|
|
|
|
Machine 3 |
|
|
|
|
|
X |
The simplified configuration described in this document is for a test environment only. It is not a recommended or supported configuration for a production environment. For example, the configuration database installed with Administration Console must not be used as an LDAP user store in a production environment. In a production environment, you would not want to install Administration Console, Identity Server, and web server on the same machine. This simplified configuration is designed to minimize the number of machines required for a tutorial.
After deploying the Digital Airlines example, you must understand the concepts required to deploy Access Manager in a number of other configurations. In a production environment, you need to install the necessary Access Manager components according to your specific requirements. For more information about other possible installation configurations, see the Installing Access Manager Components on On-Premises Servers in the NetIQ Access Manager 5.0 Installation and Upgrade Guide.