Soap Invoke Axis 2 Fails on 7.1.5
SOAP integration which uses WS Security, the SOAP request works from a standalone java program and from SOAP UI, however it does not work with PRPC.
The expectation from configuring WS Security is that PRPC will add WS Security xml elements in the SOAP Header.
Steps to Reproduce
Import the wsdl file. Run the Activity to invoke Connect SOAP rule.
The WS-Addressing checkbox had to be selected on Advanced tab of Connect-SOAP to avoid this error being thrown:
"SOAP Envelope can not have children other than SOAP Header and Body "
This then resulted in a new exception:
10.31.4.47|10.31.4.15|Rule-Connect-SOAP.Athl-Int-ICMore-Account-.AccountQueryPage titto - Exception
com.pega.pegarules.pub.services.ConnectorException: Couldn't create SSL connection : Invalid SSL configuration: Keystore and Truststore both cannot be empty.
A dummy keystore had to be created to enable the SOAP integration with WS Security enabled to work.
Published June 12, 2015 - Updated October 8, 2020
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.