Embed IAC gadget in different websites
Hi,
We have a requirement to embed IAC (Mashup) gadget in different websites. The domain name for these different websites are different. While trying to do a POC, realized the domain names should be similar and were getting cross-domain errors in the JS console. Any guidance to satisfy this requirement would be really appreciated.
Thanks,
Thilak
You can have prgateway installed on each of those websites to avoid cross domain issues while invoking gateway URL. This is from mashup help -
There are three main components in Pega Web Mashup:
. Pega Composite Gadget Manager, a JavaScript file that you load on your web page that implements your Pega gadgets
. An application running on a system
. Pega Composite Gateway, a servlet that manages the HTTP traffic between the Pega gadgets and the application
The Gateway servlet and the web application hosting the Pega gadget must be located in the same domain and sometimes runs on the same web server. The application typically runs in a different domain.
Thanks,
Abhishek
Macquarie Group
AU
Thanks Abhishek. What if the web application is hosted in a third party partner website, and PRPC nodes are hosted in a VPN inside organization network? What is the recommendation?
Updated: 23 Oct 2015 2:24 EDT
Pegasystems Inc.
JP
>What if the web application is hosted in a third party partner website, and PRPC nodes are hosted in a VPN inside organization network?
Deploying prgateway servlet on the third party side server alone won't work, since PRPC nodes doesn't belong to the same network.
To make the communication between the prgateway and the PRPC nodes hosted in a private network inside an organization,
either the third party needs a VPN connection to join the organization's network, or a proxy server deployed in the DMZ in the organization's network is needed to mediate the communication.
ConEdison
US
What if the external application is a .net application hosted on windows servers?
The same origin policy issue is making IAC implementation very challenging and making it less re-usable. Some times I feel it's better to implement a PRPC webservice and let the external web application build their own UI if those users need not progress a case thru the gadget.