Style and encoding in XI SOAP Adapter

Hello all,
when describing a SOAP web service with WSDL using SOAP binding, there are two parameters affecting how SOAP messages are formatted:
a.) style (may be 'document' or 'rpc')
b.) encoding (may be 'literal' or 'encoded')
Is there any information about what styles and encodings are supported by the XI SOAP Adapter? I looked in the help and in the FAQ OSS note, but didn't find it...
I made some tests and could only get the combination document/literal to work. Is this the only supproted combination?
Any help is appreciated.
Regards,
Matthias

Hi
There are other combinations also.
A WSDL SOAP binding can be either a Remote Procedure Call (RPC) style binding or a document style binding. A SOAP binding can also have an encoded use or a literal use. This gives you four style/use models:
1.RPC/encoded
2.RPC/literal
3.Document/encoded
4.Document/literal
Add to this collection a pattern which is commonly called the document/literal wrapped pattern and you have five binding styles to choose from when creating a WSDL file.
Please go through the link:
http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/
This contains all the scenarios mentioned above.
Hope this helps you out.
regards
Victoria

Similar Messages

How to have Header and body in reciever SOAP adapter channel

Hi Experts,
Please help me with the following scenario.
I am designing a webservice scenario and have the WSDL available .
The webservice expect the SOAP message as follows
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
    <SecurityHeader xmlns="http://onefile.cyzone.co.uk/webservices/proactive">
      <PortalID>int</PortalID>
      <Username>string</Username>
      <Password>string</Password>
    </SecurityHeader>
</soap:Header>
<soap:Body>
    <OrganisationCreate xmlns="http://onefile.cyzone.co.uk/webservices/proactive">
      <Organisation>
        <Title>string</Title>
        <Standards>
          <Standard>
            <StandardID>int</StandardID>
          </Standard>
          <Standard>
            <StandardID>int</StandardID>
          </Standard>
        </Standards>
      </Organisation>
    </OrganisationCreate>
</soap:Body>
</soap:Envelope>
I imported the WSDL as external definition and can see all messages in XI
In the corresponding operation( from WSDL) as given below, it indicates SecurityHeader to be used as SOAP header. However, the WSDL has OrganisationCreate and OrganisationSecurityHeader as separete messages. How do we combine these two in Message Interface.
- <wsdl:operation name="OrganisationCreate">
<soap:operation soapAction="http://onefile.cyzone.co.uk/webservices/proactive/OrganisationCreate" style="document" />
- <wsdl:input>
<soap:body use="literal" />
<soap:header message="tns:OrganisationCreateSecurityHeader" part="SecurityHeader" use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
Please advice.
Thanks in advance,
Mona

Hi,
Yes you are not supposed to create SOAP envelop, you have to cerate whole.
See below links Consuming XI Web Services using Web Dynpro Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
Consuming XI Web Services using Web Dynpro Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d7349b6-0901-0010-ddbe-ec43178a61ff
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
/people/kevin.liu/blog/2006/04/12/wsdl-11-binding-extension-for-soap-12
Regards
Chilla..

Soap adapter default encoding

Hi there,
we have a XI <-> webservice scenario, where the XML messages are sent in a string (the wsdl is wrapped, literal) with digital signing.
As of now, we have a problem in the digital signing, since the webservice won't validate the signature. We made some tests and this is what I've concluded.
From what I've observed, there are three ways of sending XML file content in a string (let me know if there are more). They are:
1. putting the xml content between "<![CDATA[" and "]]>";
2. replacing '<', '>' and '"' with "<", ">" and """;
3. replacing '<' and '>' with "<" and ">".
2 and 3 appear to be different encodings.
We tried to send three messages to a test webservice, each with a different way of defining the string, using receiver soap adapter. This test webservice was located in a local machine and we ran a sniffer on it. The three incoming messages were logged by the sniffer, but the upseting news were that the three of them had the same encoding in the input string, which was the third one above ("<" and ">", which by the way is the default by UTF-8).
This only occurs when using SOAP adapter. I tested File adapter and it sent the file exactly how delivered by the sender service (meaning, with the different encodes or with CDATA). We even thought about using module processor for replacing the characters in the message, but since any custom module processor comes before the main adapter module processor, it won't have any effect on the final message.
Using XMLSpy, I sent some test messages to our digital signer (which is also a webservice) with the three ways and it returned a different output when using "<" encoding in the input. Then, I sent this signed message to the webservice and it validated the signature!
We are suspecting that the webserver (which is IBM's WebSphere) always converts the input string to "<", and when they calculate the message hash code, it's different from what we sent (since we always sign a "<" encoded message).
My question is: is there any way of changing the default encode that the soap adapter module processor uses? Or at least of making it not changing the encode of the payload? If it were possible, we would send the message to the signer webservice with "<" encoding and the problem would be solved.
Thanks in advance,
Henrique.

Morten,
actually, we've found out that < = < , in both UTF-8 and ISO-8859-1 encodings. It makes no difference if you use one or the other.
The point which was troublesome for us were the special characters (like á,â,à,ã,é, etc) which have different encoding for UTF-8 and ISO-8859-1. Since we had identified that the service we were accessing wasn't able to identify these characters properly, we just removed them from the string fields and that worked out for us.
Hope it helps you out.
Regards,
Henrique.

SOAP Adapter And Protocol issue

Why and when we use SOAP adapter ? Does Xi uses processed XML messages using SOAP protocol ? I am new to Xi and confused over the issue. Can anyone please explain this to me. Thanks for your time.

HI KM
When you want to Send Data to XI from a Webservice and vice versa, your SOAP adapter is used.
Check these links for reference...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
A SOAP adapter is used in order to post messages to a webservice or provide a web service for receiving messages.
How ToUse the XI 3.0 SOAP Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
Please follow stefan's weblog
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
SOAP adapters are used for communicating with the WEB SERVICE. Web service is a software system designed to support interoperable Machine-to-Machine interaction over a network. Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services. In common usage Web Service refers to clients and servers that communicate using XML messages that follow the SOAP standard. So we communicate the WEB SERVICE using the SOAP adapters.
This is an example WEB SERVICE which follows the SOAP standards
http://www.webservicex.com/CurrencyConvertor.asmx?op=ConversionRate
A scenario using SOAP adapter..
RFC -> XI -> WebService - A Complete Walkthrough (Part 1) by Shabarish Vijayakumar
RFC -> XI -> WebService - A Complete Walkthrough (Part 2) by Shabarish Vijayakumar
SOAP , we will use for Webservices.. for sender and receiver side..also
one example from Webbrowser to XI to receiver ...system
another example is we can send it to end point URL..
Webservice
http://help.sap.com/saphelp_nw04/helpdata/en/9b/dad1ae3908ee44a5caf57e10918be9/frameset.htm
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
Soap adapter?
Regards
Abhishek Agrahari

HTTP Header fields in SOAP adapter

Hi All,
I have a scenario IDoc to SOAP adapter. In which my receiver given the details as
URL : https://b2b.ecsc.us.gxs.com/invoke/GXSGateway:receiveCTE
Header Name:             Header Value
Ent-sender                xxxx
Ent-receiver              yyyyy
Ent-APRF                 zzzzz
Ent-filename             (not sure what data need to give)
1. I request you to let me know where I need to give these headername and hader values in soap adapter.
2. my client require file as an attachment. Please let me know how I need to send the payload as an file and where the name need to be given in the header name (Ent-filename).
Currently I used MessageTransformBean to conver my XML to text structure(flatfile structure).
Please let me know if any more details required
Regards,
Dhill

Was out for lunch break..
Juz Rechecking
Transport Protocol : HTTP
Message Protocol: Soap 1.1
Adapter Engine -> Adapter Engine on the Integration Server
Connection Parameters
Target URL - > https://b2b.ecsc.us.gxs.com/invoke/GXSGateway:receiveCTE
Sure about no sever authentication required and they are not using any HTTP proxy for webservice >????
Conversion Parameters
Do Not Use SOAP Envelope -> Unchecked
Keep Headers -> Checked.
Keep Attachments -> Unchecked
Use Encoded Headers -> Unchecked
Use Query String -> not so sure might be Unchecked
<b>Authentication Keys</b>
If authentication is required for the receiver system, you can enter a password and a confirmation for each key value. This means that you do not need to write passwords in the enhanced message header.
If you want to specify or display authentication keys, select View Authorization Keys.
You can enter and confirm passwords for each authentication key value (TAuthKey or TproyxAuthKey).
Try once sending the message with Adapter-Specific Message Attributes
Unchecked. See if there is a hit.I knw itz not req but juz testing.
Yeah adapter stat must be active.
Last thing need to go through the whole scenario.
<b>Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*</b>

ERROR IN SOAP ADAPTER

Hi Guys,
I am trying to send a SOAP message to an external webservice to use a proxy.
I put host and gate in receiver soap adapter.
When i execute i have the next error:
SOAP:Call Failed
SOAP:error occured:java.io.IOException: invalid content type for SOAP: TEXT/PLAIN
Has anyone got a suggestion as to how I may resolve this problem?
Thanks very much,
Antonio

Hi Antonio,
Basically the issue is with the response that the webservice is returning, it may not be a valid reposne..use the TCP-Monitor tool from SAP to see the request/response message flowing...
Please do a search onsdn itself on your issue...you should get lots of threads talking about the same problem in the XI forum...
Thanks,
Renjith

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]

Receiver Axis SOAP Adapter

I have a SOAP receiver and am using the HTTP (Axis) Transport protocol. The reason for this being that the web service expects a web service security token with username and password.
I have loaded aii_af_axisprovider.sda with the mandatory .jar files as well as the wss4j optional .jar file.
I am using Basic authentication and have specified the the username and password. The 'Keep XI Headers' box has also been ticked.
However, I getting the following error:
"WSDoAllReceiver: Request does not contain required Security header"
Does anyone know what this could be? I am already specifying the username and password in the SOAP adapter. Do I need to specify this elsewhere?
Also, does anyone know I can view the SOAP messages being sent to the web service?
Thanks,
Krishneel

Hi,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f071ff6d-5bfb-2910-a985-86ac9f6ad2a6
Ruby and the SOAP RunTime (SRT) Handler
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f071ff6d-5bfb-2910-a985-86ac9f6ad2a6
http://help.sap.com/saphelp_nw04/helpdata/en/10/287cc10e4511d5991d00508b5d5211/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/72/c730dac06511d4ad310000e83539c3/frameset.htm
Thanks,
Madhu

Prefer HTTP or SOAP Adapter for file upload

Hi,
I have the following scenario:
Data (about 50 MB) is sent to PI and should get uploaded as file to a third party system.
I don't want to the use the File Adapter as I would have to use the FTP protocol and then have to install a FTP server.
On the third party system exists already a Web service for uploading files (in this case I would take the SOAP Adapter).
Another possibility would be to transfer the data with the HTTP Adapter.
My question is what are advantages and disadvantages of transferring the data to the third party system with the HTTP Adapter and respectively with the SOAP Adapter.
Thanks and regards
Patrick

Hi,
thanks for your answer, but most of threads say only that SOAP Adapter is for communication with Web services and HTTP not.
I know this already and in my case I can use both Adapters for the same task and want to know which I should choose in this case.
Like which one is maybe faster, more reliable, practicable , better for large files...
Regards
Patrick

Asynchronous SOAP adapter

Hi,
Please let me know under what circumstances would one want to use the SOAP Adapter with asyncrnous interfaces.
Edited by: Jyotika Manghani on Dec 28, 2007 8:48 AM

Hi,
You need to configure the SOAP adapter so that you can exchange SOAP messages between the Integration Engine and remote clients or servers of Web services.
The SOAP adapter provides a runtime environment that includes various SOAP components for the processing of SOAP messages. You can combine these SOAP components with separate components to meet your needs and requirements.
The SOAP adapter uses a helper class to instantiate and control SOAP components. If you want to use your own SOAP processing logic you must make your helper class known to the SOAP adapter.
To configure the SOAP adapter you must specify the following:
●     The helper class that implements the following interface:
com.sap.aii.messaging.adapter.ModuleBubbleHelper
●     The parameter values for the specified helper class
For example, you must specify the following parameters for the helper class ModuleBubbleHelperXMBWSImpl (instantiates a BubbleBag to integrate remote Web services with the Integration Engine):
○     Information about the Integration Engine destination (when the Integration Engine is acting as a service provider and therefore the SOAP adapter must be configured as a sender adapter).
○     Information about the Web service provider destination (when the Integration Engine is acting as a service client and therefore the SOAP adapter must be configured as a receiver adapter).
○     Various options for controlling the conversion of multi-part Integration Engine SOAP messages and Web service SOAP messages
The following arguments are mandatory:
○     XI.QualityOfService=<QualityOfService>
Specifies how the Integration Engine should process a message. The following values are permitted:
■      XI.QualityOfService=BE (Best Effort, means synchronous processing)
■      XI.QualityOfService=EO (Exactly Once, means asynchronous processing)
■      XI.QualityOfService=EOIO (Exactly Once in Order, means asynchronous processing using queues)
You must also define a queue name for EOIO:
Refer http://help.sap.com/saphelp_nw04/helpdata/en/bf/27fd3b651f6a1ce10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2f/41e641fb6e3f5de10000000a1550b0/content.htm
Hope this will help you in some extend.
Regards
Aashish Sinha
PS : reward points if helpful
Edited by: Aashish Sinha on Dec 28, 2007 9:01 AM

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

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

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

Soap Adapter : Encoding

Hi guys,
I'm having problems sending characters such as é ç è ô ... to my soap adapter. My scenario is that I am using a servlet to encode my soap envelop and then i'm sending it to my soap adapter. Here is a sample of my code :
HttpURLConnection connection = null;
StringBuffer sb = new StringBuffer();
sb.append(mapProp.getProperty(SOAP_BEG_ENVL));
                    sb.append(mapProp.getProperty(SOAP_BEG_BODY));
                    sb.append(mapProp.getProperty(SOAP_BEG_MT));
                    sb.append(mapProp.getProperty(SOAP_BEG_HDR));
                    sb.append(mapProp.getProperty(SOAP_BEG_INST)
                                + confProp.getProperty(INSTITUTION)
                                + mapProp.getProperty(SOAP_END_INST));
                    sb.append(mapProp.getProperty(SOAP_BEG_DATE)
                                + date
                                + mapProp.getProperty(SOAP_END_DATE));
                    sb.append(mapProp.getProperty(SOAP_BEG_TIME)
                                    + time
                                + mapProp.getProperty(SOAP_END_TIME));
                    sb.append(mapProp.getProperty(SOAP_END_HDR));
                    sb.append(mapProp.getProperty(SOAP_BEG_DETAIL));
                    buffReader = request.getReader();
                    do {
                         data = buffReader.readLine();
                         if (data != null) {
                              data = data.replaceAll("&", "&");
                              data = data.replaceAll("<", "<");
                              data = data.replaceAll(">", ">");
                              data = data.replaceAll(""", """);
                              data = data.replaceAll("'", "'");
                         sb.append(mapProp.getProperty(SOAP_BEG_DATA)
                                     + data
                                     + mapProp.getProperty(SOAP_END_DATA));
                    while(data != null);
                    sb.append(mapProp.getProperty(SOAP_END_DETAIL));
                    sb.append(mapProp.getProperty(SOAP_END_MT));
                    sb.append(mapProp.getProperty(SOAP_END_BODY));
                    sb.append(mapProp.getProperty(SOAP_END_ENVL));
                    //java.net.Authenticator.setDefault(new Auth());
                    url = new URL(confProp.getProperty(HTTP_URL));
                    connection = (HttpURLConnection) url.openConnection();
                    connection.setDoInput(true);
                    connection.setDoOutput(true);
                    connection.setRequestProperty("Content-Length", String.valueOf(sb.toString().length()));
                    connection.setRequestProperty("Content-Type","text/xml; charset=ISO-8859-1");
                    connection.setRequestProperty("SOAPAction","SomeAction");
                    connection.setRequestMethod( "POST" );
                    Charset cs = Charset.forName("ISO-8859-1");
                    out = connection.getOutputStream();
                    OutputStreamWriter osw = new OutputStreamWriter(out, cs);
                    osw.write(sb.toString().toCharArray());
                    osw.close();
                    out.close();
This is the error message I get back from my client :
java.io.IOException: Server returned HTTP response code: 400 for URL: https://XXXXX.wshs.:3405/dev/RM/Sync/Procurement
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
     at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(DashoA12275)
     at App.main(App.java:117)
I have no problems when their are no accented characters.
thanks for your help.
Steeve

Hi,
This might also cause due to time out, Check this Note - Note : 705013.
This might help you
400 Bad HTTP request (error -21)
invalid content type for SOAP: TEXT/HTML
Regards
Agasthuri Doss

The difference between SOAP adapter and WS adapter in PI 7.1

Hello all,
can anybody explain what is the main difference between SOAP adapter and WS adapter in PI 7.1?
I have checked this [link|http://help.sap.com/saphelp_nwpi71/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm]
but was not able to find the real difference.
Or better, what can I do with WS adapter I can't do with SOAP adapter? What are their advantages/disadvantages?
Thank you all, Igor.

In addition to RM, ws adapter also support other ws standard like SAML which is not available in SOAP adatper. Beside:
if your sender or receiver is SAP system, you can also monitor the message in the sender/receiver in addition to the PI box. This is a very good thing, because sometime the MONI in PI shows nothing wrong, but the MONI in your receiver will show you error message that's only related to the receiver system.
However, if you define ws sender CC, and your ws client doesn't support RM, you will have issue sending ws request.
And ws CC will generate ws runtime in PI box, if your configuration is wrong (like user name and password not correct), even if you correct it, the ws runtime sometime won't be regenated based on the correction. In this case you need to delete the ws CC/agreement, and re-create it with all correct information.
Beside make sure your basis team configured the PI system properly regarding ws. If not, you will have lot of pain to figure the problem which was my case.
Jayson

Style and encoding in XI SOAP Adapter

Similar Messages

Maybe you are looking for