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,
<?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>
Am using the STOCK Quote for testing purposes and this is the error I am getting when testing my interface,
<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>
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 ,
HTTP server code 400 reason Bad Request explanation <h1>Bad Request (Invalid Header Name)</h1>
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

Similar Messages

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 scenario "Do not use SOAP Envelope" check problems

Hi Gurus!
I'm again here.
I've an scenario with SOAP Receiver, the WS do I need consume, looks like:
POST /SumTotalws1/services/Authentication.asmx HTTP/1.1
Host: xxx.xxx.xxx.xxx
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/Login"
<?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:Body>
 <Login xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/">
 <credentials>
 <Username>string</Username>
 <Passcode>string</Passcode>
 <AuthenticationType>NotSpecified or Anonymous or NTAuthentication or Passport or LDAP</AuthenticationType>
 <AccountType>NotSpecified or WebService or WebUI</AccountType>
 </credentials>
 </Login>
</soap:Body>
</soap:Envelope>
but the response looks like:
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?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>
 <UserToken xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/">
 <Value>string</Value>
 </UserToken>
</soap:Header>
<soap:Body>
 <LoginResponse xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/" />
</soap:Body>
</soap:Envelope>
when I create my communication channel with "Do not Use SOAP Envelope" uncheck it, all run ok, but I only get in response message "<LoginResponse>" and I need <UserToken>
When I check it "Do not use SOAP Envelope" and I use XSLT mapping to add SOAP Env to request message, I get response message empty.
I tried the web Service with the message that I obtained from de XSLT mapping in the program SOAPUI. I get ok response with the <UserToken> value.
some idea to solve this problem??
Thanks in advance.
Edited by: KrlosRios on Sep 30, 2011 8:07 PM

Hi, thanks for your answer.
Can I use AXIS to execute any WS?
The WS that I tried execute looks like this:
POST /xxxx/services/Authentication.asmx HTTP/1.1
Host: xxx.240.106.39
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://xxx/Authentication/Login"
<?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:Body>
 <Login xmlns="http://xxxxAuthentication/">
 <credentials>
 <Username>string</Username>
 <Passcode>string</Passcode>
 <AuthenticationType>NotSpecified or Anonymous or NTAuthentication or Passport or LDAP</AuthenticationType>
 <AccountType>NotSpecified or WebService or WebUI</AccountType>
 </credentials>
 </Login>
</soap:Body>
</soap:Envelope>
and for the response:
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?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>
 <UserToken xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/">
 <Value>string</Value>
 </UserToken>
</soap:Header>
<soap:Body>
 <LoginResponse xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/"></LoginResponse>
</soap:Body>
</soap:Envelope>
also I found in Trace node in SXI_MONITOR, jus before execute response mapping :
<Trace level="1" type="B" name="PLSRV_MAPPING_RESPONSE"></Trace>
<Trace level="1" type="Timestamp">2011-11-01T19:33:34Z UTC-6 Start of pipeline service processing PLSRVID= PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV"></Trace>
<Trace level="2" type="T">......attachment XI_Context not found </Trace>
<Trace level="3" type="T">Das Mapping wurde bereits in der Interface-Ermittlung bestimmt. </Trace>
<Trace level="3" type="T">Objekt-Id des Interface-Mappings 8594D8C2E6DA3C008F45B112FFCC86B8 </Trace>
<Trace level="3" type="T">Versions-Id des Interface-Mappings C3BB8FB0A1D511E0A688E9FCB9F06E16 </Trace>
<Trace level="1" type="T">Interface-Mapping http://xxxxx.net/pi/lms/Authentication OM_LMS_Authentication </Trace>
<Trace level="3" type="T">Mapping-Schritte 1 XSLT Response_LMS_Auth5 </Trace>
<Trace level="3" type="T">MTOM-Attachments werden nicht in die Payload überführt. </Trace>
<Trace level="1" type="T">Payload is empty. </Trace>
<Trace level="3" type="T">Dynamische Konfiguration ist leer. </Trace>
<Trace level="2" type="T">Modus 0 </Trace>
<Trace level="2" type="T">Call XSLT processor with stylsheet Response_LMS_Auth5.xsl. </Trace>
<Trace level="3" type="T">Method fatalError called, terminate transformation, because of
Thrown:
javax.xml.transform.TransformerException: java.io.IOException: Parsing an empty source. Root element expected!
 at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:250)
Say Payload is empty.
and in left directory tree, not exist "payload" node, only existe SOAP Body and in "Manifest" node looks like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Manifest wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" 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">
<SAP:Payload xlink:href="cid:att-60c3078b066911e1bc1500000093b25a @sap.com">
<SAP:Name>MainAttachment</SAP:Name><
SAP:Description>Main document</SAP:Description>
<SAP:Type>Application</SAP:Type></SAP:Payload>
</SAP:Manifest>
Thanks for your help.

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

SOAP Adapter: DO not use soap envelope

Hi Guys
I have a scenario, which calls a webservice from my ABAP Proxies, the twist in this is that SOAP request expects license info into the header of SOAP envelope, I could achive this by XSLT mapping in the receiver SOAP adapter I selected the option "Do not use SOAP envelope" and could do the call.
Due to this the response received from the webservice is treated as payload, as shown below...
response message payload:
<?xml version="1.0" encoding="utf-8"?>
<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">
<Header xmlns="http://schemas.xmlsoap.org/soap/envelope/">
 <SubscriptionInfo xmlns="http://ws.strikeiron.com">
 <LicenseStatusCode>0</LicenseStatusCode>
 <LicenseStatus>Valid license key</LicenseStatus>
 <LicenseActionCode>0</LicenseActionCode>
 <LicenseAction>Decremented hit count</LicenseAction>
 <RemainingHits>18</RemainingHits>
 <Amount>0</Amount>
 </SubscriptionInfo>
</Header>
<soap:Body>
 <getRateResponse xmlns="CurrencyRates">
 <getRateResult>44.945</getRateResult>
 </getRateResponse>
</soap:Body>
</soap:Envelope>
and when i am trying to do the response mapping, it is not able to read the value.
Anyone having any idea, on how we could do this.
Thanks
Dheeraj

Hi
I am sorry for replying in so late, was busy with some projects.
I got few mails and this post is cathing up again, so thought of giving the solution I followed without any adapter module or anything, simple plain XSLT mapping.
Integration Repository
1. Created data type and message type for Outbound Interface
2. Imported the WSDL
3. Created an XSD out of the sample response I got by calling the WSDL (this you can do from any tool available, i used the strikeiron website), pls refer below to see the XSD below, and you will have to use the message type envelope from it.
4. Most Important step, created 2 XSLT mappings, one for request and the other for response., Pls refer below for both these mappings.
5. did the interface mapping
Integration Directory
1. pls configure your scenario as normaly you do, and while you configure the communication channel for your soap receiver, make sure you click on the do not use soap envelop option.
thats it done.
XSLT Request Mapping
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 <xsl:template match="/">
 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP-ENV:Header>
 <LicenseInfo xmlns="http://ws.strikeiron.com">
 <RegisteredUser>
 <UserID>xyz</UserID>
 <Password>xyz</Password>
 </RegisteredUser>
 </LicenseInfo>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 <getConversion xmlns="CurrencyRates">
 <FromCurrencyCode>
 <xsl:value-of select="//fromCurrency"/>
 </FromCurrencyCode>
 <ToCurrencyCode>
 <xsl:value-of select="//ToCurrency"/>
 </ToCurrencyCode>
 <Amount>1</Amount>
 </getConversion>
 </SOAP-ENV:Body>
 </SOAP-ENV:Envelope>
 </xsl:template>
</xsl:stylesheet>
XSLT Response Mapping
<?xml version='1.0' ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:a="CurrencyRates" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <xsl:template match="/">
 <ns0:MT_Cur_res xmlns:ns0="http://www.april.in/WebService/SOAPHeader">
 <Rate>
 <xsl:value-of select="soap:Envelope/soap:Body/a:getConversionResponse/a:getConversionResult"/>
 </Rate>
 </ns0:MT_Cur_res>
 </xsl:template>
</xsl:stylesheet>
Webservice Response XSD
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://ws.strikeiron.com" xmlns:ns2="CurrencyRates">
<xs:import namespace="CurrencyRates" schemaLocation="ns2.xsd"/>
<xs:import namespace="http://ws.strikeiron.com" schemaLocation="ns1.xsd"/>
<xs:element name="Envelope">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="soap:Header"/>
 <xs:element ref="soap:Body"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
<xs:element name="Header">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="ns1:SubscriptionInfo"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
<xs:element name="Body">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="ns2:getConversionResponse"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
</xs:schema>
let me know in case somebody gets stuck somewhere for this scenario.
Take Care
Dheeraj

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.

Do Not Use SOAP Envelope doesn't show on SOAP Parameters

Hi!..
Somebody knows why the Do Not Use SOAP Envelope option on conversion Parameters for SOAP Adapter isn't there?...I have XI 3.0 SP19 and I'd seen on a lot of notes and how's to that there is a kind of option. I need the functionality that that check does but I can't find it.
I Only have Keep headers, Keep Attachments, Use Encoded headers and Use query string.
Thanks in advance..
Carlos.

HI Carlos,
I've got same problem, which metadata should I reimport?
cheers,
Edu

Do not use SOAP Envelope checkbox, MainDocument set as MainAttachment after call the receiver adapter

Hi experts,
We have a Proxy to SOAP scenario and we have the same issue mentioned in this post and in note 1522630, the version is SAP PI 7.31 (AEX). We configured 2 XSLT mappings and we use the MessageTransformBean (Transform.ContentType=text/xml;charset=utf-8) before call the standar module for SOAP receiver adapter.
Everything looks good but in the payload appears MainAttachment (in SAP PI and SXI_MONITOR in SAP ECC 6.0 SAP_BASIS 731) and the proxy can´t read the response for this reason.
This is that we see in the message content:
<sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink'><sap:Payload xlink:type='simple' xlink:href='cid:[email protected]'><sap:Name>MainAttachment</sap:Name><sap:Description>Main document</sap:Description><sap:Type>Application</sap:Type></sap:Payload></sap:Manifest>
Do you have any updates of this problem or any suggestion?
Thanks and regards.

Hi Sriram and Mark,
Thanks a lot for your help.
After a lot of test we solve the problem.
We are using an Integrated Configuration and the keepAttachment checkbox is not necesary.
The problem was that the value "ns0" in the message type of the xml was not added by the XSLT mapping(altova), we added manually in the xsl file and the proxy read the information.
The message content was not changed and looks like an attachment, also y sxi_monitor looks as MainAttachment in the payload but is interpreted good.

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

In the supportprofile my 5s is shown with do not use

Hi... In the Supportprofil my 5S is marked with do not use.
Can me somebody tell me why?
Thx

Since your contract is not up, you would only be eligible for Early Edge. However, a requirement of this early upgrade program is to return your current phone in good working order. That is not possible with your situation, so you will not be able to go to Edge early. Look at swappa for used phone at reasonable cost until your contract is over, if you can't borrow one from friends or family.

Import errors with numbers, not enough memory

Import errors with numbers, not enough memory

Hi heiko,
From your system profile line, it appears you should be asking this question in the iWork For iOS forum, not this one, which deals with Numbers for Mac OS X. I'd also suggest being a bit less cryptic in writing your question.
The link will take you to the iWork for iOS forum.
Regards,
Barry

Web Service Proxy error: "No operation found using soap keys"

I'm trying to use the new tools, and having a little trouble. Not many results when searching for this error message.
I have developed and deployed a new Java web service proxy using the outside-in approach according to the [help docs|http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/7f2fef88190ad3e10000000a11466f/frameset.htm] (PI 7.1 SP07, NWDS 7.1 CE SP09 PAT0000). Started with a Service interface in ESR, then generated a java bean skeleton into a new EJB project in NWDS, then wrote business logic and deployed.
When I test the web service (with 3 different SOAP test clients) I get the same error, below:
 <faultstring>com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException:
No operation found using soap keys [], [spmat_jdbc_receiver_proxy]. InterfaceMapping Object class:
com.sap.engine.services.webservices.espbase.mappings.InterfaceMapping mappings: {BindingQName=
{urn:nexeninc:pi:ll:spmat:100}SI_I_Sync_SPMAT_JDBC_Receiver_ProxyBinding, BindingType=Soap, PortTypeQName=
{urn:nexeninc:pi:ll:spmat:100}SI_I_Sync_SPMAT_JDBC_Receiver_Proxy, JAXWSInterface=true, InterfaceMappingID=-
27e4d529:127632b5c52:-7ebb}.</faultstring>
My service endpoint interface looks like this (unimportant lines removed):
package nexeninc.pi.ll.spmat._100;
@javax.jws.WebService(name = "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy", targetNamespace = "urn:nexeninc:pi:ll:spmat:100")
@javax.jws.soap.SOAPBinding(parameterStyle = javax.jws.soap.SOAPBinding.ParameterStyle.BARE, style = javax.jws.soap.SOAPBinding.Style.DOCUMENT, use = javax.jws.soap.SOAPBinding.Use.LITERAL)
public interface SIISyncSPMATJDBCReceiverProxy {
@javax.jws.WebMethod(operationName = "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy", action = "http://sap.com/xi/WebService/soap1.1")
@javax.jws.WebResult(name = "spmat_jdbc_receiver_proxy_response", targetNamespace = "", partName = "spmat_jdbc_receiver_proxy_response")
public generated.SpmatJdbcReceiverProxyResponse siISyncSPMATJDBCReceiverProxy(@javax.jws.WebParam(name = "spmat_jdbc_receiver_proxy", targetNamespace = "", partName = "spmat_jdbc_receiver_proxy") generated.SpmatJdbcReceiverProxy spmat_jdbc_receiver_proxy);

(continued from above post)
And my implementation bean looks like this (unimportant lines removed):
package nexeninc.pi.ll.spmat._100;
@SessionHandlingDT(enableSession = false)
@AuthenticationDT(authenticationLevel = AuthenticationEnumsAuthenticationLevel.BASIC)
@TransportGuaranteeDT(level = TransportGuaranteeEnumsLevel.NONE)
@WebService(serviceName = "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy_Service", portName
= "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy_Port", endpointInterface
= "nexeninc.pi.ll.spmat._100.SIISyncSPMATJDBCReceiverProxy", targetNamespace = "urn:nexeninc:pi:ll:spmat:100", wsdlLocation
= "META-
INF/wsdl/nexeninc/pi/ll/spmat/_100/SI_I_Sync_SPMAT_JDBC_Receiver_Proxy/SI_I_Sync_SPMAT_JDBC_Receiver_Proxy.wsdl")
@Stateless
public class SIISyncSPMATJDBCReceiverProxyImplBean {
 @RelMessagingNW05DTOperation(enableWSRM = false)
 public generated.SpmatJdbcReceiverProxyResponse siISyncSPMATJDBCReceiverProxy(
 generated.SpmatJdbcReceiverProxy spmat_jdbc_receiver_proxy) {
 System.out.println("Starting siISyncSPMATJDBCReceiverProxy.");
When we first created the new endpoint in NWA, we tried asigning a new name for both "Service Endpoint Name" and "In New Service", and we received this error.
We then deleted the endpoint and created another new one, setting "Service Endpoint Name" to match the portName in the implementation bean: "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy_Port", but that didn't work either. The only option we enabled in the endpoint was HTTP authentication: User ID/Password.
My ejb-j2ee-engine.xml and application-j2ee-engine.xml are both empty (but they exist).
I am new to EJBs and JAX-WS so hopefully it's something simple. All help appreciated!
Apologies for the long (and wide) post.
- Rob

Error while testing webservice using SOAP

Hi,
While i was testing my published webservice using soap-ui it gave me following error,
<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>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Internal SOAP Processing Failure</faultstring>
<detail/>
</soap:Fault>
</soap:Body>
</soap:Envelope>
and in the event log i can see a event as follows and there is no warning or error
Upon investigation i got to know the following steps might solve the problem..i.e..
- Is the receive location for the SOAP webservice enabled? - YES
- Can you browse to (the WSDL of) the webservice? Is displayed correctly? -YES
- Is the webservice configured to run in the correct application pool? -YES
-The user under which application pool is running have the read/write permission on the %temp% folder.-Dont Know how to check
-In IIS,Check the identity of the application pool on which Web service is running and make sure that the user is the member of both “IIS_WPG” and “BizTalk Isolated host users”.
-DONT Know how to check
Please Help me in guiding me in the last two points
and if there are any other solutions for this..
Thanks,
Sarva.

You mentioned you checked that the webservice is configured under correct application pool. you can find the user under which the application pool is configured (open iis- > select application pools -> find out the "Identity column" to
know the user for your application pool.
-The user under which application pool is running have the read/write permission on the %temp% folder.-Dont Know how to check
Go to run -> type "%temp%" -> Go one step back -> Right click to the folder -> Properties -> Security -> check the application pool user is present under "Group or user names"
-In IIS,Check the identity of the application pool on which Web service is running and make sure that the user is the member of both “IIS_WPG” and “BizTalk Isolated host users”.
-DONT Know how to check
Refer How to Add Service Account to the IIS_WPG Group to add your application pool user under IIS_WPG. Also similar activity to add your service account to "BizTalk Isolated
host users" if it is local groups. Or Ask your network support team if "BizTalk Isolated host users" is domain group.
Please Help me in guiding me in the last two points
and if there are any other solutions for this..
Thanks,
Sarva.
Your event viewer might have more information pointing exactly what is causing "Internal SOAP processing failure".
Also refer this
which might be helpful for you.
If this answers your question please mark it as Answer and if this post is helpful, please vote as helpful. Thanks !

Time Machine Error Prevention - Do Not Use "/" Symbols on the names on HD!

This is a warning message:
If your Time Machine Backup Fails with the Message:
"The Backup Was Not Performed Because an Error Occurred while Copying Files To the Backup Disk. The problem May be temporary. Try again later to back up.etc.."
*If you Use Symbols In Your Names DONT!*
*Do Not Use this / slash Symbol on the names of your Hard Drives*! Also check your logs to see if the TM backup is hanging on a file name with : or / symbol.
*Back Story*
I had purchased a new 3TB Western Digital HD and needed to do a full backup. I never had issues with Time Machine before. But After trying 2 times and received the error message I new something was wrong.
I did some research installed the Time Machine Widget and checked Console for the error codes.
I was searching on the forums here and just read a post from Pandini regarding the use of characters in file names. I was having an issue with an error code #2 every time. I reformatted with a GUID Partition (Intel Only) and verified and repaired the disks and permissions on everything was good on all my HD's.
After reading his short post about the characters possibly causing the issue I changed the naming on one of the external USB drives to be backed up.
I had it labeled as "Audio/Video/Docs 1TB."
I changed to: "Audio Video Docs 1TB" then tried the backup again it worked great.
It's amazing how a / slash can hang then entire system. I wish Apple would provide some informational notes about these very very simple subtle issues.
Thanks to Pandini for the post, it was the key clue. Save yourself some time and check your logs and hard drive naming to be sure there are no / Slashes.
Thanks to everyone on the forum for their contributions.

Problem solved. Issue resolved. Problem was due to the : or / symbol in the file or HD name.

Error with Do Not use SOAP envelope

Similar Messages

Maybe you are looking for