To Prepare to Install Agent for Apache Tomcat Servlet/JSP Container

Perform the following pre-installation tasks:

1. Ensure that the Policy Agent 2.2 for Apache Tomcat Servlet/JSP Container is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for Apache Tomcat Servlet/JSP Container.

2. Install Apache Tomcat Servlet/JSP Container if not already installed.

   ---

   Caution –

   The present release of agent bits supports Apache Tomcat Servlet/JSP Container bits with the .zip extension. Apache Tomcat Servlet/JSP Container bits with the .exe extension are not supported by the agent. For example, for version 5.5.9, the correct compressed file supported by the agent is as follows:

   jakarta-tomcat-5.5.9.zip

   Compressed files for Apache Tomcat Servlet/JSP Container are available at the Apache web site. For example, you can attempt to retrieve the compressed file specifically for version 5.5.9 using the following link: http://archive.apache.org/dist/tomcat/tomcat-5/archive/v5.5.9/bin/jakarta-tomcat-5.5.9.zip.

   ---

   Refer to the Apache web site at http://apache.org/ for installation-related documentation regarding Apache Tomcat Servlet/JSP Container.

3. (Conditional) If the Apache Tomcat Servlet/JSP Container instance on which you are about to install the agent is running, shut it down.

4. 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.

5. 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.