Chapter 7 Uninstalling Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1

The agentadmin program is used for initiating the installation and uninstallation programs of Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1. 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, which has two phases. The pre-uninstallation process requires that you interact with both the agent and with BEA WebLogic Server 9.0/9.1.

The uninstallation process varies 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 BEA WebLogic Server 9.0/9.1:

Perform the pre-uninstallation (preparation) tasks outlined in this section prior to uninstalling Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1. The first task involves removing the BEA WebLogic Server 9.0/9.1 Administration Console. The second task is to unconfigure and undeploy various aspects of the agent and of BEA WebLogic Server 9.0/9.1.

To Prepare to Uninstall Agent for BEA WebLogic Server 9.0/9.1: Console Task

Before you uninstall the agent for BEA WebLogic Server 9.0/9.1, perform the task described in this section to remove the Agent Authentication Provider that was configured after the installation of the agent.

A few scenarios, besides the task of uninstalling the agent, can necessitate, or at least be benefitted by, the removal of the Agent Authentication. Therefore, this task is described in another location within this guide where the task is not part of the uninstallation process. See, Removing the Agent Authenticator From BEA WebLogic Server 9.0/9.1.

This section outlines the steps necessary to successfully remove the Agent Authentication Provider from BEA WebLogic Server 9.0/9.1. Note that the information provided in this section is only to facilitate the removal of the Agent Authentication Provider and should not be taken as a substitute for the information provided in BEA WebLogic Server 9.0/9.1 documentation.

1. Log on to the BEA WebLogic Server 9.0/9.1 Administration Console.

2. In the left pane, under Domain Structure and under the host name of the server you are configuring, click “Security realm.”

3. In the right pane, click the name of the realm you are configuring.

4. Click the Providers tab.

5. Click the Authentication tab.

6. In the right pane, specify the Policy Agent Authentication Provider.

7. Click Delete.

8. Click Yes.

9. In the left pane, click activate changes.

   Agent Authentication Provider is not removed from the configuration until you restart the BEA WebLogic Server 9.0/9.1 instance. The best practice is to restart, the BEA WebLogic Server 9.0/9.1 instance after you perform the following:

   • The agent unconfiguration task (described subsequently)

   • The respective agent uninstallation task (also described in this chapter)

To Prepare to Uninstall Agent for BEA WebLogic Server 9.0/9.1: Unconfiguration Task

To prepare for the uninstallation of Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1, perform the following unconfiguration-related steps:

Throughout this guide scripting files apply to both UNIX platforms and Windows platforms even when the script for Windows platforms is not expressly mentioned. The difference is that scripts for UNIX platforms have the .sh extension while scripts for Windows platforms have the .cmd extension.

1. Undeploy any protected applications from BEA WebLogic Server 9.0/9.1.

   Refer to the BEA WebLogic Server 9.0/9.1 documentation for more information.

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

3. Before you uninstall the agent for BEA WebLogic Server 9.0/9.1, ensure that the following server is shut down:

   • BEA WebLogic Server 9.0/9.1 instance protected by the agent

4. Undeploy the agent application.

   The agent application must be undeployed from BEA WebLogic Server 9.0/9.1 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 BEA WebLogic Server 9.0/9.1.

5. (Conditional) If the BEA WebLogic Server 9.0/9.1 instance was originally configured using Node Manager, remove the classpath and agent java options using the BEA WebLogic Server 9.0/9.1 Administration Console.

   1. Expand the Servers node.

   2. Select the node for the server you want to manage with Node Manager.

   3. Remove the agent classpath entries in Node Manager.

      1. In the BEA WebLogic Server 9.0/9.1 Administration Console, select the Configuration tab.

      2. Select the Remote Start tab.

      3. Remove the following classpath entries:

         ${CLASSPATH}:PolicyAgent-base/lib/agent.jar:PolicyAgent-base/
         lib/amclientsdk.jar:PolicyAgent-base/locale:PolicyAgent-base/
         AgentInstance-Dir/config

         where AgentInstance-Dir represents an agent instance directory, such as agent_001.

         For information about PolicyAgent-base, see J2EE Agent Directory Structure in Policy Agent 2.2.

   4. Remove the agent java options in Node Manager.

      1. In the BEA WebLogic Server 9.0/9.1 Administration Console, select the Configuration tab.

      2. Select the Remote Start tab.

      3. Remove the following java options from the Arguments text field:

         -Djava.util.logging.config.file=PolicyAgent-base/config/
         AMAgentLogConfig.properties 
         -DLOG_COMPATMODE=Off

6. (Conditional) If the agent has been installed on a BEA WebLogic Server 9.0/9.1 instance on which Access Manager was previously deployed, modify the Access Manager configuration properties.

   The Access Manager configuration properties are modified in the AMConfig.properties file. Specifically, you must remove the entry that specifies the location of the agent configuration file associated with the agent instance being removed. For more information on the entry that must be removed, see Combining J2EE Agents With Access Manager.

7. Shut down the BEA WebLogic Server 9.0/9.1 domain before launching the agent uninstallation program.

Solaris Systems — Packages: Uninstalling Agent for BEA WebLogic Server 9.0/9.1

This method for uninstalling Agent for BEA WebLogic Server 9.0/9.1 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 BEA WebLogic Server 9.0/9.1:

SJS_Weblogic_9_agent_2.2_SUNWamwl.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 BEA WebLogic Server 9.0/9.1.

To Uninstall Agent for BEA WebLogic Server 9.0/9.1 on Solaris Systems — Packages

Issue the following command:

# pkgrm SUNWamwl

The preceding command removes the J2EE agent packages from the directory in which they were installed.

All Systems — Non-Packages: Uninstalling Agent for BEA WebLogic Server 9.0/9.1

This method for uninstalling Agent for BEA WebLogic Server 9.0/9.1 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 BEA WebLogic Server 9.0/9.1:

SJS_Weblogic_9_agent_2.2.tar.gz
SJS_Weblogic_9_agent_2.2.zip

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

Launching the Uninstallation Program of Agent for BEA WebLogic Server 9.0/9.1

Perform the steps outlined in this section to launch the uninstallation program of Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1.

To Launch the Uninstallation Program of Agent for BEA WebLogic Server 9.0/9.1

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 BEA WebLogic Server 9.0/9.1

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 BEA WebLogic Server 9.0/9.1.

Example of Uninstallation Program Interaction in Agent for BEA WebLogic Server 9.0/9.1

************************************************************************
Welcome to the Access Manager Policy Agent for BEA WebLogic 9 Platform.
If the Policy Agent is used with Federation Manager services, User needs to
enter information relevant to Federation Manager.

************************************************************************
Enter the path to the location of the script used to start the WebLogic domain.

[ ? : Help, ! : Exit ]
Enter the Startup script location
[/usr/local/bea/user_projects/domains/mydomain/startWebLogic.sh]:

Enter the name of the WebLogic domain secured by the agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the WebLogic domain name [myserver]:

-----------------------------------------------
SUMMARY OF YOUR RESPONSES
-----------------------------------------------
Startup script location :
/usr/local/bea/user_projects/domains/mydomain/startWebLogic.sh
WebLogic domain name : myserver

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]: