Question
CTS
CA
Last activity: 23 Aug 2017 11:28 EDT
PEGA 5.4 - Connector Wizard not generating all the required rules for integration
Hi everybody,
for 5.4 application, I need to consume a downstream WSDL. I tried importing the WSDL in pega - it just created the connect soap rule and connector activity and one request and response property. No class or properties created.
Then I have 7 XSD referred to the imported WSDL. I tried consuming the XSD which I wanted - class and property generated but the main stream and parse rule used for request and response is not created.
my WSDL and XSD has element type "anyType"
Anybody from your experience in 5.4 did you face the issue, please share the solution if you know? the same WSDL works fine in 7 application.
Thanks,
Indumathy M
***Edited by Moderator: Marissa to add SR Details***
Pegasystems Inc.
US
Do you want to share the WSDL and XSD files? I've found it best to place the WSDL and its required XSD files on a webserver and have Pega access the WSDL through a URL. It should get the WSDL and supporting XSD data all together.
If you attach them, I'll test it out against a 5.4 OOB system and a 5.4 "hotfix" system (has all available hotfixes installed).
CTS
CA
Thanks Paul for your reply.
I have tried hosting in webserver and consumed the WSDL and XSD.. still no use.
I am not sure i can share the the WSDL in the open forum
Thanks,
Indumathy M
Pegasystems Inc.
US
Please open an SR and we can look at this offline. Update this post, once you have done so ... and mention the SR # so that we can provide updates here with any solutions we find.
Cognizant Technology Solutions
IN
SR-B66058 is opened
CTS
CA
HI Team,
I have raised SR, but I want to try other option of fixing this problem.
approach followed is consumed WSDL in 6.2 and imported the package in 5.4. rules are migrated successfully but obviously compatibility issue was there for many rules especially with stream rule and activity.
after fixing the activity and stream rule, now I get a new message when I tested the connect soap
XML stream:
<pega:withEmbedded name=".LogOn2Parameters"><ns1:LogOn2 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://www.kofax.com/agility/services/sdk">
<pega:when test=".userIdentity!=.userIdentity"><pega:withEmbedded name=".userIdentity"><ns1:userIdentity>
<pega:choose><pega:when test=".UserId!=.UserId"><ns1:UserId><pega:reference name=".UserId" mode="normal"/></ns1:UserId></pega:when><pega:otherwise><ns1:UserId xsi:nil="true"/></pega:otherwise></pega:choose>
<ns1:LogOnProtocol><pega:reference name=".LogOnProtocol" mode="normal"/></ns1:LogOnProtocol>
<ns1:UnconditionalLogOn><pega:reference name=".UnconditionalLogOn" mode="normal"/></ns1:UnconditionalLogOn>
</ns1:userIdentity></pega:withEmbedded></pega:when>
</ns1:LogOn2></pega:withEmbedded>
HI Team,
I have raised SR, but I want to try other option of fixing this problem.
approach followed is consumed WSDL in 6.2 and imported the package in 5.4. rules are migrated successfully but obviously compatibility issue was there for many rules especially with stream rule and activity.
after fixing the activity and stream rule, now I get a new message when I tested the connect soap
XML stream:
<pega:withEmbedded name=".LogOn2Parameters"><ns1:LogOn2 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://www.kofax.com/agility/services/sdk">
<pega:when test=".userIdentity!=.userIdentity"><pega:withEmbedded name=".userIdentity"><ns1:userIdentity>
<pega:choose><pega:when test=".UserId!=.UserId"><ns1:UserId><pega:reference name=".UserId" mode="normal"/></ns1:UserId></pega:when><pega:otherwise><ns1:UserId xsi:nil="true"/></pega:otherwise></pega:choose>
<ns1:LogOnProtocol><pega:reference name=".LogOnProtocol" mode="normal"/></ns1:LogOnProtocol>
<ns1:UnconditionalLogOn><pega:reference name=".UnconditionalLogOn" mode="normal"/></ns1:UnconditionalLogOn>
</ns1:userIdentity></pega:withEmbedded></pega:when>
</ns1:LogOn2></pega:withEmbedded>
error in activity invoke axis 2
The property pyTempDataPage.LogOn2Parameters.userIdentity was of mode Page while com.pega.pegarules.engine.clipboard.ClipboardPropertyImpl.getStringValue() was expecting String mode. Details: (none)
userIdentity - is page property but it is expecting as string.
can you help me who have experience in 5.4 please?
Accepted Solution
Pegasystems Inc.
Merging of the multiple WSDL/XSD files into a single WSDL file and striping out the WS-Policy definitions, custom SOAP fault definitions, custom enumerations, proprietary WSDL extensions present in the WSDL helped to resolve the issue. The Connector & Metadata wizard in Pega 5.4 SP2 release can't process a WSDL with these.