WSDL connection to call a Webservice --urgent

Hi ,
1) Created a interactive form in using form builder
2) The form is genearted and the the purpose is to save the data in a online mode from a PDF forms directly .
3) an RFC FM is created in backend and planning to invoke this from the PDF forms .
code has been written in click event of a regular button (Control Type = Regular).
In this example I use my function module ZHRABAM_ECHO_STRING which can be called as a web service which genrates a XML .. This XML will be tracked by my FM now I have created a webservice in SAP ABAP .
what all I need to do in PDF form to get the call to webservice invoked ...
1) as far as I know I need to create data conncection ( but I find 2 options )
a) Creating a data connection to a WSDL file
b) Creating a data connection to an XML schema and XML data files
which one should I use for my scenario and if so what all needs to be done . I mean how will option a or option b work .. pls explain in detail .. I am not gtg confused in reading the documentation
urgent help will be appreciated
Regards
Abhilash

Hi Abhilash,
I don't understand where is your problem. You write you are able call RFC FM from an adobe form and you are able send xml data to this RFC FM. It's all you need (in adobe side). Now you must only write in RFC FM a code which will process sended xml data.
Regards
Michal

Similar Messages

Escape special charter in WSDL url for calling a webservice

I am trying to call a webservice which has "&" in the WSDL url.
http://server:8080/asd?id=123gh3&wsdl=1
It is throwing "The refernece to entity must end with the ';' delimeter." error
How can I excape it or encode this specail character in WSDL url
Thanks

Is this a compiler error? If so, replace & with &
If it is a runtime error, there is a top-level escape() function.

Web Dynpro resets connection when calling webservice

Hi,
I get a very very strange problem by using Web Dynpro to implement a webservice client.
The Webservice provider is running on a IBM WebSphere Server. I can use xmlspy to call this service and get the response correctly as expected.
But when my web dynpro application (running on WebAS 6.40 Stack 13) calls this webservice, I only get incomplete SOAP response message. It looks like the HTTP response had been broken beforte it finished. To verify this, I use ethereal to analyse the tcp packet. And I find that the WebAS server has sent some tcp reset packets to the websphere server, before the http response can be finished. This problem can be reproduced on different WebAS server. So it can'b be caused by hardware defect.
When I use web dynpro client to call other webservice on other WebAS server, there is no problem at all.
I have really no idea, how could this happen.
Thanks in advance.
Kanyin

Hi,
Now we know how it happens.
The reason is the content of the soap message from webservice provider is by means of the WSDL definition not complete, although the message structure is complete.
The Web Dynpro deserialise the soap response on the fly, without getting the complete SOAP message first. When the parser throws any exception, the connection will be broken by the WebAS.

How to use a WSDL file to call webservice? Help!

Hi Experts,
     I have exposed a SAP function module as webservice using the
     Utilities -> More Utilities -> Create Web Service -> From Function module
     What does this step actually does? Does it create some kind of web application like BSP for the function module in the background?
     After creating the web service I have released the service definition for the SOAP runtime using the transaction WSCONFIG.
    Finally I have generated the WDSL file ofr the webservice using WSADMIN transaction.
    After this how will my third party application like Java will use the WSDL? Will I need any connector software to be installed in Java side.
    How exactly will java call my webservice using WSDL?
    What actually happens or what is the message flow when java application calls by webservice?
    Kindly help.
Thanks
Gopal

Hi, Your solution should be correct and it's a quite common approach for Login authentication.Informatica's webservice provider also need 2 steps for calling its webservice1. Getting the session ID using username and password 2. Use the session ID to call any active operation 3. Use the session ID to log out if webservice do not have any time out settings for each session. SOAP standard is listed in the WSDL of saleforce webservice. It affects if you cannot find/call any operation in PowerCenter level. My lastest information is for PWC 9.1 version only, I don't know if they have enhanced this function in 9.5. If you can call the operation, you can just put it (SOAP standard) way first. Regards,Felix

Is it possible to call a webservice with just the url to its WSDL

hi all
can anyone tell me if it is possible to call a webservice with just the url to its WSDL file. must we create the proxy class for webservice client? thanks

if you are in the context of a J2EE 1.4 container, you do not need to generate any stub, you can use either a dynamic proxy mechanism or dynamic invocation.
check JWSDP tutorial.

How to call a WebService method using HttpsURLConnection?

Hi,
I want to know how i could use HttpsURLConnection to call a WebService method.
I can use the following:
String endpoint = "https://xyz:8443/axis/services/MSecurity";
System.setProperty("javax.net.ssl.keyStore", keyStorepath);
System.setProperty("javax.net.ssl.keyStoreType", "PKCS12");
System.setProperty("javax.net.ssl.keyStorePassword", keyStorePassword);
System.setProperty("javax.net.ssl.trustStore", trustStorePath);
System.setProperty("javax.net.ssl.trustStoreType", "JKS");
System.setProperty("javax.net.ssl.trustStorePassword", trustpass);
//Call Web Service
URL url = new URL(endpoint);
MSecuritySoapBindingStub service = new MSecuritySoapBindingStub(url, null);
//get list of people
String[] vo = service.getVO();
for (int i = 0; i < vo.length; i++) {
System.out.println(vo);
However, loading my cert. this way is not flexible. Therefore, I am using SSLContext to initialize my keystore and truststore and then I am using the following to connect to my webservice:
SSLContext sc = SSLContext.getInstance("SSLv3");
sc.init(kmf.getKeyManagers(), tmf.getTrustManagers(), null);
SSLSocketFactory ssf = sc.getSocketFactory();
URL url = new URL(endpoint);
HttpsURLConnection htp = (HttpsURLConnection) url.openConnection();
htp.setSSLSocketFactory(ssf);
However, I do not know how I could use the "htp" object to call the getVO() method above.

Use Apache Axis to do SOAP in Java.
Nobody can just mail you the code. You first have to create java source files from the web service via its WSDL file.

Call SAP WebService in Excel

Hello,
I want to call a WebService from a SAP-System in Excel. I created this WebService with the WebService Creation Wizard by using a RFC function. The WebService expects two parameters of string and it delivers a table.
I'm using the MS SOAP Type Library v3.0 to call the WebService.
Here's my code:
01 Dim SOAPClient As SoapClient30
02 Set SOAPClient = New SoapClient30
03
04 SOAPClient.mssoapinit "http://" & User & ":" & pswd & "@bcrsap27.de.emea.csc.com:8000/sap/bc/srt/wsdl/bndg_DE22AF411A745FF19F270014C25BCDE3/wsdl11/allinone/ws_policy/document?sap-client=800"
05
06 With SOAPClient
07         .ConnectorProperty("UseSSL") = True
08 End With
09
10 Dim ret() As ZETT_DEFECT_T
11
12 ret = SOAPClient.ZETT_WS_READ_DEFECT("2009-01-01", "2009-04-07")
At line 4 'User' and 'pswd' is needed to authenticate the user.
But on line 12 I allways get an error:
    Run-time error '5419'
    Client: unspecifiedclient erro. HRESULT=0x800A152B
I hope someone can help me.
Thank you,
Frank

Hi,
I have progressed upto a stage where it actully connects to R/3 and goes into class
"CL_HTTP_EXT_SOAPHANDLER_RFC"
but i always get a error
<i><b>"SoapMapper:Restoring data into SoapMapper <obj> failed"</b></i>
It looks like that it is to do with complex data type.
But the function which i am using is just reutrning a result of type string.
I will post more once i solve the issue.
Regards
Raja

Calling a Webservice via a Function in PL/SQL

Hi
I am trying to call a webservice from a function, but i am getting an error, i am not sure that i am using the correct url for the end point or actions
Below is the class i am calling..
Please could some assist.
FUNCTION add_new_user (xmlstruct IN VARCHAR2)
RETURN VARCHAR2
IS
req xx_demo_soap.request;
resp xx_demo_soap.response;
BEGIN
req :=
xx_demo_soap.new_request
('processRequest',
'xmlns="http://extServices"'
xx_demo_soap.ADD_PARAMETER (req, 'processReq', 'xsd:string', xmlstruct);
resp :=
xx_demo_soap.invoke
(req,
'http://wbrbap92/LDAP_Self-Service/services/LdapProcWS',
'http://wbrbap92/LDAP_Self-Service/services/LdapProcWS/'
RETURN xx_demo_soap.get_return_value
(resp,
'processRequestResponse',
'xmlns="http://extServices"'
END;
Also here is the WSDL file
\<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://extServices" xmlns:impl="http://extServices" xmlns:intf="http://extServices" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsi="http://ws-i.org/profiles/basic/1.1/xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<schema targetNamespace="http://extServices" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<element name="firstTestResponse">
<complexType>
<sequence>
<element name="firstTestReturn" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="processDelete">
<complexType>
<sequence>
<element name="processDel" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="processDeleteResponse">
<complexType>
<sequence>
<element name="processDeleteReturn" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="processRequest">
<complexType>
<sequence>
<element name="processReq" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="processRequestResponse">
<complexType>
<sequence>
<element name="processRequestReturn" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="processModify">
<complexType>
<sequence>
<element name="processMod" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="processModifyResponse">
<complexType>
<sequence>
<element name="processModifyReturn" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="firstTest">
<complexType>
<sequence/>
</complexType>
</element>
</schema>
</wsdl:types>
<wsdl:message name="processRequestResponse">
<wsdl:part element="impl:processRequestResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="processDeleteRequest">
<wsdl:part element="impl:processDelete" name="parameters"/>
</wsdl:message>
<wsdl:message name="firstTestResponse">
<wsdl:part element="impl:firstTestResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="processRequestRequest">
<wsdl:part element="impl:processRequest" name="parameters"/>
</wsdl:message>
<wsdl:message name="processModifyRequest">
<wsdl:part element="impl:processModify" name="parameters"/>
</wsdl:message>
<wsdl:message name="processModifyResponse">
<wsdl:part element="impl:processModifyResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="processDeleteResponse">
<wsdl:part element="impl:processDeleteResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="firstTestRequest">
<wsdl:part element="impl:firstTest" name="parameters"/>
</wsdl:message>
<wsdl:portType name="LdapProcWS">
<wsdl:operation name="firstTest">
<wsdl:input message="impl:firstTestRequest" name="firstTestRequest"/>
<wsdl:output message="impl:firstTestResponse" name="firstTestResponse"/>
</wsdl:operation>
<wsdl:operation name="processDelete">
<wsdl:input message="impl:processDeleteRequest" name="processDeleteRequest"/>
<wsdl:output message="impl:processDeleteResponse" name="processDeleteResponse"/>
</wsdl:operation>
<wsdl:operation name="processRequest">
<wsdl:input message="impl:processRequestRequest" name="processRequestRequest"/>
<wsdl:output message="impl:processRequestResponse" name="processRequestResponse"/>
</wsdl:operation>
<wsdl:operation name="processModify">
<wsdl:input message="impl:processModifyRequest" name="processModifyRequest"/>
<wsdl:output message="impl:processModifyResponse" name="processModifyResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="LdapProcWSSoapBinding" type="impl:LdapProcWS">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="firstTest">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="firstTestRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="firstTestResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="processDelete">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="processDeleteRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="processDeleteResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="processRequest">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="processRequestRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="processRequestResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="processModify">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="processModifyRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="processModifyResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="LdapProcWSService">
<wsdl:port binding="impl:LdapProcWSSoapBinding" name="LdapProcWS">
<wsdlsoap:address location="http://wbrbap92/LDAP_Self-Service/services/LdapProcWS"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thanks

Try this..
CREATE OR REPLACE PACKAGE L_WEBSERVICE_INVOKE
AS
**         Name:    L_WEBSERVICE_INVOKE
PROCEDURE P_CREATE_XML(envolope IN OUT NOCOPY varchar2);
PROCEDURE P_INVOKE_WEBSERVICE(rs_error_msg      IN OUT VARCHAR2,
                     on_result         IN OUT NUMBER);
PROCEDURE SHOW_ENVELOPE(env IN VARCHAR2);
END L_WEBSERVICE_INVOKE;
show errors;
create or replace PACKAGE BODY L_WEBSERVICE_INVOKE
AS
PROCEDURE P_CREATE_XML(envolope IN OUT NOCOPY varchar2)
AS
BEGIN
     envolope := '<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:q0="http://extServices" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><q0:processRequest><processReq><?xml version='1.0'?><users><user><uid>W0001</uid><surname>Bruce</surname><firstName>Jacob</firstName><idNumber>6611254858081</idNumber><idType>P</idType><email>[email protected]</email><employer>FNB</employer><empNumber>W3546333</empNumber><department>Collections</department><region></region><branch>Southside</branch><division>Corporate</division></user><user><uid>W0034</uid><surname>Brian</surname><firstName>Sutters</firstName><idNumber>3445554858081</idNumber><idType>V</idType><email>[email protected]</email><employer>Wesbank</employer><empNumber>W3455455</empNumber><department>Fraud</department><region>PTA West</region><branch>Southside</branch><division>Corporate</division></user></users></processReq></q0:processRequest></SOAP-ENV:Body></SOAP-ENV:Envelope>';
END P_CREATE_XML;
PROCEDURE P_INVOKE_WEBSERVICE(rs_error_msg      IN OUT VARCHAR2,
                     on_result         IN OUT NUMBER)
AS
ls_out_resp varchar2(32767);
http_req utl_http.req;
http_resp utl_http.resp;
ls_http_req_url varchar2(4000);
ls_result VARCHAR2(2000);
name VARCHAR2(256);   -- Response header name
value VARCHAR2(1024); -- Response header value
line VARCHAR2(4000); -- Response body
ls_webservice_url varchar2(1024);
ls_in_request     varchar2(4000);
is_webservice_err varchar2(2000);
BEGIN
     on_result:=0;
     ls_http_req_url := 'http://wbrbap92/LDAP_Self-Service/services/LdapProcWS';
     --Construct the Input Soap Request
     P_CREATE_XML(ls_in_request);
     --show_envelope(ls_in_request);
        -- Establish the connection
     http_req := utl_http.begin_request(ls_http_req_url, 'POST' ,'HTTP/1.1');
     -- The Content-Length header has to indicate the amount of data in the XML document
      utl_http.set_header(http_req, 'Content-Type', 'text/xml');
      utl_http.set_header(http_req, 'Content-Length', to_char(length(ls_in_request)) );
      -- POST the XML document
      utl_http.write_text(http_req,ls_in_request);
       -- Now process the HTTP server's response
       http_resp := utl_http.get_response(http_req);
       dbms_output.put_line('HTTP response status code: ' || http_resp.status_code);
       dbms_output.put_line('HTTP response reason phrase: ' || http_resp.reason_phrase);
       utl_http.read_text(http_resp, ls_out_resp);
       show_envelope(ls_out_resp);
       utl_http.end_response(http_resp);
EXCEPTION
WHEN Utl_Http.request_failed   THEN
           on_result:=-1;
           rs_error_msg:='L_WEBSERVICE_INVOKE.p_invoke_webservice-request_failed: ' ||UTL_HTTP.GET_DETAILED_SQLERRM;
           Utl_Http.end_request (http_req);
WHEN Utl_Http.http_server_error THEN
          on_result:=-1;
          rs_error_msg:='L_WEBSERVICE_INVOKE.p_invoke_webservice-Http_Server_Error: ' ||UTL_HTTP.GET_DETAILED_SQLERRM;
          Utl_Http.end_request (http_req);
WHEN Utl_Http.http_client_error THEN
           on_result:=-1;
           rs_error_msg:='L_WEBSERVICE_INVOKE.p_invoke_webservice-Http_Client_Error: ' ||UTL_HTTP.GET_DETAILED_SQLERRM;
           Utl_Http.end_request (http_req);
when others then
     on_result:=-1;
     rs_error_msg := 'L_WEBSERVICE_INVOKE.P_INVOKE_WEBSERVICE: ' || SQLERRM;
     Utl_Http.end_request (http_req);
END P_INVOKE_WEBSERVICE;
PROCEDURE SHOW_ENVELOPE(env IN VARCHAR2)
AS
i pls_integer;
len pls_integer;
BEGIN
     i := 1;
     len := length(env);
     WHILE (i <= len)
     LOOP
     dbms_output.put_line(substr(env, i, 100));
     i:=i+100;
     END LOOP;
END SHOW_ENVELOPE;
END L_WEBSERVICE_INVOKE;
Now execute the anonymous block
set serverout on size 1000000;
DECLARE
RS_ERROR_MSG VARCHAR2(2000);
ON_RESULT NUMBER;
BEGIN
L_WEBSERVICE_INVOKE.P_INVOKE_WEBSERVICE(RS_ERROR_MSG,ON_RESULT);
END;
Good luck!!!
Bhagat
Message was edited by:
        Bugs
Message was edited by:
        Bugs

Trying to call a webservice generated by coldfusion

Hi
We are running SAP PI 7.11.
We are trying, from SAP PI, to call a webservice that is created by coldfusion - the target url is called
http:/...../edb_service.cfc?wsdl via the SOAP adapter (RECEIVER)
Our adapter/comm channel fails with a http error 500:
"SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error. Setting message to status failed."
It appears that we are not getting any connection at all. When trying to call the webservice from XMLSPY it works fine? Are there any restriction to call a webservice created by coldfusion?
How can I get any better logging of the call attempt, because I can not see anything out of the comm. channel eror message.
Any help would be appreciated.
Thx

Hi
the target url should be http:/...../edb_service.cfc
also mention the correct action.
you would not get the error.
Regards
Monika

How to call SAP Webservice in standalone java program

Hi,
In our Java application, we want to use the SAP Webservices. I dont know much about authentication mechanism used by SAP. Can any one please help me with any sample code how to Call SAP webservice in Standalone Jave Program. I searched alot on the web regarding this, but helpless. Please help me.
Thanks,
Mohan

Hi Mohan,
You need an account for the ES Workplace. I'm afraid this is not free, e.g. check [SAP NetWeaver, Composition Subscription|https://www.sdn.sap.com/irj/sdn/subscriptions/composition].
But I thought you wanted to play with a WSDL [you already had at hand|Sample code to access BAPI Web services from JAVA required;?

Wsdl connection not refreshed in QA and Prod

We have developed a offline
interactive adobe from based on a WSDL Data connection.
The form works fine in development. We moved the form to QA system. But
in the XML source code in the form which is based on the WSDL still
contains the Development host.
Although dynamically Hostname and Port are captured in the
Java script and made a soap connect , it still also use the Values in
the WSDL to connect to development system webservice.
=========================================================
Dynamic hostname and port generation
=========================================================
var cURL = enter the WSDL url generated in the first step;
var service = SOAP.connect(cURL);
xfa.connectionSet.name of our custom data connection.execute(0);
=========================================================
Development server hostname in WSDL source which is carried over to
subsequent systems
=========================================================
service name="ZQI_EXDATA_QUALITYCHECKLISTService">
<documentation>SAP Service ZQI_EXDATA_QUALITYCHECKLIST via
SOAP</documentation>
- <port name="ZQI_EXDATA_QUALITYCHECKLISTPortType"
binding="s0:ZQI_EXDATA_QUALITYCHECKLISTBinding">
<soap:address
location="http://<Dev hostname>:<Abap port>/sap/bc/soap/rfc" />
</port>
============================================
The WSDL is getting refreshed in the QA system only if create a New
data connection based on the WSDL downloaded from QA system.
We cannot do this in our QA system or Production system as the System
settings will not allow for modifications.

Hello Tanuj,
we have the same problem. Have you got any idea how to fix ist? Or has any one else an idea?
Thank you.

Error while calling PI webservice from EJB

Hi Experts,
We are getting exception while calling PI webservice from EJB which is deployed in CE 7.2. Earlier we used to call the same webservice but from different PI system at that it worked fine. Now we have changed the consumer proxies required in CE and tried to call from CE and it is throwing error. We have checked usernames and passwords that we are using to call the service and that is working fine. PI team tested from their side and li is also fine. We have also restarted the CE system but invain. Can somebody help on this. The below is the trace that we got.
Location: com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding
Text: Connection IO Exception. Check nested exception for details. (Connection reset).
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Connection reset).
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:419)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1364)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:168)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:121)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65)
at $Proxy780.mioaRDMDataDistribution(Unknown Source)
at com.MDMEventListener.callToPIWS(MDMEventListener.java:100)
at com.MDMEventListener.ListenerMethod(MDMEventListener.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_WS.invoke(Interceptors_WS.java:31)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:39)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:730)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:682)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:324)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:199)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:65)
at com.sap.engine.services.webservices.servlet.SoapServlet.doPost(SoapServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:404)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:204)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:440)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:429)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:82)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:268)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:54)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:950)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:414)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:319)
at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getResponseCode(ClientHTTPTransport.java:209)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:385)
... 78 more
Regards,
Pradeep

Hi Pradeep,
this looks like if the server is not reachable. Have you checked if both server are able to communicate? Maybe firewall rules block the request.
Regards,
Tobias

Error getting while calling a webService from XI

Hi
We are getting the follwoing error while calling a webservice from XI. We Could call the same webservice from XML spy. Have checked the SOAP adapter it was running fine and the communication channel parameters too.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code area="MESSAGE">GENERAL</SAP:Code><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessagingException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault</SAP:AdditionalText><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack/><SAP:Retry>M</SAP:Retry></SAP:Error>
Please try to help.
Thanks
Ramesh

Hi
Thanks a lot for your kind support.
Hi Moorthy
We have created one Asyn MI and wrapped the external definition into that, Haven't done any mapping for responce. Please find the trace below.
Hi Bhavesh
It was great helpful link but the payload days is not visible for this message it was containing details about sending. For some other message i could see payload.
I Could see one differnce in the XML Spy and "XI payload before entering SOAP Adapter"
The following line doesnt appear in the XI payload.
<m:StatusUpdate xmlns:m="http://localhost/StatusUpdate" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
</m:StatusUpdate>
Is this line would be embeded in the SOAP Adapter??? Please find the trace below. Please help me if you have any additional info.
The message was successfully received by the messaging system. Profile: XI URL: Using connection AFW. Trying to put the message into the receive queue.
Message successfully put into the queue.
The message was successfully retrieved from the receive queue.
The message status set to DLNG.
Delivering to channel: CC_SOAP_Rcvr_D_Pick_ZALEAUD
SOAP: request message entering the adapter
SOAP: completed the processing
SOAP: response message received 4cb3fab0-7fc5-11db-8c5a-000f203c93e0
SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
SOAP: sending a delivery error ack ...
SOAP: sent a delivery error ack
Exception caught by adapter framework: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
Delivery of the message to the application using connection AFW failed, due to: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault.
The asynchronous message was successfully scheduled to be delivered at Wed Nov 29 16:23:51 GMT 2006.
The message status set to WAIT.
Retrying to deliver message to the application. Retry: 1
Kind Regards
Ramesh
Message was edited by:
Ramesh Reddy Pothireddy

Calling a webservice from weblogic EJB Application

Hello,
I have a webservice running on IIS server. I created a simple java client program to call the webservice and it works fine. However, when I wrapped the same java client program as a EJB Application, I am unable to call the webservice.
I get the following error:
####<Apr 3, 2007 1:59:30 AM CDT> <Info> <WebService> <CASEJBServer> <ExecuteThread: '24' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-220094> <An IOException was thrown trying to access the WSDL at the given URL.>
And
"java.io.FileNotFoundException: Response: '401: Unauthorized' for url: XXXXXX"
Could you please give some simple steps as what are the JAR Files required to be included in the Weblogic Server's classpath to call the webservice.
Thanks.

To start off you need to make sure that your client api is in the classpath, either in your ejb or your ear or the server classpath.
The other concern I would have is that it seems you are just not authorized to access the URL.
- Does the WSDL require credentials? So in other words when you go to the URL are you allowed to access the WSDL without athenticating.
- How does your Impl get created?
MyServiceImpl service = new MyServiceImpl()
If you are using the empty constructor then what is the wsdl endpoint in your jar file since that is the wsdl it will use. If the endpoint is localhost/xxx/xxx then you will have issues since that means your not deployed on localhost. What url is at the endpoint? Do you have access to the url from your server?
If you are using "new MyServiceImpl(url);" then again is the wsdl locked down because in this case you will need to do somthing like http://username:[email protected]/xxx?wsdl
Hope this helps.
-Jesus

Calling secured webservice from java

Hi Experts,
I am trying to call a secured webservice from java.
I got the code to call a non secured web service in java.
What changes do i need to do in this to call a secured webservice.
Please help me.
Thank you
Regards
Gayaz
calling unsecured webservice
package wscall1;
import java.io.BufferedReader;
import java.io.ByteArrayOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.io.OutputStream;
import java.io.StringBufferInputStream;
import java.io.StringReader;
import java.io.StringWriter;
import java.io.Writer;
import java.net.HttpURLConnection;
import java.net.MalformedURLException;
import java.net.URL;
import java.net.URLConnection;
import java.security.Permission;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.ParserConfigurationException;
import org.apache.xml.serialize.OutputFormat;
import org.apache.xml.serialize.XMLSerializer;
import org.w3c.css.sac.InputSource;
import org.w3c.dom.Document;
import org.w3c.dom.NodeList;
import org.xml.sax.SAXException;
public class WSCall2 {
public WSCall2() {
super();
public static void main(String[] args) {
try {
WSCall2 ss = new WSCall2();
System.out.println(ss.getWeather("Atlanta"));
} catch (Exception e) {
e.printStackTrace();
public String getWeather(String city) throws MalformedURLException, IOException {
//Code to make a webservice HTTP request
String responseString = "";
String outputString = "";
String wsURL = "https://ewm52rdv:25100/Saws/SawsService";
URL url = new URL(wsURL);
URLConnection connection = url.openConnection();
HttpURLConnection httpConn = (HttpURLConnection)connection;
ByteArrayOutputStream bout = new ByteArrayOutputStream();
//Permission p= httpConn.getPermission();
String xmlInput =
"<soapenv:Envelope xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:ser=\"http://www.ventyx.com/ServiceSuite\">\n" +
" <soapenv:Header>\n" +
"     <soapenv:Security>\n" +
" <soapenv:UsernameToken>\n" +
" <soapenv:Username>sawsuser</soapenv:Username>\n" +
" <soapenv:Password>sawsuser1</soapenv:Password>\n" +
" </soapenv:UsernameToken>\n" +
" </soapenv:Security>" + "</soapenv:Header>" + " <soapenv:Body>\n" +
" <ser:GetUser>\n" +
" <request><![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?> \n" +
            "                        <GetUser xmlns=\"http://www.ventyx.com/ServiceSuite\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">\n" +
            "                        <UserId>rs24363t</UserId>\n" +
            "                        </GetUser>]]>\n" +
" </request>\n" +
" </ser:GetUser>\n" +
" </soapenv:Body>\n" +
"</soapenv:Envelope>";
byte[] buffer = new byte[xmlInput.length()];
buffer = xmlInput.getBytes();
bout.write(buffer);
byte[] b = bout.toByteArray();
String SOAPAction = "GetUser";
// Set the appropriate HTTP parameters.
httpConn.setRequestProperty("Content-Length", String.valueOf(b.length));
httpConn.setRequestProperty("Content-Type", "text/xml; charset=utf-8");
httpConn.setRequestProperty("SOAPAction", SOAPAction);
// System.out.println( "opening service for [" + httpConn.getURL() + "]" );
httpConn.setRequestMethod("POST");
httpConn.setDoOutput(true);
httpConn.setDoInput(true);
OutputStream out = httpConn.getOutputStream();
//Write the content of the request to the outputstream of the HTTP Connection.
out.write(b);
out.close();
//Ready with sending the request.
//Read the response.
InputStreamReader isr = new InputStreamReader(httpConn.getInputStream());
BufferedReader in = new BufferedReader(isr);
//Write the SOAP message response to a String.
while ((responseString = in.readLine()) != null) {
outputString = outputString + responseString;
//Parse the String output to a org.w3c.dom.Document and be able to reach every node with the org.w3c.dom API.
Document document = parseXmlFile(outputString);
NodeList nodeLst = document.getElementsByTagName("User");
String weatherResult = nodeLst.item(0).getTextContent();
System.out.println("Weather: " + weatherResult);
//Write the SOAP message formatted to the console.
String formattedSOAPResponse = formatXML(outputString);
System.out.println(formattedSOAPResponse);
return weatherResult;
public String formatXML(String unformattedXml) {
try {
Document document = parseXmlFile(unformattedXml);
OutputFormat format = new OutputFormat(document);
format.setIndenting(true);
format.setIndent(3);
format.setOmitXMLDeclaration(true);
Writer out = new StringWriter();
XMLSerializer serializer = new XMLSerializer(out, format);
serializer.serialize(document);
return out.toString();
} catch (IOException e) {
throw new RuntimeException(e);
private Document parseXmlFile(String in) {
try {
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
InputSource is = new InputSource(new StringReader(in));
InputStream ins = new StringBufferInputStream(in);
return db.parse(ins);
} catch (ParserConfigurationException e) {
throw new RuntimeException(e);
} catch (SAXException e) {
throw new RuntimeException(e);
} catch (IOException e) {
throw new RuntimeException(e);
} catch (Exception e) {
throw new RuntimeException(e);
static {
javax.net.ssl.HttpsURLConnection.setDefaultHostnameVerifier(new javax.net.ssl.HostnameVerifier() {
public boolean verify(String hostname, javax.net.ssl.SSLSession sslSession) {
if (hostname.equals("ewm52rdv")) {
return true;
return false;
}

Gayaz wrote:
What we are trying is we are invoking webservice by passing SOAP request and we will get soap response back.I understand what you're trying to do, the problem is with tools you're using it will take a while for you do anything a little away from the trivial... Using string concatenation and URL connection and HTTP post to call webservices is like to use a hand drill... It may work well to go through soft wood, but it will take a lot of effort against a concrete wall...
JAX-WS and JAXB and annotations will do everything for you in a couple of lines and IMHO you will take longer to figure out how to do everything by hand than to learn those technologies... they are standard java, no need to add any additional jars...
That's my thought, hope it helps...
Cheers,
Vlad

WSDL connection to call a Webservice --urgent

Similar Messages

Maybe you are looking for