Application has multiple SOAP Integrations - all the WSDLs are currently sourced from a server location which is being decommissioned. So, need to modify existing server details for WSDL URL under Connect-SOAP.
Application has multiple SOAP Integrations - all the WSDLs are currently sourced from a server location which is being decommissioned. So, need to modify existing server details for WSDL URL under Connect-SOAP. But , system not allowing to modify the existing Connect SOAP rules to update the WSDL URL and WSDL Content.
Reimporting all the WSDLs is not an option given that we have more than 35 such CONNECT SOAPs.
I think you're referring to the intentionally read-only area that contains the metadata that the Connect SOAP rule was created from, if it was generated by a Wizard. The WSDL data does not get used for anything other than displaying to the user, so I am confused as to what value you would get out of modifying it.
Again, if you need to switch the endpoint to which the SOAP connections are made so that your application uses a different endpoint that provides the same exact service, you should be updating the service endpoint URL.
Posted: 5 years ago
Posted: 14 Sep 2017 14:17 EDT
Aditya Joshi (AdityaJ0363)
Pega Lead Systems Architect
Had issues with option b; it was not as simple as updating the wsdl url in the connector. when url was updated, it did not generate the underlying axis classes, hence connector failed. did not dive into the details of this because of time constraints.
Since connector needs to be upgraded to 'axis2' in the near future, option c(reimport) was picked & it worked.