Support Article
Issue with Connect - SOAP rule Integration
SA-35345
Summary
Migration from PEGA CASL DEV(Server : 127.0.0.1) to AWS CASL (Server : 127.0.0.1) has been done.
After migration users are getting the exception in all the connect - SOAP rule stating that "Could not load XSD document from URL 'http://127.0.0.1/prweb"
Some time back, the user has migrated their CASL DEV from Solaris to Cloud DEV.
They encountered similar exception at that time.
They requested the concerned team to place all the WSDL and XSD under 'http://127.0.0.1/prweb" and modified the WSDL URL in the WSDL tab of the Connect - SOAP rule.
So similarly they have requested for "http://127.0.0.1/prweb/", which did not worked this time.
Error Messages
Could not load XSD document from URL 'http://127.0.0.1/prweb'
Steps to Reproduce
- Access PEGA DEV URL : http://127.0.0.1/prweb/PRServlet/
- Search Connect - SOAP : SearchCBD.
- Click on Test connectivity.
The same issue encountered for all the Connect - SOAP rules in Dev environment.
Root Cause
An issue in the custom application code where user had provided "file" protocol to access the web services.
Resolution
The protocol in place is not correct to resolve the issue.
Published April 7, 2017 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.