Chapter 6 Uninstalling Policy Agent 2.2 for IBM WebSphere Portal Server 5.1.0.2

The agentadmin program is used for initiating the installation and uninstallation programs of Policy Agent 2.2 for IBM WebSphere Portal Server 5.1.0.2. 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 type of information 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. Finally, remove the agent files unless you want to configure a new agent using the same files.

Removing the agent files varies depending upon the format of the deliverable files used during the initial installation of the agent. Package formatted deliverable files are removed differently than files that are not package formatted.

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 IBM WebSphere Portal Server 5.1.0.2

Perform the pre-uninstallation (preparation) steps outlined in this section before uninstalling Policy Agent 2.2 for IBM WebSphere Portal Server 5.1.0.2.

To Prepare to Uninstall Agent for IBM WebSphere Portal Server 5.1.0.2

To prepare for the uninstallation of Policy Agent 2.2 for IBM WebSphere Portal Server 5.1.0.2, perform the following steps:

1. (Conditional) Stop the IBM WebSphere Portal Server 5.1.0.2 instance if it is running.

2. Restore the JSP files modified during post-installation of the agent.

   If backup copies were made of these files during the post-installation process, replace each file with its respective backup copy. For information about how these files were modified during post-installation of the agent, see To Change the Login and Logout Link Actions for IBM WebSphere Portal Server 5.1.0.2.

3. Restore the ConfigService.properties file modified during post-installation of the agent.

   If a backup copy was made of the ConfigService.properties file during the post-installation process, replace the current file with the backup. For information about how this file was modified during post-installation of the agent, see To Change the Login and Logout Link Actions for IBM WebSphere Portal Server 5.1.0.2.

4. Restore the two web.xml files of the IBM WebSphere Portal Server 5.1.0.2 application.

   If backup copies were made of these web.xml files during the post-installation process, replace the current files with the backup files.

   For information about how these files were modified during the post-installation of the agent, see To Add the Agent Filter to the IBM WebSphere Portal Server 5.1.0.2 Application.

5. Undeploy the agent application.

   The agent application must be undeployed from IBM WebSphere Portal Server 5.1.0.2 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 Deploying the Agent Application for J2EE Agents in Policy Agent 2.2.

6. (Conditional) If the agent has been installed on a IBM WebSphere Portal Server 5.1.0.2 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. Restart the associated IBM WebSphere Application Server's Administration instance.

All Systems: Uninstalling Agent for IBM WebSphere Portal Server 5.1.0.2

This method for uninstalling Agent for IBM WebSphere Portal Server 5.1.0.2 applies to all the supported platforms.

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

Launching the Uninstallation Program of Agent for IBM WebSphere Portal Server 5.1.0.2

Perform the steps outlined in this section to launch the uninstallation program of Policy Agent 2.2 for IBM WebSphere Portal Server 5.1.0.2.

To Launch the Uninstallation Program of Agent for IBM WebSphere Portal Server 5.1.0.2

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 IBM WebSphere Portal Server 5.1.0.2

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 IBM WebSphere Portal Server 5.1.0.2.

Example of Uninstallation Program Interaction in Agent for IBM WebSphere Portal Server 5.1.0.2

Uninstall the agent from every instance of the underlying IBM WebSphere Application Server.

The following interaction example demonstrates the uninstallation of Agent for IBM WebSphere Portal Server 5.1.0.2, where WebSphereServer-instance-name represents the WebSphere Server instance name. The default instance is often named server1 and the IBM WebSphere Portal Server instance is often named WebSphere_Portal.

************************************************************************
Welcome to the Access Manager Policy Agent for IBM WebSphere Portal Server
5.1.0.2 Agent. If the Policy Agent is used with Federation Manager services,
User needs to enter information relevant to Federation Manager.

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


Enter the fully qualified path to the configuration directory of the Server
Instance for the WebSphere node. Please ensure that the installer is run on
the WebSphere instance that will host the WebSphere Administration Console
first before the installer is run on the WebSphere Portal instance.
[ ? : Help, ! : Exit ]
Enter the Instance Config Directory
[/opt/WebSphere/AppServer/config/cells/wpshost/nodes/wpshost/servers/WebSphereServer-instance-name]: 

Enter the Server/Portal Instance name.
[ ? : Help, < : Back, ! : Exit ]
Enter the Server/Portal Instance name [WebSphereServer-instance-name]:


Enter the WebSphere Install Root directory.
[ ? : Help, < : Back, ! : Exit ]
Enter the WebSphere Install Root directory [/opt/WebSphere/AppServer]: 


-----------------------------------------------
SUMMARY OF YOUR RESPONSES
-----------------------------------------------
Instance Config Directory :
/opt/WebSphere/AppServer/config/cells/wpshost/nodes/wpshost/servers/WebSphereServer-instance-name

Instance Server/Portal name : WebSphereServer-instance-name
WebSphere Install Root Directory : /opt/WebSphere/AppServer


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

Remove agent.jar,amclientsdk.jar from
/opt/WebSphere/AppServer/lib/ext...DONE.

Deleting the config directory
/opt/j2ee_agents/am_wps_agent/agent_001/config...DONE.

Unconfigure server.xml file
/opt/WebSphere/AppServer/config/cells/wpshost/nodes/wpshost/servers/WebSphereServer-instance-name/server.xml
...DONE.


Uninstall log file location:
/opt/j2ee_agents/am_wps_agent/logs/audit/uninstall.log

Thank you for using Access Manager Policy Agent

All Systems: Removing Files of Agent for IBM WebSphere Portal Server 5.1.0.2

Once all instances of Agent for IBM WebSphere Portal Server 5.1.0.2 have been removed as part of the uninstallation process, you must then remove the agent files unless you want to configure a new agent using the same files. Removing the agent files is a simple process. However, the process is different depending upon how the agent deliverables were originally installed.

Two task descriptions follow. In most cases the first task description applies. Perform the appropriate task.

To Remove Files of Agent for IBM WebSphere Portal Server 5.1.0.2 on All Systems — Non-Packages

Perform the steps in this task description if the following conditions applied when the agent was originally installed:

• On any supported platform.

• Without package formatted deliverables.

Delete the PolicyAgent-base directory from the file system.

To Remove Files of Agent for IBM WebSphere Portal Server 5.1.0.2 on Solaris Systems — Packages

Perform the steps in this task description if both of the following conditions applied when the agent was originally installed:

• On a supported Solaris platform.

• With package formatted deliverables.

Issue the following command:

# pkgrm SUNWamwas

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