test

Sun Java System Access Manager Policy Agent 2.2 Guide for Apache HTTP Server 2.0.54

Windows Systems: Configuring Agent for Apache HTTP Server for a Web Site

Configure Agent for Apache HTTP Server for a web site after you have created an agent configuration file. If you have not already created an agent configuration file, create one as explained in Windows Systems: Creating Configuration Files, Agent for Apache HTTP Server.

To configure the agent for a web site, follow these steps:

ProcedureWindows Systems: To Configure Agent for Apache HTTP Server for a Web Site

  1. Change to the directory:

    PolicyAgent-base\apache\bin

  2. Run the following command:

    cscript.exe ApacheAdmin.vbs -config defaultConfig

    ApacheAdmin.vbs

    is a VB script that uses the output of the ApacheCreateConfig.vbs script. The output was saved to a configuration file, which for this example is represented by defaultConfig.

    -config

    is the option that allows the output to be used to configure the web site.

    defaultConfig

    represents the agent configuration file created previously as described in Windows Systems: To Create Configuration Files, Agent for Apache HTTP Server.

    The script displays messages to indicate the progress of the configuration as shown in the following sample.


    Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

Copyright c 2004 Sun Microsystems, Inc. All rights reserved
Use is subject to license terms

Enter the Agent Resource File Name [ApacheResource.en]:

Creating the AMAgent.properties File
Modifying httpd.conf
Completed Configuring the Agent for Apache 2.0.x. Re-start your server instance

  3. Restart the web site.

  4. Try accessing the web site (http://fqdn:port/index.html).

    This link should take you to the Access Manager login page. After a successful authentication, if the policy is properly defined, you should be able to view the resource.

    If you want to view the agent log file amAgent, do so at the following location:


    PolicyAgent-base\debug\apache_port

    where port is the port number of Apache HTTP Server.

    Note –

    If you want to configure the agent for multiple web sites, you must follow the preceding steps for each of the web sites.

Next Steps

The last step of this task addresses verification of the agent installation. See the section that follows (All Systems: Verifying a Successful Installation on Policy Agent 2.2) for an expanded explanation on verifying the agent installation.

If you want to configure multiple instances of Apache HTTP Server, you must set up multiple Apache HTTP Server Virtual Hosts, as described in All Systems: Configuring Agent for Apache HTTP Server on Multiple Apache HTTP Server Virtual Hosts.