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.