on 08-25-2009 3:34 PM
Hi,
I am following the blog of Stefan Grube.
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
However I have difficulties.
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: u201CHTTPu201D
Message Protocol: u201CSOAPu201D
Conversion Parameters: u201CDo not Use SOAP Envelopeu201D
Target URL: u201Chttp://<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>u201D
SOAP Action: u201Chttp://sap.com/xi/WebService/soap1.1u201D
I am however getting the following error on the SandBox Pi AE.
u201CSOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 MOVED TEMPORARILYu201D
Please can you assist in this matter.
Regards
Willie Hugo
Hi,
Thank you to all that have responded. The problem was that I had the port number wrong. For some reason it requires the JAVA port although it is posting it to the IE. Once I have changed the port number it worked as Stefan indicated in the blog.
Regards
Willie Hugo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thank you to all that have responded. The problem was that I had the port number wrong. For some reason it requires the JAVA port although it is posting it to the IE. Once I have changed the port number it worked as Stefan indicated in the blog.
Regards
Willie Hugo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What stefan mentioned in the blog is that during generation of WSDL in PI by defaults it points out the integration engine link
and we need to change it explicty...
so instead of sending the request to SOAP sender adapter from external applications request can be send directly to integration engine as request received to SOAP adapter will be any how passeed to Integration engine
File-SOAP -SOAP -ABAP PROXY
tha above will work as there is a scenario in PI which sends the request to ABAP proxy and this entire scenario of pi might have been exposed as WSDL and other system applications will make a request after importing the WSDL
SO what I mean you need to import WSDL provided by other applications in order to use SOAP receiver channel
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
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.