When is it necesssary to Configure IAC Using Gateway Configuration
We have Pega 7.2.1. Do we need to consider Configure IAC Using Gateway Configuration or we can do everything via case desiner?
Accepted Solution
Pegasystems Inc.
US
Hi Dyan,
Let me explain you clearly. Apart from Case Designer, we are now aware that once can use Gateway configuration console (gateway.war) for configuring specific Pega Actions and the same war contains the PRGateway servlet which communicates between Pega and Gadget. But please note that starting from Pega 7.2.x series, PRGateway is not mandatory, once can directly communicate with Pega from Gadget.
When you generate mash up code from Case Designer, the URL mentioned in the mashup gadget code would be direct Pega host.
If you generate Gadget after choosing actions from Gateway configuration console, gadget HTML file will have the below format.
Looks at the highlighted part, we have an option to connect to Pega host without a Gateway. You just need to change the gateway URL to direct Pega host URLfor no gateway. And in this case prgateway.war is not required after you done with generating the gadget code
On the above screenshot URL's - 8719 is hosting the PRGateway, 8718 is the actual Pega host.
Hi Dyan,
Let me explain you clearly. Apart from Case Designer, we are now aware that once can use Gateway configuration console (gateway.war) for configuring specific Pega Actions and the same war contains the PRGateway servlet which communicates between Pega and Gadget. But please note that starting from Pega 7.2.x series, PRGateway is not mandatory, once can directly communicate with Pega from Gadget.
When you generate mash up code from Case Designer, the URL mentioned in the mashup gadget code would be direct Pega host.
If you generate Gadget after choosing actions from Gateway configuration console, gadget HTML file will have the below format.
Looks at the highlighted part, we have an option to connect to Pega host without a Gateway. You just need to change the gateway URL to direct Pega host URLfor no gateway. And in this case prgateway.war is not required after you done with generating the gadget code
On the above screenshot URL's - 8719 is hosting the PRGateway, 8718 is the actual Pega host.
In short - Yes, you can also go without gateway on Pega 7.2.1. This PDN link states the same - https://community.pega.com/knowledgebase/release-note/pega-composite-gateway-not-required-pega-web-mashup
Hope this helps and let me know if you have any other queries to close this off.
- Harish
Pegasystems Inc.
IN
Hi Dyan,
Not sure that you are aware that we have an Ask the Expert session on Case Management topic, that went live today!
I would like to invite you to ask your question to our experts!
Click here to post your question as a reply: Ask the Expert - Case Management with Vijay Vaddem & Drew Piekarski
Hope to see you there!
Lochan | Community Moderator | Pegasystems Inc.
Pegasystems Inc.
US
Hi Dyan,
Case flows are a common requirement when embedding Pega 7 Platform content in another application's web page. Therefore Generate mashup code via case designer will generate Gadget code for actions like opening cases by specifying flows like pyStartCase or any other case flows.
If one is interested in performing specific operations like Displaying a harness or Open a work item using URL or By handle or operations like getNextWork, one can use Gateway configuration console to generate appropriate gadget code.
Few particular actions like above can't be generated via Case designer, however if someone has full understanding about generated mashup code from case designer, they can change the generated code to refer a harness name instead of a case flow.
Hope this helps.
-Harish
Accepted Solution
Pegasystems Inc.
US
Hi Dyan,
Let me explain you clearly. Apart from Case Designer, we are now aware that once can use Gateway configuration console (gateway.war) for configuring specific Pega Actions and the same war contains the PRGateway servlet which communicates between Pega and Gadget. But please note that starting from Pega 7.2.x series, PRGateway is not mandatory, once can directly communicate with Pega from Gadget.
When you generate mash up code from Case Designer, the URL mentioned in the mashup gadget code would be direct Pega host.
If you generate Gadget after choosing actions from Gateway configuration console, gadget HTML file will have the below format.
Looks at the highlighted part, we have an option to connect to Pega host without a Gateway. You just need to change the gateway URL to direct Pega host URLfor no gateway. And in this case prgateway.war is not required after you done with generating the gadget code
On the above screenshot URL's - 8719 is hosting the PRGateway, 8718 is the actual Pega host.
Hi Dyan,
Let me explain you clearly. Apart from Case Designer, we are now aware that once can use Gateway configuration console (gateway.war) for configuring specific Pega Actions and the same war contains the PRGateway servlet which communicates between Pega and Gadget. But please note that starting from Pega 7.2.x series, PRGateway is not mandatory, once can directly communicate with Pega from Gadget.
When you generate mash up code from Case Designer, the URL mentioned in the mashup gadget code would be direct Pega host.
If you generate Gadget after choosing actions from Gateway configuration console, gadget HTML file will have the below format.
Looks at the highlighted part, we have an option to connect to Pega host without a Gateway. You just need to change the gateway URL to direct Pega host URLfor no gateway. And in this case prgateway.war is not required after you done with generating the gadget code
On the above screenshot URL's - 8719 is hosting the PRGateway, 8718 is the actual Pega host.
In short - Yes, you can also go without gateway on Pega 7.2.1. This PDN link states the same - https://community.pega.com/knowledgebase/release-note/pega-composite-gateway-not-required-pega-web-mashup
Hope this helps and let me know if you have any other queries to close this off.
- Harish
PEG
PL
Hi,
We need gateway war file to generate the gadget. So, gateway servlet is a must. Infact this gateway servlet is responsible to communicate with the PRPC.
Blue Rose Technologies GmbH
DE
Earlier we had the cross origin policy restriction to talk between iframes. Now cross window messaging is possible using PostMessage APIs.
Yes there is no need for PRGateway now.