Removing XML definition & XML tage from the XML message....

[Former Member]

Dear All,

We are using PI 7.1 and implementing a scenario in which we need to send a signed payment message to our partner, our implemented scenario goes as follows:

1) We are using SOAP without header to send the message.

2) We are signing the payload using our own java code as UDF in graphical mapping.

3) the main issue that we have is that in the final XML message which is being sent to our partnet, XMl definition and the topmode XML tage are again added to the signed message. Please see the following for reference:

Source Message:

We are using only I node in the graphical mapping and one UDF to sign in between the source and the target node. So after signingwe get the following in the target node:

Signed Message

0u201A#u0152# *u2020Hu2020÷ ### u201A#}0u201A#y###1#0 ##+######0u201A#h# *u2020Hu2020÷ ### u201A#Y#u201A#U

u201A#ý0u201A#¸0u201A# ######5gu0152yu2022ݬ½´b#¿#u2019 u01780 # *u2020Hu2020÷ #####0�Ý1#0 ##U####US1#0###U# ##VeriSign, Inc.1#0###U####VeriSign Trust Network1;09##U### BLAH BLAH BLAH SOME VERISGIN CERTIFICATE SIGNING INFORMATION

but the final message that get through the SOAP and reaches our partner look liks the following:

, as all this is appearing twice in our final message.

I'll appriciate if anyone can help us finding a solution for that, as we tried to remove it in our java class at the adapter level in the module tab, but that produces java error.

Regards,

[VijayKonam · Accepted solution]

Did you consider using the HTTPS on the SOAP receiver side? It looks more like that. I do not think you can avoid the XML header in any of the PI message communication because XML is the standard for carrying the messages in and out of the systems.

Another thought is to create a text file with no XML header by dumping you signed message data. Then writing some application to read the file and send it to your partner..or something like that!!

VJ

[Former Member]

Vijaya, we already have solved this problem by creating an EJB and adding it to SOAP Adapter processing modules, so rather signing our payload in the UDF in graphical mapping we are now signing the payload in the SOAP adapter module and removing any unwarranted characters etc over there as well. We cannot send SOAP with header in our scenario as it is adding hell lot of extra bites that our partner system cannot understand, so we have adapted the EJB way of solving it. Thanks anyways for your suggestion.

Athar Ullah Khan