Unable to send pdf data via SOAP as MTOM
Hi, As part of the Visa Claims Resolution process I am trying to connect to Visa's RTSI SOAP services to pass PDF data in the form of Base 64 encoded data via both MTOM and inline within xml. We are currently on 6.1 SP2 (not sure if it's supported on this version though we have options to send binary attachments on Connect-SOAP).
I was able to send the PDF data via SOAP UI, however the same is not working in Pega. I have followed the instructions mentioned in one of the PDN link to set the pyAttachmentPage - this is not working. Please refer to the attached document which has the configuration, request snippet and the raw header generated by Pega and SOAP UI and the error response.
My guess is due to the first Content Type generated by Pega - though it is multipart/related which is expected, the type is type="text/xml" instead of type="application/xop+xml". I see the Base 64 data that SOAP UI generates and Pega generates is the same - so there is no issue with data.
The error message returned by web service is - "The supplied MimeType element specified a PDF image, but the actual image was not a PDF"
Has anyone faced this issue earlier ? Is there a way I can update the ContentType's type="application/xop+xml" ? I am trying to see if I can do this in InvokeAxis2.
***Edited by Moderator Marissa to add SR Details***
Accepted Solution
Global Payments
US
6.1 SP2 does not support MTOM OOB, this was finally resolved via SR-B75821 (local change from Pega). Once you have the Connect-SOAP Send Binary attachment checked the only change required was in the InvokeAxis2 activity for the below steps -
Step 3 (Initialize client options)
if (sendAttachments){
//SR-B75821 ADDED THE BELOW FOR MTOM on 9/12/2017 by Sachin based on Pega's recommendation
if(sendViaMTOM){
options.setProperty(com.pega.apache.axis2.Constants.Configuration.ENABLE_MTOM, "true");
}
else{
options.setProperty(com.pega.apache.axis2.Constants.Configuration.ENABLE_SWA, "true");
}
}
and Step 6 (Build the SOAP request envelope only if sendViaMTOM is true else call the default one that Pega has)
6.1 SP2 does not support MTOM OOB, this was finally resolved via SR-B75821 (local change from Pega). Once you have the Connect-SOAP Send Binary attachment checked the only change required was in the InvokeAxis2 activity for the below steps -
Step 3 (Initialize client options)
if (sendAttachments){
//SR-B75821 ADDED THE BELOW FOR MTOM on 9/12/2017 by Sachin based on Pega's recommendation
if(sendViaMTOM){
options.setProperty(com.pega.apache.axis2.Constants.Configuration.ENABLE_MTOM, "true");
}
else{
options.setProperty(com.pega.apache.axis2.Constants.Configuration.ENABLE_SWA, "true");
}
}
and Step 6 (Build the SOAP request envelope only if sendViaMTOM is true else call the default one that Pega has)
//ADDED THE BELOW FOR MTOM on 9/12/2017 by Sachin based on Pega's recommendation
boolean isOptimizableContentPresent = false;
//ADDED THE BELOW FOR MTOM on 9/12/2017 by Sachin based on Pega's recommendation -
//Create setOptimizeOnChildren in your ruleset (Refer Pega 7.x)
//ImageData here is your Node Name of type base64Binary
if (((String) paramVal).contains("ImageData")) {
oLog.info("Setting MTOM content");
com.pegarules.generated.gpacquirer_mtomlibrary.setOptimizeOnChildren(
builder.getDocumentElement());
isOptimizableContentPresent = true;
}
//END CUSTOM CODE FOR MTOM
//set OptimizeOnChildren (accepts parameter aNode of type OMElement)
Iterator children = aNode.getChildElements();
while (children.hasNext())
{
OMElement node = (OMElement)children.next();
// Again ImageDate is node containing base64Binary type - avoid hard coding this
if ("ImageData".equals(node.getLocalName()))
{
// expecting single text element, optimize it for MTOM
OMNode child = node.getFirstOMChild();
if (child != null)
{
int type = child.getType();
if (type == OMNode.TEXT_NODE || type == OMNode.CDATA_SECTION_NODE)
{
com.pega.apache.axiom.om.OMText textNode = (com.pega.apache.axiom.om.OMText) child;
textNode.setOptimize(true);
oLog.info("Set optimization flag on binaryData element content");
}
}
} else {
setOptimizeOnChildren(node);
}
}
Post this change it started to to build application/xml, automatically generated the cid's.
Accepted Solution
Global Payments
US
6.1 SP2 does not support MTOM OOB, this was finally resolved via SR-B75821 (local change from Pega). Once you have the Connect-SOAP Send Binary attachment checked the only change required was in the InvokeAxis2 activity for the below steps -
Step 3 (Initialize client options)
if (sendAttachments){
//SR-B75821 ADDED THE BELOW FOR MTOM on 9/12/2017 by Sachin based on Pega's recommendation
if(sendViaMTOM){
options.setProperty(com.pega.apache.axis2.Constants.Configuration.ENABLE_MTOM, "true");
}
else{
options.setProperty(com.pega.apache.axis2.Constants.Configuration.ENABLE_SWA, "true");
}
}
and Step 6 (Build the SOAP request envelope only if sendViaMTOM is true else call the default one that Pega has)
6.1 SP2 does not support MTOM OOB, this was finally resolved via SR-B75821 (local change from Pega). Once you have the Connect-SOAP Send Binary attachment checked the only change required was in the InvokeAxis2 activity for the below steps -
Step 3 (Initialize client options)
if (sendAttachments){
//SR-B75821 ADDED THE BELOW FOR MTOM on 9/12/2017 by Sachin based on Pega's recommendation
if(sendViaMTOM){
options.setProperty(com.pega.apache.axis2.Constants.Configuration.ENABLE_MTOM, "true");
}
else{
options.setProperty(com.pega.apache.axis2.Constants.Configuration.ENABLE_SWA, "true");
}
}
and Step 6 (Build the SOAP request envelope only if sendViaMTOM is true else call the default one that Pega has)
//ADDED THE BELOW FOR MTOM on 9/12/2017 by Sachin based on Pega's recommendation
boolean isOptimizableContentPresent = false;
//ADDED THE BELOW FOR MTOM on 9/12/2017 by Sachin based on Pega's recommendation -
//Create setOptimizeOnChildren in your ruleset (Refer Pega 7.x)
//ImageData here is your Node Name of type base64Binary
if (((String) paramVal).contains("ImageData")) {
oLog.info("Setting MTOM content");
com.pegarules.generated.gpacquirer_mtomlibrary.setOptimizeOnChildren(
builder.getDocumentElement());
isOptimizableContentPresent = true;
}
//END CUSTOM CODE FOR MTOM
//set OptimizeOnChildren (accepts parameter aNode of type OMElement)
Iterator children = aNode.getChildElements();
while (children.hasNext())
{
OMElement node = (OMElement)children.next();
// Again ImageDate is node containing base64Binary type - avoid hard coding this
if ("ImageData".equals(node.getLocalName()))
{
// expecting single text element, optimize it for MTOM
OMNode child = node.getFirstOMChild();
if (child != null)
{
int type = child.getType();
if (type == OMNode.TEXT_NODE || type == OMNode.CDATA_SECTION_NODE)
{
com.pega.apache.axiom.om.OMText textNode = (com.pega.apache.axiom.om.OMText) child;
textNode.setOptimize(true);
oLog.info("Set optimization flag on binaryData element content");
}
}
} else {
setOptimizeOnChildren(node);
}
}
Post this change it started to to build application/xml, automatically generated the cid's.
Virtusa IT Consulting
AE
Please check this article for sending or receiving document using SOAP https://docs-previous.pega.com/how-configure-soap-or-dotnet-connector-send-or-receive-soap-attachments
Global Payments
US
For 6.1 SP2 this alone would not help - we need the changes in InvokeAxis2. As we were not supposed to send the PDF stream as part of inline xml, instead it had to be sent as multipart attachment with cid references.