To Add the Agent Filter to the IBM WebSphere Portal Server 5.1.0.2 Application

This required task more tightly integrates the IBM WebSphere Portal Server 5.1.0.2 instance with the Access Manager environment.

This task is only required once per IBM WebSphere Portal Server 5.1.0.2 instance for a given host.

Agent for IBM WebSphere Portal Server 5.1.0.2 provides a servlet filter that can be added to the IBM WebSphere Portal Server 5.1.0.2 application. This filter allows the enforcement of coarse grained URL policies defined within Access Manager to further control the access to protected resources on the IBM WebSphere Portal Server 5.1.0.2 instance. The filter can also be configured to provide additional personalization information in the form of HTTP Headers, cookies, or HTTP Request Attributes that can be used to further enhance the functionality of protected components. The following steps detail how this filter can be installed.

1. Ensure that the instance of IBM WebSphere Application Server on which the IBM WebSphere Portal Server 5.1.0.2 is deployed is stopped.

2. Locate the wps.war/WEB-INF/web.xml file that contains the deployment descriptors for IBM WebSphere Portal Server 5.1.0.2.

   The IBM WebSphere Application Server runtime can read this file from either of the following directories:

   • WPS-base/installedApps/Cell-Name/wps.ear/wps.war/WEB-INF

   • WPS-base/config/cells/Cell-Name/applications/wps.ear/deployments/wps/wps.war/WEB-INF

   WPS-base

   represents the directory within which the IBM WebSphere Portal Server 5.1.0.2 instance was installed.

   Cell-Name

   represents the IBM WebSphere Portal Server 5.1.0.2 cell protected by the agent.

3. Create the necessary backups before proceeding to modify these descriptors.

   Since you will modify the deployment descriptor in the next step, creating backup files at this point is important.

4. Edit both of the web.xml files referred to in this task.

   The two web.xml files should be edited as follows:

   <web-app id="IBM_WPS"> <display-name>WebSphere Portal Server</display-name> <filter id="Filter_PolicyAgent"> <filter-name>Policy Agent</filter-name> <filter-class> com.sun.identity.agents.filter.AmAgentFilter </filter-class> </filter> ... //other filter definitions <filter-mapping id="FilterMapping_PolicyAgent"> <filter-name>Policy Agent</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>... //other filter mappings </web-app>