- 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.
- In the header of Dev Studio, click .
- In the Extract Edge Server Files window, complete the following
- In the Select Rule Application field, select the Application Name key part of an application rule.
- In the Application Version field, select the Version key part of an application rule.
- Enter a file name for the .zip file output.
- 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.
- 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.
- 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.
- 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.
Replace the first step of the activity with a Property-Set method that sets the
property to the appropriate path, such as
- Save the Activity form.
- Update the application rule (identified in step 1) to include the new ruleset version.
- Log in as a user who belongs to the updated access group.
- 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.
- 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.
- If the static content changes, repeat steps 1 to 4.