Table of Contents

Pega Web Mashup on Pega Cloud

You create a mashup, or composite web application, when you embed UI content from one web application into another web application to provide a seamless user experience. With Pega Web Mashup, you can generate the mashup code directly in the Pega 7 Platform that is hosted on Pega Cloud, and then deploy that code in applications on your website.

Pega Web Mashup provides the following benefits:

  • Simplified configuration – a Pega gateway server or web node is not required.
  • Streamlined mashup gadget deployment – you generate mashup gadget code in Designer Studio.
  • Seamless mashup fits into any website architecture.
  • Pega 7 Platform authentication and authorization.
  • A rich mashup API.
  • Support for autogenerated Pega application UI controls and features.

Pega Web Mashup for Pega Cloud

A Pega Web Mashup for a Pega Cloud application is configured on your website

There are two requirements for using Pega Web Mashup in Pega Cloud:

  • You must deploy the mashup code, along with mashup pages, on your website.
  • You must deploy a reverse proxy server (or a device that can perform in that capacity). A reverse proxy allows content hosted in one domain, but appearing in another (such as a mashup), to be seen as all coming from the same place. This is necessary to avoid violating web browsers’ “same origin” policies.
Starting with Pega 7.2.1, a reverse proxy is no longer required, because site origins are configured directly in Designer Studio.

Generating mashup code

Mashup code is generated directly from case types in Pega 7 Designer Studio. For more information, see the Pega 7 Platform help topic Generating mashup code.

Configuring Pega Web Mashups when using a proxy server

In the Pega 7 Platform, if your Pega 7 Platform application will be accessed through a proxy server, add the following Dynamic System Setting in the Pega-Engine ruleset:

prconfig/initialization/ContextRewriteEnabled = true

Configuring the reverse proxy

The types of servers that you can use for reverse proxy functionality range from Microsoft Internet Information Services (IIS) web servers to enterprise-class network devices.

For example, to configure a NGINX server as a reverse proxy:

  1. In the nginx.conf file, set up the proxy_pass in your location {}:

proxy_pass https://yourPega7host/prweb;

  1. Set the following header in your location {}:

proxy_set_header PegaRULES-SetContextURI https://CustomerWebsite/prweb;

  1. Optional: Set these headers to facilitate logging:

proxy_set_header X-Forwarded-Host CustomerWebsite;

proxy_set_header X-Forwarded-Proto https;

proxy_set_header X-Forwarded-Port 443;

where CustomerWebsite is the full hostname:port for your website (for example, CustomerWebsite.com).

Using other products as a reverse proxy

Each product provides its own means for configuring a proxy pass-through host and setting proxy headers. Remember to set the header PegaRULES-SetContextURI.


100% found this useful


Related Content

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.