on 07-30-2007 6:35 PM
Hi All,
With regards to my previous thread
my header issue is solved and hence I have closed the thread but still I am not able to make the connection successful. The new problem is below
My vendor requirement is to specify the header as "Ent-sender" but when we give the same in XI in communication channel it automatically convets into uppercase "ENT-SENDER". Due to case-sensitive in vendor server the connection is not gettingestablished.
Please help me out how to solve the problem.
<b>Note:</b> Sorry for the new thread as it was created due to new problem and also the previuos thread is already too long.
Regards,
Dhill
god alternate solution as mentioned above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
god alternate soluation as mentioned above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check out OSS
Note 856597 - FAQ: XI 3.0 SOAP Adapter
https://service.sap.com/sap/support/notes/856597
Use the tcpgw.zip to get a trace on the SOAP adapter and find out the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Neaves,
Thank you, I jave seen the note and find the below solution will be some what realated to my prblem.
<u><b>The nosoap mode lets the adapter send the XI payload directly without wrapping it in the SOAP envelope. Although the main use of this mode is to send some plain text content directly to some web server, one can use this mode to send their own SOAP message (e.g., with arbitrary headers) to an external web service (See related questions). In this case, the XI payload must be formatted in the SOAP envelope.
To use the nosoap mode, the channel must be configured to use no SOAP envelope.</b></u>
If yes, can you please let me know how to use nosoap mode otherise let me the other possibilities. I am already using tcpg2.zip to trace the SOAP adapter in which it was confirmed that XI is changing the header automatically into CAPS whatever case we give,
Regards,
Dhill
Hi Aamir,
Can you provide details about this. I will implement and let you know and it would be very helpful for me if you could provide detailed information because I already using one user defined function in message mapping to populate the header values as given in the blog and also suggested by Stefan
/people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping
Regards,
Dhill
hey
in the receiver SOAP adapter select the "Do Not Use SOAP Envelope." option,then use XSLT or java mapping to create this SOAP header manually.
also have a look at the following
https://websmp201.sap-ag.de/~sapdownload/011000358700002953992006E/HowToUseSOAPAdapter.pdf
Thanx
Aamir
Hi Aamir,
I have gone through the document and I could find the section 4.1 says about SOAP Header fields but not able to find any mapping relation information. I am sorry I never worked on XSLT or java maping.
It would be helpful if you could give any document relating to this header mapping or any blogs on this.
Regards,
Dhill.
The SOAP header wound not help you, as you need the HTTP header.
When the receiver expects the HTTP header case sensitive, then I expect there is no standard solution for this issue.
When you already have SP20 you could use the AXIS modules to provide the message in a way that the receiver can understand.
http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm
But I cannot give you any help on that module, as I have not worked with this so far.
Regards
Stefan
Hi Stefan,
Currently the issue is solved by making the header as required by XI (my vendor changed it accordingly ) and I also raised one OSS note but no responce till now. Can you send me details on AXIS modules if you come across in future. My mail Id is sapsenthil.kumar@gmail.com
Thanks for your co-operation and time.
Regards,
Dhill
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
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.