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

ProcedureTo Prepare to Install the Apache HTTP Server 2.2 Agent

  1. Ensure that the Apache HTTP Server 2.2 agent is supported on the desired platform, as listed in Supported Platforms and Compatibility for the Apache HTTP Server 2.2 Policy Agent.

  2. If necessary, install and configure the Apache HTTP Server 2.2 web container.

    Also, check that the Apache HTTP Server 2.2 has the latest patches.

    For more information, refer to the Apache HTTP Server 2.2 documentation: http://httpd.apache.org/docs/2.2/

  3. Set your JAVA_HOME environment variable to a JDK version 1.5.0 or higher.

    The installation program requires that your JAVA_HOME variable be set correctly. If you have incorrectly set the JAVA_HOME variable, the setup script will prompt you to supply the correct path:

    Please enter JAVA_HOME path to pick up java:

  4. (Conditional) Create a valid agent profile in the Access Manager Console, if one has not already been created.

    Web agents can function using the default agent profile (UrlAccessAgent), but creating a different agent profile provides greater security. You must also create a different agent profile if Access manager is configured for cross domain single sign-on (CDSSO).

    For information about how to create an agent profile, see Chapter 5, Relationship Between the Agent Profile and Web Agents.

    To avoid configuration problems for the agent, you must know the agent profile ID and password used to create the agent profile. You must specify the agent profile password in the next step, and you must enter the agent profile ID when you install the agent.

  5. Create an agent profile password word file.

    An agent profile password file is a text file with one line that contains the agent profile password. You will need to provide the path to this file during the agent installation process. By using an agent profile password file, you do not need to enter the password during the agent installation. Set the security permissions for this file as required for your specific deployment.

  6. Unzip the web agent .zip file. For example:

    # unzip apache_v22_platform_agent.zip

    where platform identities the specific platform where you are installing the agent:

    SunOS — Solaris SPARC systems

    SunOS_x86 — Solaris x86 systems

    Linux — Linux systems

    WINNT — Windows systems

  7. On UNIX-based systems, ensure that the following programs have executable permissions:

    • agentadmin

    • crypt_util

    • certutil

    These programs are located in the PolicyAgent-base/bin directory. For example, to secure these programs on Solaris systems:

    # chmod +x agentadmin crypt_util certutil