Sun Java System Access Manager Policy Agent 2.2 Guide for Apache Tomcat 6.0

ProcedureTo Prepare to Install Agent for Apache Tomcat 6.0

Perform the following pre-installation steps:

  1. Ensure that the agent distribution files are properly unzipped on the Apache Tomcat 6.0 instance as described in the substeps that follow:

    1. Create a directory in which to download the tomcat_v6_agent.zip file.

      For example:

      Agent_Home
      
    2. Download the tomcat_v6_agent.zip file to the newly created directory.

    3. From the newly created directory, unzip the tomcat_v6_agent.zip file using the appropriate utility or command for your platform.

      For example, on Solaris systems, issue the following:

      unzip tomcat_v6_agent.zip

  2. Ensure that Policy Agent 2.2 for Apache Tomcat 6.0 is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for Apache Tomcat 6.0.

  3. Install Apache Tomcat 6.0 if not already installed.


    Caution – Caution –

    While the present release of Agent for Apache Tomcat 6.0 supports the .exe extension of the Apache Tomcat 6.0 bits, an extra task is required to make the installation work. For those instructions, see (Conditional) To Use the .exe Version of Apache Tomcat 6.0 Server.

    The extra task is unnecessary if you use the .zip files or .gz files. For example, for version 6.0.14, you could download either of the following compressed files and perform the installation without having to implement the extra task:

    apache-tomcat-6.0.14.zip
    apache-tomcat-6.0.14.tar.gz

    Compressed files for Apache Tomcat 6.0 as well as installation-related documentation are available at the Apache web site at http://apache.org/


  4. (Conditional) If the Apache Tomcat 6.0 instance on which you are about to install the agent is running, shut it down.

  5. Create a valid agent profile in Access Manager Console if one has not already been created.

    For information on how to create an agent profile, see Creating a J2EE Agent Profile.

    To avoid a misconfiguration of the agent, ensure that you know the exact ID and password used to create the agent profile. You must enter the agent profile password correctly in the next step and you must enter the agent profile ID correctly when installing the agent.

  6. Create a text file and add the agent profile password to that file.

    Ensure that this file is located in a secure directory of your choice. You will refer to this file during the agent installation process.

    With the agent profile password in this file, stored in a secure location, you do not need to enter sensitive information in the console. A valid password file can have only one line that contains the agent profile password.

  7. (On Red Hat Enterprise Linux Advanced Server only) Ensure that the Sun Microsystems java file is configured to be retrieved instead of the Red Hat java file.

    You can achieve this using various methods. Pick the method of choice. The following is an example of how you can accomplish this:

    Set the JAVA_HOME environment variable to point to the Sun Microsystems java file. The location varies, but the following example illustrates a feasible location for this file:

    /share/builds/components/jdk/1.5.0_06/Linux