Program guide > (deprecated) Partitioning facility > Partitioning facility programming > HTTP partitions
Deprecated feature: The partitioning facility (WPF) feature is deprecated. You can configure partitioning with WebSphere eXtreme Scale.
The HttpPartitionFilter packaging
Each servlet contained within a Web application that accesses a partition must make use of the HttpPartitionFilter. This filter ensures that incoming HTTP requests destined for a specific partition are delivered correctly to the application instance housing that partition. Small timing windows exist during partition movement where an on demand router's (ODR) partition-to-server mapping is temporarily out-of-date (due to a small delay in propagation this information from the target servers to the ODR). In these case, the servlet filter ensures that the request is not delivered to an incorrect application instance. Rather, the servlet filter detects the inconsistency and redirects the request to the appropriate target server.
To insert the HttpPartitionFilter into the processing chain, the filter must declared and mapped in the web.xml deployment descriptor of the web module archive (WAR file). An example of this is illustrated here:
<filter> <filter-name>HttpPartitionFilter</filter-name> <display-name>HttpPartitionFilter</display-name> <filter-class>com.ibm.websphere.http.wpf.HttpPartitionFilter</filter-class> </filter> <filter-mapping> <filter-name>HttpPartitionFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
Parent topic:HTTP partitions