Table of Contents

Best practices for using multiple mashups


Only available versions of this content are shown in the dropdown
Applicable to Theme Cosmos applications

Learn about how Pega Platform supports semantic and non-semantic URLs, and discover the best practices for loading multiple mashups to ensure that your mashups work as intended.

In earlier versions than Pega Platform 8.3, support for multiple mashups was restricted to one operator and one application. Starting with Pega Platform 8.3, the Pega domain in mashups is based on semantic URLs, which contain the application name and its unique identifier. This solution supports the capability of running multiple mashups of the same application or different applications on a target website.

Consider the following limitations and follow the best practices for using multiple mashups which point to the same Pega domain to prevent errors.

  • If you use mashups that you developed with Pega Platform 8.2.x and earlier versions, run multiple mashups that point to the same Pega domain outside of Pega Platform at the infrastructure level by using a different virtual domain with a reverse proxy server that points to the same Pega Platform application.

    For more information, go to Pega Support.
  • To avoid authentication issues, never load mashups simultaneously.

    When you load the first mashup, a pre-authentication cookie parameter is sent to authenticate the requestor. When you load the second mashup, the server registers the second request, which has a pre-authentication cookie, even though the server validated the requestor for the first mashup.
  • Run multiple mashups on different threads.

  • Give the mashups unique names.

    When you register a gadget, the _initAllPegaObjects() method stores the gadget as a map with a gadget ID and a few parameters. If other gadgets have the same ID, new entries are not created in the gadget map and all the other gadgets do not load.
  • Add the data-pega-isdeferloaded ='true' parameter to the mashup <div> code of the second and subsequent mashups.

    Whenever you add this setting, use the (pega.web.api.doAction("GadgetName", "load")) API to load the subsequent mashups when you load the first mashup.
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.