SOAP Envelope Requirements

Hi,
i have a question concerning SOAP envelope.
(We run on XI30 SP19.)
A message sent to SOAP adapter with
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-SOAP-Envelope">
runs on error:
Caused by: org.apache.xmlbeans.XmlException: error: The document is not a Envelope@http://www.w3.org/2003/05/soap-SOAP-Envelope: document element namespace mismatch expected "http://www.w3.org/2003/05/soap-SOAP-Envelope" got http://schemas.xmlsoap.org/soap/envelope/
If i use
<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">
it works.
Can anyone point me to a ressource which describes the XI requirements to the SOAP envelope?
What is/isnt allowed for XI in special?
Thank you very much in advance.
Michael
Edited by: Michael Höcht on Oct 28, 2008 2:56 PM

Hmm, based on error it looks like service provider expecting some security headers. Are you able to test from other utility soapUI or browser?
Regards,
Chintan

Similar Messages

JAVA/ XSLT Mapping to Create a SOAP Envelope

Hello,
I have a File to SOAP scenario and it requires the SOAP message with a custom SOAP envelope. I have searched SDN and could only find that SOAP envelope can be created using a JAVA or XSLT mapping. However, I could not find any blog/ article which will help me understand, with an example, how this is actually coded (creating of a custom SOAP envelope).
Can anyone please point me to a valid blog/ article/ wiki which describes the procedure?
Thanks,
Pankaj.
P.S. Please no spamming of post with links on SOAP Envelope; I have already searched on SDN

Hello,
Here is a wiki using PI 7.1
https://wiki.sdn.sap.com/wiki/display/XI/SampleJAVAMappingcodeusingPI7.1+API
If you want to create a SOAP Envelope, comment out the codes
private static final DynamicConfigurationKey KEY_FILENAME =
         DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String inParam = arg0.getInputParameters().getString("PARAM_IN1");
     getTrace().addInfo("Input Parameter: " +inParam);
     int offset = inData.indexOf(inParam);
     //7. Reader Message ID from Message Header
     InputHeader messageHeader = arg0.getInputHeader();
     String messageId = messageHeader.getMessageId();
     //8. A DynamicConfiguration is a map containing adapter specific message attributes.
     // It associates DynamicConfigurationKeys with string values. The DynamicConfiguration object is obtained using
     // method getDynamicConfiguration()of class com.sap.aii.mapping.api.TransformationInput;
     DynamicConfiguration conf = arg0.getDynamicConfiguration();
     conf.put(KEY_FILENAME, "This Test file is set by JAVA Mapping");
     String outData = "";if(offset > 0){
     int offset1 = inData.indexOf(">", offset);
     String StartString =inData.substring(0,offset1);
     String DocumentNameSpace = " xmlns=\"urn:iso:std:iso:20022:tech:xsd:pain.002.001.02\"";
     String RemainingString = inData.substring(offset1);
lastly, instead of using
outData = StartString + DocumentNameSpace + RemainingString;
replace it with something like this
String outData = "";
outData = "<soap:Envelope xmlns:soap=\"http://www.w3.org/2003/05/soap-envelope\" xmlns:tem=\"http://yournamespace/\"><soap:Header/><soap:Body>"+inData.substring(inData.indexOf("?>")+2)+"</soap:Body></soap:Envelope>";
Hope this helps,
Mark

Generating SOAP Envelope when DO NOT USE ENVELOPE option is marked

My scenario: SPROXY => XI => 3rdParty WebService. Communication is synchronous. I've a problem with soap envelope. It is required by webservice, but when I use standard soap envelope generated by SAP I've a problem with receiving response from webservice.
So I want to create my own envelope. For this reason I've used DO NOT USE SOAP ENVELOPE option. Now the challenge comes. How can I create my own soap envelope?
Do you have any working example? Soap envelope should be added to message send from XI to 3rdParty WebService.
Helping answers => a lot of points

I'm talking about HTTP header.
When I'm sending SOAP request from SAP my whole message looks like when I use soap envelope
POST / HTTP/1.0
Accept: */*
Host: 192.168.132.179:54000
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Content-ID: <soap-02cce7702b1a11dd9902000c29ee261e[at]sap.com>
Content-Type: text/xml; charset=utf-8
Content-Disposition: attachment;filename="soap-02cce7702b1a11dd9902000c29ee261e[at]sap.com.xml"
Content-Description: SOAP
Content-Length: 259
SOAPACTION:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body><ns0:Sd2Ids_SzfExport xmlns:ns0='http://www.dat.de/sdii/ids/Sd2SOAP.wsdl'><arg1>1234567899-0</arg1><arg2>1</arg2></ns0:Sd2Ids_SzfExport></SOAP:Body></SOAP:Envelope>
Always after such request I got and HTTP 411 error.
In opposite, when I'm sending request from e.g. Altova or SoapUI, my message looks:
POST / HTTP/1.1
Content-Type: text/xml; Charset=UTF-8
User-Agent: XML Spy
Host: 192.168.132.179:54000
Content-Length: 489
Connection: Keep-Alive
Cache-Control: no-cache
<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:Body>
          <m:Sd2Ids_SzfExport xmlns:m="http://www.dat.de/sdii/ids/Sd2SOAP.wsdl">
               <arg1 xsi:type="xsd:string">1234567899-0</arg1>
               <arg2 xsi:type="xsd:string">1</arg2>
          </m:Sd2Ids_SzfExport>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
After that request WebService response is correct.
You can find such differences (except Content-length which is a result of XML message formatting) in those two headers:
- for first is used HTTP 1.0 protocol for later 1.1
- in SAP header an info about attachment is added
After a lot of test I thing that those attachment info in header of HTTP is causing a problem. So I want to use DO NOT USE SOAP ENVELOPE option to generate HTTP header without Content-Disposition and generate SOAP Envelope manually.

Unsing RequestOneWayBean with Do Not Use SOAP Envelope

HI All ,
I have a requriement where Ecc is calling PI with an Asyn Proxy and PI calls a Sync Webservice and gets the Response back and sends the response back to ECC in Async manner . (Async - Sync Bridge).
I need to call aWeb Service which required specifc SOAP Headers . SO I have created a Custom Structure via XSLT mapping and calling the Web Service with the Option Do Not Use SOAP Envelope as checked . I have also used the RequestResponse Bean & ResponseOneWay Bean in the SOAP Receiver adapter to make the call from Sync to Asyn. When I execute the Interface the response from the Web Service is not flowing into PI .
I am getting the error "Exception caught by adapter framework: InterfaceDetermination did not yield any actual interface" .
Has anyone worked on the ResponseOneway Bean with parameter "Do Not Use SOAP Envelope as checked" . Can some one please help me out with this issue..
Thanks
Regards
NIlesh Taunk.

HI Eng ,
I have not been able to accept the SOAP Fault Response. The link that you have provided above works for accepting the SOAP Fault . But in my case the SOAP Receiver Adapter has the Option "DO NOT Use SOAP Envelope " checked . So it is still not working in my case .
I have made all the Configurations in the Receiver SOAP adapter but am unable to get the fault response back .
Please find below the Screenshot of the Receiver SOAP Adapter.
Im my case I am able to receive the successfull response in my Response Mappping (I have created a diff ICO for Response Message and a diff ICO for Fault Message). When a fault is received even the Fault message goes to the response mapping and it fails in the response mapping as the fault structure & the response structure do not match .
Do we need to make some additional configuration for the handing faults, whn the option "DO NOT use SOAP envlope is checked" as it removed the Env from the messgaes.
Am I missing something, would you be able to have a look.
Thanks
Regards
Nilesh Taunk.

Do not use SOAP envelope

I have a scenario in which a Webservice is called from PI; as the webservice request some specific fields in the SOAP-header I have found that I should check the "Do not use SOAP envelope" option in the SOAP-receiver channel.
I have searched the forum/SDN for examples of how to create the SOAP envelope including the required header fields. I have found some posts refering to XSLT-mapping; however I'm not famliar with XSLT so I'm looking for an example or guide how to create the SOAP envelope for this scenario.
Can anybody be of assistance?
Kind regards,
John.

Here is a sample of an xlst I used for this purpose.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/>
<soapenv:Body>
      <p262:operationName xmlns:p262="http://othersite.com">
      <xsl:apply-templates/>
    </p262:operationName>
</soapenv:Body>
</soapenv:Envelope>
</xsl:template>
<xsl:template match="shippingOptions">
      <shippingOptions>
          <xsl:apply-templates select="destination" />
          <equipmentId><xsl:value-of select="equipmentId"/></equipmentId>
          <xsl:apply-templates select="origin" />
      </shippingOptions>
</xsl:template>
<xsl:template match="destination">
        <destination>
          <countryCode><xsl:value-of select="countryCode"/></countryCode>
          <postalCode><xsl:value-of select="postalCode"/></postalCode>
        </destination>
</xsl:template>
<xsl:template match="origin">
        <origin>
          <countryCode><xsl:value-of select="countryCode"/></countryCode>
          <postalCode><xsl:value-of select="postalCode"/></postalCode>
        </origin>
</xsl:template>
</xsl:stylesheet>

How to capture SOAP fault when using "Do not use SOAP envelope" parameter

Hi,
we have a synchronous RFC -> XI -> Web Service scenario. The Web Service requires some custom SOAP header elements for user authorization which forced us create the entire SOAP message in a message mapping and to set the "Do not use SOAP envelope" parameter in the receiving SOAP adapter.
In order to capture the SOAP fault message from the Web Service we have created a message interface with a fault message and also created an interface mapping with a fault message mapping.
Our problem is that the fault message is not populated when we get a SOAP fault message back from the Web Service. Is this due to the fact that we have set the "Do not use SOAP envelope" parameter?
Thanks in advance!
Stefan
Message was edited by:
Stefan Nilsson

Hi Bhavesh,
I have exaactly same scenario. But the only difference is that the Successful payload is also not coming into PI.
The request is successfully hittng the webservice.
Please guide me on how to capture the paylod.
I am using the WSDL provided by the thirdparty but sill the message is not coming into PI.

Proxy to SOAP Scenario, payload with the SOAP envelops

Hi ,
We have Scenario like Proxy to SOAP,As per Business requirement they are asking payload with ENVELOP . Like below message
================================================================
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding">
     <SOAP-ENV:Header>
          <nseps:endpoints xmlns:nseps="urn:schemas-IBX:/docs/endpoint.nsendpoint" SOAP-ENV:mustUnderstand="true">
               <nseps:to>
                    <nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
               </nseps:to>
               <nseps:from>
                    <nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
               </nseps:from>
          </nseps:endpoints>
          <nsprop:properties xmlns:nsprop="urn:schemas-IBX:/docs/property.nsproperty" SOAP-ENV:mustUnderstand="true">
               <nsprop:identity>3198841w-fa4d-dafa-2797-89029c15255b</nsprop:identity>
               <nsprop:sentAt>2010-01-18T02:42:08Z</nsprop:sentAt>
               <nsprop:topic>CostObjectInformation</nsprop:topic>
          </nsprop:properties>
     </SOAP-ENV:Header>
     <SOAP-ENV:Body>
//Payload of the message to be added here.
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I am trying out this in XSLT, but I am not sure how to add the SOAP Envelops and these Envelops are Static.
Can someone help me out in this.
Joe

But if you look at the SOAP Envelop Structure below it is not XI generated SOAP Envelop. IBX (3rd party) has its own standards, so XI has to Produce the SOAP Envelop according to their standards.
I have created the XSD with SOAP Envelop stucture with what ever structure 3rd party wants, but the problem is when Creating the SOPA Envelp tag, where it has a ":" where its not allowing me to create the valid XSD. And at the same time 3rd party is not in position to give us even WSDL file and we are not using Webservice call and they are not able to provide the XSD with SOAP envelop structure.
I thought of going for XSLT and started doing as well with what ever XSD 3rd party has provided, which does not have the SOAP Envelop structure and has only payload XSD structure.
80% of the SOAP Envelop structure is Static, it does not change. Only 2 fields keeps changing. IS there any solution that we can create XSD with the SOAP structure with Special Character ": "or is there any way in doing in XSLT.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding">
<SOAP-ENV:Header>
<nseps:endpoints xmlns:nseps="urn:schemas-IBX:/docs/endpoint.nsendpoint" SOAP-ENV:mustUnderstand="true">
<nseps:to>
<nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
</nseps:to>
<nseps:from>
<nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
</nseps:from>
</nseps:endpoints>
<nsprop:properties xmlns:nsprop="urn:schemas-IBX:/docs/property.nsproperty" SOAP-ENV:mustUnderstand="true">
<nsprop:identity>3198841w-fa4d-dafa-2797-89029c15255b</nsprop:identity>
<nsprop:sentAt>2010-01-18T02:42:08Z</nsprop:sentAt>
<nsprop:topic>CostObjectInformation</nsprop:topic>
</nsprop:properties>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
its a high priority issue.
Thanks in Advance.
Joe.

More information regarding 'Don't Use SOAP Envelope' in SOAP sender Adapter

Hi,
maybe this document could help you:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
It says about selecting Do Not Use SOAP Envelope.
> In this case the sender SOAP adapter requires an additional
parameter nosoap=true in the URL.
Regards
Patrick

Answered

Avoid using Username and password in SOAP Envelope

Hi Team
I am working on calling the sercured web-service from PLSQL and able to call it successfully and get the response.
In the SOAP envelope, I have header and body.
Header contains the WS Security which includes username and password to authenticate the web-service and body contains the actual input pay load for service.
Currently, header has username and password as 'hard-coded', is there a way to avoid the usage of username and password.
We already tried to SIF for EBS methodology where in following steps are done:
1) Create and event in EBS.
2) Pass the event along with payload to SOA.
3) SOA receives the event and triggers web-service and gets the response.
4) Pass the response to EBS.
This technique does avoid usage of username and password but takes 20 seconds to do the job. However, the appraoch above takes hardly 1 second.
Please let me know in case any one has any idea on how to avoid credentials usage in SOAP envelope.
Thanks
Mirza Tanzeel

How about doing away with that approach entirely?
Password authentication requires one to keep a secret, secret. And that is the primary problem as how does one safely guard the secret, and manage the secret (by regularly changing)?
Relying on secrets is a problem. I have never been a fan of password based security.
Instead:
a) use HTTPS to secure communication between sender and receiver
b) use robust firewall rules to ensure that only sender is allowed to communicate with receiver
c) implement sound network management and exception reporting (to detect and prevent violations on network infrastructure level)
If you lack in the network infrastructure and administration areas, then:
a) make the web service endpoint on server on localhost only (do not expose it to the outside world)
b) establish a trusted ssh connection between sender and receiver using strongly encrypted RSA/DSA keys
c) configure sender with a service that opens a reverse tunnel to target, exposing the web service as a local port on its localhost

How to override the default SOAP envelope prefix?

I have a Web service as an external reference. In run-time WebLogic generates SOAP messages with a default prefix <env:Envelope xmlns:env=http://schemas.xmlsoap.org/soap/envelope/”…>. Normally this is fine. However the Web service required a prefix as <soapenv:…>. How can I have WebLogic generate soap envelope prefix as soapenv instead env?

hello!
It's possible. You must implement handler and change envelope and body prefix. Here is example:
public class WsHandler implements SOAPHandler<SOAPMessageContext> {
public boolean handleMessage(SOAPMessageContext context) {
Boolean outboundProperty =
(Boolean) context.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);
if (outboundProperty.booleanValue()) {
try {
SOAPEnvelope envelope = context.getMessage().getSOAPPart().getEnvelope();
envelope.setPrefix("soapenv");
envelope.removeNamespaceDeclaration("env"); //remove old prefix
envelope.getBody().setPrefix("soapenv");
context.getMessage().saveChanges();
} catch (Exception e) {
throw new ProtocolException(e);
}

SOAP prefixes required

Hi Experts,
I have an SOAP inbound interface comming to XI.
The SOAP envelop has not prefixes defined.
This message was genareted by Microsoft Bizztalk
The message is generating error in mapping.
But, when I run the interface with the same WSDL but using XMLSpy, it's working fine.
The question is, SOAP prefixes are allways required ?
The message genareted by BizzTalk shoud be wrong or XI mapping is wrong ?
Follow bellow the messages example:
MESSAGE FROM BIZZTALK - ERROR !!!
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<MTP_Qualidade_Celulose_Seca
MESSAGE FROM XMLSPY - WORKING FINE !!!
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<m:MTP_Qualidade_Celulose_Seca
Cheers !
Regis Ferrato

are you able to see the message in XI. If yes can you post the error message from log.

SOAP Envelope element descriptions

Does anybody have a link to a document that explains the semantic meaning of all of the elements that exist within the PI message SOAP Header?
BR,
Tony.
Edited by: Anthony Bateman on Apr 14, 2008 12:42 PM

Hi ,
This is from some document ...check it.
<i>The SOAP adapter creates the SOAP envelope. You cannot influence this procedure. If
you need to apply special tags inside the SOAP header, the only option is to create the
whole SOAP envelope during mapping, and in the case of a synchronous call, to remove
the SOAP envelope in the mapping.
In the SOAP adapter channel, select Do Not Use SOAP Envelope.
By using this parameter, you can use the SOAP adapter to send or receive non-
SOAP messages. In this case the sender SOAP adapter requires an additional
parameter nosoap=true in the URL. For example:
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
channel=<party>:<service>:<channel>&nosoap=true</i>
Sekhar

Sending SOAP Envelope to MQ

Hi
we have requirement that we need to send the request message to 3rd party system (invoked using MQ) as SOAP envelope
we have used Invoke activity and added header value in Headers in invoke activity but our 3rd party system is unable to get it as SOAP format it is only getting SOAP body and SOAP header is not getting passed

You can find "HOWTO: Consume Webservices via PL/SQL" at http://www.liberidu.com/blog/?p=1249. It shows the basics for sending a SOAP message to a remote WS and getting the response back. It also links to another example in the OTN forums you can use as a reference point.
Hope that helps.

How to resolve error "No SOAP Envelope but 1 {} PARAMETERS"

Hi,
I have configured an interface where the sender (SAP system) sends out a message via proxy on the Local Integration Engine, which is after XI processing supposed to be posted via HTTP (using the SOAP Adapter).
The message is processed correctly by XI, but fails to pass the SOAP Comm Channel. The error message in the Communication Channel Monitoring reads:
SOAP: call failed: java.io.IOException:No SOAP Envelope but 1 {} PARAMETERS; HTTP 200 OK
Can anyone help me understand what this means and how I can resolve this? Thanks!

Dear Johannes,
Is the SOAP call taking place synchronously ? It looks like at the end of your SOAP channel, system is not responding as expected by XI (you seem to receive the regular HTTP 200 OK code, but it does not match SOAP protocol requirements) ...
I've had such issues when web services were down due to web server issue (in this case, you just get, for instance, HTTP 500 response body, which not really SOAP compliant)
Rgds
Chris

Enclosing Transformed XML in SOAP envelope

All,
I am currently facing difficulty to send a XML document via HTTP Post enclosed in a SOAP envelope.
1. The BPEL process, using database polling feature of DB Adapter, will get the records from the database.
2. Transform the message
3. Now I want to enclose the transformed message into a SOAP envelope and send it via HTTP Post to a third party system.
I am facing difficulty in Step 3. Could some one suggest me how to enclose the XML messages inside a SOAP envelope and some pointers to use HTTP Adapter?
Thanks in advance

I just found out that HTTP binding activity does not support XMLs with complex types.(Note ID: 1328955.1) Now I guess the only choice for me is to use Java or any other programming language to do the HTTP post.
This is what i am thinking.
1. Create a XML file with the required format using SOA
2. Use a Java program to pick the file from a location and send it to the target URL( enclosing it in a SOAP envelope)
3. Get the response and update oracle status tables.
The trouble i will face here is to pass the file name , target URL as the parameters.
Is there a way to create this program and orchestrate using BPEL? Meaning- call this java program after i finish generating the file and pass the file name and the target URL as parameter?
Please suggest if a better approach could be followed for this.
Thanks,
Dwarak

SOAP Envelope Requirements

Similar Messages

Maybe you are looking for