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.