Posted: 9 Nov 2015 2:09 EST Last activity: 11 Nov 2015 9:36 EST
How do i generate connector rules if the WSDL supplied does doesn't have a working Endpoint
How do i generate connector rules if the WSDL supplied does doesn't have a working Endpoint <time being> and has Multiple XSD's referred from it? its not working even if i keep the XSDs in service export directory. How do we mention the File Location? PRPC expects it to be like file// but my service export is in E drive of app server forlder. E:\IBM\BPMCPM\Tmp\PegaTempDir\StaticContent\global\ServiceExport
If you are in 7.x version try placing the referencing files i.e xsd's and wsdl's under StaticContent(E:\IBM\BPMCPM\Tmp\PegaTempDir\StaticContent\global\ServiceExport) Folder and try consuming the wsdl using Local File Option? In case if it doesn't work please paste the error here.
Its 6.3 SP1. Am actually confused as to how will i give the FilePath in the local file option. I gave the above path,tries to add the port address etc.but it didn't work. can you tell me the path that i need to give? the above is the folder path for me. Please let me know how do i refer it in the Local File Option.
If you had the WSDL and XSD files stored in a directory on the Pega server that can be accessed by the Pega software, you also could have tried using a File URL such as file:///c/users/me/Desktop/wsdlFiles/service1.wsdl This would allow PRPC to "find" the XSD files that are at relative paths to your WSDL.
That’s what even I knew and was obviously my first approach âº, but it didn’t work as such â¹. It was not able to pull the XSDs from the relative path. That’s why I gave the path as http://myenviromentip:Port/prweb/wsdlfile and it worked.
Posted: 5 years ago
Updated: 5 years ago
Posted: 10 Nov 2015 21:23 EST Updated: 10 Nov 2015 21:24 EST