Using the SOAP inbound channel of the Integration Engine

September 21, 2006 | 697 Views |

Stefan Grube

Retagging required

When you have used the WSDL wizard in the Integration Directory and have clicked on “Propose URL” in the second screen, did you ever wonder, why the URL does not point to a sender SOAP adapter channel, it is the URL of the Integration Server instead?

The reason for this is an undocumented feature of the Integration Server. You cannot send only XI messages to the Integration Server, you have the option to send standard SOAP messages as well. This picture shows the way to send SOAP messages with help of the SOAP adapter:

This picture shows the feature to send SOAP messages directly to the Integration Server. The adapter engine is not used:

To report this post you need to login first.

32 Comments

You must be Logged on to comment or reply to a post.

Michal Krawczyk September 21, 2006 at 11:04 am

Hi Stefan,

thanks for this info :))
everyone likes undocumented features 🙂

btw
>>>>The SOAP inbound channel of the adapter engine does not support attachments

shouldn’t it be integration server
instead of adapter engine?

Regards,
michal

like (0)
1. Stefan Grube Post authorSeptember 22, 2006 at 2:51 am
  
  Hi Michal,
  
  thanx for the feedback. I have corrected the blog.
  
  Regards
  Stefan
  
  like (0)
  1. Dhanachezhiyan Mahalingam September 18, 2007 at 11:59 am
    
    Certainly increased the performance!!!..useful blog
    
    like (0)
Bhavesh Kantilal September 28, 2006 at 2:17 am

Stefan,

>>Additionally you must set the HTTP header parameter “SOAP action” to http://sap.com/xi/WebService/soap1.1

Am lost in this step. Where is this to be done?

Also, as we are sending the request directly to the Integration Engine, I guess we would not need a Sender SOAP adapter. Please correct me if I am wrong.

Regards,
Bhavesh

like (0)
1. Stefan Grube Post authorOctober 2, 2006 at 2:04 am
  
  >>Additionally you must set the HTTP header parameter “SOAP action” to http://sap.com/xi/WebService/soap1.1
  >Am lost in this step. Where is this to be done?
  
  Your web service client has to provide the SOAP action.
  
  >Also, as we are sending the request directly to the Integration Engine, I guess we would not need a Sender SOAP adapter.
  
  Yes. The sender SOAP adapter is not needed in this scenario.
  
  like (0)
  1. FIT CONSULTANT July 20, 2010 at 12:09 am
    
    It is a great blog thanks! However what if SOAP Client cannot provide a SOAP action?
    
    like (0)
    1. Stefan Grube Post authorJuly 20, 2010 at 2:15 pm
      
      SOAP action is part of SOAP 1.1 protocol, so any SOAP client must support SOAP action.
      
      like (0)
Anonymous October 2, 2006 at 12:55 am

hi Stephan,

Can i also use operations in the sender using this feature?

like (0)
1. Stefan Grube Post authorOctober 2, 2006 at 2:09 am
  
  Hi Udo,
  
  I don’t understand what you mean. Can you explain your scenario?
  Besides the handling of attachments, the direkt SOAP access to the Integration Builder behaves the same as the sender SOAP adapter.
  
  If you have general questions about the handling of web services and SOAP, post them to the XI forum.
  
  Regards
  Stefan
  
  like (0)
Nuno Pereira November 28, 2006 at 7:57 am

Hi Stefan,

How are you?
We met in EDP project – Portugal, remember?

Just to congratulate you for the very nice blog.

One little comment:
When you say “Only for asynchronous calls you need to change the URL inside the WSDL file with an editor and add &QualityOfService=ExactlyOnce.
” it shouldn’t be “…for synchronous calls..” instead?

Best Regards
Nuno Pereira

like (0)
1. Stefan Grube Post authorJanuary 14, 2007 at 11:02 am
  
  Hi Nuno,
  
  The default of the “Quality of Service” is “BestEffort” which implies a synchronous call.
  
  For an asynchronous call you have to change the QoS to “ExaclyOnce”.
  
  Regards
  Stefan
  
  like (0)
Mikhail Koshkin February 9, 2007 at 5:24 am

which cc must be used between sender and XI in this case?
i try to use this link instead of adapter and getting error “Message is incomplete. No Sender found”

like (0)
1. Bhavesh Kantilal February 9, 2007 at 5:42 am
  
  As you are posting to the Integration Engine Directly, you do not need a Sender Communication Channel.
  
  Regards
  Bhavesh
  
  like (0)
  1. Mikhail Koshkin February 11, 2007 at 11:04 pm
    
    so what about “Message is incomplete. No Sender found”? What i do wrong?
    
    like (0)
2. Suraj S.R. February 12, 2007 at 5:30 am
  
  As bhavesh told no CC is required but you have to include the Sender Service in your configuration (in ID)… Just add the sender service and now check…
  
  PS: please post questions in forum, thanks 🙂
  
  regards
  Suraj
  
  like (0)
Gabriele Morgante April 19, 2007 at 5:38 am

Hi,

when I try to do a test with XML Spy by using a WSDL document previously generated in Integration Directory, I receive a Response of this type:



               SOAP:Server
               System Error



                         RCVR_DETERMINATION.MESSAGE_INCOMPLETE
                         Message is incomplete. No Sender found





Why “No Sender Found”? My scenario is very simple; it have a sender channel of SOAP type and a receiver channel of JDBC Type and I have specified Receiver agreement and Determination and Interface determination and sender egreement. This is the request that XML spy generates for a SOAP Request:


          2001-12-17T09:30:47.0Z


Thanks!

like (0)
1. Stefan Grube Post authorJuly 9, 2008 at 6:58 pm
  
  I think this error comes, when the SOAP action is not correct. Check the WSDL for the SOAP action according to the description above.
  
  Regards
  Stefan
  
  like (0)
2. Supriya Sawant October 1, 2009 at 12:18 pm
  
  Hi Gabriele,
  
  I am getting the same error while trying using XML Spy.
  
  Can you pls tell me the solution you implemented for this problem.
  
  Regards,
  Supriya Sawant.
  
  like (0)
Yaki Zano May 25, 2007 at 12:37 am

Hi Stefan,

It’s really a good blog, it might solve a problem we have.
It a poosible that when we are using the XI to recieve Web Services the requests come directly to the Integration Engine (And not to the SOAP adapter), how can we verify whether the SOAP message goes directly to the Integration engine?

Here is an examlpe for SOAP url that we created:
http://milano.bezeq.com:8040/sap/xi/engine?type=entry&version=3.0&Sender.Service=BSKarat&Interface=http%3A%2F%2Fbezeq.com%2Fxi%2FMM%2FKarat%2FWebServices%5EWSTestPrincipalPropagation

Regards,
Yaki

like (0)
1. Stefan Grube Post authorMay 30, 2007 at 12:33 am
  
  You can see for example in the hop list of the message whether the message comes from the adapter framework or not.
  You can also check the trace.
  
  Regards
  Stefan
  
  like (0)
Praveen Sirupa June 26, 2007 at 6:26 am

Hi Stephen,

thanks for coming up with such a nice blog..

I’ve tried implementing this and facing an error..can you please look at my message in XI forum RECEIVER_DETERMINATION: Message Incomplete Error

thx
praveen

like (0)
Praveen Sirupa July 11, 2007 at 6:13 am

praveen

like (0)
Wojciech Gasiorowski February 27, 2008 at 5:28 am

Hi Stefan,
Very nice blog which pictures us very dangerous feature of SAP XI. If someone knows the Integration Directory landscape and knows the user and password can run any interface on the XI machine. Also it shows that ID should be controlled and secured. What do you think about it?

Best regards,
Wojciecch

like (0)
1. Stefan Grube Post authorFebruary 27, 2008 at 6:05 am
  
  Hi Wojciech,
  
  what you mention is nothing special for this special feature of the Integration Engine. You can always do harm, when you know the right user. 😉
  
  Regards
  Stefan
  
  like (0)
Willem Daniel Hugo August 25, 2009 at 5:27 am

Stefan, Hi is this blog still relevant for SAP PI7.10? I have set this up as a test for a scenario I have. Current Scenario NOT using your Blog and working perfectly. SandBox PI Development PI –

 –

 File > SOAP > SOAP > ABAP Proxy What I am attempting now is. SandBox PI Development PI —

 –

 File > SOAP > Integration Engine > ABAP Proxy I am using our SAP PI Sandbox to push a SOAP message using a Receiver SOAP adapter channel. Transport Protocol: “HTTP” Message Protocol: “SOAP” Conversion Parameters: “Do not Use SOAP Envelope” Target URL: “http://<Integratio Server Host Development PI>:<Port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=FigmentD&Interface=urn:figment-co-za:fleetcard:efuel_50ppm^oa_Msg50ppm&QualityOfService=ExactlyOnce&sap-user=<PIAPPLUSER>&sap-password=<PASSWORD>” SOAP Action: “http://sap.com/xi/WebService/soap1.1” I am however getting the following error on the SandBox Pi AE. “SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 MOVED TEMPORARILY” Please can you assist in this matter. Regards Willie Hugo 

like (0)
Willem Daniel Hugo August 25, 2009 at 11:28 pm

Stefan,

I had the port wrong, once corrected that resolved the issue I had. Somehow if you put in the ABAP port it does not seem to work. That is another issue.

Thanks for the blog very helpful.

Regards
Willie Hugo

like (0)
Praveen Gujjeti January 11, 2010 at 12:04 am

Can we send a SOAP message to local Integration Engine of SAP Application System(SAP ECC R/3).

I know we can send XI SOAP message using XI adapter but I am intrested in the above topic………

Regards,
Praveen Gujjeti.

like (0)
1. Praveen Gujjeti January 11, 2010 at 2:39 am
 
 Hi Stefan,
 
 Can we send a SOAP message from SAP XI to local Integration Engine of SAP Application System (e.g.,SAP ECC R/3) using SOAP Adapter..
 
 I know that, we can send XI SOAP message using XI adapter, but I am interested in the above topic………
 
 Regards,
 Praveen Gujjeti.
 
 like (0)
 1. Stefan Grube Post authorFebruary 9, 2010 at 10:49 pm
 
 This is not possible with PI version<7.11.
 
 With PI 7.11 the SOAP adapter has an XI protocol feature that you can use for that scenario.
 
 like (0)
Rahul Thunoli February 9, 2010 at 3:47 pm

; nested exception is:
org.xml.sax.SAXParseException: White spaces are required after keyword PUBLIC in DOCTYPE decl.

the client has the soap action set to as told in the blog . But still getting the above error . Tried everything possible . Would appreciate the response . Thanks.

like (0)
1. Stefan Grube Post authorFebruary 9, 2010 at 10:52 pm
  
  I am sorry, I have not worked with stylus studio before, so I cannot help.
  
  Regards
  Stefan
  
  like (0)
Ninu Sankar February 18, 2013 at 8:22 am

hi Stefan,

Can you please help me out with the below thread:- I need to connect the SOAP receiver to an ICO in a second PI box using SOAP with XI protocol

http://scn.sap.com/thread/3309874

Regards,

Ninu

like (0)