Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Saurabh Gupta (SaurabhG4406)
Scotiabank

Scotiabank
CA
SaurabhG4406 Member since 2016 10 posts
Scotiabank
Posted: May 16, 2016
Last activity: May 26, 2016
Posted: 16 May 2016 14:28 EDT
Last activity: 26 May 2016 17:43 EDT
Closed

Sizing prgateway for PRPC 7.2

I need a method to size prgateway server that will be rendering screens from 1 Pega application into many different legacy applications. Where can I find the minimum server requirements?

Message was edited by: Vidyaranjan Av | Included Category

To see attachments, please log in.
Installation and Deployment
Data Integration
System Administration

Posted: 8 years ago
Posted: 26 May 2016 17:43 EDT
David Kircheis (David+Kircheis) Product Manager - Cloud
Pegasystems Inc.
US

the gateway has negligible overhead (its just a pass through reverse proxy - a java servlet).

I would size the box as you would for a standard web server.

Fail-over is more important - you should have at least two gateway servers deployed.

To see attachments, please log in.
Posted: 8 years ago
Posted: 20 May 2016 9:09 EDT
David Kircheis (David+Kircheis) Product Manager - Cloud
Pegasystems Inc.
US

For Pega 7.2 the Gateway is no longer required for Pega Web Mashup. Just generate the mashup code directly from your case type. You just need to have a reverse proxy in order to ensure the Pega content is served to the browser from the same origin as the website

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice