Calling a webservice having an abstract element

hi ,
I want to call a webservice which takes one element namely
"data" as part of request info.But "data" is of abstract type and
"EnterpriseData" is another element which is of type "data" .
So when I form the request object as <mx:request>
<data></data> </mx:request> obviously it's not
gonna work because i'm not passing the other attributes.SO I get
Http request error. If I Pass <mx:request> <EnterpriseData
userId="mflex" password="xyz"/> </mx:request> then it
throws the expected error saying the required request parameter
"data" is missing.What to do in this case.
Regards
mflex.

Hi Eric,
Thanks for the reply...
While creating a SOAP service in the ESB, i need to give the WSDL location right??? There instead of browsing from the local directory i need to click the external link button right??? Please let me know there where i can mention the URL ?? Do we need any UDDI registry here ??? if so can you please guide me how to do that aswell...
And also i am facing the problem with the WSDL provided by the Siebel team. There seems to be version mismatch. I am unable to generate XSD for the provided WSDL. JDeveloper was not able to parse the given WSDL. And also in the given WSDL there are more than one part type in the message types. Could you please help me on this....

Similar Messages

How to pass a xml CDATA in string element when OSB calling a webservice?

How to pass a xml CDATA in string element when OSB calling a webservice?
I have a business service (biz) that route to operation of a webservice.
A example of request to this webservice legacy:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:eg="example">
<soapenv:Header/>
<soapenv:Body>
<ex:execute>
<ex:arg><![CDATA[<searchCustomerByDocumentNumber>
<documentNumber>12345678909</documentNumber>
</searchCustomerByDocumentNumber>]]></ex:arg>
</ex:execute>
</soapenv:Body>
</soapenv:Envelope>
the type of ex:arg is a string.
How to pass this CDATA structure to webservice in OSB?

Steps to solve this problem:
1. Create a XML Schema. E.g.:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
 elementFormDefault="unqualified">
 <xs:complexType name="searchCustomerByDocumentNumber">
 <xs:sequence>
 <xs:element name="documentNumber" minOccurs="0">
 <xs:annotation>
 <xs:documentation>
 </xs:documentation>
 </xs:annotation>
 <xs:simpleType>
 <xs:restriction base="xs:string" />
 </xs:simpleType>
 </xs:element>
 </xs:sequence>
 </xs:complexType>
 <xs:element name="searchCustomerByDocumentNumber" type="searchCustomerByDocumentNumber"></xs:element>
</xs:schema>
With this XSD, the XML can be generate:
<?xml version="1.0" encoding="UTF-8"?>
<searchCustomerByDocumentNumber xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="searchCustomerByDocumentNumber.xsd">
<documentNumber>documentNumber</documentNumber>
</searchCustomerByDocumentNumber>
2. Create a XQuery to create a searchCustomerByDocumentNumber ComplexType. E.g.:
(:: pragma bea:global-element-return element="searchCustomerByDocumentNumber" location="searchCustomerByDocumentNumber.xsd" ::)
declare namespace xf = "http://tempuri.org/NovoSia/CreateSearchCustomerByDocumentNumber/";
declare function xf:CreateSearchCustomerByDocumentNumber($documentNumber as xs:string)
as element(searchCustomerByDocumentNumber) {
<searchCustomerByDocumentNumber>
<documentNumber>{ $documentNumber }</documentNumber>
</searchCustomerByDocumentNumber>
declare variable $documentNumber as xs:string external;
xf:CreateSearchCustomerByDocumentNumber($documentNumber)
3. In your stage in pipeline proxy add a assign calling the XQuery created passing the document number of your payload.
Assign to a variable (e.g.: called searchCustomerByDocumentNumberRequest)
4. Create another XQuery Transformation (XQ) to create a request to the webservice legacy. E.g.:
<ex:arg>{fn-bea:serialize($searchCustomerByDocumentNumberRequest)}</ex:arg>
For more information about xquery serialize function:
41.2.6 fn-bea:serialize()
You can use the fn-bea:serialize() function if you need to represent an XML document as a string instead of as an XML element. For example, you may want to exchange an XML document through an EJB interface and the EJB method takes String as argument. The function has the following signature:
fn-bea:serialize($input as item()) as xs:string
Source: http://docs.oracle.com/cd/E14571_01/doc.1111/e15867/xquery.htm

How to receive a xml CDATA in string element when OSB calling a webservice?

How to receive a xml CDATA in string element when OSB calling a webservice?
I have a business service (biz) that route to operation of a webservice.
A example of response to this webservice legacy:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:eg="example">
<soapenv:Header/>
<soapenv:Body>
<ex:executeResponse>
<ex:arg><![CDATA[<searchCustomerByDocumentNumberResponse>
<name>John John</name>
</searchCustomerByDocumentNumberResponse>]]></ex:arg>
</ex:executeResponse>
</soapenv:Body>
</soapenv:Envelope>
the type of ex:arg is a string.
How to receive this CDATA structure to webservice in OSB?

Similiar to the answer How to pass a xml CDATA in string element when OSB calling a webservice?
Use the xquery function fn-bea:inlinedXML rather than fn-ben:serialize
Steps to solve this problem:
1. Create a XML Schema. E.g.:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="unqualified">
<xs:complexType name="searchCustomerByDocumentNumberResponse">
<xs:sequence>
<xs:element name="name" minOccurs="0">
<xs:annotation>
<xs:documentation>
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string" />
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:element name="searchCustomerByDocumentNumberResponse" type="searchCustomerByDocumentNumberResponse"></xs:element>
</xs:schema>
2. Create a XQuery to create a searchCustomerByDocumentNumber ComplexType. E.g.:
3. Create a XQuery Transformation (XQ) to get the CDATA response to the webservice legacy. E.g.:
declare namespace ns0 = "novosiaws";
declare function xf:getReponse($searchCustomerByDocumentNumberResponse as element(ns0:searchCustomerByDocumentNumberResponse))
as element(searchCustomerByDocumentNumberResponse) {
fn-bea:inlinedXML($searchCustomerByDocumentNumberResponse/ns0:arg)
For more information about xquery function:
fn-bea:inlinedXML
The fn-bea:inlinedXML() function parses textual XML and returns an instance of the XQuery 1.0 Data Model.
The function has the following signature:
fn-bea:inlinedXML($text as xs:string) as node()*
where $text is the textual XML to parse.
Examples:
fn-bea:inlinedXML(“<e>text</e>”) returns element “e”.
fn-bea:inlinedXML(“<?xml version=”1.0”><e>text</e>”) returns a document with root element “e”.
Source: http://docs.oracle.com/cd/E13162_01/odsi/docs10gr3/xquery/extensions.html

Error calling COM+ webservice

Hey guys,
I am having problems to call COM+ webservices using Mediator.
My composite needs to call some legacy Delphi DLL that are published in a Windows 2003 COM+ SOAP services.
When I try to call the services using the HTTP Analyser tool, everything works fine. However, when I try to call it in my composite application using a Mediator component, I got the following exception:
javax.xml.ws.soap.SOAPFaultException: **** System.Runtime.Serialization.SerializationException - Parse Error, no assembly associated with Xml key wsa Action.
Have anybody faced problems like this to call COM+ SOAP services?
Here is my COM+ SOAP WSDL:
<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions
name="StringCon"
targetNamespace="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"
xmlns:tns="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"
xmlns:inp1="http://xmlns.oracle.com/singleString"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<wsdl:documentation>
<abstractWSDL>http://anvisa-soa-dev:8001/soa-infra/services/default/StringCon!1.0/StringCon.wsdl</abstractWSDL>
</wsdl:documentation>
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://xmlns.oracle.com/singleString" schemaLocation="http://anvisa-soa-dev:8001/soa-infra/services/default/StringCon/StringCon?XSD=xsd/singleString.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="requestMessage">
<wsdl:part name="input" element="inp1:singleString"/>
</wsdl:message>
<wsdl:message name="replyMessage">
<wsdl:part name="output" element="inp1:singleString"/>
</wsdl:message>
<wsdl:portType name="execute_ptt">
<wsdl:operation name="execute">
<wsdl:input message="tns:requestMessage"/>
<wsdl:output message="tns:replyMessage"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="execute_pttBinding" type="tns:execute_ptt">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="execute">
<soap:operation style="document" soapAction="execute"/>
<wsdl:input>
<soap:body use="literal" namespace="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="StringCon">
<wsdl:port name="execute_pt" binding="tns:execute_pttBinding">
<soap:address location="http://anvisa-soa-dev:8001/soa-infra/services/default/StringCon/StringCon"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Edited by: 904488 on Dec 26, 2011 5:56 AM

soa suite ws binding sends out wsa headers - that is what fails to be parsed on the .NET side ("Parse Error, no assembly associated with Xml key wsa Action.")
there is a flag on the outbound ws binding properties (omit.wsa.headers) that let's you turn this off.

Calling a webservices from Oracle 10G ( 10.2.0.2)

Hi:
I am in the process of putting a database Java stored procedure that can call an external webservices.
PL/SQL Wrapper -> Java Stored Procedure-> External Web services
I loaded the following jars in the dataase.
dbwsa.jar
dbwsclient.jar
1. I am having issues consuming this external webservice from SQL*PLUS. Do you know whether I need to load any other JARS ?
2. How can I debug this issue ? I enabled TCP Monitor in JDeveloper and don't see anything when I call the PL/SQL wrapper in SQL*PLUS.
3. I can use a Java client and tested the Web services OK.
error message:
SQL> l
1 declare
2 x varchar2(100);
3 begin
4
5 x := tester.test_db1();
6* end;
SQL> /
calling
http://XX.XX.YY.121:8988/Application9-ViewController-context-root/MyWebService1S
oapHttpPort
java.rmi.RemoteException: Error parsing envelope; nested exception is:
javax.xml.soap.SOAPException: Error parsing envelope
at
view.proxy.runtime.MyWebService1SoapHttp_Stub.sayhello2(MyWebService1SoapHttp_St
ub.java:99)
at
prpd.MyWebService1SoapHttpPortClient.sayhello2(MyWebService1SoapHttpPortClient.j
ava:41)
at prpd.TEST_DB.TEST_DB1(TEST_DB.java:21)
Caused by: javax.xml.soap.SOAPException: Error parsing envelope
at
oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplemen
tation11.java:103)
at oracle.j2ee.ws.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:75)
at oracle.j2ee.ws.saaj.soap.MessageImpl.getSOAPBody(MessageImpl.java:934)
at
oracle.j2ee.ws.client.StreamingSender._preHandlingHook(StreamingSender.java:692)
at oracle.j2ee.ws.client.StubBase._preHandlingHook(StubBase.java:688)
at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:207)
at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
at
view.proxy.runtime.MyWebService1SoapHttp_Stub.sayhello2(MyWebService1SoapHttp_St
ub.java:76)
... 2 more
Caused by: java.lang.IllegalArgumentException
at oracle.xml.parser.v2.XMLParser.setAttribute(XMLParser.java:794)
at
oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplemen
tation11.java:54)
... 9 more
PL/SQL procedure successfully completed.
SQL> /
thx
Raj

thanks Tugduall for the comments. here are the instructions I followed to create a java stored procedure that can call a webservices. Unfortunately, this seems like a very complex task. Do you have any ideas how I could debug or troubleshoot this issue ?
Please note that I used JDeveloper to generate the client code.
========================================================
1. download the dbws-callout-utility-10R2.zip from OTN at:
http://www.oracle.com/technology/sample_code/tech/java/jsp/dbwebservices.html
2. create an application/project with 1.4 JDK.
3. create a web service by ‘Business Tier’->Web Service->Web Service Proxy->UDDI
4. next… to ‘Search for’, type ‘quote’.
5. from the list select one. For me ‘Quote of day’ was picked.
6. click Next all the way to Finish.
7. from the ‘Application Sources’ select ‘QuotoProxy’ then find its main method.
8. at the section
// Add your own code here, add the line like:
System.out.println("quote "+myPort.getQuote());
9. run it to see its return.
10. cteate a class that has a method to call client method to be invoked (static)
like the following:
package dbws;
import dbws.QotdPortClient;
public class MainClientStub {
public MainClientStub() {
public static String getMyQoute(){
QotdPortClient myClient = null;
try {
myClient = new QotdPortClient();
return myClient.getQuote();
} catch (Exception e) {
e.printStackTrace();
return null;
note that the package name in your project.
11. create a deployment profile as ‘JAR File’. Uncheck the box ‘Project Dependencies’
12. deploy it to the local box. ‘Deploy to JAR File’.
13. unzip the dbws-callout-utility-10R2.zip to get dbwsa.jar.
14. execute the following from command line:
loadjava –user test/[email protected] -resolve –verbose –synonym –grant public to dbwsa.jar myarchive1.jar
loadjava -user test/test@orcl1020 -resolve -verbose -synonym -genmissing -grant public myarchive1.j
ar dbwsa.jar
loadjava -user sys/<sys_pass> -resolve -verbose -synonym -genmissing -grant public myarchive1.jar dbwsa.jar
15. create a function like the following:
CREATE OR REPLACE FUNCTION teststub RETURN VARCHAR2 AS
LANGUAGE JAVA NAME ‘dbws.MainClientStub.getMyQoute() return java.lang.String’;
16. Run at sqlplus: Select teststub from dual;
======================================================

Error calling a webservice from one server process of the cluster

Hi ,
I have a servlet which on startup makes a call to a webservice. I deploy this webapp on the cluster.
The cluster has two instances each instance having one server process.
So when the server restarts one server process on one instance calls the web service the other process on other instance fails with a 503 response code.
When I tried to reproduce the same problem using two server processes on the same instance both processes are able to call the webservice properly.
I am slightly confused as to how different the second scenario is from first one as both are individual server process and may or may not run on same instance.
Can anyone tell me the real cause.
Rgds
Shashank

Hi Rajat,
This is how the default trace looks
FATAL: Application Servlet failed to notify devices.
Caught java.rmi.RemoteException: Service call exception; nested exception is:
 com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://<<server>>:50000/ManagementService/ManagementService?style=document"
 at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1289)
 at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1298)
 at com.om.ApplicationServlet$NotifyDevices.run(ApplicationServlet.java:86)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://<<server>>:50000/ManagementService/ManagementService?style=document"
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:980)
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)
 at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1282)
 ... 2 more
java.lang.NoSuchMethodError
at java.lang.Thread.destroy(Thread.java:779)
 at com.omApplicationServlet$NotifyDevices.run(ApplicationServlet.java:92)
Rgds
Shashank

Problems calling a Webservice

Hi All!
I'm having some problems calling a Webservice. I've created a deployable proxy and a client bean and from this bean I've generated a Webservice. When I test this Webservice the actual webservice call is succesfull but I get the following response from the Webservice:
HTTP/1.1 200 OK
Connection: close
Date: Fri, 13 May 2005 10:26:37 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR ADM DEV PSA PSD HIS OTP OUR IND STA"
X-Powered-By: ASP.NET
X-Powered-By: PHP/4.3.9
Status: 200 OK
Server: PEAR-SOAP 0.8.0RC2-devel
Content-Type: text/xml; charset=UTF-8
Content-Length: 1887
X-Zend-WinEnabler: 1.2.0
 
Notice: Undefined property: actor in C:Program FilesZendWinEnablerphppearSOAPServer.php on line 318 
Notice: Undefined property: mustunderstand in C:Program FilesZendWinEnablerphppearSOAPServer.php on line 322 
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/ ....etc"
As you can see there is some HTML code in the response. This HTML code causes problems for the SAP parser as it expects a SOAP:Envelope and not some HTML junk.
I've looked up what the properties mustunderstand and actor do in a SOAP header and they seem to be optional properties. On the Webservice side the SOAP parser unfortunately seem to think these properties are mandatory.
There's probably two ways to solve this problem. The first way is to ask the guys who host this Webservice to change it are their side. The other option is to add these properties to the SOAP header on the SAP side....which brings me to my question: Is there any way to add these two properties to the SOAP header before the deployable proxy calls the Webservice?

Hi Arnouid,
as far as I understand your post, the HTML code is the body of the response.
If it is so, it is not a correct SOAP-message. A SOAP header is inside of the envelope and not outside of it.
So, it is not very a big surprise, that the parser don't like this.
Aside from the form of a SOAP-message, it is not even a XML-message, which must begin with <?xml...
tom

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

Calling Java WebService from Adobe

Hi,
Iam using a simple java service. I need to call this WebService from my Online/Offline forms.
When Iam running the form in Portal , Iam getting the following error:
Error attempting to read from file :
http: / / hostname:port/ServiceName/Config1?Style=document.
The way I imported the wsdl. Saved wsdl , merged 3 wsdls and imported in Adobe Form.
Please let me know is there anything else missing here?
Thanks,
Uma.A
Edited by: Uma Anbazhagan on Sep 28, 2009 8:20 PM

Hi,
Regarding this question, I was able to save the wsdl file, make relevant changes as mentioned in help document and consume it.
However , without authentication WS worked fine. The WS with authentication is having issues.
Need to try with latest version and see if this is resolved.
Thanks,
Uma.

Error calling SAP webservice

Hi,
I have created a ZBAPI that is published as webservice via SE37 --> using the wizard, and I have created a flex web that invoke this webservice. When I runs the web in my local the call to webservice works perfect, but when I deploy the web in my Composite Environment and I execute the web I get the following error:
[RPC Fault faultString="Security error accessing url" faultCode="Channel.Security.Error" faultDetail="Unable to load WSDL. If currently online, please verify the URI and/or format of the WSDL (http://xxxxxxxxxxxx:8000/sap/bc/srt/wsdl/bndg_4A02EE1AE83732C2E10000000AA51C62/wsdl11/allinone/standard/document?sap-client=330)"]
I have been searching the solution and only I have found to deploy in the server (Composite Environmentt) the crossdomain.xml in the root, but it doesn't work.
the crossdomain.xml content is:
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
 <site-control permitted-cross-domain-policies="all"/>
 <allow-access-from domain="*" secure="false"/>
 <allow-http-request-headers-from domain="" headers="" secure="false"/>
</cross-domain-policy>
and the route where is deployed is:
D:\usr\sap\XXXX\J00\j2ee\cluster\apps\sap.com\com.sap.engine.docs.examples\servlet_jsp\_default\root
any idea?
thanks in advance
Jose Manuel

Dear Vinay,
Does your other FM are also using arrays.?
Deserialization problem comes when xml parser is not able to convert XML schema or values to language specific elements.
And this problem normally comes if you are using complex data types.
Can you check once again and reply.
Regards,
Piyush

What is the url for calling a webservice which takes boolean input

Hi
Can anyone help me out to know how to call a webservice which takes boolean as input? Here my webservice is developed in Java.
Regards

I'm not sure what your context is, but you can test out your new Web Service by using soapui (www.soapui.org). Assuming your using a literal format, the encoding information will not be required in the XML elements. Therefore your message could be:
<element>true</element>

How to call java webservice from plsql procedure.

Hi,
Could any one please provide any reference document for invoking a java webservice from pl/sql procedure.
regards,
Venkat

Hi,
There are basically various platforms where u develop the code with different patterns, though the idea is same everywhere.
1. If you want develop a Java Client to call a WebService from NWDS then Pls refer >>
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/cb2e29578c0262e10000000a11466f/frameset.htm
Note: By default the WebService developed under NWDS is Document Based WebService (i.e. In WSDL the style element would be 'document')
2. If you want to call a WebService from the platform other than NWDS than, Sun's official site would be the best choice to go for.
Pls refer >>
http://java.sun.com/developer/technicalArticles/J2EE/j2ee_ws/#design
Would appreciate if you reward the points if the answer is helpful.
Regards,
Arvind Kugasia [[email protected]]

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;?

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 having an abstract element

Similar Messages

Maybe you are looking for