Skip to Content

Issue after Migration: ID and Content-ID are different in SOAP Payload

Hi Experts,

I am facing a strange issue in the PI landscape after the migration from XI 3.0 to PI 7.1.

The scenario is from R/3 system to TIBCO System (Proxy-to-SOAP). The TIBCO system receives the file in SOAP Format. The message is sent from PI via SOAP adapter to TIBCO System.

There is a attachment coming from the R/3 System along with the main message and the main payload/message has a "attachment-ID" as a field. Earlier what used to happen in XI 3.0 that the "Attachment-ID" used to equal to the "Content-ID" when the SOAP payload was generated at the TIBCO end. Now after migration, in PI 7.1 the "Attachment-ID" and "Content-ID" are different. We have control over the "Attachment-ID" as it is coming from the source payload but we do not have any control over the "Content-ID" as we are not creating it.

Can anyone of you please let me know how the SOAP Payload is created and how the content-ID gets populated in the Header of the SOAP Envelope? Also, can anyone help me to fix this issue? Is it something which needs to be handled by us or the BASIS Team?

Thanks,

Arkesh

Edited by: Arkesh Sharma on Dec 16, 2011 12:53 PM

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Dec 16, 2011 at 12:44 PM

    Hi,

    Please refer the following discussion. It might be helpful for you

    contentid-format-in-soap-request

    content-id-using-java-mapping

    Regards

    Ramesh

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Arkesh Sharma

      Arkesh,

      I think you might have to keep the values of soap header in buffer and add the content id.

      I suggest you to test once before whether you need to or not to provide details., trying the above one!

      Regards

      Ramesh