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

ProcedureTo Deploy the Agent Software Delivery Archive for SAP Web Application Server 6.40

This is one of the post-installation tasks required when Agent for SAP Portal 6.0/Server 6.40 has been installed on SAP Web Application Server 6.40.

Before You Begin

The following file is the Software Delivery Archive for this agent: AMSAPAgent2.2.sda.

For this task, you must provide the full path name to this Software Delivery Archive, as such:

PolicyAgent-base/etc/AmSAPAgent2.2.sda

Therefore, locate this file and record the full path name for use as part of the task.

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

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

  3. Log in to the GUI.

  4. Select the Deployment tab.

  5. Add the full path name to the following file:

    PolicyAgent-base/etc/AmSAPAgent2.2.sda
  6. Click the icon of the clipboard with the plus sign.

  7. Click Next until you reach the deployment Start button.

  8. Click Start.

  9. (Conditional) If using the agent with Access Manager 6.3, configure the appropriate library.


    Note –

    This step is similar to the steps required for the general configuration of the agent for Access Manager 6.3. For more information, see To Configure a J2EE Agent With Access Manager 6.3.


    By default, the AmSAPAgent2.2.library library is configured specifically for Access Manager 7. To use the agent with Access Manager 6.3, perform the following substeps.

    1. Stop the J2EE Engine.

    2. Change to the following directory:


      /usr/sap/SID/instanceName/j2ee/cluster/server0/bin/ext/AmSAPAgent2.2
      SID

      represents the SAP system ID.

      instanceName

      represents the SAP Web Application Server 6.40 instance.

    3. Create a backup copy of the Access Manager 7 amclientsdk.jar file, giving the copy a name such as amclientsdk70.jar

    4. Copy the amclientsdk63.jar file to the same directory, which is as follows:


      /usr/sap/SID/instanceName/j2ee/cluster/server0/bin/ext/AmSAPAgent2.2

      The following is the full path to the amclientsdk63.jar file:

      PolicyAgent-base/etc/amclientsdk63.jar
    5. Restart the J2EE engine.