SOAP version

Hai Gurus,
Could I know which version of the SOAP is compatible with SAP.  I am able to run Google example. But I am unable to run my own WSDL file in Net Weaver Studio.
Do Net WEaver studio Supports WSDL 2.1 version. I am not able to acces all the objects in the WSDL file(complex objects). Right now I am using  EP6 SP6 sneak preview and NetWEaver Studio Version: 2.0.7.
I am able to access context But not the content.
{{0}#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : myProject.myTest
Component class : com.factiva.myTest
User : bandi
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:627)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:337)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:315)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:815)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:151)
Caused by: java.lang.NullPointerException
at com.factiva.myTest.doContent(myTest.java:23)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
thanks in advance
venkata

hey fedric
public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
          response.write("hello<br>");
          DateFormat dateFormat = new DateFormat("MMDDCCYY");
          SearchSortOrder sortOrder = new SearchSortOrder("Relevance");
          SearchContentCategory searchContentCategory = new SearchContentCategory("Publications");
          IServiceName factivaSearch = (IServiceName) PortalRuntime.getRuntimeResources().getService("myAlias");
          PerformContentSearch performContentSearch = new PerformContentSearch(10,"bush", "UID=quilogydk&PWD=factivadk&NS=65",dateFormat, searchContentCategory, sortOrder);
          PerformContentSearchResponse     csr = factivaSearch.PerformContentSearch(performContentSearch);
          //ContentHeadline[] ch =              csr.getContentSearchResult().getContentHeadline();
response.write(csr.getContentSearchResponse().getContentSearchResult().getSearchContext()"searchContent" "<br>");
response.write(Integer.toString(csr.getContentSearchResponse().getContentSearchResult().getQueryHitCount())+ "queryHitcount"+"<br>");
response.write(csr.getContentSearchResponse().getContentSearchResult().getContentHeadlinesResultSet().getContentHeadlinesResultSet().toString()"HeadLineResultSet" "<br>");
See the reference in WSDL file
<xsd:element name="contentSearchResult" type="ContentSearchResult" />
- <xsd:complexType name="ContentSearchResult">
- <xsd:all>
  <xsd:element ref="queryHitCount" />
  <xsd:element ref="indexOfFirstHeadline" />
  <xsd:element ref="highlightString" />
  <xsd:element ref="searchContext" />
  <xsd:element ref="contentHeadlinesResultSet" />
  </xsd:all>
  </xsd:complexType>
  <xsd:element name="contentHeadlinesResultSet" type="ContentHeadlinesResultSet" />
- <xsd:complexType name="ContentHeadlinesResultSet">
- <xsd:sequence>
  <xsd:element ref="contentHeadline" minOccurs="0" maxOccurs="unbounded" />
  </xsd:sequence>
  <xsd:attribute name="count" type="xsd:int" use="required" />
  </xsd:complexType>
  <xsd:element name="contentHeadline" type="ContentHeadline" />
- <xsd:complexType name="ContentHeadline">
- <xsd:all>
  <xsd:element ref="accessionNo" />
  <xsd:element ref="baseLanguage" />
  <xsd:element ref="byline" minOccurs="0" />
  <xsd:element ref="credit" minOccurs="0" />
  <xsd:element ref="columnName" minOccurs="0" />
  <xsd:element ref="copyright" minOccurs="0" />
  <xsd:element ref="contentParts" minOccurs="0" />
  <xsd:element ref="headline" />
  <xsd:element ref="ipDocumentID" />
  <xsd:element ref="publicationDate" />
  <xsd:element ref="publicationTime" minOccurs="0" />
  <xsd:element ref="sectionName" minOccurs="0" />
  <xsd:element ref="snippet" minOccurs="0" />
  <xsd:element ref="sourceCode" />
  <xsd:element ref="sourceName" />
  <xsd:element ref="truncationRules" minOccurs="0" />
  <xsd:element ref="wordCount" />
  </xsd:all>
  </xsd:complexType>
I am able to access till contentHeadLineResultSet, but I am not able to access content Headline.
What do u mean by description of that objects

Similar Messages

  • Error Calling Web Service - VersionMismatch Wrong SOAP Version

    Hello,
    I am attempting to create a web service from a function module, and to call this web service from outside of SAP.
    I used the Web Service Creation Wizard to create a web service from BAPI_CURRENCY_GETLIST, and tested it using the Web Service Homepage button from transaction WSADMIN. Everything seems to work OK so far.
    To test calling the web service, I copied the SOAP envelope from the web service homepage into a vbscript file:
    Const HOST = "http://<server>.<domain>:<port>"
    Const URL = "/sap/bc/srt/rfc/sap/ZWSD_Currency?sap-client=<nnn>"
    ' Create the HTTP object
    Set xmlhttp = CreateObject("Microsoft.XMLHTTP")
    Dim Request
    Request = "<?xml version=""1.0"" encoding=""UTF-8"" ?>" & _
              "<SOAP-ENV:Envelope xmlns:SOAP-ENV=""http://schemas.xmlsoap.org/soap/envelope"" xmlns:xsi=""http://www.w3.org/2001/XMLSchema"" xmlns:xs=""http://www.w3.org/2001/XMLSchema-instance"">" & _
              "<SOAP-ENV:Header>" & _
              "<sapsess:Session xmlns:sapsess=""http://www.sap.com/webas/630/soap/features/session/"">" & _
              "<enableSession>true</enableSession>" & _
              "</sapsess:Session>" & _
              "</SOAP-ENV:Header>" & _
              "<SOAP-ENV:Body>" & _
              "<ns1:CurrencyGetlist xmnls:ns1='urn:sap-com:document:sap:soap:functions:mc-style'>" & _
              "<CurrencyList><item>" & _
              "<CURRENCY></CURRENCY>" & _
              "<CURRENCY_ISO></CURRENCY_ISO>" & _
              "<ALT_CURR></ALT_CURR>" & _
              "<VALID_TO></VALID_TO>" & _
              "<LONG_TEXT></LONG_TEXT>" & _
              "</item></CurrencyList>" & _
              "</ns1:CurrencyGetlist>" & _
              "</SOAP-ENV:Body>" & _
              "</SOAP-ENV:Envelope>"
    xmlhttp.open "POST", HOST & URL, False
    xmlhttp.send (request)
    MsgBox (xmlhttp.responseXML.xml)
    When I execute the vbscript, the response is
    <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelop/">
    <soap-env:Body>
      <soap-env:Fault>
        <faultcode>
          soap-env:VersionMismatch
        </faultcode>
        <faultstring xml:lang="en">
          Wrong SOAP Version
        </faultstring>
      </soap-env:Fault>
    </soap-env:Body>
    </soap-env:Envelope>
    The system log (transaction SM21) contains the messages:
    SOAP Runtime: SOAP Fault exception occurred in program CL_SOAP_MESSAGE===============CP in include CL_SOAP_ME SSAGE===============CM00X at position 34
    SOAP Runtime: Exception message: Severe processing error; SOAP fault handling required
    In the RFC trace (transaction SM59) I see
    XRFC> INFO 14:25:10: SOAP Transport Binding CL_SOAP_TRANSPORT_BINDING     <
    XRFC> ROOT->IFSOAP_TRANSPORT_BINDING~RESPONSE() Try to create response  <
    XRFC> message                                                             <
    XRFC>                                                                     <
    XRFC> INFO 14:25:10: SOAP Transport Binding CL_SOAP_TRANSPORT_BINDING     <
    XRFC> ROOT->IFSOAP_TRANSPORT_BINDING~RESPONSE() Response message        <
    XRFC> created                                                             <
    XRFC>                                                                     <
    XRFC> INFO 14:25:10: SOAP Transport binding CL_SOAP_HTTP_TPBND_ROOT       <
    XRFC> ->IF_SOAP_TRANSPORT_BINDING~RECEIVE() Try to receive message        <
    XRFC>                                                                     <
    XRFC> 20071218 142510 00037640: SOAP Fault Exception caught: : Wrong      <
    XRFC> SOAP Version                                                        <
    XRFC>                                                                     <
    XRFC>                                                                     
    XRFC> End of user trace                                                   
    How can I tell what version(s) of SOAP the NetWeaver 2004 platform supports? Has anyone seen and resolved this error?
    Thanks in advance,
    Mark

    Hi Anton,
    Thanks for the helpful suggestion. I did try setting SOAPAction using xmlhttp.setRequestHeader, but that didn't seem to make any difference. I may not have formatted the SOAP header correctly, however.
    What I noticed is that if I added a slash at the end of the xmlns:soap tag in the SOAP envelope, I got a different error message (SOAP Processing failure, error id = 112).
    I downloaded version 2.0 of the .NET framework and the SOAPSonar tool. SOAPSonar was able to format the SOAP envelope from the WSDL. When I pasted the SOAP envelope from SOAPSonar into my vbscript file, it worked. So, the vbscript looks like this:
    Const HOST = "http://nwr051.nwenergy:1080"
    Const URL = "/sap/bc/srt/rfc/sap/ZWSD_Currency?sap-client=100"
    Const FORMAT = "dd-MMM-yy"
    ' Create the HTTP object
    Set xmlhttp = CreateObject("Microsoft.XMLHTTP")
    Dim Request
    Request = "<?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"" xmlns:tns=""urn:sap-com:document:sap:soap:functions:mc-style"">" & _
              " <soap:Body>" & _
              "    <tns:CurrencyGetlist>" & _
              "      <CurrencyList>" & _
              "      </CurrencyList>" & _
              "    </tns:CurrencyGetlist>" & _
              "  </soap:Body>" & _
              "</soap:Envelope>"
    xmlhttp.open "POST", HOST & URL, False
    xmlhttp.send (request)
    MsgBox (xmlhttp.responseXML.xml)
    Again, thanks for taking the time to read through this and offer your insight.
    Regards,
    Mark

  • SOAP version for B2B HTTP inbound message in SOA Suite 11.1.1.7

    Is there a way to find out the SOAP version supported by B2B HTTP inbound message in SOA Suite 11.1.1.7? Has there been a upgrade of SOAP version to SOAP 1.2?
    The reason behind this assumption is because we are facing following error when an external service posts an XML message enclosed in SOAP envelope (SOAP 1.1) to B2B Sync Receiver Servlet:
    Mime Header Content-Type: text/xml requires SOAP envelope namespace
    Since SOAP headers are already added in the message we are not expecing to face such issue. As per my understanding this issue maybe seen when there is a SOAP version mismatch.
    Moreover, this issue is not seen when this external service posts the same SOAP message to B2B Sync Receiver of SOA suite 11.1.1.6.
    Any help would be highly appreciated.
    Thanks,

    I resolved the issue by myself, The connection factory which I was referring was duplicated. Hence messages were not dequeueing.
    I would be able to found the issues by creating a similar test case scenario.
    Cheers,
    B

  • Determinations Server - SOAP version

    I have generated a java client from my WSDL file (http://localhost:9000/determinations-server9000/interview/soap/MyRuleBase?wsdl) using JAX-WS wsimport.
    However when I attempted to use the Java client, I get the following run time exception.
    SEVERE: SAAJ0140: No NamespaceURI, SOAP requires faultcode content to be a QName
    javax.xml.ws.WebServiceException: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: No NamespaceURI, SOAP requires faultcode content to be a QName
    After a bit of googling, I found that the my JAX-WS client is using SOAP1.2 whereas the Determinations server is using SOAP 1.1?
    How do I force my JAX-WS client to use SOAP 1.1?
    I understand that I can generate a client using Axis2 as well- but my preference would be to use JAX-WS.

    Actually I don't think this has anything to do with the soap version that jax-ws uses.
    In some 10.2 versions of the Determination Server a fault was being incorrectly returned as "SOAP-ENVClient" instead of "SOAP-ENV:Client". This is probably causing the error you are seeing.
    This bug was fixed in 10.3 which has just been released as General Availability and you can get it from Oracle E-Delivery (https://edelivery.oracle.com/)
    Also, the fact that you are getting a soap fault means that you are sending wrong information to the determinations server. I suggest using a tool like tcpmon to trap the request and response so you can see what the error is.

  • How to change the SOAP version from 1.0 to 1.2 while registering to ESB

    Hi All,
    I have problem here,
    Is there any possibility to change the soap version from 1.0 to 1.2 for oracle ESB.
    Because it is using SOAP1.1 while registering any service to ESB, Is there any possiblity to change it.
    Hi guys is there any solution for this...........:-(
    OR Will SOA suite 10.1.3.4 supports SOAP 1.2 ?
    Cheers,
    Kalyan.P

    Hi,
    The current version of ESB does not support SOAP 1.2. You need to make sure your message contains the correct SOAP 1.1 namespace so ESB uses the correct SOAP version:
    SOAP 1.1: http://schemas.xmlsoap.org/soap/envelope/
    SOAP 1.2: http://www.w3.org/2003/05/soap-envelope
    For SOAP 1.2 you have to wait until 11g SOA Suite is released.
    Kind Regards,
    Andre Jochems

  • SOAP Version Mismatch

    Hi,
    I too facing the issue with web services.
    Previously, My web servieces are deployed in 32bit server now its moved to 64bit server.
    Any further details you are looking for, let me know.
    Thanks,
    Krishna
    Error: SOAP Response Version Mismatch
    at mx.rpc.soap::SOAPDecoder/decodeEnvelope()[C:\autobuild\3.3.0\frameworks\project s\rpc\src\mx\rpc\soap\SOAPDecoder.as:266]
    at mx.rpc.soap::SOAPDecoder/decodeResponse()[C:\autobuild\3.3.0\frameworks\project s\rpc\src\mx\rpc\soap\SOAPDecoder.as:236]
    at mx.rpc::AsyncResponder/result()[C:\autobuild\3.4.0\frameworks\projects\rpc\src\mx\rpc\Asy ncResponder.as:80]
    at mx.rpc::AsyncRequest/acknowledge()[C:\autobuild\3.4.0\frameworks\projects\rpc\src\mx\rpc\ AsyncRequest.as:74]
    at DirectHTTPMessageResponder/completeHandler()[C:\autobuild\3.4.0\frameworks\projects\rpc\s rc\mx\messaging\channels\DirectHTTPChannel.as:409]
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at flash.net::URLLoader/onComplete()

    I got answered myself, there was a mismatch in the web
    service URL.
    Where i managed to change the same.
    Now its working fine.
    Thanks

  • Which Soap version does Flex support

    Hello,
    I have a flex application trying to talk (via web service) to
    a gSoap server.
    If I send this:
    <SOAP-ENV:Envelope 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">
    <SOAP-ENV:Body>
    <hpvcm:userLogIn xmlns:hpvcm="
    http://hp.com/iss/net/vcm/resourceModel">
    <hpvcm:username>Administrator</hpvcm:username>
    <hpvcm:password>Administrator</hpvcm:password>
    <hpvcm:breakLockedSession>false</hpvcm:breakLockedSession>
    </hpvcm:userLogIn>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    I get a Soap fault version mismatch.
    I have an apache client that sends almost the exact same
    thing, this:
    <soap:Envelope xmlns:soap="
    http://www.w3.org/2003/05/soap-envelope">
    <soap:Body>
    <ns1:userLogIn xmlns:ns1="
    http://hp.com/iss/net/vcm/resourceModel"
    xmlns:ns2="
    http://hp.com/iss/net/vcm/resourceDomain"
    xmlns:ns3="
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <ns1:username>Administrator</ns1:username>
    <ns1:password>Administrator</ns1:password>
    <ns1:breakLockedSession>false</ns1:breakLockedSession>
    </ns1:userLogIn>
    </soap:Body>
    </soap:Envelope>
    and I get a valid response this:
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="
    http://www.w3.org/2003/05/soap-envelope"
    xmlns:SOAP-ENC="
    http://www.w3.org/2003/05/soap-encoding"
    xmlns:xsi="
    http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="
    http://www.w3.org/2001/XMLSchema"
    xmlns:c14n="
    http://www.w3.org/2001/10/xml-exc-c14n#"
    xmlns:wsu="
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
    xmlns:ds="
    http://www.w3.org/2000/09/xmldsig#"
    xmlns:wsse="
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
    xmlns:hpvcm="
    http://hp.com/iss/net/vcm/resourceModel"
    xmlns:hpoa="hpoa.xsd" xmlns:hpvcd="
    http://hp.com/iss/net/vcm/resourceDomain">
    <SOAP-ENV:Body><hpvcm:userLogInResponse>
    <hpvcm:HpVcmSessionKeyToken>
    <hpvcm:vcmSessionKey>PCmB3HCKsiSkE9zIRytsaiTx</hpvcm:vcmSessionKey>
    </hpvcm:HpVcmSessionKeyToken></hpvcm:userLogInResponse>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    From what I can tell the only difference is this portion:
    <soap:Envelope xmlns:soap="
    http://schemas.xmlsoap.org/soap/envelope/">
    BAD BAD BAD
    <soap:Envelope xmlns:soap="
    http://www.w3.org/2003/05/soap-envelope">
    GOOD GOOD
    The first is SOAP 1.1 the second 1.2
    My WSDL specifies 1.2. But I cannot get Flex to send 1.2.
    How can I tweak this?

    Did you get this figured out because I think I'm having the same problem?  I looked at your two requests and see that the soap envelope values are not the same, which is what is going on with me; that triggers the runtime soap mismatch error.  Is something happening when it runs through a soap proxy (soap server)?

  • SOAP Version supported by J2EE Engine 7.0

    Hi,
    Can somebody please tell me that which verison of SOAP is supported by J2EE Engine 7.0 (Netweaver2004s)?
    Thanks in advance,
    Manish

    Hi Manish,
    Have you checked the other link, that I have supplied, check it up, the page says that:
    "If you have any problems with the SOAP Processor within the SAP Web AS, our customer support can help you. Please create a problem message on the SAP Service Marketplace under the component BC-MID-SRT (SOAP Run Time). "
    So you might want to parallelly post your query over there too, cause i don't see any other note describing the version.
    Regards,
    Siddhesh

  • SOAP VERSION Issues

    Hi,
    We are using Coldfison 8/IIS 6.0/Windows 2003 server. We are
    invoking a third party web services which are hosted in Internet.
    When we invoke the web service, Coldfusion is using SOAP1.1
    and the generated SOAp is in version 1.1
    But the web service is expecting the request in SOAP 1.2
    format. Hence getting a Server exception from AXIS server
    We narrowed down the problem to the below:
    The generated SOAP request has the following security tag in
    SOAP header
    <wsse:Security soapenv:actor="" soapenv:mustUnderstand="1"
    xmlns:wsse="
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    soapenv:actor="" attribute is from SOAP1.1, SOAP1.2 do not
    support it anymore. SOAP1.2 uses role attribute instead
    Can some body help me configuring Coldfusion to use SOAP 1.2
    by default

    Hi,
    We are using Coldfison 8/IIS 6.0/Windows 2003 server. We are
    invoking a third party web services which are hosted in Internet.
    When we invoke the web service, Coldfusion is using SOAP1.1
    and the generated SOAp is in version 1.1
    But the web service is expecting the request in SOAP 1.2
    format. Hence getting a Server exception from AXIS server
    We narrowed down the problem to the below:
    The generated SOAP request has the following security tag in
    SOAP header
    <wsse:Security soapenv:actor="" soapenv:mustUnderstand="1"
    xmlns:wsse="
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    soapenv:actor="" attribute is from SOAP1.1, SOAP1.2 do not
    support it anymore. SOAP1.2 uses role attribute instead
    Can some body help me configuring Coldfusion to use SOAP 1.2
    by default

  • Soap Version supported by SAP J2EE Engine 7.0

    Hi,
    Cna somebody tell me that which version of SOAP is supported by SAP J2EE Engine 7.0?
    Thanks in advance,
    manish

    Hi Manish,
    Have you checked the other link, that I have supplied, check it up, the page says that:
    "If you have any problems with the SOAP Processor within the SAP Web AS, our customer support can help you. Please create a problem message on the SAP Service Marketplace under the component BC-MID-SRT (SOAP Run Time). "
    So you might want to parallelly post your query over there too, cause i don't see any other note describing the version.
    Regards,
    Siddhesh

  • Any issues using Apache's SOAP version 2 with Weblogic

    Hi,
    The Weblogic sever is not one in the list of servers that have been tried
    succesfully with Apache's SOAP. This is the list:
    Apache Tomcat v3.1
    IBM WebSphere v3.02
    JRun vx.y.z
    Microsoft Internet Information Server
    Has anyone tried SOAP with Weblogic?
    A recent thread mentions some problems (and solutions) with Weblogic and Xerces 1.1.2.
    SOAP requires Xerces 1.1.3. Therefore, I would also like to know if there is any issue
    using Weblogic with Xerces 1.1.3. I am using Weblogic 4.5 but I would try 5.1 if necessary
    for this.
    Thanks in advance,
    Javier

    In the apache soap binary download, there is a soap web application ( in the
    form of an exploded war file ). Just copy and paste this directory in the
    domain's "applications" directory. You will need to add a servlet-mapping
    element in the web.xml file, which could be something like this
    <servlet-mapping>
    <servlet-name>rpcrouter</servlet-name>
    <url-pattern>/rpcrouter/*</url-pattern>
    </servlet-mapping>
    Cheers
    Sandeep
    "Jan-Paul" <[email protected]> wrote in message
    news:[email protected]...
    Do you have something similar for the BEA Weblogic 6.0?
    "Sudhir Kolli" <[email protected]> wrote in message
    news:[email protected]...
    You might want to take look at this:
    David Jian <[email protected]> wrote in message
    news:[email protected]...
    Gavin:
    I did the same thing except for servlet register. soap is webapp to WLS,so
    I add:
    weblogic.httpd.webApp.soap=D:/foo/soap-2_0/webapps/soap
    to weblogic.properties. Because sopa20 has a web.xml file in
    /foo/soap-2_0/webapp/soap/web-inf, I can only edit it to registerrpcrouter
    and keep the default webapp as the same. Otherwise, how do you add thesoap
    to you myserver/public_html? Unfortunately, it does not recognize the
    URL
    when I click the Visit link on soap admin page.
    I edit my web.xml as
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
    "http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">
    <web-app>
    <servlet>
    <servlet-name>
    rpcrouter
    </servlet-name>
    <servlet-class>
    org.apache.soap.server.http.RPCRouterServlet
    </servlet-class>
    <init-param>
    <param-name>ServicesStore</param-name>
    <param-value>DeployedServices.ds</param-value>
    </init-param>
    </servlet>
    </web-app>
    Can you try this? How did you add your rpcrouter servlet to the defualt
    webapp?
    Thanks
    DJ
    "Gavin Hyde" <[email protected]> wrote in message
    news:[email protected]...
    After several painstaking hours I finally was able to get Apache Soap
    v2.0
    to work with weblogic. The version of weblogic I'm using is 4.51.
    You
    can
    get Apaceh soap from http://www.apache.org/soap. This version of Soap
    requires xerces v 1.2.1 which you can get from
    http://www.apache.org/xerces-j. To make it work with weblogic you
    have
    to
    first place the soap.jar file included with Apache soap and thexerces.jar
    file in both the classpath AND WEBLOGIC_CLASSPATH. Don't ask me why
    but
    I
    wasn't able to get it to work without it in both. Next you have to
    add
    the
    directory that your class files reside in to the classpath. Next you
    have
    to register the RCPRouter servlet in weblogic. The line to do thislooks
    like this:
    weblogic.httpd.register.rpcrouter=org.apache.soap.server.http.RPCRouterServl
    et
    where rpcrouter can be any name you want to use to call the routerservlet.
    That's all I had to do to set it up to view the stock quote example
    and
    the
    address book. The calculator is giving me a few other probems at the
    moment. Don't forget to deploy the different services but the command
    for
    that is given in the readme file for each example. For the router URL
    I
    used http://localhost:7001/rpcrouter which is that servlet you
    registered
    above.
    Gavin
    "Javier Deniz" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    The Weblogic sever is not one in the list of servers that have been
    tried
    succesfully with Apache's SOAP. This is the list:
    Apache Tomcat v3.1
    IBM WebSphere v3.02
    JRun vx.y.z
    Microsoft Internet Information Server
    Has anyone tried SOAP with Weblogic?
    A recent thread mentions some problems (and solutions) with Weblogic
    and
    Xerces 1.1.2.
    SOAP requires Xerces 1.1.3. Therefore, I would also like to know if
    there
    is any issue
    using Weblogic with Xerces 1.1.3. I am using Weblogic 4.5 but I
    would
    try
    5.1 if necessary
    for this.
    Thanks in advance,
    Javier

  • Unable to parse soap fault due to SOAP version

    The business logic deployed to my Weblogic server invokes a 3rd party web service. When the 3rd party web service throws a soap fault, the web service client fails to parse it:
    SOAPFaultException - FaultCode [[http://schemas.xmlsoap.org/soap/envelope/]env.Server <http://schemas.xmlsoap.org/soap/envelope/%5denv.Server> <http://schemas.xmlsoap.org/soap/envelope/%5denv.Server> ] FaultString [RMSX1000:An unrecoverable system error has occured. please contact RMS support at [email protected] Message > [0]. [ java.rmi.RemoteException: /app/bea103/user_projects/domains/novella/<unknown>:0: error: com.bea.xml.XmlException: java.lang.IllegalArgumentException nested exception is:
    com.bea.xml.XmlRuntimeException: /app/bea103/user_projects/domains/novella/<unknown>:0: error: com.bea.xml.XmlException: java.lang.IllegalArgumentException:/app/bea103/user_projects/domains/novella/<unknown>:0: error: com.bea.xml.XmlException: java.lang.IllegalArgumentException nested exception is:
    com.bea.xml.XmlRuntimeException: /app/bea103/user_projects/domains/novella/<unknown>:0: error: com.bea.xml.XmlException: java.lang.IllegalArgumentException ]] FaultActor [NO ACTOR] Detail [<detail>
    I used a network packet analyzer and found out that the soap fault structure is different as the 3rd party use the soap 1.1 implementation which has a different structure. My question is how do I generate the client stubs for a specific version (as currently they appear to be generated for Soap 1.2)? I reviewed the clientgen Ant task documentation and found no clue.
    I think I may try to use stub._setProperty(WLStub.CONVERSATION_VERSION_PROPERTY, WLStub.CONVERSATION_VERSION_ONE) or some of its properties and see it that works - documentation is unclear.
    Edited by: user8651233 on Oct 15, 2009 1:02 PM

    I used a network packet analyzer and found out that the soap fault structure is different as the 3rd party use the soap 1.1 implementation which has a different structureAre you using soap 1.1 when you invoke the service?

  • SOAP Versions Support

    Hi Experts,
    PI 7.0 supports SOAP1.1 and AXIS Soap adapter supports SOAP1.2. Is it correct?
    Regards
    Sara

    Hi
    Axis supports both  Message protocols SOAP 1.1 and SOAP 1.2
    regards
    krishna

  • PI 7.11 Receiver SOAP (Axis) Adapter with MTOM (Attachments)

    Hello,
    Iu2019m trying to configure the Receiver SOAP (Axis) adapter for sending SOAP attachments via MTOM to a third-party webservice, but I'm not getting that PI transform the binary encode64 data in an payload element into a MTOM attachment (xop:include).
    The configuration looks like this:
    Transport Protocol: HTTP (Axis)
    SOAP Version: 1.2
    Encapsulation Format: MTOM
    Keep Attchments: enabled
    Payload Extraction: SOAP Body Child
    First of all, could you confirm if this is supported?
    Or Axis only supports MTOM for the transport protocol 'File (Axis)' like it seems refered in [Configuring the Receiver Axis SOAP Adapter|http://help.sap.com/saphelp_nwpi711/helpdata/en/45/a3c48c87cd0039e10000000a11466f/frameset.htm]
    Can you please provide me some guidance here?
    Thanks in advance!
    Kind Regards,
    Alexandre

    Hello,
    I am facing the exact same issue.
    I can't seem to set the cookie in the http header after following the guide.
    Cookie: WSL-credential=MyOwnCookie
    I managed to set the SOAPAction though.
    Anyone has any ideas?

  • SOAP receiver adapter for Axis

    Hi,
    I used SOAP receiver adapter for Axis  like below:
    Transport Prorocol : HTTP
    Message Protocol : Axis
    Url: http://<IP>:<Port>/xxx/WebService/services/Head/yyy
    Authentication : Basic
    User: <user>
    Password: <password>
    SOAP Version : 1.1
    SOAP Action: : <method>
    Encapsulation Format : MIME
    Payload Extraction : SOAP Body
    When i drive PI message it generates error below.
    What must i do to solve this problem?
    Thanks.
    Error message
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.adapter.axis.modules.AFAdapterBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@20715646 for bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: javax.ejb.CreateException: java.lang.NoClassDefFoundError: org/apache/axis/types/URI$MalformedURIException

    *Url:*  http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest
    When i use Url with *?wsdl* it generates below (it'is very long. I give part of it)
    wsdl
    <?xml version="1.0" encoding="UTF-8" ?>
    - <wsdl:definitions targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:intf="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:tns1="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" xmlns:tns2="http://schemas.hp.com/AssetManager/R51/ACMetaData" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    - <!--
    WSDL created by Apache Axis version: 1.2.1
    Built on Jun 14, 2005 (09:15:57 EDT)
      -->
    - <wsdl:types>
    - <schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:AdministrationTypes="http://schemas.hp.com/AssetManager/Custom/Head/Administration/Types" xmlns:CableTypes="http://schemas.hp.com/AssetManager/Custom/Head/Cable/Types" xmlns:CatalogTypes="http://schemas.hp.com/AssetManager/Custom/Head/Catalog/Types" xmlns:ChargebackTypes="http://schemas.hp.com/AssetManager/Custom/Head/Chargeback/Types"
      <import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" />
      <import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" />
    - <annotation>
      <documentation>Auto-generated schema for AssetCenter web services for Head/SapTest Implementation</documentation>
      </annotation>
      <import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SAM/Types" schemaLocation="../../schema/Head/SAM/SAMTypes.xsd" />
      <import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" ......
    <wsdl:operation name="retrieveAllBusinessAPIListByName">
      <wsdlsoap:operation soapAction="retrieveAllBusinessAPIListByName" />
    <wsdl:input name="retrieveAllBusinessAPIListByNameRequest">
      <wsdlsoap:body use="literal" />
      </wsdl:input>
    <wsdl:output name="retrieveAllBusinessAPIListByNameResponse">
      <wsdlsoap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    <wsdl:service name="SapTestService">
    <wsdl:port binding="impl:SapTestSoapBinding" name="SapTest">
      <wsdlsoap:address location="http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>

Maybe you are looking for