Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Servlet and Filter management

Updated on March 15, 2022

Use the Servlet & Filter management landing page to manage settings in your Pega Cloud applications without the need to create service requests to manage filtering configurations.

Servlet Management and Filter Management have URL patterns in common. Both the filter and servlet are pieces of code that are run.

Filters are run before servlets. If the request proceeds, the servlet processes the request and then returns a response. The filter is an in-bound response only. The filter sits in front of the servlet.

The filter information is saved in database and is registered during server startup using the dynamic filter registration mechanism that the Servlet 3.0 provides through Java reflection APIs.

  • Servlet management

    Use the Servlet Management tab in your Pega Cloud applications to securely add, modify, and disable servlet configurations without editing the web.xml file.

  • Filter management

    Use the Filter Management tab in your Pega Cloud applications to create and manage Tomcat Java-based filters. Use this feature to securely filter traffic from your application URL without creating service requests to manage filter configurations.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us