test

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

Chapter 6 Uninstalling Policy Agent 2.2 for IBM WebSphere Application Server 5.1.1

The agentadmin program is used for initiating the installation and uninstallation programs of Policy Agent 2.2 for IBM WebSphere Application Server 5.1.1. 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 Application Server 5.1.1

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

ProcedureTo Prepare to Uninstall Agent for IBM WebSphere Application Server 5.1.1

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

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

    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 5.1.1.

  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 5.1.1.

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

    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 5.1.1.

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

    Specific Access Manager roles were granted access to IBM WebSphere Application Server 5.1.1 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 5.1.1 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 5.1.1 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 5.1.1.

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

  7. Undeploy the agent application.

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

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

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

All Systems: Uninstalling Agent for IBM WebSphere Application Server 5.1.1

This method for uninstalling Agent for IBM WebSphere Application Server 5.1.1 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 Application Server 5.1.1

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

ProcedureTo Launch the Uninstallation Program of Agent for IBM WebSphere Application Server 5.1.1

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 Application Server 5.1.1

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 Application Server 5.1.1.

Example of Uninstallation Program Interaction in Agent for IBM WebSphere Application Server 5.1.1


************************************************************************
Welcome to the Access Manager Policy Agent for IBM WebSphere Application
Server 5.1.1 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.
[ ? : Help, ! : Exit ]
Enter the Instance Config Directory
[/opt/WebSphere/AppServer/config/cells/host2/nodes/host2/servers/server1]:


Enter the Server Instance name.
[ ? : Help, < : Back, ! : Exit ]
Enter the Server Instance name [server1]:


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/host2/nodes/host2/servers/server1

Instance Server name : server1
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
/export/WASagent/j2ee_agents/am_websphere_agent/agent_001/config
...DONE.

Unconfigure server.xml file
/opt/WebSphere/AppServer/config/cells/host2/nodes/host2/servers/server1/server.x
ml
...DONE.


Uninstall log file location:
/export/WASagent/j2ee_agents/am_websphere_agent/logs/audit/uninstall.log

Thank you for using Access Manager Policy Agent
--------------------------------------------------

All Systems: Removing Files of Agent for IBM WebSphere Application Server 5.1.1

Once all instances of Agent for IBM WebSphere Application Server 5.1.1 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.

ProcedureTo Remove Files of Agent for IBM WebSphere Application Server 5.1.1 on All Systems — Non-Packages

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

  1. Delete the PolicyAgent-base directory from the file system.

ProcedureTo Remove Files of Agent for IBM WebSphere Application Server 5.1.1 on Solaris Systems — Packages

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

  1. Issue the following command:

    # pkgrm SUNWamwas

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