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

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

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

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

   • WAS-base/AppServer/profiles/wp_profile/installedApps/
     Cell-Name/wps.ear/wps.war/WEB-INF

   • WAS-base/AppServer/profiles/wp_profile/config/cells/
     Cell-Name/applications/wps.ear/deployments/wps/wps.war/WEB-INF

   where:

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

   Cell-Name represents the IBM WebSphere Application Server 6.0 cell protected by the agent.

3. Backup the two web.xml files before modifying the deployment descriptors.

   Since you will modify the deployment descriptor in the next step, creating backup files at this point is important, especially if you need to uninstall the agent in the future.

4. Edit both of the web.xml files referred to in this task, as follows:

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