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

Chapter 6 Uninstalling Policy Agent 2.2 for Apache Tomcat 6.0

The agentadmin program is used for initiating the installation and uninstallation programs of Policy Agent 2.2 for Apache Tomcat 6.0. The difference is that the installation program is started with the --install option while the uninstallation program is started with the --uninstall option. For more information about the agentadmin program, see Key Features and Tasks Performed With the J2EE agentadmin Program. The uninstallation program is similar to the installation program in that it provides step by step explanations of the information you need to enter. However, the uninstallation program has fewer and simpler steps.

The uninstallation process follows a series of tasks similar to the installation process. First, perform the pre-uninstallation (preparation) steps. Then, perform the uninstallation, itself.

The first phase of uninstallation is the launching of the uninstallation program. The second phase of uninstallation involves interacting with the uninstallation program. During this phase, the program prompts you step by step to enter specific information while providing you with explanations about that information.

You must access the PolicyAgent-base directory for uninstallation-related tasks. For more information about this directory, see J2EE Agent Directory Structure in Policy Agent 2.2.

Preparing to Uninstall Agent for Apache Tomcat 6.0

Perform the pre-uninstallation (preparation) steps outlined in this section before uninstalling Policy Agent 2.2 for Apache Tomcat 6.0.

ProcedureTo Prepare to Uninstall Agent for Apache Tomcat 6.0

To prepare for the uninstallation of Policy Agent 2.2 for Apache Tomcat 6.0, perform the following steps:

  1. Undeploy any protected applications from Apache Tomcat 6.0.

    Refer to the Apache Tomcat 6.0 documentation for more information.

  2. Restore the deployment descriptors of these applications to their original deployment descriptors.

  3. Ensure that the Apache Tomcat 6.0 instance from which you are about to uninstall the agent is not running.

  4. Undeploy the agent application.

    The agent application must be undeployed from Apache Tomcat 6.0 before the agent is uninstalled.

    The agent application was installed during the post-installation steps. For more information about the installation of this application see Chapter 3, Installing Policy Agent 2.2 for Apache Tomcat 6.0.

Uninstalling Agent for Apache Tomcat 6.0

This uninstallation process involves two phases as described in the following subsections.

Launching the Uninstallation Program of Agent for Apache Tomcat 6.0

Perform the steps outlined in this section to launch the uninstallation program of Policy Agent 2.2 for Apache Tomcat 6.0.

ProcedureTo Launch the Uninstallation Program of Agent for Apache Tomcat 6.0

To launch the uninstallation program, perform the following steps:

  1. Change to the following directory:

    PolicyAgent-base/bin

    This directory contains the agentadmin program, which is used for uninstalling a J2EE agent and for performing other tasks. For more information on the agentadmin program, see Key Features and Tasks Performed With the J2EE agentadmin Program.

  2. Issue one of the following commands:


    ./agentadmin --uninstall

    or


    ./agentadmin --uninstallAll

    These two commands are different in that the --uninstallAll option removes all configured instances of the agent.

    After you issue one of the preceding commands, the uninstallation program launches and presents you with the first prompt as illustrated in the following section.

Using the Uninstallation Program of Agent for Apache Tomcat 6.0

The steps in the uninstallation program are displayed in the following example. The interaction process of this uninstallation program is similar to that of the installation program. One difference is that the uninstallation program does not present a license agreement. For a more detailed explanation of the interaction process, see Using the Installation Program of Agent for Apache Tomcat 6.0.

Example of Uninstallation Program Interaction in Agent for Apache Tomcat 6.0


************************************************************************
Welcome to the Access Manager Policy Agent for Apache Tomcat 6.0 Servlet/JSP
Container

************************************************************************


Enter the complete path to the directory which is used by Tomcat Server to
store its configuration Files. This directory uniquely identifies the
Tomcat Server instance that is secured by this Agent.
[ ? : Help, ! : Exit ]
Enter the Tomcat Server Config Directory Path
[/opt/apache-tomcat-6.0.14/conf]:

-----------------------------------------------
SUMMARY OF YOUR RESPONSES
-----------------------------------------------
Tomcat Server Config Directory :
/opt/apache-tomcat-6.0.14/conf
Verify your settings above and decide from the choices below.
1. Continue with Uninstallation
2. Back to the last interaction
3. Start Over
4. Exit
Please make your selection [1]:
Removing the agent classpath from
/opt/apache-tomcat-6.0.14/bin/setclasspath.sh script ...DONE.

Deleting the config directory
Agent-HomeDirectory/j2ee_agents/tomcat_v6_agent/Agent_001/config
...DONE.

Removing SJS Tomcat Agent Realm from Server XML file :
/opt/apache-tomcat-6.0.14/conf/server.xml ...DONE.

Removing filter from Global deployment descriptor file :
/opt/apache-tomcat-6.0.14/conf/web.xml ...DONE.

Removing SJS Tomcat Agent Filter and Form login authentication from Web
applications ...DONE.


Uninstall log file location:
Agent-HomeDirectory/j2ee_agents/tomcat_v6_agent/logs/audit/uninstall.log

Thank you for using Access Manager Policy Agent
----------------