Skip to main content


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

Moving the * URL pattern between servlets

Updated on June 30, 2021

The * is a wildcard character that is not used in the URL. * is the default servlet URL pattern that you can replace with another servlet.

Moving the * is optional and is done to change to the default and set up automatic redirection. For example, if one of your teams decides to move the * from default WebStandard to DeltaTeam, all access is automatically redirected from https://deltateam.pega.com to https://deltateam.pega.com/Prweb/deltateam by default.

If a request is received that does not match any of the defined URL patterns, then the definition for * is used to determine to what servlet the request is dispatched.

If you access something after /prweb and the servlet is not found, you are redirected to the default servlet, where * is configured as the URL pattern.

If the * URL pattern is not provided, then system becomes inaccessible. * is the minimum servlet requirement for a servlet to be accessible. Without *, the servlet produces a 403 error. The Servlet Management landing page provides a validation to ensure that at least one servlet is in the Enabled state with * as the URL pattern.

  1. Access the servlet from which you want to move the * URL pattern:
    1. In the header of Dev Studio, click ConfigureSystemSettingsServlet Management.
    2. Identify the servlet from which you want to remove the * URL pattern, click the More icon on the right side of the window, and then select Configure.
    3. Under URL patterns, click the delete icon beside the * URL pattern.
    4. Click Update.
  2. Add the * URL pattern to the servlet that you want to update:
    1. Identify the servlet to which you want to add the * URL pattern, click the More icon on the right side of the window, and then select Configure.
    2. Under URL patterns, click Add.
    3. Enter the * URL pattern.
    4. Click Update.
    5. For the changes to take effect, you must restart your entire environment.
What to do next: To request a restart of the entire environment, select New request in My Support Portal. For more information, see:
  • Adding a servlet

    Add a new servlet, without editing the web.xml file, by cloning and modifying existing servlets where necessary.

  • Cloning a servlet

    Servlet Management is only available for Pega Cloud, and allows you to add, modify, and disable servlet configurations without editing the web.xml file. Clone a servlet to create a new servlet without having to recreate all the parameters.

  • Configuring a servlet

    Servlet Management is only available for Pega Cloud, and allows you to add, modify, and disable servlet configurations without editing the web.xml file. Create new servlets by cloning existing servlets and modifying where necessary.

  • Disabling a servlet

    Servlet Management is only available for Pega Cloud, and allows you to add, modify, and disable servlet configurations without editing the web.xml file. If there is a servlet that is not commonly used within the application and that you want to keep in the system, you can disable the servlet.

  • Deleting a servlet

    Servlet Management is only available for Pega Cloud, and allows you to add, modify, and disable servlet configurations without editing the web.xml file. You can delete user-defined servlets that are no longer used in the system and that you do not need to keep within the system.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us