Problem calling a web service

I attempting to connect to a web service with code generated by xrpcc from a WSDL file. I am receiving this exception:
java.rmi.RemoteException: Runtime exception; nested exception is:
        unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/enco
ding/, actual=
        at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:227
)I am guessing that there is something wrong in my WSDL. Any ideas?

1) there is an "soap-enc" attribute in the "schema" tag within the "types" definition in the WSDL, looking for example like this:
<types>
- <schema targetNamespace="http://jacomac.de/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://jacomac.de/types" xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
- <complexType name="ArrayOfstring">
- <complexContent>
- <restriction base="soap-enc:Array">
<attribute ref="soap-enc:arrayType" wsdl:arrayType="string[]" />
</restriction>
</complexContent>
</complexType>
- <complexType name="ArrayOfArrayOfstring">
- <complexContent>
- <restriction base="soap-enc:Array">
<attribute ref="soap-enc:arrayType" wsdl:arrayType="tns:ArrayOfstring[]" />
</restriction>
</complexContent>
</complexType>
</schema>
</types>
2) but your fault could also come from the soap message format itsself. The "Envelope" has an attribute "encodingStyle". See below:
<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" soap-env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><soap-env:Body><m:getNumUsers xmlns:m="http://jacomac.de/wsdl"><String_1>rzbw0</String_1></m:getNumUsers></soap-env:Body></soap-env:Envelope>
I hope that helps..;-)

Similar Messages

  • Problem calling a web service via SOAP ad.

    Hi,
    I need to call a web service in an synchronous RFC to Web service scenario.The provider of service said me that they are going to accept production order with the service they provide. However, service semms to have only 2 request parameters one is a string enumeration ("online" or "offline") but the other has no type. In WSDL it is shown as the following -
    -<s:element minOccurs="0" maxOccurs="1" name="strFilenameOrXML">
    - <s:complexType mixed="true">
    - <s:sequence>
      <s:any />
      </s:sequence>
      </s:complexType>
      </s:element>
    When I try to test the web service with Altova XML Spy it gives me the error "Object reference not set to an instance of an object" .. at StokbarPlus.ProdService.WriteProdToSB(XmlNode strFilenameOrXML, IntegrationType EntegrasyonTip)..
    I guess the service is waiting for a xmlNode object...
    Is it possible to assign an XI message(coming from RFC) as an xmlNode object to an element of a webservice message and send it by using SOAP adapter?.
    I tried send the SOAP message by putting the whole xml(a sample order document) as a string constant in the strFilenameOrXML element and send but it did not work...
    How should I proceed?
    Thanks in advance for your help,
    -Tarik

    Hi,
    Problem is still unsolved.
    By the way I figured out that they are waiting the xml message inside strFilenameOrXML tag and tried to send it so. However it does not work. I have tried two different ways to send it.
    First one is by using messages in WSDL: did not work because special chars like <,> in the message that I am sending in the tag is escaped  .
    The Second way is using the data types that I developed, it did not work too since the receiver expects one of the inner node's namespace prefix to exist.
    I tried exporting the xsd of the message type, adding attributeFormDefault="qualified" to header, and reimporting it. It did not work, because it changes all nodes, but they want some specific node to be qualified.
    Any suggestions?

  • Problems calling external Web Service from a Java Stored Procedure

    I'm using a sample code that I found here about calling external web services from a Java Store Procedure ( Credit Agency Web Service http://www.oracle.com/technology/sample_code/tech/java/jsp/samples/wsclient/Readme.html ) but when I run it ,send this error. I dont know what can I do or what is missing. Please help me. Thanks.
    Error: Premature EOF encountered [java.io.EOFException] [SOAPException: faultCode=SOAP-ENV:IOException; msg=Premature EOF encountered; targetException=java.io.EOFException: Premature EOF encountered] at org.apache.soap.SOAPException.(SOAPException.java:77) at oracle.soap.transport.http.OracleSOAPHTTPConnection.send(OracleSOAPHTTPConnection.java:765) at org.apache.soap.rpc.Call.invoke(Call.java:261) at oracle.otnsamples.wsclient.CreditAgencyServiceStub.authorizeCustomer(CreditAgencyServiceStub.java:84) at Products.jspService(Products.jsp:120) at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:139) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:349) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:795) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:794) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192) at java.lang.Thread.run(Thread.java:534)

    I'm also facing problem in running the example on the page http://www.oracle.com/technology/sample_code/tech/java/jsp/samples/wsclient/Readme.html
    I've Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 and Oracle Application Server 10g (10.1.3). When I executed the following command,
    loadjava -thin -user sys/password@localhost:1521:oradb -resolve -synonym -verbose -grant public %OC4J_HOME%/webservices/lib/soap.jar %OC4J_HOME%/lib/dms.jar %OC4J_HOME%/jlib/javax-ssl-1_1.jar %ORACLE_HOME%/lib/servlet.jar %OC4J_HOME%/j2ee/home/lib/mail.jar
    ... mentioned in step 3 under the "Configuring the Application" section on the above link, the process terminates with the following error
    The following operations failed
    class oracle/net/www/protocol/https/Handler: resolution
    class oracle/net/www/protocol/https/HttpsURLConnection: resolution
    class oracle/soap/client/ProviderManagerClient: resolution
    class oracle/soap/client/ServiceManagerClient: resolution
    class oracle/soap/providers/JavaProvider: resolution
    class oracle/soap/providers/ejbprov/EntityEJBProvider: resolution
    class oracle/soap/providers/ejbprov/StatefulEJBProvider: resolution
    class oracle/soap/providers/ejbprov/StatelessEJBProvider: resolution
    class oracle/soap/providers/sp/SpProvider: resolution
    class oracle/soap/server/http/SOAPServlet: resolution
    class oracle/soap/transport/http/OracleSOAPHTTPConnection$1: resolution
    class oracle/soap/transport/http/OracleSOAPHTTPConnection: resolution
    class org/apache/soap/messaging/Message: resolution
    class org/apache/soap/rpc/Call: resolution
    class org/apache/soap/rpc/RPCMessage: resolution
    class org/apache/soap/rpc/Response: resolution
    class javax/net/DefaultServerSocketFactory: creation (createFailed)
    class javax/net/DefaultSocketFactory: creation (createFailed)
    class javax/net/ServerSocketFactory: creation (createFailed)
    class javax/net/SocketFactory: creation (createFailed)
    class javax/net/ssl/DefaultSSLServerSocketFactory: creation (createFailed)
    class javax/net/ssl/DefaultSSLSocketFactory: creation (createFailed)
    class javax/net/ssl/HandshakeCompletedEvent: creation (createFailed)
    class javax/net/ssl/HandshakeCompletedListener: creation (createFailed)
    class javax/net/ssl/SSLException: creation (createFailed)
    class javax/net/ssl/SSLHandshakeException: creation (createFailed)
    class javax/net/ssl/SSLKeyException: creation (createFailed)
    class javax/net/ssl/SSLPeerUnverifiedException: creation (createFailed)
    class javax/net/ssl/SSLProtocolException: creation (createFailed)
    class javax/net/ssl/SSLServerSocket: creation (createFailed)
    class javax/net/ssl/SSLServerSocketFactory: creation (createFailed)
    class javax/net/ssl/SSLSession: creation (createFailed)
    class javax/net/ssl/SSLSessionBindingEvent: creation (createFailed)
    class javax/net/ssl/SSLSessionBindingListener: creation (createFailed)
    class javax/net/ssl/SSLSessionContext: creation (createFailed)
    class javax/net/ssl/SSLSocket: creation (createFailed)
    class javax/net/ssl/SSLSocketFactory: creation (createFailed)
    class javax/security/cert/Certificate: creation (createFailed)
    class javax/security/cert/CertificateEncodingException: creation (createFailed)
    class javax/security/cert/CertificateException: creation (createFailed)
    class javax/security/cert/CertificateExpiredException: creation (createFailed)
    class javax/security/cert/CertificateNotYetValidException: creation (createFailed)
    class javax/security/cert/CertificateParsingException: creation (createFailed)
    class javax/security/cert/X509Certificate: creation (createFailed)
    exiting : Failures occurred during processing
    I've checked the path to all the jar files.
    I tried to run the command again with system/password instead sys/password but then I got the following stacktrace:
    The following operations failed
    class oracle/net/www/protocol/https/Handler: resolution
    class oracle/net/www/protocol/https/HttpsURLConnection: resolution
    class oracle/soap/client/ProviderManagerClient: resolution
    class oracle/soap/client/ServiceManagerClient: resolution
    class oracle/soap/providers/JavaProvider: resolution
    class oracle/soap/providers/ejbprov/EntityEJBProvider: resolution
    class oracle/soap/providers/ejbprov/StatefulEJBProvider: resolution
    class oracle/soap/providers/ejbprov/StatelessEJBProvider: resolution
    class oracle/soap/providers/sp/SpProvider: resolution
    class oracle/soap/server/http/SOAPServlet: resolution
    class oracle/soap/transport/http/OracleSOAPHTTPConnection$1: resolution
    class oracle/soap/transport/http/OracleSOAPHTTPConnection: resolution
    class org/apache/soap/messaging/Message: resolution
    class org/apache/soap/rpc/Call: resolution
    class org/apache/soap/rpc/RPCMessage: resolution
    class org/apache/soap/rpc/Response: resolution
    exiting : Failures occurred during processing
    Thanks in advance for any useful help.
    -

  • Problem calling a web Service from BI Publisher (10.1.3.2 )

    We have published a PL/SQL Web Service (from Jdeveloper 10.1.3 ) into a SOA Suite server.
    As requirements from BI Publisher , we chose Document/Literal, SOAP 1.1.
    The Program Unit accept an input parameter (we tried NUMBER & STRING)
    The result is an XML formatted (PL/SQL functions returns a CLOB then converted as a String).
    When testing the Service call from the SOA Suite console, no problems.
    We declined a page with APEX to test this Web Service too : Test is OK
    We added this web service as a data source in BI Publisher :
    After typing WSDL URL, Method, Parameter
    After testing , we do not get the XML result but an error message, coming from Apache AXIS (seems to be the DynamicInvoker) :
    not know how to convert '50740' into org.apache.axis.client.Call@cd7fdb
    Our demo is very near to this example : http://blogs.oracle.com/xmlpublisher/2006/11/01#a123
    and the one from the BI Publisher documentation

    I can't say I know the answer but I wanted to share a thought on debugging the issue. Like you I am seeing an axis error for a parameter on a web service I know works. I can call it using BPEL, SoapUI, etc... I suspect that perhaps BI pub is having trouble interpreting the WSDL for the web service. Specifically, I suspect that since I have imported schemas in the WSDL and nested imports in the supporting XSD files, the process is getting confused. The request message is fairly simple with three optional parameters but the WSDL does use an import via the WSDL. I wanted to share this since this problem often comes up with various tooling and I am lacking time to work out a test case to prove this theory out any time soon. I will try to post once I find some time to test this theory but it may be a while. Reading the results of someone else's test would be just as good!

  • Problems calling a web service

    I have a process where I send an html tagged note to a webservice (our own) for insert into a database.  The process works fine. I make the call and send an xml string with patient info, provider info, and the note contents.
    Now we are wanting to use this for another process that will send a html document and I'm trying to use the same process. Unfortunately, when I make the web service call, I get back an error: 
    FAILURE: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
    <title>404 - File or directory not found.</title>
    <style type="text/css">
    which I'm assuming is returned from IIS on the web service server.  I've tried working with the web service developer but he says the message is never making it to him to see.  I had someone check the server logs and IIS logs and they didn't find
    anything useful.
    If I replace the html note contents with just a simple string then it works. This tells me that it is in the note content.  I've tried encoding the note contents but that doesn't work either.
    Is there any way to figure out what the actual problem is here short of systematically removing html tags until it works?
    Thanks,
    Rut
    Mike Rutledge

    The web service call itself is an HTML document; when you put the content of another document inside you wind up with multiple document, header, and body sections.  My guess would be that this is what causes the problem.
    How about taking your HTML Document data and encoding it as a UTF8 byte array and then sending the hex of those bytes as the string data in the web method?  If not a byte array and hex string, at least perform some kind of encoding on the HTML so that
    it is no longer HTML while being passed through the web method.  The service on the receiving end can decode the data back into the HTML text to store the value as a string.
    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

  • I have a problem calling external web service

    Hi all bpel gurus,
    Please help me. I want to call a external web service which return "Hello" +parameter1.  My web service is ready. And i put it with my partnerlink. When i want to call it from bpel console, i wait for a long time and the bpel instance got time out.
    Can you help me how to solve this beginning issue problem?

    Hi again,
    Firstliy i create a very simple Web service which take a string parameter and return a "Hello" + paramaterName.
    Then i drag and drop that web service's wsdl file to .bpel file and i identified the partner role of partner link using
    this wsdl. My bpel process a basic simple synhronous bpel process. And i drap and drop an invoke activitiy. And i map
    this partner link to my invoke activity. two assign activity. One assign component is before invoke activity and the
    other is after invoke activity. Then i used first assign activity mapping input variable-->input_Invoke_Variable, i used
    second assign activity mapping output_Invoke_Variable-->outputVariable.
    After this, when i write any string into the parameter field of BPEL Console's instance, i wait for a long time, but i
    responds "timeout" problem and failed.
    I'm in trouble to call any external web service from BPEL. Please help me.
    I'm waiting and following your answers. Thanks a lot.

  • Calling a web service with two tables

    Hello all,
         I am having a problem calling a web service in VC which has data of the format order and orderitems.
    that is I have a record of information a recordset is part of that information. Please point to any blogs or any info available on SDN.
       I appreciate all your help
    Thank You
    Shekar

    Hi,
    Please check the below links.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/vc71/webServiceDestination.
    https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4679. [original link is broken] [original link is broken] [original link is broken]
    Govindu

  • DNS problem when calling a web service

    Hi,
    when I try to call a web service from the Studio I get the following error message:
    return code: 503
    Network Error
    Network Error (dns_server_failure)
    Your request could not be processed because an error occurred contacting the DNS server.
    The DNS server may be temporarily unavailable, or there could be a network problem.
    Looks not like an OBPM problem, but I can access the web service via SoapUI and I can access it from an OBPM enterprise installation on a server here in the network. The problem is only when I try to access the service from OBPM Studio. I also tried accessing a local web service, also does not work.
    Does anyone have a hint, what it could be? Thanks for your help!
    Regards
    Matthias

    No, it is in my local LAN, so it should work without proxy (and in SoapUI it also works without Proxy). But nevertheless I tried it also with a proxy, but unfortunately without success.
    Regards
    Matthias

  • Problem trying to call a web service.

    I have a CF page that needs to use user authentication from an ASP.NET machine, so I'm trying to call a web service to determine whether or not the user has been authenticated.
    I'm using this code:
    <cfinvoke
        webservice="https://my-domain.com/SessionQueryService?wsdl"
        method="UserLookupServiceService"
        returnvariable="authenticated"
        >
    Running this returns the following error:
    Unable to read WSDL from URL: https://my-domain.com/SessionQueryService?wsdl.
    Error: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated.
    I'm assuming this is a certiificate problem, since when I visit the ASP.NET machine via a browser, I get a certificate warning and have to add an exception.  Is my assumption correct, and is there a way around it?

    Now I have the sesssion ID I needed, and it's on to the next point of failure.
    Web service operation userLookupBySessionResponse with parameters {applicationName={xxxx},endUserIPAddress={xxxx},accessCode={xxxx},sessionId={xxxx}} cannot be found.
    I've Googled and Googled, with no luck.  If I browse my web service URL I get an Axis 1.4 XML file with several entries.  I'm assuming that the "wsdl:message name=" part is what I use for my <cfinvoke> method, but I could be wrong.  I assume that because there are "wsdl:part name="s that match my invokearguments.
    It seems like I'm doing everything right, yet still the message above.  I have no idea where to go from here.

  • Problem in calling a web service hosted on tomcat from BEA WebLogic portal

    Hi,
    I have a wsdl file for my web service which is hosted on apache tomcat 5.5(running on port : 8080). The contents of the wsdl file are-
    *<?xml version="1.0" encoding="UTF-8"?>*
    *<wsdl:definitions targetNamespace="http://soa.tutorials.serg.edu" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://soa.tutorials.serg.edu" xmlns:intf="http://soa.tutorials.serg.edu" 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.4*
    Built on Apr 22, 2006 (06:55:48 PDT)-->
    *<wsdl:types>*
    *<schema elementFormDefault="qualified" targetNamespace="http://soa.tutorials.serg.edu" xmlns="http://www.w3.org/2001/XMLSchema">*
    *<element name="getNums">*
    *<complexType>*
    *<sequence>*
    *<element name="n" type="xsd:int"/>*
    *<element name="m" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNumsResponse">*
    *<complexType>*
    *<sequence>*
    *<element maxOccurs="unbounded" name="getNumsReturn" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNums2">*
    *<complexType>*
    *<sequence>*
    *<element name="n" type="xsd:int"/>*
    *<element name="m" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNums2Response">*
    *<complexType>*
    *<sequence>*
    *<element maxOccurs="unbounded" name="getNums2Return" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *</schema>*
    *</wsdl:types>*
    *<wsdl:message name="getNums2Request">*
    *<wsdl:part element="impl:getNums2" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNumsRequest">*
    *<wsdl:part element="impl:getNums" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNums2Response">*
    *<wsdl:part element="impl:getNums2Response" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNumsResponse">*
    *<wsdl:part element="impl:getNumsResponse" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:portType name="Echo">*
    *<wsdl:operation name="getNums">*
    *<wsdl:input message="impl:getNumsRequest" name="getNumsRequest"/>*
    *<wsdl:output message="impl:getNumsResponse" name="getNumsResponse"/>*
    *</wsdl:operation>*
    *<wsdl:operation name="getNums2">*
    *<wsdl:input message="impl:getNums2Request" name="getNums2Request"/>*
    *<wsdl:output message="impl:getNums2Response" name="getNums2Response"/>*
    *</wsdl:operation>*
    *</wsdl:portType>*
    *<wsdl:binding name="EchoSoapBinding" type="impl:Echo">*
    *<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>*
    *<wsdl:operation name="getNums">*
    *<wsdlsoap:operation soapAction=""/>*
    *<wsdl:input name="getNumsRequest">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:input>*
    *<wsdl:output name="getNumsResponse">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:output>*
    *</wsdl:operation>*
    *<wsdl:operation name="getNums2">*
    *<wsdlsoap:operation soapAction=""/>*
    *<wsdl:input name="getNums2Request">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:input>*
    *<wsdl:output name="getNums2Response">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:output>*
    *</wsdl:operation>*
    *</wsdl:binding>*
    *<wsdl:service name="EchoService">*
    *<wsdl:port binding="impl:EchoSoapBinding" name="Echo">*
    *<wsdlsoap:address location="http://localhost:8080/SOATest/services/Echo"/>*
    *</wsdl:port>*
    *</wsdl:service>*
    *</wsdl:definitions>*
    I created a client from the above wsdl file using ClientGen wizard in WebLogic. This client contains the follwoing classes-
    Echo.java
    EchoService.java
    EchoService_Impl.java
    Echo_Stub.java
    I created a JSP portlet and the jsp content of it is-
    String url = "http://localhost:8080/SOATest/services/Echo";
    Echo echo = new EchoService_Impl(url).getEcho();
    getNumsResponse = echo.getNums(getNums);
    I tried to call that web service from BEA weblogic portal through a JSP potlet. I got an error saying -
    *<An exception [javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element] was thrown while rendering the content at [TestEcho.jsp].*
    *javax.servlet.ServletException: javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.servlet.jsp.PageContextImpl.handlePageException(PageContextImpl.java:420)*
    *     at jsp_servlet.__testecho._jspService(__testecho.java:112)*
    *     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)*
    *     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)*
    *     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)*
    *     Truncated. see log file for complete stacktrace*
    *javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.throwServiceException(ServiceImpl.java:174)*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:485)*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)*
    *     at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
    *     at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
    *     Truncated. see log file for complete stacktrace*
    *weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:391)*
    *     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)*
    *     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)*
    *     Truncated. see log file for complete stacktrace*
    *java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:38)*
    *     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:122)*
    *     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)*
    *     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
    *     Truncated. see log file for complete stacktrace*
    *javax.xml.stream.XMLStreamException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:206)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:73)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:35)*
    *     Truncated. see log file for complete stacktrace*
    *Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.babel.baseparser.BaseParser.parseProlog(BaseParser.java:417)*
    *     at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:328)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:195)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
    *     Truncated. see log file for complete stacktrace*
    My web service is using soap binding. I have tested it with eclipse and other tools also. It is working well and good. But when I tried to call a web service which is created and hosted on WebLogic server(running on port : 7001), I got the correct output.
    Can anyone help me out in calling a web service hosted on different server from WebLogic server.
    Thanks in advance,
    Tiijnar
    Edited by: user8715057 on Aug 13, 2009 1:11 AM

    Hi
    1. The way you are invoking the WebService deployed on Tomcat server is looks suspicious. It may be valid by adding extra ?wsdl etc into the url, but still I have not seen this way to invoke the webservice.
    2. So you used Weblogic ant task to generate client JARs by giving this WSDL. So looks like it generated the 4 classes (.java) and in addition any other classes for Request/Response xml objects.
    3. Look at the source code of EchoService.java. It should have one default empty constructor. Internally it uses the default wsdl defined in this class. You will see another constructor that takes WSDL URL as one of the parameters (QName) etc. Echo.java is the class corresponding to the Port. In the same EchoService you should see an instance method like getEcho() something like that. This Echo.java class will have methods for all the Operations defined on this Port. So the standard code snippet we use most of the times will be like this:
    EchoService myEchoService = new EchoService(); // Default it uses WSDL deployed on Tomcat at localhost:8080
    Echo myEchoPort = myEchoService.getEchoPort(); // Something along these lines.
    myEchoPort.xxxYYY(); // NOW this is the operation name that takes the input parameters and returns outputs defined as per the WSDL defintions. If the Input and Outputs are complex xml types, it will have corresponing .JAVA files with setters and getters.
    Now if this WebService is deployed on same Tomcat but on different machine or different port, you just give the full WSDL URL with that host and port in the constructor for new EchoService(...). You may need to instantiate QName object. But look at the methods generated in EchoService.java class.
    The way you are using with Impl and Stubs class may also work. I am not much famiiar with this APIs apporach. Still look at the methods generated in these classes.
    Also if you latest Sun JDK 1.6, it also has one command like wsimport. Infact if you install WLS 10.3 with Sun JDK, it should have C:\beawlp103\jdk160_05\bin\wsimport command. This will also generate client jar given a WSDL URL.
    Thanks
    Ravi Jegga

  • Problem while calling a web service in BOBJ Data services

    Hello Experts,
    I am trying to call a web service in bobj data services. A real time job has been scheduled and published as a web service. I want to consume this service in web dynpro java.
    I tried both the methods the adaptive web services and depricated version. I also tried calling the url directly and with the metadata and execution destinations.
    No matter what I do, I keep getting the following error.
    Exception on execution of web service with WSDL URL 'http://XXXXX:28080/DataServices/servlet/webservices?ver=2.0&wsdl' with operation 'SERVICE_<NAME>' in interface 'Real-time_Services'
    The call never reaches data services system.  If I try to call the service from soapUI (web service testing tool) it works fine.
    I am using SAP NW 7.0 SP22 .
    Here is my code in dynpro to call the service.
         AdaptiveModel mod = new AdaptiveModel();
         Request_SERVICE_MDM_LOOKUP request = new Request_SERVICE_MDM_LOOKUP(mod);
         Query1 query1 = new Query1(mod);
         Response_SERVICE_MDM_LOOKUP response = new Response_SERVICE_MDM_LOOKUP(mod);
         request.setQuery(query1);
         request.setResponse(response);
         List list = new ArrayList();
         DefinitionsTypes_XsdSchema_1__XsdElement_1__XsdComplexType_Sequence1 element = new DefinitionsTypes_XsdSchema_1__XsdElement_1__XsdComplexType_Sequence1(mod);
         element.setCustomer_Name(wdContext.currentContextElement().getCustomerName());
         element.setZip_Code(wdContext.currentContextElement().getZipcode());
         element.setAddr1("");
         element.setAddr2("");
         element.setCity("");
         element.setCountry("");
         element.setState("");
         list.add(element);
         query1.set$002fDefinitions$002fTypes$002fXsdSchema$005b1$005d$002fXsdElement$005b1$005d$002fXsdComplexType$0023Sequence1(list);
         wdContext.nodeRequest_SERVICE_MDM_LOOKUP().bind(request);
          wdContext.currentRequest_SERVICE_MDM_LOOKUPElement().modelObject().execute();
          wdContext.nodeResponse().invalidate();
          wdContext.nodeQueryResponse().invalidate();
          wdContext.nodeSequenceResponse().invalidate();
    Please let me know if you have any pointers on how to solve this.
    Thanks in advance
    Praveen.

    have you create the destination?
    do  you use the wizard to generate code?
    usually there is catch clause for this line of code
    wdContext.currentRequest_SERVICE_MDM_LOOKUPElement().modelObject().execute();
    Edited by: John Wu on Dec 16, 2010 11:51 PM

  • Problem about Calling SQLplus Web Service on Aspen Watch Server

    Hi all,
    We're using MII 11.5 and trying to call a web service from a Aspen Watch server through the web service block in transaction. The web service enclosed a function call ExecuteSQL which will accept a sql query function and return a set of Data. Now, using the same web service on two different servers, we got a success(server A) and a failure(Server B). On the failed call, right in the first page of enter a URL, it will return a "SOAP Service could not be loaded: The element type 'META' must be terminated by the machine end-tag '</META>'" error.
    According to the admin of the web server, the web service on both servers can be called correctly when he created two simple ASP pages. After serious testing, he thought that the only reason should be MII may not be compatible with .Net 2.0 binding web service. The following is some comparison we made to the two servers.
                                                                                    Server A / Server B / Error, if applicable
    .Net Framework installed on MII server:                                 1.1, 2.0 /      1.1, 2.0     
    .Net Binding:                                                                          1.1 /               2.0
    IIS version on MII server:                                                 6 /                 6     
    From MII server broser to Server A web service:                 Yes /      Yes     
    From MII server browser to Server B web service:                 No /     No /      Return on web "The test form is only available for requests from the local machine"
    From localhost browser to Server A web service:                 n/a //     Yes     
    From localhost browser to Server B web service:                 Yes //     n/a     
    From PC browser to Server B web service:                                No /        Yes /     Return on web "The test form is only available for requests from the local machine"
    Credentials required to run web service:                                 No /     Yes /     
    The following are the SOAP generated:
    Server A
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
    - <s:element name="ExecuteSQL">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ExecuteSQLResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
      <s:element name="string" nillable="true" type="s:string" />
      </s:schema>
      </wsdl:types>
    - <wsdl:message name="ExecuteSQLSoapIn">
      <wsdl:part name="parameters" element="tns:ExecuteSQL" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLSoapOut">
      <wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpGetIn">
      <wsdl:part name="command" type="s:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpPostIn">
      <wsdl:part name="command" type="s:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
      </wsdl:message>
    - <wsdl:portType name="SQLplusWebServiceSoap">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLSoapIn" />
      <wsdl:output message="tns:ExecuteSQLSoapOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:portType name="SQLplusWebServiceHttpGet">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLHttpGetIn" />
      <wsdl:output message="tns:ExecuteSQLHttpGetOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:portType name="SQLplusWebServiceHttpPost">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLHttpPostIn" />
      <wsdl:output message="tns:ExecuteSQLHttpPostOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
      <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceHttpGet" type="tns:SQLplusWebServiceHttpGet">
      <http:binding verb="GET" />
    - <wsdl:operation name="ExecuteSQL">
      <http:operation location="/ExecuteSQL" />
    - <wsdl:input>
      <http:urlEncoded />
      </wsdl:input>
    - <wsdl:output>
      <mime:mimeXml part="Body" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceHttpPost" type="tns:SQLplusWebServiceHttpPost">
      <http:binding verb="POST" />
    - <wsdl:operation name="ExecuteSQL">
      <http:operation location="/ExecuteSQL" />
    - <wsdl:input>
      <mime:content type="application/x-www-form-urlencoded" />
      </wsdl:input>
    - <wsdl:output>
      <mime:mimeXml part="Body" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="SQLplusWebService">
    - <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
      <soap:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
      <soap12:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceHttpGet" binding="tns:SQLplusWebServiceHttpGet">
      <http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceHttpPost" binding="tns:SQLplusWebServiceHttpPost">
      <http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Server B
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
    - <s:element name="ExecuteSQL">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ExecuteSQLResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
      </s:schema>
      </wsdl:types>
    - <wsdl:message name="ExecuteSQLSoapIn">
      <wsdl:part name="parameters" element="tns:ExecuteSQL" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLSoapOut">
      <wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
      </wsdl:message>
    - <wsdl:portType name="SQLplusWebServiceSoap">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLSoapIn" />
      <wsdl:output message="tns:ExecuteSQLSoapOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
      <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="SQLplusWebService">
    - <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
      <soap:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
      <soap12:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Please advise me on how to fix the probelm. And please let me know any additional information is needed. Greatly appreciated~
    Best regards,
    Lawrence
    Edited by: UMeng Lai on Feb 6, 2009 4:07 PM

    Hi all,
    We're using MII 11.5 and trying to call a web service from a Aspen Watch server through the web service block in transaction. The web service enclosed a function call ExecuteSQL which will accept a sql query function and return a set of Data. Now, using the same web service on two different servers, we got a success(server A) and a failure(Server B). On the failed call, right in the first page of enter a URL, it will return a "SOAP Service could not be loaded: The element type 'META' must be terminated by the machine end-tag '</META>'" error.
    According to the admin of the web server, the web service on both servers can be called correctly when he created two simple ASP pages. After serious testing, he thought that the only reason should be MII may not be compatible with .Net 2.0 binding web service. The following is some comparison we made to the two servers.
                                                                                    Server A / Server B / Error, if applicable
    .Net Framework installed on MII server:                                 1.1, 2.0 /      1.1, 2.0     
    .Net Binding:                                                                          1.1 /               2.0
    IIS version on MII server:                                                 6 /                 6     
    From MII server broser to Server A web service:                 Yes /      Yes     
    From MII server browser to Server B web service:                 No /     No /      Return on web "The test form is only available for requests from the local machine"
    From localhost browser to Server A web service:                 n/a //     Yes     
    From localhost browser to Server B web service:                 Yes //     n/a     
    From PC browser to Server B web service:                                No /        Yes /     Return on web "The test form is only available for requests from the local machine"
    Credentials required to run web service:                                 No /     Yes /     
    The following are the SOAP generated:
    Server A
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
    - <s:element name="ExecuteSQL">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ExecuteSQLResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
      <s:element name="string" nillable="true" type="s:string" />
      </s:schema>
      </wsdl:types>
    - <wsdl:message name="ExecuteSQLSoapIn">
      <wsdl:part name="parameters" element="tns:ExecuteSQL" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLSoapOut">
      <wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpGetIn">
      <wsdl:part name="command" type="s:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpPostIn">
      <wsdl:part name="command" type="s:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
      </wsdl:message>
    - <wsdl:portType name="SQLplusWebServiceSoap">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLSoapIn" />
      <wsdl:output message="tns:ExecuteSQLSoapOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:portType name="SQLplusWebServiceHttpGet">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLHttpGetIn" />
      <wsdl:output message="tns:ExecuteSQLHttpGetOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:portType name="SQLplusWebServiceHttpPost">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLHttpPostIn" />
      <wsdl:output message="tns:ExecuteSQLHttpPostOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
      <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceHttpGet" type="tns:SQLplusWebServiceHttpGet">
      <http:binding verb="GET" />
    - <wsdl:operation name="ExecuteSQL">
      <http:operation location="/ExecuteSQL" />
    - <wsdl:input>
      <http:urlEncoded />
      </wsdl:input>
    - <wsdl:output>
      <mime:mimeXml part="Body" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceHttpPost" type="tns:SQLplusWebServiceHttpPost">
      <http:binding verb="POST" />
    - <wsdl:operation name="ExecuteSQL">
      <http:operation location="/ExecuteSQL" />
    - <wsdl:input>
      <mime:content type="application/x-www-form-urlencoded" />
      </wsdl:input>
    - <wsdl:output>
      <mime:mimeXml part="Body" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="SQLplusWebService">
    - <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
      <soap:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
      <soap12:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceHttpGet" binding="tns:SQLplusWebServiceHttpGet">
      <http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceHttpPost" binding="tns:SQLplusWebServiceHttpPost">
      <http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Server B
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
    - <s:element name="ExecuteSQL">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ExecuteSQLResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
      </s:schema>
      </wsdl:types>
    - <wsdl:message name="ExecuteSQLSoapIn">
      <wsdl:part name="parameters" element="tns:ExecuteSQL" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLSoapOut">
      <wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
      </wsdl:message>
    - <wsdl:portType name="SQLplusWebServiceSoap">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLSoapIn" />
      <wsdl:output message="tns:ExecuteSQLSoapOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
      <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="SQLplusWebService">
    - <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
      <soap:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
      <soap12:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Please advise me on how to fix the probelm. And please let me know any additional information is needed. Greatly appreciated~
    Best regards,
    Lawrence
    Edited by: UMeng Lai on Feb 6, 2009 4:07 PM

  • HELP!!! Problem of Calling external Web Service from a Java Stored Procedur

    1.I read the topic on http://www.oracle.com/technology/sample_code/tech/java/jsp/samples/wsclient/Readme.html about Calling external Web Service from a Java Stored Procedur.
    2.After I import .jar to Oracle what is required by the topic,som error occued.
    Like: ORA-29521: javax/activation/ActivationDataFlavor class not found,
    ORA-29545: badly formed class.
    3.These is not enough .jar required on the topic? What can I do for ORA-29545: badly formed class?
    Thany you!

    Try this
    Re: HELP! Loading Java Classes into Oracle ERROR

  • UWL connector: problems with calling a web service with a SAPLOGONTICKET

    Hi,
    I want to implement a uwl connector that calls a web service to retrieve the uwl items data with a SAPLOGONTICKET. If I refresh the UWL I get the following error.
    An error occured while reading data from the destination sap.com/com.xxxx.connector.RequestLeaveDP/com.xxxx.connector.RequestLeave/Config1Port_Document. The error was: com.sap.security.core.client.ws.SSO2Exception No SAP Logon Ticket was found for the user. Please ensure the user authenticated using HTTP/HTTPS and the JAAS login stack has been configured correctly. As an alternative, consider changing the authentication type to Assertion Ticket. .
    If I call  the Web Service in an iView I don't get this error. Maybe the UWL calls the web service not with the current authenticated user.
    I tried the following code, to get the current SSO2 Ticket from the current user. It looks like, that is the current user, but the web service will not accept this. (testing purpose)
    com.sap.security.api.IUser currentUser = com.sap.security.api.UMFactory.getAuthenticator().getLoggedInUser();
    String logonTicketUwlUser = (String) context.getUser().getTransientAttribute("com.sap.security.core.usermanagement", "MYSAPSSO2_STRING");
    String logonTicketCurrentUser = (String) currentUser.getTransientAttribute("com.sap.security.core.usermanagement", "MYSAPSSO2_STRING");
    InitialContext contextWebService = new InitialContext();
    RequestLeaveWebService requestLeaveWebService = (RequestLeaveWebService) contextWebService.lookup(wsClient);
    RequestLeaveWebServiceViDocument webServiceEndPoint = requestLeaveWebService.getLogicalPort("Config1Port_Document");
    UWLHolidayItem holidayItem = webServiceEndPoint.getHolidayItem("");
    Any ideas?
    Regards
    Markus
    Edited by: Markus Karsch on Oct 18, 2008 11:15 PM

    Are you calling invoke()?
    Do you have the port type in the servlet context?

  • Error in calling a web service

    hi,
    i am facing a problem in calling a web service.
    following are the steps i followed.
    1. created a client proxy object in transaction se80
    2. called that proxy object in my program
    3. executed the program
    problem
    1. an exception 'CX_AI_SYSTEM_FAULT' is caught with error code 'GET_BUSINESS_SYSTEM_ERROR' and error text 'An error occurred when determining the business system (SLD_API_EXCEPTION)'
    some facts abt the system:
    1. we do not have XI server.
    2. i havent created a logical port manually still there exists one entry in table SRT_LP which is as follows-
    PROXYCLASS - CO_CAT_PING
    LP_NAME - CO_CAT_PING
    ACTIVE - A
    DEFAULTPORT - X
    3. i found error messae in transaction 'sldcheck' as 'Summary: Connection to SLD does not work'
    4. i havent created a rfc destination.
    please reply ASAP.
    thanks in advance,
    Sagar

    Got a new file for testing the web service and it executed fine. Closing the thread.
    Regards
    Barada

Maybe you are looking for