Sun Java System Access Manager Policy Agent 2.2 Guide for Sun Java System Web Server 7.0

Using the Installation Program of Agent for Sun Java System Web Server 7.0

After you issue the agentadmin command and accept the license agreement (if necessary) the installation program appears, prompting you for information.

The steps in the installation program are displayed in this section in an example interaction. Your answers to prompts can differ slightly or greatly from this example depending upon your specific deployment. In the example, most of the defaults have been accepted. This example is provided for your reference and does not necessarily indicate the precise information you should enter.

The following bulleted list provides key points about the installation program.

Each step in the installation program includes an explanation that is followed by a more succinct prompt.
For most of the steps you can type any of the following characters to get the results described:

?

Type the question mark to display Help information for that specific step.

<

Type the left arrow symbol to go back to the previous interaction.

!

Type the exclamation point to exit the program.
Most of the steps provide a default value that can be accepted or replaced. If a default value is correct for your site, accept it. If it is not correct, enter the correct value.

About Installation Prompts in Agent for Sun Java System Web Server 7.0

The following list provides information about specific prompts in the installation. Often the prompt is self explanatory. However, at other times you might find the extra information presented here to be very helpful. This extra information is often not obvious. Study this section carefully before proceeding.

The Deployment URI for Access Manager Services

Enter a Universal Resource Identifier (URI) that will be used to access Agent for Sun Java System Web Server 7.0. The default value is /amagent.

Note –

The web agent uses the value of the com.sun.am.policy.agents.config.agenturi.prefix property in the web agent AMAgent.properties configuration file to support some essential functions such as notification and POST data preservation. Web agent URI prefix is a configurable subset of Web Agent Deployment URI. It is important to set a valid URL for this property. Its value should be http://agentHost1.domain:port/web-agent-deployment-uri where agentHost1, domain and port are FQDN and port number of the Sun Java System Web Server 7.0 instance where the agent is installed and web-agent-deployment-uri is the URI where the Sun Java System Web Server 7.0 instance will look for web-agent related HTML pages. Its default value is amagent.

The following is an example of an Agent Deployment URI:

http://agentHost1.example.com:80/amagent

The Agent Profile Name

An agent profile should have been created as a pre-installation step. The creation of the agent profile is mentioned in that section. For the pre-installation steps, see Preparing to Install Agent for Sun Java System Web Server 7.0. For the actual information on creating an agent profile, see Chapter 5, The Relationship Between the Agent Profile and Web Agents in Policy Agent 2.2.

In summary, the web agent communicates with Access Manager with a specific ID and password created through an agent profile using Access Manager Console. For web agents, the creation of an agent profile is not mandatory. However, Access Manager uses the agent profile to authenticate an agent. This is part of the security infrastructure.

The Agent Profile Password File

The web agent profile password file should have been created as a pre-installation step. For the pre-installation steps, see Preparing to Install Agent for Sun Java System Web Server 7.0.

When the installation program prompts you for the password for the agent, enter the fully qualified path to this password file.

After you have completed all the steps, a summary of your responses appears followed by options that allow you to navigate through those responses to accept or reject them.

When the summary appears, note the agent instance name, such as Agent_001. You might be prompted for this name during the configuration process.

About the options, the default option is 1, Continue with Installation.

If you are satisfied with the summary, choose 1 (the default).
If you want to edit input from the last interaction, choose 2.
If you want to edit input starting at the beginning of the installation program, choose 3.
If you want to exit the installation program without installing, choose 4.

You can edit your responses as necessary, return to the options list, and choose option 1 to finally process your responses.

Example of Installation Program Interaction in Agent for Sun Java System Web Server 7.0

The following example is a sample installation snapshot of Policy Agent 2.2 for Sun Java System Web Server 7.0. By no means does this sample represent a real deployment scenario.

The section following the installation summary section, Implications of Specific Deployment Scenarios in Agent for Sun Java System Web Server 7.0, explains specific deployment scenarios, such as installing multiple agent instances. Review the information in that section before proceeding with the installation. That information is divided into subsections as follows:

************************************************************************
Welcome to the Access Manager Policy Agent for Sun Java System Web Server If
the Policy Agent is used with Federation Manager services, User needs to
enter information relevant to Federation Manager.
************************************************************************
Enter the complete path to the directory which is used by Sun Java System Web
Server to store its configuration Files. This directory uniquely
identifies the Sun Java System Web Server instance that is secured by this
Agent.
[ ? : Help, ! : Exit ]
Enter the SJS Web Server Config Directory Path
[/var/opt/SUNWwbsvr7/https-agentHost1/config]:

Enter the fully qualified host name of the server where Access Manager
Services are installed.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Host: amHost.com

Enter the port number of the Server that runs Access Manager Services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services port [80]: 8080

Enter http/https to specify the protocol used by the Server that runs Access
Manager services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Protocol [http]:

Enter the Deployment URI for Access Manager Services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Deployment URI [/amserver]:

Enter the fully qualified host name on which the Web Server protected by the
agent is installed.
[ ? : Help, < : Back, ! : Exit ]
Enter the Agent Host name: agentHost1.com

Enter the preferred port number on which the Web Server provides its
services.
[ ? : Help, < : Back, ! : Exit ]
Enter the port number for Web Server instance [80]: 7000

Select http or https to specify the protocol used by the Web server instance
that will be protected by Access Manager Policy Agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the Preferred Protocol for Web Server instance [http]:

Enter a valid Agent profile name. Before proceeding with the agent
installation, please ensure that a valid Agent profile exists in Access
Manager.
[ ? : Help, < : Back, ! : Exit ]
Enter the Agent Profile name [UrlAccessAgent]:

Enter the path to a file that contains the password to be used for identifying
the Agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the path to the password file: /opt/password

-----------------------------------------------
SUMMARY OF YOUR RESPONSES
-----------------------------------------------
SJS Web Server Config Directory : /var/opt/sun/SUNWwbsvr7/https-agentHost1/config
Access Manager Services Host : amHost.com
Access Manager Services Port : 8080
Access Manager Services Protocol : http
Access Manager Services Deployment URI : /amserver
Agent Host name : agentHost1.com
Web Server Instance Port number : 7000
Protocol for Web Server instance : http
Agent Profile name : UrlAccessAgent
Agent Profile Password file name : /opt/password

Verify your settings above and decide from the choices below.
1. Continue with Installation
2. Back to the last interaction
3. Start Over
4. Exit
Please make your selection [1]:

Summary of a Web Agent Installation in Policy Agent 2.2

At the end of the installation process, the installation program prints the status of the installation along with the installed web agent information. The information that the program displays can be very useful. The program also displays the location of specific files, which can be of great importance. In fact, you might want to view the installation log file once the installation is complete, before performing the post-installation steps as described in Chapter 6, Post-Installation of Policy Agent 2.2 for Sun Java System Web Server 7.0.

The location of directories displayed by the installer are specific. However, throughout this guide and specifically in Summary of Agent Installation shown in this section, PolicyAgent-base is used to describe the directory where the distribution files are stored for a specific web agent.

The following example serves as a quick description of the location of the web agent base directory (PolicyAgent-base) of Policy Agent 2.2 for Sun Java System Web Server 7.0.

Example 4–1 Policy Agent Base Directory of Agent for Sun Java System Web Server 7.0

The following directory represents PolicyAgent-base of Agent for Sun Java System Web Server 7.0:

Agent-HomeDirectory/web_agents/sjsws_agent

where Agent-HomeDirectory is the directory you choose in which to unpack the web agent binaries.

Information regarding the location of the web agent base directory is also explained in Location of the Web Agent Base Directory in Policy Agent 2.2.

The following type of information is printed by the installer:

SUMMARY OF AGENT INSTALLATION
-----------------------------
Agent instance name: Agent_001
Agent Configuration file location:
PolicyAgent-base/Agent_001/config/AMAgent.properties
Agent Audit directory location:
PolicyAgent-base/Agent_001/logs/audit
Agent Debug directory location:
PolicyAgent-base/Agent_001/logs/debug

Install log file location:
PolicyAgent-base/logs/audit/install.log

Thank you for using Access Manager Policy Agent

Once the agent is installed, the directories shown in the preceding example are created in the Agent_00x directory, which for this example is specifically Agent_001. Those directories and files are briefly described in the following paragraphs.

PolicyAgent-baseAgent_001/config/AMAgent.properties

Location of the web agent AMAgent.properties configuration file for the agent instance. Every instance of a web agent has a unique copy of this file. You can configure this file to meet your site's requirements. For more information, see the following sections:

PolicyAgent-base/Agent_001/logs/audit

Location of the web agent local audit trail.

PolicyAgent-base/Agent_001/logs/debug

Location of all debug files required to debug an agent installation or configuration issue.

PolicyAgent-base/logs/audit/install.log

Location of the file that has the agent install file location. If the installation failed for any reason, you can look at this file to diagnose the issue.

Implications of Specific Deployment Scenarios in Agent for Sun Java System Web Server 7.0

The following sections refer to specific deployment scenarios involving Policy Agent 2.2 for Sun Java System Web Server 7.0. These scenarios are likely to affect how you respond to prompts during the installation process. You might also need to perform additional configurations.

Installing a Web Agent on Multiple Sun Java System Web Server 7.0 Instances

After you install the agent for a specific Sun Java System Web Server 7.0 instance, you can install the agent on another Web Server 7.0 instance by executing the agentadmin --install command again.

Installing Agent for Sun Java System Web Server 7.0 on the Access Manager Host

Note –

Installing Agent for Sun Java System Web Server 7.0 on the Access Manager Host is not recommended for production deployments in that performance is degraded.

To install this web agent on the Access Manager host, on the same Sun Java System Web Server 7.0 instance, add all of the URLs related to Access Manager to the not enforced URL list. Configuring the not-enforced URL list is described in Configuring the Not-Enforced URL List. If you are installing the agent on a different Sun Java System Web Server 7.0 instance, configuration of the not-enforced URL list is not required.