Question
Exavalu Inc
US
Last activity: 4 Oct 2017 15:35 EDT
Unable to modify server details in WSDL URL Under Connect-SOAP
Accepted Solution
Pegasystems Inc.
US
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.
Pegasystems Inc.
US
Could you explain where the values are that you would like to change? Simply updating the value in the the endpoint URL in the "Service endpoint URL" field should let you use your new endpoint.
Pegasystems Inc.
US
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.
Exavalu Inc
US
Exceprt from WSDL Data in Connect-SOAP rule:
<xsd:schema>
<xsd:import namespace="http://XXXX.kp.org/info/clm_admn/claims_status/CDWClaimsService/v1" schemaLocation="CDWClaimsService_schema1.xsd"/>
</xsd:schema>
Getting this Error in invokeaxis:
** Could not load document from URL
'http://XXXX.kp.org/svc/clm_admn/claims/CDWClaimsService/v1/CDWClaimsService/CDWClaimsService_schema1.xsd
Pegasystems Inc.
US
Ah. Interesting.
It seems you generated these SOAP Connectors on a relatively old version of Pega. The "modern" InovkeAxis2 implementation (which uses the Axis2 library) does not have this issue.
What version of Pega are you currently using?
At any rate, I would suggest opening a Service Request with Global Customer Support in order to have your options explored.
A couple quick ideas that come to mind are:
Option a: Temporarily check-out the UI rules that have the fields you want to modify, update the fields manually (and save the Connectors)
Option b: Create an Activity record that opens each of these Connectors (using a lookup and a loop), modifies the properties, then saves. Don't forget to do a Commit after the last save
Option c: if you are using a version of Pega that has invokeAxis2, attempt to re-generate your Connector rules (into a new ruleset version!) to create modern SOAP Connectors
Exavalu Inc
US
Your observation is correct.
We upgraded from 6.1sp2 to 7.1.9. In the process of upgrade, we did not upgrade the connector rules.
As you listed above, we have already explored these options but have some issues:
'Option c' is the best way forward but is time consuming and the new rules generated have to be consumed in the application.
'Option b' or 'Option a' look feasible at this point but still the error below has to be addressed.
Save is not working since these connect rules are generated in older PRPC version, we are not able to cleanly save in 7.1.9 because of errors -
Request was mapped from/to Clipboard directly from a Clipboard Page with request style as 'Document/literal'.
Your observation is correct.
We upgraded from 6.1sp2 to 7.1.9. In the process of upgrade, we did not upgrade the connector rules.
As you listed above, we have already explored these options but have some issues:
'Option c' is the best way forward but is time consuming and the new rules generated have to be consumed in the application.
'Option b' or 'Option a' look feasible at this point but still the error below has to be addressed.
Save is not working since these connect rules are generated in older PRPC version, we are not able to cleanly save in 7.1.9 because of errors -
Request was mapped from/to Clipboard directly from a Clipboard Page with request style as 'Document/literal'.
** The specified Data Type value is only valid when the Message Style is RPC
So I am inclined to use 'option b' where I can ignore the error and save the rule.
Your thoughts. Please.
Pegasystems Inc.
US
Yes, I think "option b" is your best bet, given the fact that you may have more than 1 record to modify and you would like to avoid the validation ("save with errors.")
Accepted Solution
Pegasystems Inc.
US
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.