test

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

Preparing to Install Agent for SAP Enterprise Portal 7.0/Web Application Server 7.0

These agent binaries are available in .zip file format only. The example that follows provides details about the unpacking process.

Caution – Caution –

You must unpack the .zipfile as the SAP Instance User, SIDadm, in a directory owned by this user. Where SID is a place holder that represents the SAP system ID.

Do not perform this action as the root user. Furthermore, after unpacking the binaries, give execution permissions to the agentadmin utility, which is in the PolicyAgent-base/bin directory. For example:

chmod +x PolicyAgent-base/bin/agentadmin

Always issue the agentadmin utility as the SAP Instance User, SIDadm.

For more information, see , To Prepare to Install Agent for SAP Enterprise Portal 7.0/Web Application Server 7.0.

Example 3–1 Unpacking the .zip compressed file of Agent for SAP Enterprise Portal 7.0/Web Application Server 7.0

unzip sap_v7_agent.zip

Follow the specific steps outlined in the following section before you install the agent to reduce the chance of complications occurring during and after the installation.

ProcedureTo Prepare to Install Agent for SAP Enterprise Portal 7.0/Web Application Server 7.0

Perform the following pre-installation tasks:

  1. Ensure that the Policy Agent 2.2 for SAP Enterprise Portal 7.0/Web Application Server 7.0 is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for SAP Enterprise Portal 7.0/Web Application Server 7.0.

  2. Install SAP Enterprise Portal 7.0/Web Application Server 7.0 if not already installed.

  3. Ensure that the SAP Enterprise Portal 7.0/Web Application Server 7.0 instance that will be protected by the agent is not running.

  4. Create a valid agent profile in Access Manager Console if one has not already been created.

    For information on how to create an agent profile, see Creating a J2EE Agent Profile.

    To avoid a misconfiguration of the agent, ensure that you know the exact ID and password used to create the agent profile. You must enter the agent profile password correctly in the next step and you must enter the agent profile ID correctly when installing the agent.

  5. Create a text file and add the agent profile password to that file.

    Ensure that this file is located in a secure directory of your choice. You will refer to this file during the agent installation process.

    With the agent profile password in this file, stored in a secure location, you do not need to enter sensitive information in the console. A valid password file can have only one line that contains the agent profile password.

  6. Ensure that the agentadmin utility has execution permissions

    The following command is an example of how you can add execution permissions for this utility:

    chmod +x PolicyAgent-base/bin/agentadmin
    Caution – Caution –

    Always issue the agentadmin utility as the SAP Instance User, SIDadm.