The manual file handling errors can be mitigated if they use relative references (no hostnames in the URLs) by uploading all files to an appropriate directory structure on the Pega system and then referencing the WSDL via file URL such as "file:///C:/temp/myWSDL.xml" (MS windows example) or "file:///etc/temp/myWSDL.xml" (unix example)
Note: the three slashes before " C:" are required because the file is local to the Pega system, so the hostname part of the file URL is blank.
This option is only feasible if you have read/write access to the file system on the Pega system, which is not always the case.
I tried creating Dynamic System Setting but for some reason it was not getting referenced. Found that in Activity pyValidateURLSource step 8 we have 'seconds' defined which is getting referenced at run time to set the timeout.
I still did not review whole scenario but looks like we should use input parameter 'timeout' in java step rather than redefining.
yes, that is working on my side as well. Thanks for trying out the local change, Mohit!
I am fixing issues with DSS in "pyValidateURLSource" for inclusion in a future Pega release. If you are interested in an official change for the version of Pega that you are using, please reach out to Global Customer Service.
There's no config setting for this. You should raise an SR to investigate this. I have a concern that the quantity of XSD metadata being loaded to generate the connectors could be massive, based on the comment that it takes a full minute to load the WSDL into SOAP UI. Assuming this delay is due to data volume and not network latency, this could be an issue for the wizard that the customer would encounter after increasing the timeout.