Sun Java System Access Manager Policy Agent 2.2 Guide for Apache Tomcat 5.5 Servlet/JSP Container

Preparing to Install Agent for Apache Tomcat Servlet/JSP Container

Detailed information about unpacking the distribution files for J2EE agents in Policy Agent 2.2 is covered in Chapter 2, Vital Installation Information for a J2EE Agent in Policy Agent 2.2. The best practice is to follow the detailed steps outlined in that chapter before you implement any steps outlined in this chapter.

The following examples provide quick details about the unpacking process. Furthermore, this section provides the opportunity to present again the cautionary note that follows about the GNU_tar program.


Caution – Caution –

For .tar.gz archives, do not use a program other than GNU_tar to untar the contents of the J2EE agent deliverables. Using a different program, such as another tar program, can result in some files not being extracted properly. To learn more about the GNU_tar program, visit the following web site:

http://www.gnu.org/software/tar/tar.html



Example 3–1 Format of the Distribution Files of Agent for Apache Tomcat Servlet/JSP Container

SJS_Tomcat_Server_55_agent_2.2.tar.gz
SJS_Tomcat_Server_55_agent_2.2.zip
SJS_Tomcat_Server_55_agent_2.2_SUNWamtc.tar.gz

For detailed information on the format of the distribution files, see Format of the Distribution Files for a J2EE Agent Installation in Policy Agent 2.2.



Example 3–2 Unpacking Non-Package Formatted Deliverables of Agent for Apache Tomcat Servlet/JSP Container

# gzip -dc SJS_Tomcat_Server_55_agent_2.2.tar.gz | tar xvf -

For detailed information about this command, see To Unpack Non-Package Formatted Deliverables of a J2EE Agent in Policy Agent 2.2.



Example 3–3 Unpacking Package Formatted Deliverables of Agent for Apache Tomcat Servlet/JSP Container


# gzip -dc SJS_Tomcat_Server_55_agent_2.2_SUNWamtc.tar.gz | tar xvf -

For detailed information about this command, see To Unpack Package Formatted Deliverables of a J2EE Agent in Policy Agent 2.2.



Example 3–4 Unpacking a .zip Compressed file of Agent for Apache Tomcat Servlet/JSP Container

unzip SJS_Tomcat_Server_55_agent_2.2.zip

For detailed information about this command, see To Unpack a .zip Compressed file of a J2EE Agent in Policy Agent 2.2.


Follow the specific steps outlined in the following section before you install the agent to reduce the chance of complications occurring during and after the installation.

ProcedureTo 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 – 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.