How to make PI 7.0 soap adapter support SOAP 1.2

hi all:
Is there some idea make PI 7.0 soap adapter support SOAP 1.2?
I have look the document about soap adapter,and it specified that soap adapter only support SOAP 1.1.
http://help.sap.com/saphelp_nw70/helpdata/EN/ae/d03341771b4c0de10000000a1550b0/frameset.htm.
my scenario:
external system send message via soap 1.2 to xi.

for more detail about axis soap adapters refer this link[http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm]

Similar Messages

Does the sender SOAP adapter support multiple operations per interface

Hi guys,
does the sender SOAP adapter support multiple operations per interface? (interface type of 7.1)?
Thanks,
Andrzej

theoretically Yes.
Do have a look into this when you get time
/people/shabarish.vijayakumar/blog/2010/09/08/service-interface-and-multiple-operations--is-it-just-an-hype

Sender SOAP adapter: get soap header data

Hi,
I've been going through various posts and blogs here on SDN + looked in the how to guide for SOAP adapter, but still find it quite difficult to actually find out how to do it. I've tried to follow recommendations seen, but it doesn't add up.
So can someone please tell me how to get an element situated in the SOAP header of the request sent to XI via sender soap adapter?
Let's for instance say the request looks like this:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <SOAP-ENV:Header>
 <SSN>1234567890</SSN>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 <event>
 <elem1>data 1</elem1>
 <elem2>data 2</elem2>
 <elem3>data 3</elem3>
 </event>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
How can I get the data in the SSN-header element at mapping time?
I'm sure this can be done by using adapter modules as the first step adapter, but I prefer doing it at mapping time if possible.
Best Regards,
Daniel

I solved it on my own now. My missing link was the fact that I'm using XMLSPY to send request and thus need to replace all '&' with & in Connection Endpoint.
Message was edited by:
 Daniel Engsig-Karup

SOAP Adapter without SOAP envelope sets contenttype to application/xml

Hi,
I wrote a adaptermodul for the SOAP adapter to create a SOAP:HEADER.
I disable the SOAP envelope in the communication channel.
Now I get a error from the WebService Provider because the SOAP Adapter sends with Content-Type application/xml and not text/xml. I set the content-type in the adapter module but it seens to not work.
How can I correct this ?
Regards,
Gerald

Hi
Simple answer is NO, it is not possible (without party/channel/ service etc to process the request)
but it is worth a try to check if the URL encoding works.. though I have not tried..
for example sending the hex value of the "?" - %3F%
URL is a generic topic, you can search that to get more information
(ex : http://www.blooberry.com/indexdot/html/topics/urlencoding.htm)
Regards
Vishnu

Receiver SOAP Adapter Problem-soap fault: Server did not recognize the valu

I have a scenario for service orders using async call : IDOC-XI-SOAP.
I used the XML Spy tool to test the Service order's web services and it works fine. I imported the same WSDL file in XI. When I send a SOAP message from XI, I get a following error in the adapter engine.
MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: AddUpdateCostObjectLevel1.
Can someone please help me...
Thanks in advance!
Mrudula

This problem is resolved by me by passing the "http://company's URL/AddUpdateCostObjectLevel1" in the SOAP action.
Thanks to all for your input.
Mrudula

How to create a Doc/Literal WebService that supports SOAP attachment?

Hi,
I need a sample that works with OC4J to provide a doc/literal WS which supports attachment for input/output.
How to create that with JDeveloper?
Thanks!

Hi there!
Thanks for the info. Actually I am using v10.1.3.2 (OracleAS and Jdeveloper) and tried to follow the "Working With Attachments'. However, the steps described there don't use JDeveloper.
I tried to feed the Example 2-2 WSDL into JDeveloper's Create J2EE 1.4 Java Web Service from WSDL wizard but it doesn't work due to this line:
<xsd:import namespace="http://ws-i.org/profiles/basic/1.1/xsd"
schemaLocation="http://ws-i.org/profiles/basic/1.1/xsd"/>
It should be this:
<xsd:import namespace="http://ws-i.org/profiles/basic/1.1/xsd" schemaLocation="WS-ISwA.xsd"/>
WS-ISwA.xsd:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
targetNamespace="http://ws-i.org/profiles/basic/1.1/xsd"
xmlns:tns="http://ws-i.org/profiles/basic/1.1/xsd">
 <xsd:simpleType name="swaRef">
 <xsd:restriction base="xsd:anyURI" />
 </xsd:simpleType>
</xsd:schema>
But then not sure what to do with step 3 & 4 in the wizard. So kind of confusing....
So far, I couldn't find a complete doc/literal WS/attachment sample (for OracleAS). Wonder if you know of any out there.
Thanks,
Daniel

SOAP adapter and WS with rpc/encoded

Hi All,
Does anyone know if and how the SAP XI 3.0 SOAP Adapter supports WebServices which expects XML messages in rpc/encoded.
Cheers,
FRank

Hi Frank,
I have the same issue and I got a reply from OSS:
This problem is caused by the diversification of the WSDL binding
styles.
A Web service is described by a WSDL document. A WSDL binding
describes how the service is bound to a messaging protocol, particularly
the SOAP messaging protocol. A WSDL SOAP binding can be either an RPC
style binding or a document style binding. A SOAP binding can also have
an encoded use or a literal use. This gives us four style/use models:
- RPC/encoded
- RPC/literal
- document/encoded(It will probably disappear from future versions of
WSDL.)
- document/literal
RPC styled web services have serious interoperability problems. This
is the reason that the rpc style is not in the basic profile
specification of the web interoperability and also it has been
deprecated in the current soap specification. For these reason, the
integration directory does not currently support the RPC style! I would
suggest you to use other document style web service provider if possible
. It's the best way to solve this problem. But if you persist in using
this RPC web service provider, we still have a workaround solution:
you need to convert your RPC wsdl to a document styled wsdl and import
it to the directory and if necessary, you need to add some mapping to
solve some RPC interoperability problems.
In your case,
1. The WSDL file you used is RPC style.
2. The XI SOAP adapter doesn't support the RPC style. It only sends the
document/literal SOAP message which can't be understand by your web
service provider.
One of the significant differences between the SOAP message of RPC
style and that of the document style: the operation name is contained in
the RPC style SOAP message but not in the document's.
However, you can't solve this problem by simply specify a method
name. What you should do is convert your RPC wsdl to a document styled
wsdl. RPC turns out to be a subset of document/literal. This
means for any given RPC WSDL, you can create a completely
equivalent document/literal WSDL that would describe the same wire
messages. Here are the steps for doing this (mostly schema element
declarations).
Solution:
For each RPC operation:
1. For each part in the input and output messages of that operation,
declare a type with the contents described in step 2.
2. Declare an element with the name of the part, the type referenced by
type=". The element form must be unqualified.
3. Declare a global element with the operation name and the namespace
from soap:body/@namespace in the binding. Make the type of this element
the one defined in step 1 for the input message.
4. Declare a global element with the operation name and the word
Response appended to it and the namespace from soap:body/@namespace in
the binding. Make the type of this element the one defined in step 1 for
the output message.
5. Change the input message to contain one part and reference the
element you declared in step 3.
6. Change the output message to contain one part and reference the
element you declared in step 4.
7. Change the style to document in the binding.
After that, import the new WSDL file to the integration directory. You
will find the "method name" appears in the document style SOAP message.
But actually it's the name of the input element which is the same as
the name of the operation. It's just a little trick.
Cheers Stefan

Base64 encoding in SOAP adapter

Hi,
Is it possible to transform outgoing messages to Base64 encoding format in XI using module processors and security encryption? I'm using receiver SOAP adapter (without SOAP header) and using PayloadZipBean module processor to zip the outgoing message. Also I need to add digital signature and base64 encryption to the zipped message. Please let me know how this can be achieved.
Thanks,
Dipankar

hi dipankar
check the below blog
How to use Digital Certificates for Signing & Encrypting Messages in XI
How to use Digital Certificates for Signing & Encrypting Messages in XI
hope this resolves your issue
additionally check this
How to use Client Authentication with SOAP Adapter
How to use Client Authentication with SOAP Adapter
also
How XML Encryption can be done using web services security in SAP NetWeaver XI
How XML Encryption can be done using web services security in SAP NetWeaver XI
reward points if helpfull
regards
kummari
Edited by: kummari on Jul 19, 2008 7:24 AM

Security settings in Receiver SOAP adapter

Hey guys
i m trying to incorporate some security features in my receiver SOAP adapter and taking help from help.sap.com,it mentions some entries in 'Security setting frame' but i cant find it even though i have checked the message security checkbox in my communication channel.
i m on SP9,is it not available in SP9?
my message protocol is XI 3.0
thanx
ahmad

Ahmad,
SOAP adapter supports SSL and Digital Certificates and you need to configure your SSL on the J2EE stack before you can use the same on your SOAP adapter.
Look into this blog to understand what needs to be done.
/people/aparna.chaganti2/blog/2007/01/23/how-xml-encryption-can-be-done-using-web-services-security-in-sap-netweaver-xi
Regards
Bhavesh

Socket time out exception in Reciver Soap Adapter

Dear friends,
I have one errror in Soap Reciever adapter as follows:
"java.net.SocketTimeoutException: Read timed out"
Scenario:
From Portal the data is posted to siebel system
Portal -
> PI -
> Siebel
Adapter: Sender Soap Adapter & Receiver soap adapter
It is Synchronous Interface.
When the Customer is going to siebel system via PI for validation.It is reaching SIEBEL.
From siebel the response message iS not coming back.... it is happening randomly ...
At that point we are getting error message as follows:
"java.net.SocketTimeoutException: Read timed out"
How can we resolve this ..freinds...

Hi,
Ask your Siebel guys to check the application in which your SOAP msg is going........i think the application is throwing some error while processing your SOAP req msg and so it is not able to send a response msg to PI..........
Moreover, just check if your source msg size is too large and it is getting timed out in Siebel application while reading your req msg - if this is the case, then ask your Siebel guys to increase some timeout parameter in Siebel system for processing of your SOAP req msg...........but if it is not the case, then ask your Siebel guys to check their application as i suggested above.........
Regards,
Rajeev Gupta

Urgent ---- SOAP Adapter

Hai,
The scenario that we are working now is IDOC-XI-SOAP.
We are having problem at SOAP Adapter.
SOAP Adapter Receiver configurations:
TargetUrl : .net webservice
proxy settings : done
soap action : given
In the audit log error code is : General Error
giving error that : soap call failed
any inputs would be highly appreciated.
Thanks
Sri Krishna Charan

Hai All,

How can i check whether my .net webservice is accessible or not in xi server....
bcause xi server is runnig on remote host
Audit log information in message monitor is:
Success The message was successfully received by the messaging system. Profile: XI URL: http://iccxi.sap.com:58000/MessagingSystem/receive/AFW/XI
Success Using connection AFW. Trying to put the message into the receive queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the receive queue.
Success The message status set to DLNG.
Success Delivering to channel: TEST_VONDELSOAP_DEMO
Success SOAP: request message entering the adapter
Success SOAP: call failed
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack

Extension of Standard SOAP Header Information in SOAP Adapter

We are currently trying to call an eBay Web Service via SAP XI and we are using the SOAP Adapter in XI to achieve this.
The following Authentication Information is required in the SOAP Header for accessing the eBay Web Service:
- Token
- ApplicationID
- DevelopmentID
- CertificationID.
Unfortunately, the standard SOAP Adapter supports only certain SOAP Header Information (like User Authentication or Certificate Authentication).
Is it possible to extend the SOAP Header Information in the SOAP Adapter (or somewhere else in XI) beyond the standard configurations?
Thanks for your support.
Alexander Bange

Hi Jin,
thanks for your input and sorry for my late reply but I wanted to wait for feedback from SAP who actually confirmed your recommendation.
I had a second thought about this and it came to my mind that I actually don't want to extend the SOAP Header elements but simply fill the mentioned authentication elements with values. This cannot be done in the message mapping as only the SOAP body elements (i.e. the payload) can be mapped.
Do you know if and how I can fill the SOAP header elements with values in XI?
I already tried to include this information as fixed values in the WSDL description and load it into XI. Then I looked into the WSDL description and an error message occured stating that XI could not parse the XML Document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: = expected in attlist(:main:, row:18074, col:54)).
If there is no solution for the latter, I will have to try nosoap solution. Still this would be a little awkward.
Thanks again for your valuable support.
Best Regards.
Alex

Security Issues: SSL on SOAP Adapter and Digital Signature in BPM

Hi there,
we're developing a R/3-XI-3rd Party Application scenario, where the XI/3rd Party communication is based on a webservice (SOAP adapter with SSL). Also, the messages in the XI/3rd Party communication must be digitally signed. I've got some questions on both subjects.
1. About the SSL. I've started to investigate what will be necessary to enable the HTTPS option under SOAP Adapter (it's not enabled now). If I'm not correct, all I need to do is:
- check whether the SAP Java Crypto Lib is installed in the Web AS;
- generate the certificate request in the Visual Administrator and, after acquiring the certificate, store it with the KeyStorage option.
Is that right?
I'm considering that I won't need to use SSL in the ABAP Web AS, only the J2EE Java Engine (since the SOAP Adapter is based on J2EE).
2. About the digital signature. As a first solution, we had decided on accessing a webservice based on another machine running a signature application. We'd send the unsigned XML and receive a signed XML. But since that needed to be done into the BPM, I thought that using a piece of Java code in a mapping would suit it better.
But to be able to use the hashing/encrypting/encoding algorithms, which library needs to be installed? Is it the same SAP Java Crypto Lib that was installed for the SSL enabling?
Thanks in advance!

Hello Henrique,
1. You're right. For detailed instructions please have a look at the online help: http://help.sap.com/nw04 - Security - Network and Transport Layer Security - Transport Layer Security on the SAP J2EE Engine
2. The SOAP adapter supports security profiles. Please have a look at the online docu http://help.sap.com/nw04 -Process Integration - SAP Exchange Infrastructure - Runtime - Connectivty - Adapters - SOPA Adapter - Configuring the Sender SOAP adapter and from the link under Security Parameters to the Sender Agreement. You'll find some additional information in the following document: http://service.sap.com/~sapdownload/011000358700002767992005E/HowToMLSXI30_02_final.pdf
Rgds.,
Andreas

SOAP Adapter: java.io.IOException: unable to create a socket

Hi,
I am trying to use the soap adapter to connect to a URL and post a document. When I try, the adapter throws the following
java.io.IOException: unable to create a socket
Does anyone know what causes this?
I get it both with the SOAP Envelope turned on and off.
I am trying to post to a URL that is usually used for straight HTTPS posts, could this cause an issue? The only reason we are using the SOAP adapter is to be able to send attachments! Hence, SOAP adapter, no SOAP envelope.
Kind Regard,
Chris

Hi,
Had faced the same issue. The possible reasons were :
1. Either the target server might not be responding.
2. The Target URL configured in the communication channel might be wrong.
3. The port to which the message is being sent might not be opened which you need to cross-verify.
For me the issue was the port, which wasn't enabled from our end. The messages went past successfully once it was enabled.
Cheers!!
Jithin James.

HTTPS Port for SOAP Adapter PI 7.1 (XI)

Hello Colleagues,
we plan to configure an Sender SOAP Adapter (without SOAP envelope) as HTTPS message receiver with HTTP Security Level "HTTPS with Client Authentication".
Does anyone know if this works and which port will be used. For my understanding it must be 443.
If not, it's possible to change the port to 443?
Regards,
Jochen

Hi Prateek,
many thanks!
Where can i do the port change?
Many thanks in advance!
Regards,
Jochen

How to make PI 7.0 soap adapter support SOAP 1.2

Similar Messages

Maybe you are looking for