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