on 12-29-2011 2:51 PM
Hello Experts,
We have an Proxy to soap scenario which sends attachments:
When i check the Soap Document/Envelop in the RWB i can find the following data.
<sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:payload-4EEF61413DB52D3FE10000000A0C0167xxxxxcom">
<sap:Name>1 FB-8226040.doc</sap:Name>
<sap:Description />
<sap:Type>ApplicationAttachment</sap:Type>
</sap:Payload>
- <sap:Payload xlink:type="simple" xlink:href="cid:payload-4EEFFA032D4F3E24E10000000A0C0185xxxxxsap.com">
<sap:Name>MainDocument</sap:Name>
<sap:Description />
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
cid:payload-4EEF61413DB52D3FE10000000A0C0167xxxxxsap.com refers to the attachment ID
FB-8226040.doc refers to the attachment name.
Please let me know how the attachment ID field is generated in the soap document?
Thanks,
Sudhansu
This attachment-Id is generated randomly and you don't really have any control over it. What is your requirement?
Regards,
Prateek Raj Srivastava
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
We have recently migrated the scenario from XI 3.0 to PI 7.1 Ehp 1.
This is a scenrio from SRM to TIBCO, ie Proxy to SOAP.In this scenario(s) we have two message mappings (no other mapping used)
Scenario 1: Mapping A is executed
SRM sends a Purchase Order(with attachment) with a field called ID(in the payload).We observe that this ID (from the payload) is same as attachment ID in the soap documet
Scenario 2: Mapping B is executed
SRM sends a Purchase Order Change(with the same attachemt as above).Now though the ID field which SRM sends is same but the attachment ID in the soap documet changes.
In XI 3.0 we have seen that the attachment ID and the ID(from payload) to be same in both scenarios.
Is there any work-around?
Thanks,
Sudhansu
We have 2 receiver Determination,2 Interface determination and 1 Receiver Agreement.
So, we have 2 sender message interfaces and 1 receiver message interface.
There is only one communication channel which sends the data to TIBCO in both cases.
Yes,In scenario 2 the attachment ID is not equal to message ID.
Thanks,
Sudhansu
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.