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

Implications of Specific Deployment Scenarios in Agent for SAP Portal 6.0/Server 6.40

The following sections refer to specific deployment scenarios involving Policy Agent 2.2 for SAP Portal 6.0/Server 6.40. These scenarios are likely to affect how you respond to prompts during the installation process. You might also need to perform additional configurations.

Selecting the Domain Type on Which To Install Agent for SAP Portal 6.0/Server 6.40

During installation, you are prompted about the domain on which you are installing the agent. The installer configures the installation differently depending upon the deployment container to which the domain is associated: SAP Web Application Server 6.40 or SAP Enterprise Portal 6.0.


Note –

The two deployment containers each require that you perform specific post-installation tasks as described in Chapter 4, Post-Installation Tasks of Policy Agent 2.2 for SAP Portal 6.0/Server 6.40.


As shown in the following task description, to install this agent on a Web Application Server 6.40 (WebAS) domain, enter true when prompted. If you are installing the agent on an Enterprise Portal 6.0 domain, do not change this value from its default value of false.

ProcedureTo install Agent for SAP Portal 6.0/Server 6.40 on a WebAS Domain

The prompt shown in this procedure appears in the agent installation program, which is described in Example of Installation Program Interaction in Agent for SAP Portal 6.0/Server 6.40.

  1. Enter true to the following prompt:

    Enter true if the agent is being installed on a WebAS domain
    [ ? : Help, < : Back, ! : Exit ]
    Is the agent being installed on a WebAS domain ? [true]:

Protecting Applications Simultaneously on SAP Web Application Server 6.40 and SAP Enterprise Portal 6.0

One instance of Agent for SAP Portal 6.0/Server 6.40 protecting the SAP Enterprise Portal 6.0 application in addition to another instance running on Web Application Server 6.40 is a supported configuration, however the installation process differs slightly. For example, if you first run the installation program on the SAP Enterprise Portal 6.0 application, you are not required to run the installation program again on the Web Application Server 6.40 instance. Also, you will only be able to configure one config and locale class path in the SAP J2EE configuration tool.

If you are installing the agent on an SAP Enterprise Portal 6.0 domain before installing the agent on an SAP Web Application Server 6.40 domain, follow the instructions for installation and post-installation of SAP Enterprise Portal 6.0 as provided in this guide. You can then configure the second agent instance for SAP Web Application Server 6.40 also following the post-installation task descriptions in this guide, but specifically for SAP Web Application Server 6.40.

Installing Agent for SAP Portal 6.0/Server 6.40 in a Clustered Environment

To create a cluster in your SAP environment, you can either add additional dialogue instances to the central instance or add additional server processes to your existing central instance. Obtain information on setting up such a cluster at http://help.sap.com/.

Whether your cluster consists of multiple dialogue instances with one or more server processes, or multiple server processes for a central instance, you will need to perform the agent installation process on each server node that you would like the agent to protect. For example the following path represents server0 on the central instance:

/usr/sap/J2E/JC03/j2ee/cluster/server0

And the following path represents server1 on the dialog instance:

/usr/sap/J2E/J04/j2ee/cluster/server1

For the preceding examples, you must provide the corresponding directory structure to the first agent installation interaction. Similarly, on each node, you must deploy the agent application as described in Deploying the Agent Application for SAP Enterprise Portal 6.0.