Question
TCS
US
Last activity: 11 Jul 2017 3:04 EDT
Where to find the PegaInternetApplicationComposer.js file for PRPC 7.2.2 WebMashup
Hi,
We are migrating from PRPC 6.3Sp1 to PRPC 7.2.2, as part of it we need to update the gadgets created in IAC (6.3) to mashup code in 7.2.2.
As in 7.2.2 we need not install the gateway.war, can any one help us on how to get the PegaInternetApplicationComposer.js file in 7.2.2.
And apart from Case type Steeings integration tab, is there any other way to generate the mashup code.
Thanks,
Gopi
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Pegasystems Inc.
US
Hi,
For 7.2.2 the setting for parameters is the following:
data-pega-action-param-parameters
Please review the following to make sure your using the correct attributes:
https://pdn.pega.com/pega-web-mashup-attribute-reference/pega-web-mashup-attribute-reference
You are using the wrong attribute. Change to this:
data-pega-action-param-parameters= "{UserIdentifier:'xxxxx',iPlanetDirectoryPro:'xxxx*',ClientMode:'Composite'}"
Notice I also changed to use double quotes around the entire parameter array and single quotes for the values.
Also, at runtime the isWebMashup=true parameter will always be there and the sendP3P=true will be there only for IE. These are need and added by our code.
Pegasystems Inc.
IN
Hi,
On the Host Configuration page of the Gateway Configuration Console, click the Gadget JS or Log JS download icons next to each configured server to get files appropriate for that server. The below link may help you further:
Thanks,
Gisela
TCS
US
Hi Gisela,
From 7.2.2 version, we need not install the gateway war file, so I was not able to launch the Gateway Configuration Console.
Please correct me if my understanding is wrong and share the url to launch the console in 7.2.2.
Thanks for the help.
Regards,
Gopi
Pegasystems Inc.
IN
Hi Gopi,
As you have created the gadgets by using IAC in PRPC6.3, the js files will be available. The existing PegaInternetApplicationComposer.js script still work for Pega7.2.2 if you are using the old <DIV> code.
As you mentioned the generate mashup code can generate under case type --> settings --> Integration --> Mashup.
When you use the Mashup code no need to add the PegaInternetApplicationComposer.js file, by default it will call the pzIncludeMashupScripts activity to generate the PegaInternetApplicationComposer.js file.
Thanks
Pegasystems Inc.
US
Customer informed me that the they need the IAC details for 7.2, whereas the info guided pertains to old versions.
Please advise if the same steps are applicable?
TCS
US
Hi,
When we have used the above configuration and set up the IAC, we are getting an error while reading the request,it is looking for two attributes isWebMashup and sendP3P.
We want to frame the request attributes to be UserIdentifier and iPlanetDirectoryPro as below
The gadget code used in 6.3 and 7.2.2 as below
6.3
============================
Pega 7 .2.2
===========================
Hi,
When we have used the above configuration and set up the IAC, we are getting an error while reading the request,it is looking for two attributes isWebMashup and sendP3P.
We want to frame the request attributes to be UserIdentifier and iPlanetDirectoryPro as below
The gadget code used in 6.3 and 7.2.2 as below
6.3
============================
Pega 7 .2.2
===========================
<div id="TestRe" style="height:800px;overflow:auto"
data-pega-gadgetname ='GadgetName'
data-pega-action = "openWorkByURL"
data-pega-query = "pyActivity=Data-Portal.ShowDesktopV"
data-pega-isdeferloaded = "false"
data-pega-redirectguests ='true'
data-pega-applicationname ='IssuerFinal'
data-pega-threadname ='STANDARD'
data-pega-systemid ='PRPC7'
data-pega-resizetype ='stretch'
data-pega-url ='https://xxxx.com/prweb/IAC'
data-pega-parameters = {UserIdentifier:"xxxxx",iPlanetDirectoryPro:"xxxx*",ClientMode:"Composite"}
></div>
Can any one please let us know why the attributes in the request are changing while the parameters are same.
The only other difference is we have made changes to include the activity in the header instead of the js script.
Thanks
Accepted Solution
Pegasystems Inc.
US
Hi,
For 7.2.2 the setting for parameters is the following:
data-pega-action-param-parameters
Please review the following to make sure your using the correct attributes:
https://pdn.pega.com/pega-web-mashup-attribute-reference/pega-web-mashup-attribute-reference
You are using the wrong attribute. Change to this:
data-pega-action-param-parameters= "{UserIdentifier:'xxxxx',iPlanetDirectoryPro:'xxxx*',ClientMode:'Composite'}"
Notice I also changed to use double quotes around the entire parameter array and single quotes for the values.
Also, at runtime the isWebMashup=true parameter will always be there and the sendP3P=true will be there only for IE. These are need and added by our code.
Vantiv
US
HI Chris,
This worked, thanks a lot for your support.
Regards,
Gopi