test

Sun Java System Access Manager Policy Agent 2.2 Guide for IBM WebSphere Application Server 6.0

Preparing to Uninstall Agent for IBM WebSphere Application Server 6.0

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

ProcedureTo Prepare to Uninstall Agent for IBM WebSphere Application Server 6.0

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

  1. Restore the Pre-Agent Registry of IBM WebSphere Application Server 6.0.

    Remove the agent Custom Registry. The Custom Registry was set as a post-installation step of the agent. Save and apply changes to Master configuration.

    For more information, see To Set the Custom Registry of IBM WebSphere Application Server 6.0.

  2. Remove the Access Manager Trust Association Interceptor

    Remove the Access Manager Trust Association Interceptor. Save and apply changes to Master configuration.

    The Trust Association Interceptor was added as a post-installation step of the agent. For more information, see To Add an Access Manager Trust Association Interceptor to IBM WebSphere Application Server 6.0.

  3. Turn off global security of IBM WebSphere Application Server 6.0.

    Turn off global security. Save and apply changes to Master configuration.

    Global security was turned on as a post-installation step of the agent. For more information, see To Turn On Global Security of IBM WebSphere Application Server 6.0.

  4. Remove access to IBM WebSphere Application Server 6.0 Administration Console.

    Specific Access Manager roles were granted access to IBM WebSphere Application Server 6.0 Administration Console as a post-installation step of the agent that involved editing the admin-authz.xmlfile. Access must be removed for all Access Manager roles previously granted access to the Administration Console. If a backup copy of the admin-authz.xml file was created when the agent was originally installed, the best practice is to restore the backed up file so that the original file is restored.

    Note –

    If you choose to edit the admin-authz.xml file using the agentadmin command, you must use the --removeGroup option. For a description of the --removeGroup option, see the Note in the section referenced in the following paragraph.

    For more information about how these roles were granted access, see To Grant Access to IBM WebSphere Application Server 6.0 Administration Console.

  5. Restore the web.xml descriptors to their original state.

    An agent filter was added to the web.xml descriptor of every deployed application and for the IBM WebSphere Application Server 6.0 Administration Console application as part of the agent post-installation configuration. For the Administration Console application, if a backup copy of the web.xml file was created during post-installation of the agent, the same file can be used to restore the original configuration. For more information about how these descriptors were edited during post-installation, see the following sections:

  6. Undeploy any protected applications from IBM WebSphere Application Server 6.0.

    Refer to IBM WebSphere Application Server 6.0 documentation for more information.

  7. Undeploy the agent application.

    The agent application must be undeployed from IBM WebSphere Application Server 6.0 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.

  8. (Conditional) If the agent has been installed on a IBM WebSphere Application Server 6.0 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.

  9. Stop all instances of IBM WebSphere Application Server 6.0.