Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Balancing HTTP traffic across multiple server nodes

Updated on April 5, 2022

In a multi-node Pega Platform system, server demands from interactive user sessions are ideally balanced across nodes in relation to their power. (Some processing workload arises from agents and services rather than from interactive users; this can occur on designated nodes.)

Typically, such load balancing is achieved with hardware routers that support "sticky" HTTP sessions, so that a user who happens to first log into node ALPHA remains with ALPHA for the duration of the session. For example, Cisco Systems Inc. and F5 Networks Inc. offer such hardware (among others).

However, in some situations, software-based load balancing is appropriate. For example, IBM's WebSphere Edge Components includes a Load Balancer module. In some environments, reverse proxy servers are useful.

To support reverse proxy serving, add the following entries to the prconfig.xml file or dynamic system settings:

<env name="Initialization/ContextRewriteEnabled" value="true" />
<env name="Initialization/SetBaseHTMLContext"value="http://revproxy/AcmeCorp/setup" />

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