Skip to main content

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

Deploying static content to an edge server

Updated on August 25, 2021

You can deploy static content to multiple web servers, also known as edge servers, to improve responsiveness in a large production system. In Web pages, the term static content usually refers to image files (.jpg, .png, .gif, and .swf), style sheet files (.css), and JavaScript files (.js) that do not frequently change. You can deploy static content to multiple web servers, also known as edge servers, to improve the responsiveness of your production system.

When your application is used in production, the user interface elements of your application are similarly considered static, even though they might differ from ruleset version to ruleset version. For example, a JavaScript routine that is saved in a text file rule is the same for all users who share the access group Alpha (and so have the same ruleset list). However, users who share a different access group that is named Beta might run a different version of the JavaScript function, from a different version text file rule, even if both the Alpha and Beta users are associated with a single application rule.

Note: To forward static content requests to an edge server, all static content references in the target application must use static JavaServer Page (JSP) tags and binaryfile JSP tags, rather than manually entering HTML tags to reference the static content file. For more information, see static JavaServer Page tag and binaryfile JavaServer Page tag.
  1. Identify an application (Rule-Application instance) that is used by target end users, and log in to Dev Studio as a developer that has access to the application.
    1. In the header of Dev Studio, click ConfigureSystemAssemblyExtract Edge Server Files.
  2. In the Extract Edge Server Files window, complete the following fields:
    1. In the Select Rule Application field, select the Application Name key part of an application rule.
    2. In the Application Version field, select the Version key part of an application rule.
    3. Enter a file name for the .zip file output.
    4. Click Create ZIP file. The activity runs and creates a .zip file that contains the static content in a subdirectory in the ServiceExport directory named RemoteWebServers of your system.
  3. Copy the .zip file to each edge server by identifying the host name, TCP/IP port, and URL path of the edge server to which you want to deploy the static content by using FTP or a similar file transfer program.
  4. In Dev Studio, copy the empty extension point activity Code-Security.ApplicationProfileSetup into a new ruleset that is made available to application users, keeping both key parts.
  5. Update the Pages & Classes tab of the new Activity form to add a row for the page name pxRequestor in the Code-Pega-Requestor class.
  6. Replace the first step of the activity with a Property-Set method that sets the pxRequestorpyEdgeServerURI property to the appropriate path, such as http://edgeserver1:8080/EdgeServer.
  7. Save the Activity form.
  8. Update the application rule (identified in step 1) to include the new ruleset version.
  9. Log in as a user who belongs to the updated access group.
  10. Clear your browser cache, and then use an HTTP sniffer program, such as Fiddler 2, to verify that static content is served from the edge server.
  11. Use the Application Explorer to access and review log entries to verify that the extraction tool records each execution as an instance of the Log-EdgeServer class and records any errors in instances of the Log-EdgeServer-Error class.
  12. If the static content changes, repeat steps 1 to 4.

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