Is there a way to extract the SOAP XML of the Req/Resp without customizing the InvokeAxis2 activity?
We are not able to programmatically retrieve the Request and the Response XML of a SOAP connector without any customization to the Rule-Connect-SOAP.InvokeAxis2 activity.
The customization of this activity causes us a lot of issues after every upgrade of the platform.
Can you suggest us another way to retrieve the XML Request and Response?
***Edited by Moderator Marissa to add Support Case Details***
Accepted Solution
Updated: 7 Aug 2024 4:41 EDT
Pegasystems Inc.
GB
@AleMax225 thanks so much for having updated this forum question. It will help other looking for solutions. Any users who are interested in this functionality can mention FDBK-116449 to their Pega Account Executive if they need more information
Here is the summary from the Enhancement Request : (No other investigation will be carried out via this forum post)
----------------------------
Users are unable to retrieve the Request and Response of a SOAP connector programmatically without customizing the Rule-Connect-SOAP.InvokeAxis2 activity. Customizing this activity causes numerous issues after each platform upgrade. This request is to add an extension point or expose the XML version of the request and response, as was done in previous versions. In Pega 7.3.0, users were able to retrieve both the Request and Response using the following methods: Request: By using a Java function -> tools.getParameterPage().getObject("pyRequestParams") Response: It was available in the parameter Param.xmlString Currently, these two methods are no longer functioning.
-------------------------------------
I am marking this post as Accepted Solution so that our GenAI product issue searches in the future will find this useful aswered question to share with other Pega users.
Updated: 6 Aug 2024 8:27 EDT
Pegasystems Inc.
GB
@AleMax225 there is a way to extract the SOAP XML of the Request/Response without customizing the InvokeAxis2 activity. You can enable debug level logging for the InvokeAxis2 activity. This will print the SOAP envelope details in the PegaRULES log file. However, please note that this method should be used cautiously in a production environment as it can generate a large amount of log data.
To retrieve the entire contents of the SOAP XML message for the Fault and the Response without customizing the InvokeAxis2 activity, you can enable specific loggers. Enabling the following loggers can help:
com.pega.pegarules.services.soap.SOAPService, com.pega.pegarules.services.soap.SOAPResponseHandler, and com.pega.pegarules.services.soap.SOAPUtils.
Additionally, you can try using functions like 'getXMLOfPageWithoutPageDataTag'.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
The SOAP service response parsing error
SOAP: How do I retrieve the entire contents of the SOAP XML message for the Fault and the Response?
Corner SA
IT
@MarijeSchillernI have opened the SR: INC-B31248 which was closed with the Feedback item.
Accepted Solution
Updated: 7 Aug 2024 4:41 EDT
Pegasystems Inc.
GB
@AleMax225 thanks so much for having updated this forum question. It will help other looking for solutions. Any users who are interested in this functionality can mention FDBK-116449 to their Pega Account Executive if they need more information
Here is the summary from the Enhancement Request : (No other investigation will be carried out via this forum post)
----------------------------
Users are unable to retrieve the Request and Response of a SOAP connector programmatically without customizing the Rule-Connect-SOAP.InvokeAxis2 activity. Customizing this activity causes numerous issues after each platform upgrade. This request is to add an extension point or expose the XML version of the request and response, as was done in previous versions. In Pega 7.3.0, users were able to retrieve both the Request and Response using the following methods: Request: By using a Java function -> tools.getParameterPage().getObject("pyRequestParams") Response: It was available in the parameter Param.xmlString Currently, these two methods are no longer functioning.
-------------------------------------
I am marking this post as Accepted Solution so that our GenAI product issue searches in the future will find this useful aswered question to share with other Pega users.