Sun Java System Access Manager Policy Agent 2.2 Guide for SAP Enterprise Portal 6.0 and Web Application Server 6.40

Previous: Chapter 5 Managing Policy Agent 2.2 for SAP Portal 6.0/Server 6.40
Next: Appendix A Silent Installation and Uninstallation of a J2EE Agent in Policy Agent 2.2

Chapter 6 Uninstalling Policy Agent 2.2 for SAP Portal 6.0/Server 6.40

The agentadmin program is used for initiating the installation and uninstallation programs of Policy Agent 2.2 for SAP Portal 6.0/Server 6.40. 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 information you need 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 SAP Portal 6.0/Server 6.40

Perform the applicable pre-uninstallation (preparation) tasks outlined in this section before uninstalling Policy Agent 2.2 for SAP Portal 6.0/Server 6.40. The uninstallation tasks are different depending upon the deployment container from which the agent is being uninstalled, as follows:

Perform the tasks that apply to the deployment container from which you want to uninstall the agent.

Pre-Uninstallation of Agent for SAP Portal 6.0/Server 6.40: SAP Enterprise Portal 6.0

Perform the tasks in this section if you are uninstalling Agent for SAP Portal 6.0/Server 6.40 from SAP Enterprise Portal 6.0. This section includes a variety of short tasks that remove the configuration performed during the installation and post-installation processes.

To Undeploy the Agent Software Delivery Archive for SAP Enterprise Portal 6.0

The Software Delivery Archive for this agent was deployed as a post-installation task. For details about that post-installation task, see To Deploy the Agent Software Delivery Archive for SAP Enterprise Portal 6.0.

(Conditional) If the SAP Enterprise Portal 6.0 is not running, start it now.

Start the Software Deployment Manager (SDM) Remote GUI.

The following example provides the path to the SDM Remote GUI on UNIX systems:
```
/usr/sap/SID/instanceName/SDM/program/RemoteGui.sh
```
SID

represents the SAP system ID.

instanceName

represents the SAP Enterprise Portal 6.0 instance.

Select the Undeployment tab.

Select AmSAPAgent2.2.

Click undeploy.

To Remove the Login Module for SAP Enterprise Portal 6.0

(Conditional) If the SAP Enterprise Portal 6.0 is not running, start it now.

Start the Visual Administration tool.

The following example provides the path to the Visual Administration tool on UNIX systems:
```
/usr/sap/SID/instanceName/j2ee/admin/go
```
SID

represents the SAP system ID.

instanceName

represents the SAP Enterprise Portal 6.0 instance.

Select the Security Provider service.

Select the User Management tab.

Click Manage Security Stores.

Select AmSAPEPLoginModule and click remove.

To Restore the Original State of the Ticket Template for SAP Enterprise Portal 6.0

This task description explains how to modify the ticket template of SAP Enterprise Portal 6.0 to the state it was in before it was modified during the post-installation of Agent for SAP Portal 6.0/Server 6.40.

Before You Begin

If necessary, start and log in to the Visual Administration tool as detailed in the preceding task description.

Select the Security Provider service.

Select the Policy Configurations tab.

In the Components list, select the ticket authentication template.

Click Add New

Select BasicPasswordLoginModule.

Click Modify.

Move BasicPasswordLoginModule between the following two login modules:
```
com.sap.security.core.server.jaas.EvaluteTicketLoginModule
com.sap.security.core.server.jaas.CreateTicketLoginModule
```
The new ticket authentication template appears as such:

EvaluateTicketLoginModule

SUFFICIENT

BasicPasswordLoginModule

REQUISITE

CreateTicketLoginModule

OPTIONAL

To Undeploy Protected Applications from SAP Enterprise Portal 6.0

Undeploy any protected applications from SAP Enterprise Portal 6.0.

Refer to SAP Enterprise Portal 6.0 documentation for more information.

To Restore the Deployment Descriptors of Applications on SAP Enterprise Portal 6.0

Restore the web.xml file of each deployed application to its original state.

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 deployment descriptors were configured during the post-installation of Agent for SAP Portal 6.0/Server 6.40, see Installing the Agent Filter for the Deployed Application on Agent for SAP Portal 6.0/Server 6.40.

To Remove the Agent Application from SAP Enterprise Portal 6.0

This task involves removing the agentapp.war file from SAP Enterprise Portal 6.0. This application is used by the agent to perform housekeeping tasks. This application was installed on the deployment container as a post-installation task. For more information, see Deploying the Agent Application for SAP Enterprise Portal 6.0.

(Conditional) If the SAP Enterprise Portal 6.0 is not running, start it now.

Start the Visual Administration tool.

The following example provides the path to the Visual Administration tool on UNIX systems:
```
/usr/sap/SID/instanceName/j2ee/admin/go
```
SID

represents the SAP system ID.

instanceName

represents the SAP Enterprise Portal 6.0 instance.

Expand the Services node.

Select the Deploy service.

Expand the servlet_jsp node under the node of SAP Enterprise Portal 6.0 (Ensure that the SAP Enterprise Portal 6.0 node is for the instance that you are preparing to uninstall).

Select the sap.com/agentapp application.

Click Remove.

Next Steps

Before you uninstall Agent for SAP Portal 6.0/Server 6.40, ensure that you stop and start the SAP Portal 6.0/Server 6.40 instance protected by the agent.

Pre-Uninstallation of Agent for SAP Portal 6.0/Server 6.40: SAP Web Application Server 6.40

Perform the tasks in this section if you are uninstalling Agent for SAP Portal 6.0/Server 6.40 from SAP Web Application Server 6.40. This section includes a variety of short tasks that remove the configuration performed during the installation and post-installation processes.

To Undeploy the Agent Software Delivery Archive for SAP Web Application Server 6.40

(Conditional) If the SAP Web Application Server 6.40 is not running, start it now.

Start the Software Deployment Manager (SDM) Remote GUI.

The following example provides the path to the SDM Remote GUI on UNIX systems:
```
/usr/sap/SID/instanceName/SDM/program/RemoteGui.sh
```
SID

represents the SAP system ID.

instanceName

represents the SAP Web Application Server 6.40 instance.

Select the Undeployment tab.

Select AmSAPAgent2.2.

Click undeploy.

To Remove the Login Module for SAP Web Application Server 6.40

(Conditional) If the SAP Web Application Server 6.40 is not running, start it now.

Start the Visual Administration tool.

The following example provides the path to the Visual Administration tool on UNIX systems:
```
/usr/sap/SID/instanceName/j2ee/admin/go
```
SID

represents the SAP system ID.

instanceName

represents the SAP Web Application Server 6.40 instance.

Select the Security Provider service.

Select the User Management tab.

Click Manage Security Stores.

Select AmSAPWASLoginModule and click remove.

To Undeploy Protected Applications from SAP Web Application Server 6.40

Undeploy any protected applications from SAP Web Application Server 6.40.

Refer to SAP Web Application Server 6.40 documentation for more information.

To Restore the Deployment Descriptors of Applications on SAP Web Application Server 6.40

Restore the web.xml file of each deployed application to its original state.

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 deployment descriptors were configured during the post-installation of Agent for SAP Portal 6.0/Server 6.40, see Installing the Agent Filter for the Deployed Application on Agent for SAP Portal 6.0/Server 6.40.

To Remove the Agent Application from SAP Web Application Server 6.40

This task involves removing the agentapp.war file from SAP Web Application Server 6.40. This application is used by the agent to perform housekeeping tasks. This application was installed on the deployment container as a post-installation task. For more information, see Deploying the Agent Application for SAP Web Application Server 6.40.

(Conditional) If the SAP Web Application Server 6.40 is not running, start it now.

Start the Visual Administration tool.

The following example provides the path to the Visual Administration tool on UNIX systems:
```
/usr/sap/SID/instanceName/j2ee/admin/go
```
SID

represents the SAP system ID.

instanceName

represents the SAP Web Application Server 6.40 instance.

Expand the Services node.

Select the Deploy service.

Expand the servlet_jsp node under the node of SAP Web Application Server 6.40 (Ensure that the SAP Web Application Server 6.40 node is for the instance that you are preparing to uninstall).

Select the sap.com/agentapp application.

Click Remove.

Next Steps

Before you uninstall Agent for SAP Portal 6.0/Server 6.40, ensure that you stop and start the SAP Portal 6.0/Server 6.40 instance protected by the agent.

All Systems: Uninstalling Agent for SAP Portal 6.0/Server 6.40

This method of uninstalling Agent for SAP Portal 6.0/Server 6.40 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 SAP Portal 6.0/Server 6.40

Perform the steps outlined in this section to launch the uninstallation program of Policy Agent 2.2 for SAP Portal 6.0/Server 6.40.

To Launch the Uninstallation Program of Agent for SAP Portal 6.0/Server 6.40

To launch the uninstallation program, perform the following steps:

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.

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 SAP Portal 6.0/Server 6.40

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 SAP Portal 6.0/Server 6.40.

Example of Uninstallation Program Interaction in Agent for SAP Portal 6.0/Server 6.40

************************************************************************
Welcome to the Access Manager Policy Agent for SAP WebAS and Enterprise
Portal

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


Enter the complete path to the directory of your SAP server ID. This directory
uniquely identifies the SAP instance that is secured by this Agent.
[ ? : Help, ! : Exit ]
Enter the SAP Server <SID> Directory Path
[/usr/sap/J2E/JC00/j2ee/cluster/server0]:
-----------------------------------------------
SUMMARY OF YOUR RESPONSES
-----------------------------------------------
SAP <SID> Directory : /usr/sap/SSO/JC00/j2ee/cluster/server0
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]:

All Systems: Removing Files of Agent for SAP Portal 6.0/Server 6.40

Once all instances of Agent for SAP Portal 6.0/Server 6.40 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 SAP Portal 6.0/Server 6.40 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 SAP Portal 6.0/Server 6.40 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.