Sun Java System Access Manager Policy Agent 2.2 Guide for JBoss Application Server 4.0

Previous: Chapter 5 Managing Policy Agent 2.2 for JBoss Application Server 4.0
Next: Appendix A Silent Installation and Uninstallation of a J2EE Agent in Policy Agent 2.2

Chapter 6 Uninstalling Policy Agent 2.2 for JBoss Application Server 4.0

The agentadmin program is used for initiating the installation and uninstallation programs of Policy Agent 2.2 for JBoss Application Server 4.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 uninstallation process differs depending upon the format of the deliverable files used during the initial installation of the agent: package formatted deliverable files or non-package formatted deliverable files.

If package formatted deliverables were used for installation of the agent, the uninstallation involves a single step.

If non-package formatted deliverables were used for installation, uninstallation consists of two phases. 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 JBoss Application Server 4.0

Perform the pre-uninstallation (preparation) steps outlined in this section before uninstalling Policy Agent 2.2 for JBoss Application Server 4.0.

To Prepare to Uninstall Agent for JBoss Application Server 4.0:

To prepare for the uninstallation of Policy Agent 2.2 for JBoss Application Server 4.0, perform the following steps:

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

Before you uninstall the agent for JBoss Application Server 4.0, ensure that the JBoss Application Server 4.0 instance protected by the agent is shut down.

(Conditional) If you are permanently removing Agent for JBoss Application Server 4.0, undeploy the agent application.

If you are permanently removing this agent, you must first undeploy the agent application from JBoss Application Server 4.0 before the agent is uninstalled. If you will install this agent again, you are not required to undeploy the agent application.

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 JBoss Application Server 4.0.

Solaris Systems — Packages: Uninstalling Agent for JBoss Application Server 4.0

This method of uninstalling Agent for JBoss Application Server 4.0 does not apply to all Solaris system uninstallations. This method only applies when the agent was originally installed using package formatted deliverables. Such deliverables are installed by issuing the following command:

# pkgadd -d

Package formatted deliverables have the string “_SUNWam” in the name of the compressed file used for delivering the Policy Agent 2.2 software. The following file name is an example of package formatted deliverable file used for Policy Agent 2.2 for JBoss Application Server 4.0:

SJS_JBoss_4.0_Server_agent_2.2_SUNWamjboss.tar.gz

For more information about package formatted deliverables for Solaris systems, see To Unpack Package Formatted Deliverables of a J2EE Agent in Policy Agent 2.2.

To uninstall this agent when the original deliverables were not in package format, regardless of the platform, see Launching the Uninstallation Program of Agent for JBoss Application Server 4.0.

To Uninstall Agent for JBoss Application Server 4.0 on Solaris Systems — Packages

Issue the following command:
```
# pkgrm SUNWamjboss
```
The preceding command removes the J2EE agent packages from the directory in which they were installed.

All Systems — Non-Packages: Uninstalling Agent for JBoss Application Server 4.0

This method for uninstalling Agent for JBoss Application Server 4.0 applies when the agent was originally installed using non-package formatted deliverables. The term “non-package formatted deliverables” refers to the format of the compressed file used for delivering the Policy Agent 2.2 software. Package formatted deliverables have the string “_SUNWam” in the name of the compressed file. Therefore, non-package formatted deliverables do not have this string in the file name. The following two file names are examples of non-package formatted deliverable files used for Policy Agent 2.2 for JBoss Application Server 4.0:

SJS_JBoss_4.0_Server_agent_2.2.tar.gz
SJS_JBoss_4.0_Server_agent_2.2.zip

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

Launching the Uninstallation Program of Agent for JBoss Application Server 4.0

Perform the steps outlined in this section to launch the uninstallation program of Policy Agent 2.2 for JBoss Application Server 4.0.

To Launch the Uninstallation Program of Agent for JBoss Application Server 4.0

To launch the uninstallation program, perform the following steps:

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.

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 JBoss Application Server 4.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 JBoss Application Server 4.0.

Example of Uninstallation Program Interaction in Agent for JBoss Application Server 4.0

************************************************************************
Welcome to the Access Manager Policy Agent for JBoss Server 4.0. If the
Policy Agent is used with Federation Manager services, User needs to enter
information relevant to Federation Manager.
************************************************************************
Enter the complete path to the directory which is used by JBoss Server to
store its configuration Files. This directory uniquely identifies the JBoss
Server instance that is secured by this Agent.
[ ? : Help, ! : Exit ]
Enter the JBoss Server Config Directory Path
[/opt/jboss-4.0.2/server/default/conf]:
-----------------------------------------------
SUMMARY OF YOUR RESPONSES
-----------------------------------------------
JBoss Server Config Directory : /opt/jboss-4.0.2/server/default/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 Agent parameters from
/opt/jboss-4.0.2/server/default/conf/jboss-service.xml file ...DONE.
Removing Agent parameters from
/opt/jboss-4.0.2/server/default/conf/server.policy file ...DONE.
Removing Agent parameters from am-login-config.xml file ...DONE.
Removing Agent parameters from
/opt/jboss-4.0.2/bin/setAgentClasspathdefault.sh file ...DONE.
Removing Agent parameters from agentapp.war file ...DONE.
Deleting the config directory
/opt/j2ee_agents/am_jboss_agent/agent_001/config ...DONE.
Uninstall log file location:
/opt/j2ee_agents/am_jboss_agent/logs/audit/uninstall.log
Thank you for using Access Manager Policy Agenta