SOAP Envelope encodingStyle

Hi experts,
I have a PI SOAP Receiver, sending to a Java Powerbuilder app. I am getting an HTTP 200, but with an error message in SXMB_MONI:
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: java.lang.NullPointerException; HTTP 200 OK</SAP:AdditionalText>
When I execute the same scenario using soapUI instead of PI, using the same SOAP Payload, I get no SOAP body, only this HTTP Response (HTTP 200 OK as well):
" No mapping found for 'class java.lang.String' using encoding style 'http://xml.apache.org/xml-soap/literalxml' "
When I change the Payload slightly in soapUI, ie. adding an encodingStyle attribute to the SOAP Envelope, I get the expected response message ("Test OK").
To summarize:
PI sends this SOAP Envelope, which the remote app cannot accept (no mapping found):
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
When the SOAP Envelope is modified like below, the test is ok:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
Any ideas how I can add an encodingStyle attribute ?
kr,
Peter Glas

An sdn search gave me this thread to create custom SOAP envelop
Generating SOAP Envelope when DO NOT USE ENVELOPE option is marked

Similar Messages

Error with Do Not use SOAP envelope

All,
I used the do not send SOAP envelope option in the SOAP receiver adapter.
Instead of XSLT, I used JAVA mapping to create the entire SOAP message ( Am more comfortable with Java and this is just a trial) , and this is the output of my java mapping with the SOAP envelope created,
<i><?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2001/12/soap-envelope"soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding"><soap:Header></soap:Header><soap:Body><ns1:GetQuote xmlns:ns1="http://www.webserviceX.NET/"><ns1:symbol>SAP</ns1:symbol></ns1:GetQuote></soap:Body></soap:Envelope></i>
Am using the STOCK Quote for testing purposes and this is the error I am getting when testing my interface,
<i><faultstring>System.Web.Services.Protocols.SoapException: Server found request content type to be '', but expected 'text/xml'. at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() at System.Web.Services.Protocols.WebServiceHandler.Invoke() at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring></i>
Any directions / inputs on how to resolve this issue?
Regards,
Bhavesh

Henrique,
Tried various permutations~~ The only new error / progress seems to be for this,
SOAPAction "http://www.webserviceX.NET/GetQuote"
This is giving me an error ,
<i>HTTP server code 400 reason Bad Request explanation <h1>Bad Request (Invalid Header Name)</h1></i>
Also, tried by adding the Colon after SOAPAction,
SOAPAction: "http://www.webserviceX.NET/GetQuote"
Same error
Final thing i guess is to make SOAPAction all small as soapaction and check if it works. Will let you know.
Regards,
Bhavesh

SOAP envelope format

Hi,
I must make sample code of web service calls for PHP and Java to our clients. So far I have got it working with PHP but I have trouble to successfuly call web service in Java.
I have generated stub files with wscompile -keep -gen:client config.xml
It makes SOAP envelope, and calls service but there is no response - unfortunetly i cant debug cause from server side, but it must have something to do with SOAP envelope. Server side is done with Microsoft SOAP Toolkit. I have included Java generated envelope and nosoap (PHP)generated envelope (PHP one works). (PS! TimeToSend field is 0 in PHP version and 0.0 in Java, can it be cause?)
Envelope with Java:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://tempuri.org/fmts/message/" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<env:Body>
<ns0:SendSMS>
<MessageText xsi:type="xsd:string">test</MessageText>
<TimeToSend xsi:type="xsd:double">0.0</TimeToSend>
<StatusURL xsi:type="xsd:string"></StatusURL>
</ns0:SendSMS>
</env:Body>
</env:Envelope>
Using nosoap lib for PHP envelope looks like this:
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:nu="http://tempuri.org/fmts/message/">
<SOAP-ENV:Body>
<nu:SendSMS>
<MessageText xsi:type="xsd:string">PHP</MessageText>
<TimeToSend xsi:type="xsd:double">0</TimeToSend>
<StatusURL xsi:type="xsd:string"></StatusURL>
</nu:SendSMS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Found out what was frong. There was password field in envelope (removed it in previous post - and i managed to enter wrong password)

SOAP envelope missing some info

Hello
I have been struggling with a web service request for some time and i need some assistance.
I have to insert subscriber info into someone elses db.They created a web service for me.
My code looks like this:
<cfinvoke webservice="http://41.208.61.35/legacyfallback/ws/legacyLifeWS.php?wsdl" method="register1" returnVariable="somereturn">
    <cfinvokeargument name="name" value="steve" />
    <cfinvokeargument name="mobilenumber" value="123456" />
</cfinvoke>
The person who created the web service uses php.
He checked my return and he saw this:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><register1 soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><mobileNumber xsi:type="xsd:string">123456</mobileNumber></register1></soapenv:Body></soapenv:Envelope>
He tried the same from his side using php to do the call and he got this return:
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://www.callagain.co.za/soap/legacyLifeWS" xmlns:types="http://www.callagain.co.za/soap/legacyLifeWS/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><register1><mobileNumber xsi:type="xsd:string">0824566072</mobileNumber><name xsi:type="xsd:string">Pieter</name></register1></soap:Body></soap:Envelope>
I am missing this in my envelope:
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://www.callagain.co.za/soap/legacyLifeWS" xmlns:types="http://www.callagain.co.za/soap/legacyLifeWS/encodedTypes"
Please can you explain how i can get the same info my soap envlope?
Thank you


<cfset wsdl_url="http://41.208.61.35/legacyfallback/ws/legacyLifeWS.php?wsdl">
<cftry>
    
    <cfsavecontent variable="msg"><?xml version="1.0" encoding="UTF-8" ?>
        <cfoutput><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         <soapenv:Body>
         <ns1:query soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://41.208.61.35/soap/legacyLifeWS">
         <wsUserName xsi:type="xsd:string">Steve</wsUserName>
          <wsUserPass xsi:type="xsd:string">a1b2c3</wsUserPass>
          <mobilenumber xsi:type="xsd:string">12345678</mobilenumber>
          </ns1:query>
          </soapenv:Body>
          </soapenv:Envelope></cfoutput>
    </cfsavecontent>
    
    
    
    <cfhttp url="#wsdl_url#" method="post" >
        <cfhttpparam type="header" name="content-type" value="text/xml">
        <cfhttpparam type="header" name="SOAPAction" value="http://41.208.61.35/legacyfallback/ws/legacyLifeWS.php/query">
        <cfhttpparam type="header" name="content-length" value="#len(msg)#">
        <cfhttpparam type="header" name="charset" value="utf-8">
        <cfhttpparam type="xml" name="registerRequest" value="#trim(msg)#">
    </cfhttp>
    
    <p><cfoutput>#xmlFormat(cfhttp.fileContent)#</cfoutput> </p>
<cfcatch type="any">
    <cfdump var="#cfcatch#">
</cfcatch>
</cftry>

WCF request with utl_dbws how to add Header into SOAP envelope

I’m trying to make WCF (Windows Communication Foundation) request and using for that utl_dbws package.
After making request (calling utl_dbws.invoke) it will give error “ORA-29532: Java call terminated by uncaught Java exception: javax.xml.rpc.soap.SOAPFaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect t”
I turned on logging (utl_dbws.set_logger_level) I see that system sends standard SOAP envelope and does not have Header at all. How can I use my own SOAP envelope and/or add Header.
All info that logging give is:
ServiceFacotory: oracle.j2ee.ws.client.ServiceFactoryImpl@eec8c59c
WSDL: null
Service: oracle.j2ee.ws.client.BasicService@7c110d23
*** Created service: -677524827 - oracle.jpub.runtime.dbws.DbwsProxy$ServiceProxy@562bd0c4 ***
ServiceProxy.get(-677524827) = oracle.jpub.runtime.dbws.DbwsProxy$ServiceProxy@562bd0c4
getOperationInfo return NULL: port={http://tempuri.org/Service/}BasicHttpBinding_Service, operation={http://tempuri.org/Service/}GetLov
setProperty(javax.xml.rpc.soap.http.soapaction.use, true)
setProperty(javax.xml.rpc.soap.http.soapaction.uri, http://tempuri.org/Service/GetLov)
setProperty(javax.xml.rpc.encodingstyle.namespace.uri, http://www.w3.org/2005/08/addressing)
setProperty(javax.xml.rpc.security.auth.username, DefaultUser)
setProperty(javax.xml.rpc.security.auth.password, MySecretPassword)
<GetLOV xmlns="http://tempuri.org/"> <request xmlns:d4p1="http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> <d4p1:AgentCode>AGENT</d4p1:AgentCode> <d4p1:Language>ENG</d4p1:Language> <d4p1:ProcessName>test</d4p1:ProcessName> </request></GetLOV>
Attribute 0: http://tempuri.org/: xmlns, http://tempuri.org/
createElement(GetLOV,null,http://tempuri.org/)
Attribute 0: http://tempuri.org/: xmlns, http://tempuri.org/
dbwsproxy.element.node.child.0: 1, null
dbwsproxy.add.map: d4p1, http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request
Attribute 0: http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request: xmlns:d4p1, http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request
dbwsproxy.add.map: i, http://www.w3.org/2001/XMLSchema-instance
Attribute 1: http://www.w3.org/2001/XMLSchema-instance: xmlns:i, http://www.w3.org/2001/XMLSchema-instance
createElement(request,null,http://tempuri.org/)
dbwsproxy.add.soap.element.namespace: d4p1, http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request
Attribute 0: http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request: xmlns:d4p1, http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request
dbwsproxy.add.soap.element.namespace: i, http://www.w3.org/2001/XMLSchema-instance
Attribute 1: http://www.w3.org/2001/XMLSchema-instance: xmlns:i, http://www.w3.org/2001/XMLSchema-instance
dbwsproxy.element.node.child.0: 1, null
dbwsproxy.lookup.map: d4p1, http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request
createElement(d4p1:AgentCode,null,http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request)
dbwsproxy.text.node.child.0: 3, E01306
dbwsproxy.element.node.child.1: 1, null
dbwsproxy.lookup.map: d4p1, http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request
createElement(d4p1:Language,null,http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request)
dbwsproxy.text.node.child.0: 3, ENG
dbwsproxy.element.node.child.2: 1, null
dbwsproxy.lookup.map: d4p1, http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request
createElement(d4p1:ProcessName,null,http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request)
dbwsproxy.text.node.child.0: 3, tesr
request:
<GetLOV xmlns="http://tempuri.org/">
<request xmlns:d4p1="http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://tempuri.org/">
<d4p1:AgentCode>AGENT</d4p1:AgentCode>
<d4p1:Language>ENG</d4p1:Language>
<d4p1:ProcessName>test</d4p1:ProcessName>
</request>
</GetLOV>
13.05.2010 14:17:28 oracle.j2ee.ws.client.ClientMessages infoAboutToInvokeCallForEndpoint
INFO: Trying to connect to URL: https://x.y.z/WS/ Service.svc
13.05.2010 14:17:30 oracle.j2ee.ws.client.StreamingSender _sendImpl
FINE: StreamingSender.request:<?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><env:Body><GetLOV xmlns="http://tempuri.org/"><request xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns:d4p1="http://schemas.datacontract.org/2004/07/x.y.z.LOV.Request"><d4p1:AgentCode>AGENT</d4p1:AgentCode><d4p1:Language>ENG</d4p1:Language><d4p1:ProcessName>test</d4p1:ProcessName></request></GetLOV></env:Body></env:Envelope>
13.05.2010 14:17:30 oracle.j2ee.ws.client.StreamingSender _sendImpl
FINE: StreamingSender.response:<?xml version="1.0" encoding="UTF-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode><faultstring xml:lang="et-EE">The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.</faultstring></s:Fault></s:Body></s:Envelope>
Exception in thread "Root Thread" javax.xml.rpc.soap.SOAPFaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
     at oracle.j2ee.ws.client.StreamingSender._raiseFault(StreamingSender.java:559)
     at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java)
     at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
     at oracle.j2ee.ws.client.dii.CallInvokerImpl.directInvoke(CallInvokerImpl.java:705)
     at oracle.j2ee.ws.client.dii.BasicCall.directInvoke(BasicCall.java:692)
     at oracle.j2ee.ws.client.dii.BasicCall.invoke(BasicCall.java:598)
     at oracle.jpub.runtime.dbws.DbwsProxy$CallProxy.invokeProxy(Unknown Source)
     at oracle.jpub.runtime.dbws.DbwsProxy$CallProxy.access$2600(Unknown Source)
     at oracle.jpub.runtime.dbws.DbwsProxy.invokeProxy(Unknown Source)

HTTP is HTPP... mostly.
In other words, the application protocol is stand and specified in RFC2616 (http://www.w3.org/Protocols/rfc2616/rfc2616.html)
The exception is specific proprietary extensions.. like for example Microsoft's NTLM authentication handshake.
The UTL_HTTP interface supports the protocol pretty well as per the protocol's specification. So using it to interact with a a web service should not be a major issue. The protocol is standard (e.g. POST command is used to supply the payload to the web service). The only real issue is formatting the payload for that as per what the web service expect. And that has nothing to do with HTTP itself - or UTL_HTTP. It is simply the delivering mechanism.
Getting that mechanism to work is fairly easy and should not pose a problem. Instead I suggest you focus on exactly how the HTTP payload needs to look like. Does that web service expects any specific name-values in the header? What does it expect in the body? Etc.

OSB not adding SOAP-ENV:encodingStyle attribute, invoke fails

Hi, I have a WSDL that when inspected by XMLSpy, creates the following payload.
<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:logOut xmlns:m="http://konnex.aarp.org/wsdl/HartfordServicesSecure" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
               <String_1 xsi:type="xsd:string">String</String_1>
          </m:logOut>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
When I try to invoke this via OSB, I get the following message.
<env:Envelope env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://konnex.aarp.org/types/HartfordServicesSecure">
     <env:Body>
          <env:Fault>
               <faultcode>env:Client</faultcode>
               <faultstring>JAXRPCTIE01: caught exception while handling request: unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/, actual=</faultstring>
          </env:Fault>
     </env:Body>
</env:Envelope>
The reason is because OSB is not putting in the *SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/* attribute. I verified this in obtunnel.
I'm currently trying to work around this in OSB using xquery but so far I've had no luck.
Thanks in Advance.

hi,
I have two policies applies on business service :
1. Password digest policy
<wsp:Policy wsu:Id="PasswrdDigest" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wssp="http://www.bea.com/wls90/security/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wssp:Identity>
          <wssp:SupportedTokens>
               <wssp:SecurityToken TokenType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken">
               <wssp:UsePassword Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest"/>
          </wssp:SecurityToken>
          </wssp:SupportedTokens>
          </wssp:Identity>
</wsp:Policy>
2. Message Interval Policy
<wsp:Policy wsu:Id="MessageAge" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<wssp:MessageAge Age="60" xmlns:wssp="http://www.bea.com/wls90/security/policy"/>
</wsp:Policy>
Please share your views.

PB & web service : how to manipulate soap envelop ?

Hi all,
I am in the process of testing PB's ability to consume an existing web service. I have done some reading left and right.
I can create the proxy , but i always end up having the Cannot invoke webservice messagebox.
Here's my little piece of PB code
PB CODE START
soapconnection conn // Define SoapConnection
checkvatport proxy_obj // Declare proxy
long rVal, lLog
real amount
date date_a
string ls_a,ls_b,ls_c
conn = create soapconnection //Instantiated connection
lLog = conn.SetSoapLogFile ("C:\mySoapLog.log")
rVal = Conn.CreateInstance(proxy_obj, "checkvatport", "")
messagebox("test rval",string(rval))
// Create proxy object
try
   date_a = today()
boolean w_t
w_t = TRUE
   str_checkvat str1
   tns1__checkvatresponse str2
str1.countrycode = "BE"
str1.vatnumber = "0810416786"
ls_a = proxy_obj.checkvat(str1.countryCode,str1.vatNumber,str2.requestdate,str2.valid,str2.address)
messagebox("LS-a",ls_a)
catch ( SoapException e )
   messagebox ("Error", "Cannot invoke Web service")
   // error handling
end try
destroy conn
PB CODE END
And here's the soaplog contents
SOAPLOG START
CLOSED
REQUEST:
CLOSED
POST /taxation_customs/vies/services/checkVatService HTTP/1.1
Host: ec.europa.eu
Connection: Keep-Alive
User-Agent: EasySoap++/0.6
Content-Type: text/xml; charset=utf-8
SOAPAction: "urn:ec.europa.eu:taxud:vies:services:checkVat#checkVat"
Content-Length: 654
<E:Envelope
xmlns:E="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:A="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:s="http://www.w3.org/2001/XMLSchema-instance"
xmlns:y="http://www.w3.org/2001/XMLSchema"
E:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<E:Body>
<m:checkVat
xmlns:m="urn:ec.europa.eu:taxud:vies:services:checkVat:types">
<ns1:countryCode
xmlns:ns1="urn:ec.europa.eu:taxud:vies:services:checkVat"
s:type="y:string">BE</ns1:countryCode>
<ns2:vatNumber
xmlns:ns2="urn:ec.europa.eu:taxud:vies:services:checkVat"
s:type="y:string">0810416786</ns2:vatNumber>
</m:checkVat>
</E:Body>
</E:Envelope>
RESPONSE:
HTTP/1.1 500 Internal Server Error
Date: Wed, 04 Jun 2014 09:33:11 GMT
Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8
Server: Europa
Connection: Keep-Alive
Transfer is Chunked!
01d7
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Unmarshalling Error: unexpected element (uri:"urn:ec.europa.eu:taxud:vies:services:checkVat", local:"countryCode"). Expected elements are <{urn:ec.europa.eu:taxud:vies:services:checkVat:types}vatNumber>,<{urn:ec.europa.eu:taxud:vies:services:checkVat:types}countryCode> </faultstring></soap:Fault></soap:Body></soap:Envelope>
0000
GetChunkLength: 01d7 = 471
Connection Disconnected
SOAPLOG END
Now i tried the to cut and paste the above soap envelop in SOAPUI , and it gives me the exact same error message as in the soaplog.
I then tried creating a request through SOAPUI but based on the wdsl ,SOAPUI is giving me a different soap envelop as the one PB generated ?
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ec.europa.eu:taxud:vies:services:checkVat:types">
   <soapenv:Header/>
   <soapenv:Body>
      <urn:checkVat>
         <urn:countryCode>?</urn:countryCode>
         <urn:vatNumber>?</urn:vatNumber>
      </urn:checkVat>
   </soapenv:Body>
</soapenv:Envelope>
If i enter parameters in the above envelop and check it through SOAPUI , i end up having the result i want.
Is there any way we can manipulate the soap envelop contents ? Or does anyone have any idea why the soap envelop generated by PB ends up having the above mentioned error in the soaplog file ?
What am i missing ?
TIA
John

You're using the EasySOAP proxy. You didn't mention what version of PowerBuilder, but if you're using a version that supports the .Net engine instead use that. The EasySOAP web service support is quite old.
Once you do that you won't be able to use the log. Instead, use something like Fiddler to trap the request and response.

Problem in mapping while using Do not Use SOAP Envelope

Hi All,
This is wrt my thread 'Removing and adding SOAP Envelope'
I am currently working on SOAP-XI-Proxy Scenario.
For some un avoiadable reason, I had to use the option 'DO not use SOAP Envelope' .So the SOAP Envelope came withen the payload and in the pipeline, I can see the payload prefixed by '<?xml version="1.0" ?>' .
Now my payload looks like
<?xml version="1.0" ?> ( no more the encoding="utf-8" notation is there)
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
   xmlns:xsd="http://www.w3.org/2001/XMLSchema"    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<Complaint_Request xmlns="urn:******createserviceticket">
<CaseNo>12345</CaseNo>
<CustomerNo>12345</CustomerNo>
</Complaint_Request>
</soapenv:Body>
</soapenv:Envelope>
To accomodate the change, I also changed my request structure as
<Complaint_Request> (My new message Type)
    <Envelope>
     <Body>
       <Complaint_Request> (My previous message Type)
        <caseNo>
        <CustomerNo>
But I am facing problem in mapping the values to the target structure (which is a flat structure),
as the payload doesnot start with ' ns1: ' notation any more . Even XSLT mapping is not working.
When I am pasting the payload in the Testing Mapping Editor, the Source Node are correctly
formed, but all come in RED . But as the root node , ie 'ns0' is not there, the value
from child nodes are not getting mapped to the target fields.
Regards,
Subhendu

Hi Joel,
SAP says, when we use the option 'DO Not Use SOAP Envelope', the payload also contains the SOAP
Envelope. So it is obvious that the payload wont start with 'ns0' notation.
So I am searching for a solution, when we use that option.
Regards,
Subhendu

XSLT mapping with SOAP Envelope

Hi
I'm trying map SOAP response (with Envelope) to pick two values into the target. Here's the data:
Source (with data):
<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <soap:Body>
          <EnumerateResponse xmlns="http://www.approva.net/BizRights/Services">
               <EnumerateResult>
                    <TaskID>-1</TaskID>
                    <Result>FinishedSuccessfully</Result>
                    <StatusInfo/>
               </EnumerateResult>
               <pageObject>
                    <startIndex>0</startIndex>
                    <pageSize>10</pageSize>
                    <totalRows>1</totalRows>
                    <moreRecords>false</moreRecords>
                    <rowsReturned>1</rowsReturned>
               </pageObject>
               <xmlObjects>(large string of valid data in here)</xmlObjects>
          </EnumerateResponse>
     </soap:Body>
</soap:Envelope>
Target:
Only need Result and xmlObjects into target.
Mapping:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <xsl:template match="/">
          <poll_status_resp_r3>
               <Result>
                    <xsl:value-of select="EnumerateResponse/Result"/>
               </Result>
               <xmlObjects>
                    <xsl:value-of select="EnumerateResponse/xmlObjects"/>
               </xmlObjects>
          </poll_status_resp_r3>
     </xsl:template>
</xsl:stylesheet>
The values are not getting picked-up into the target.
What am I missing here?
Any help is appreciated.

Hi,
Save the following XSL file as RSpace.xsl
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" indent="no"/>
<xsl:template match="/|comment()|processing-instruction()">
    <xsl:copy>
      <xsl:apply-templates/>
    </xsl:copy>
</xsl:template>
<xsl:template match="*">
    <xsl:element name="{local-name()}">
      <xsl:apply-templates select="@*|node()"/>
    </xsl:element>
</xsl:template>
<xsl:template match="@*">
    <xsl:attribute name="{local-name()}">
      <xsl:value-of select="."/>
    </xsl:attribute>
</xsl:template>
</xsl:stylesheet>
Zip it and import it under Imported Archive.
In the interface mapping click "+" to add one more mapping.
Use this XSL as first mapping and your XSL mapping as the second mapping.
In your XSLT mapping you can use the XPath as
"Envelope/Body/EnumerateResponse/Result".
I mean remove the namespace and use the XPATH.
Thanks,
Prakash

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

SOAP receiver adapter - payload inside the soap envelop

Hi,
We have to send a SOAP message to 3rd party from PI 7.1. Using SOAP receiver adapter - we are trying to achieve this. 3rd party software is unable to accept payload as an attachment of the main envelop - they want it enside the main envelop.
I tried with "Keep attachment" option - but PI still keping the payload as an attachment. I think this option is for handling "extra" attachment.
Is there any way we can keep the payload inside the envelop?
In run-time WB, at the moment envelop looks like
<SOAP:Envelope xmlns:SOAP="http://schemas....
<SOAP:Body>
<sap:Payload xlink:type="simple" xlink:href="cid:payload-d6518670ca1311debbd9ca347000800b...">
</SOAP:Body>
</SOAP:Envelope>
And the payload d6518670ca1311debbd9ca347000800b... ( again viewed from RWB) - contains the data.
<?xml version="1.0" encoding="UTF-8" ?>
<ns2:Order> ....
</ns2:Order>
Can we insert this payload directly inside the SOAP:Envelope body instead of a link there?
Regards,
Sudhin

Hi!
It seems to me that this 3rd party is expecting only XML not SOAP.
If this is the case, you should use the HTTP Receiver adapter instead of SOAP.
Some systems 'say' they can speak SOAP but they can only speak XML. Not to blame, it's a mistake many make these days.
The only way you use SOAP Receiver adapter with this 3rd party, is that if someone from the 3rd party hands you a WSDL file.
Ricardo Sancio Lóra
Brazil

No SOAP Envelope error in SOAP Receiver Adapter

Hello Friends,
Informaiton:-
I have configured one Synchronous scenarion for SAP R/3 to PI 7.1 to Java based web applicaiton.
On the Receiver/Outbound side, i have configured the SOAP Receiver Adapter with the Target URL and SOAP Action.
Outbound and Inbound service interfaces have Request/Response and Fault messages.
Issue:-
While sending the Message, Below error is noticed in ABAP stack SXMB_MONI during the Call Adapter Stage and also in RWB (Channel Monitoring) .
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 {}RESPONSES; HTTP 200 OK
I also found that Request message is not reaching to the Java Web server.
I am taking the Same message Payload (found at Call Adapter Stage) and ussing it in XML Altova SPY Web client tool. There it is running scuccessfully and getting the Response message.
please suggest.
Thanks & Regards
Jagesh

Hi,
Yesterday i consumed the same WSDL file in Altova XML SPY and there it is working, getting the Response.
Now comparing the SOAP Request message reaching to the Third party Web server (which fall within the same Lane network)
from SAP PI and Altova XML SPY tool. I used TCP Gateway for the below scenarios.
(1)First i sent the SOAP message from PI and observed the RESPONSE message without the SOAP Envelope in TCP Gatway Trace and hence i am getting the No SOAP Envelope Error in PI.
(2)I consumed the same WSDLfile in Altova XML SPY and sent the SOAP message, here i got the Proper SOAP Response message and hence success in this case. (Used the same Data Payload as used in point 1)
(3)Now to identify the issue in the SOAP Request message being sent from PI, i used the same SOAP message sent in step 1 here, that means copy the entire SOAP ENvelope from the TCP gateway Trace and pasted it in Alota Spy and sent, there it is found running (got the response message from Third Party server).
One difference i found in HTTP Protocol statements in SOAP Request message in Point no 1 and Point no 2 above.
HTTP Protocols in Point 1 (Through PI).
POST HTTP/1.0
Accept: /
Host: 172.24.138.142:4544
User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
CallingType: SA
content-id: <soap-00306EEAC2051ED1839136CEE8564900 sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 1195
SOAPACTION: "Action1"
HTTP Protocols in Point 2 (Through Altova).
POST / HTTP/1.1
Content-Type: text/xml
User-Agent: XML Spy
SOAPAction: "Action1"
Host: 172.24.138.142:4544
Content-Length: 1195
Connection: Keep-Alive
Cache-Control: no-cache
Thanks to Mr. Stefan Grube for writting such a nice blog.
Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway
Experts, please suggest me further.
Thansk & Regards
Jagesh

SOAP Envelope - HTTP_EXCEPTION - HTTP 500 Internal Server Error

Pessoal, o cliente em que estou utiliza uma solução para NFe que não é o GRC.
Para tentar solucionar o problema do SOAP 1.2 e do message header, estou tentando criar o SOAP Envelope utilizando um XSLT, e no Communication Channel eu estou flegando Do not use soap envelope e colocando os modules para os charset, assim como na nota da SAP.
O que está ocorrendo é que estou tendo o seguinte erro:
com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Conversei com um rapaz na SEFAZ e ele diz que não está chegando nada pra ele.
O SOAP Envelope que estou mandando é:
está dentro de tags CDATA.
Alguém saberia o que está ocorrendo?
Muito obrigao,
Leandro Rocha

Olá Henrique, muito obrigado pela rápida resposta.
O erro que dá no audit log é:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error. Setting message to status failed.
A mensagem que aparece no adapter é a padrão do SOAP Document:
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:wsse="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
- <SAP:Main versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
<SAP:TimeSent>2010-11-04T13:36:35Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="" scheme="" />
<SAP:Service>NFe_recepcao</SAP:Service>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SEFAZ_RS</SAP:Service>
</SAP:Receiver>
<SAP:Interface namespace="http://www.gerdau.com.br/nfe">NFe_recepcao_inbound_sync</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Diagnostic SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:HopList SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2010-11-04T13:36:39Z" wasRead="false">
<SAP:Engine type="PE" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">PE</SAP:Adapter>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2010-11-04T13:36:39Z" wasRead="false">
<SAP:Engine type="IS">is.00.ebsgerd26</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2010-11-04T13:36:41Z" wasRead="false">
<SAP:Engine type="AE">af.p7d.ebsgerd26</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
</SAP:Hop>
</SAP:HopList>
</SOAP:Header>
- <SOAP:Body>
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:payload-DFE818873F6A21F1B9330050568169B4">
<sap:Name>MainDocument</sap:Name>
<sap:Description />
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Mais uma vez, muito obrigado,
Leandro

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.

SOAP Envelope encodingStyle

Similar Messages

Maybe you are looking for