IBM Rational Application Developer or an assembly tool can configure the servlet filters. Two steps are involved in configuring a servlet filter.
Optionally, assign initialization parameters that get passed to the init method of the servlet filter. After configuring the servlet filter, the web.xml application deployment descriptor contains a servlet filter configuration similar to the following example:
<filter id="Filter_1"> <filter-name>LoginFilter</filter-name> <filter-class>LoginFilter</filter-class> <description>Performs pre-login and post-login operation</description> <init-param>// optional <param-name>ParameterName</param-name> <param-value>ParameterValue</param-value> </init-param> </filter>
After mapping the servlet filter to a URL or a servlet, theweb.xml application deployment descriptor contains servlet mapping similar to the following example:
<filter-mapping> <filter-name>LoginFilter</filter-name> <url-pattern>/j_security_check</url-pattern> // can be servlet <servlet>servletName</servlet> </filter-mapping>
You can use servlet filters to replace the CustomLoginServlet servlet, and to perform additional authentication, auditing, and logging. The WebSphere Application Server Samples Gallery provides a form login sample that demonstrates how to use the WebSphere Application Server login facilities to implement and configure form login procedures. The sample integrates the following technologies to demonstrate the WebSphere Application Server and J2EE login functionality:
The form login sample is part of the Technology Samples package. For
more information on how to access the form login sample, see Accessing Samples.