The installer needs different information about Access Manager services for different Access Manager subcomponents.
Installing Access Manager Console (Core Not Already Installed)
Installing Access Manager Federation Management (Core Already Installed)
This section describes the services information that the installer needs when you are installing the Identity Management and Policy Services Core and the Access Manager Administration Console subcomponents.
In this scenario, you can deploy a new console or use a previously deployed console. If you deploy a new console, some information in Installing Access Manager Core and Console is not needed, as the Description column indicates.
Table 1–6 Access Manager Services Information for Installing Core and Console
Label and State File Parameter |
Description |
---|---|
Host Name |
Fully qualified domain name of the host on which you are installing. The default value is the fully qualified domain name of the local host. |
Services Deployment URI |
Uniform Resource Identifier (URI) prefix for accessing the HTML pages, classes, and JAR files associated with the Identity Management and Policy Services Core subcomponent. The default value is amserver. Do not enter a leading slash. |
Common Domain Deployment URI |
URI prefix for accessing the common domain services on the web container. The default value is amcommon. Do not enter a leading slash. |
Cookie Domain |
The names of the trusted DNS domains that Access Manager returns to a browser when Access Manager grants a session ID to a user. You can scope this value to a single top-level domain, such as example.com . The session ID will provide authentication for all subdomains of example.com. Alternatively, you can scope the value to a comma-separated list of subdomains, such as .corp.example.com,.sales.example.com. The session ID will provide authentication for all subdomains in the list. A leading dot (.) is required for each domain in the list. The default value is the current domain, prefixed by a dot (.). |
Administration Console: Deploy new console and Use existing console USE_DSAME_SERVICES_WEB_CONTAINER |
Choose Deploy new console to deploy the console into the web container of the host on which Access Manager is being installed. Choose Use existing console to use an existing console that is deployed on another host. In both cases, you specify the Console Deployment URI and Password Deployment URI. If you choose to use an existing console, you must also specify the Console Host Name and Console Port. In a state file, specify true to deploy a new console or false to use an existing console. |
Console Deployment URI |
URI prefix for accessing the HTML pages, classes and JAR files associated with the Access Manager Administration Console subcomponent. Depends on the Access Manager mode: Legacy mode (6.x): /amconsole or /amserver Realm mode (7.x): /amserver The default value is amconsole. Do not enter a leading slash. |
Password Deployment URI |
URI that determines the mapping that the web container running Access Manager will use between a string you specify and a corresponding deployed application. The default value is ampassword. Do not enter a leading slash. |
Console Host Name |
Fully qualified domain name for the server hosting the existing console. This value is not needed if you are deploying a new console. In graphical installation mode, you can edit the field only if you are using an existing console. The default value contains the value that you provided for Host (IS_SERVER_HOST ), a dot, and then the value that you provided for DNS Name in the Common Server Settings. Refer to Common Server Settings. As an example, if the host is siroe and the domain is example.com, the default value is siroe.example .com. |
Console Port |
Port on which the existing console listens for connections. Permitted values are any valid and unused port number, in the range 0 (zero) through 65535. This value is not needed if you are deploying a new console. In graphical installation mode, you can edit the field only if you are using an existing console. The default value is the value you provided for one of the following web container ports:
|
This section describes the services information the installer needs when the following are both true:
You are installing only the Access Manager Administration Console subcomponent.
The Identity Management and Policy Services Core subcomponent is already installed on the same host.
You can only install AM Console by itself in Realm mode (7.x). This cannot be done in Legacy mode (6.x).
Label and State File Parameter |
Description |
---|---|
Console Deployment URI |
URI prefix for accessing the HTML pages, classes and JAR files associated with the Access Manager Administration Console subcomponent. Depends on the Access Manager mode: Realm mode (6.x): /amconsole or /amserver Legacy mode (7.x): /amserver |
Password Services Deployment URI |
URI that determines the mapping that the web container running Access Manager will use between a string you specify and a corresponding deployed application. The default value is ampassword. Do not enter a leading slash. |
This section describes the services information the installer needs when the following are both true:
You are installing only the Access Manager Administration Console subcomponent.
The Identity Management and Policy Services Core subcomponent is not installed on the same host.
Label and State File Parameter |
Description |
---|---|
Web Container for Access Manager Administration Console | |
Console Host Name |
Fully qualified domain name for the host on which you are installing. |
Console Deployment URI |
URI prefix for accessing the HTML pages, classes and JAR files associated with the Access Manager Administration Console subcomponent. Depends on the Access Manager mode: Legacy mode (6.x): /amconsole or /amserver Realm mode (7.x): /amserver |
Password Services Deployment URI |
Deployment URI for the password service. The default value is ampassword. Do not enter a leading slash. |
Web Container for Access Manager Services | |
Services Host Name |
Fully qualified domain name of the host where the Identity Management and Policy Services Core subcomponent is installed. The default value is the fully qualified domain name of this host. Use the default value as an example of format only, and edit the value to supply the correct remote host name. In a state file, supply the fully qualified domain name of a remote host. |
Port |
Port on which the Identity Management and Policy Services Core subcomponent listens for connections. This port is the HTTP or HTTPS port used by the web container. |
Services Deployment URI |
URI prefix for accessing the HTML pages, classes, and JAR files associated with the Identity Management and Policy Services Core subcomponent. The default value is amserver. Do not enter a leading slash. |
Cookie Domain |
The names of the trusted DNS domains that Access Manager returns to a browser when Access Manager grants a session ID to a user. You can scope this value to a single top-level domain, such as example.co m. The session ID will provide authentication for all subdomains of example.com. Alternatively, you can scope the value to a comma-separated list of subdomains, such as .corp.example.com,.sales.example.com. The session ID will provide authentication for all subdomains in the list. A leading dot (.) is required for each domain. The default value is the current domain, prefixed by a dot (.). |
This section describes the services information the installer needs when you are installing only the Common Domain Services for Federation Management subcomponent.
Table 1–9 Access Manager Services Information for Installing Federation Management (Core Already Installed)
Label and State File Parameter |
Description |
---|---|
Common Domain Deployment URI |
URI prefix for accessing the common domain services on the web container. The default value is amcommon. Do not enter a leading slash. |