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.