Sun Java System Access Manager Policy Agent 2.2 Guide for IBM WebSphere Portal Server 6.0

Conditional Post-Installation Steps for Version 2.2 J2EE Agents

The following steps described in this section might be required, depending on your site's specific deployment:

Creating the Necessary URL Policies

If the agent is installed and configured to operate in the URL_POLICY or ALL mode, the appropriate URL policies must be created. For example, WebSphere Application Server with Administration Console is listening on ports 10001 (http) and 10003 (https), respectively, and WebSphere Portal Server is listening on port 10038 (http), create the following polices for the WebSphere Administrative user IDs (wasadmin and wpsadmin) to allow them to access the WebSphere Administration Console and Portal Server URLs:***

Note: This example assumes that is the Administration console URL and is the Portal Server URL.

If the policies are not defined and the agent is configured to operate in the URL_POLICY or ALL mode, then no user is allowed access to the IBM WebSphere Application Server and Portal Server 6.0 resources.

For information about creating these policies using the Access Manager Console or command-line utilities, see the Sun Java System Access Manager 7.1 Administration Guide.

Installing and Configuring the WebSphere Portal 6.0 Agent With Access Manager 6 2005Q1 (6.3)

To use this agent with Access Manager 6.3, perform these steps after the agent installation.

ProcedureTo Install and Configure the WebSphere Portal 6.0 Agent With Access Manager 6 2005Q1 (6.3)

  1. Change to the PolicyAgent-base/lib directory.

  2. Download the amclientsdk63.jar and fmclientsdk.jar files to the PolicyAgent-base/lib directory from the OpenSSO project site:

  3. Change to the WAS-base/AppServer/lib/ext directory.

    where WAS-base represents the directory where IBM WebSphere Application Server 6.0 was installed.

  4. Copy the downloaded amclientsdk63.jar and fmclientsdk.jar files into the WAS-base/AppServer/lib/ext directory and remove the famclientsdk.jar file.

  5. Restart all WebSphere server instances to make these changes take effect.