Implications of Specific Deployment Scenarios for the Apache HTTP Server 2.2 Agent

The following sections refer to specific deployment scenarios involving the Apache HTTP Server 2.2 agent. These scenarios can affect how you respond to prompts during the installation process. You might also need to perform additional configuration operations.

• Configuring the Apache HTTP Server 2.2 Agent for Multiple Apache HTTP Server Virtual Hosts

• Installing the Apache HTTP Server 2.2 Agent on the Access Manager Host

Configuring the Apache HTTP Server 2.2 Agent for Multiple Apache HTTP Server Virtual Hosts

Consider the scenario where the Apache HTTP Server 2.2 has two virtual hosts: http://site1.example.com/ and http://site2.example.com/.

To Enforce Access to the Individual Virtual Hosts

1. Define the FQDN map property in the AMAgent.properties file as:

   com.sun.am.policy.agents.config.fqdn.map =
        valid1|site1.example.com,valid2|site2.example.com

2. Define policies in Access Manager with virtual host names in the policy rules.

To Protect Only http://site1.example.com/ and Not http://site2.example.com/

1. Define the FQDN map property in the AMAgent.properties file as:

   com.sun.am.policy.agents.config.fqdn.map =
      valid1|site1.example.com,valid2|site2.example.com

2. Define the site2 URLs in the not-enforced URL list.

Installing the Apache HTTP Server 2.2 Agent on the Access Manager Host

Installing the Apache HTTP Server 2.2 agent on the Access Manager host is not recommended for production deployments because performance can be degraded.

However, if you want to install the agent on the Access Manager host on the same Apache HTTP Server 2.2 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 Apache HTTP Server 2.2 instance, configuration of the not-enforced URL list is not required.