Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

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.

Error Messages

at com.pegarules.generated.activity.ra_action_invokeaxis2_3f9b437473119ddd1a261640d8c72033.step8_circum0(

Steps to Reproduce

Import the wsdl file. Run the Activity to invoke Connect SOAP rule.

Root Cause

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:||Rule-Connect-SOAP.Athl-Int-ICMore-Account-.AccountQueryPage titto - Exception 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.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us