Problem in consuming a WSDL of ME in MII

Hi Experts,
I am trying to consume a ME data in MII by using ME standard webservice.Its working fine in SOUP UI 4.0.0.But same url m trying to give MII webservice action block.its returning nothing. I am trying to pass Item,Revision,Site and I want to get remaining details of that item. I am using 12.1 build 8.Here is my Url
http://<hostname>:<port>/manufacturing-services/ItemServiceService?WSDL.
Thanks,
Eswaraiah M

Hi,
use webservice action block in transaction then assign webservice data to local parameter.
Thanks,
Ramesh

Similar Messages

Problem with Consuming ABAP Server Proxy WSDL in InfoPath

Tried to design a InfoPath (MS Office 2003) form from a WSDL file of a web service generated from an ABAP Server Proxy in a NW2004s SP10 system. InfoPath rejected this WSDL with error InfoPath cannot use the selected Web service method for receiving data because the method does not provide valid XML data. Tried other WSDL files from other web services from ABAP Proxy with InfoPath, all got rejected.
Validated the WSDL file with XMLSPY, no error. Tried to import the WSDL into XI 3.0, no error. Also tried the WSDL in .NET C#, also worked fine. It seemed only InfoPath does not like this WSDL from ABAP Proxy.
Created a similar web service in XI 3.0 and InfoPath had no problem with its WSDL. Then I compared the two WSDL files. There are differences. After try and error on changing the differences, I have nailed down to the XML tag that caused the problem. Please see the extracted WSDL line attached at the end. In the XI 3.0 generated WSDL the wsdl:message and the wsdl:part have the same name. In the ABAP Proxy generated WSDL the wsdl:part has the name Parameters which is different from the wsdl:message. After I copied the wsdl:message name to the wsdl:part name, InfoPath accepted the WSDL file without any problem.
I know the fix but I like to find out the root cause. Is this a known issue? Did we miss some configuration setting thats causing this issue? Any help will be much appreciated.
WSDL from NW2004s SP10 ABAP Proxy
<wsdl:message name="RegionR3GetList_Req_MT">
 <wsdl:part name="Parameters" element="tns:RegionR3GetList_Req_MT"/>
</wsdl:message>
<wsdl:message name="RegionR3GetList_Resp_MT">
 <wsdl:part name=" Parameters" element="tns:RegionR3GetList_Resp_MT"/>
</wsdl:message>
WSDL from XI 3.0 Interface
<wsdl:message name="RegionR3GetList_Req_MT">
 <wsdl:part name="RegionR3GetList_Req_MT" element="tns:RegionR3GetList_Req_MT"/>
</wsdl:message>
<wsdl:message name="RegionR3GetList_Resp_MT">
 <wsdl:part name="RegionR3GetList_Resp_MT" element="tns:RegionR3GetList_Resp_MT"/>
</wsdl:message>

Anne Tarnoruder has pointed out to me that her SDN article "Consuming SAP Enterprise Services in a Microsoft Office InfoPath Form" has described the the cause and workaround of this issue on page 9. I am extracting it below and mark this thread as answered. Thanks to Anne but not sure how I can award point to her.
Currently SAP supports only the Document style of WSDL, and not the Microsoft-specific RPC style, which causes a problem when consuming SAP services in the Microsoft environment. In this example, you need to apply a workaround that involves a minor correction of locally-stored WSDL files:
a. In the Project Explorer toolbar, click the Show all files icon and expand the Web reference folder.
b. For each Web reference in the project, perform the following steps:
c. Open the WSDL file, replace all instances of <wsdl:part name="parameters" with <wsdl:part name="parameter" (remove the s in parameters) and save the file.
d. Right-click the Reference.map file and choose Run Custom Tool to invoke a utility that generates code for XML Web services. This recreates the local proxy.

Problems with consuming SAP BW WSDL in Crystal Reports 2008

Hello,
I am trying to use the WSDL generated from the SAP BW in Crystal Reports 2008 using the XML and Web Services driver, but when I input the WSDL url Crystal does not interpret the url passed in as a WSDL url and the Services, Port and Method drop downs are blank.
If I manually input the values I get the error below from Crystal
"Logon failed.
Details: Web Service Location is invalid
WSDL Exception (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL:Encountered unexpected element
'Policy'."
I know this is a valid WSDL as I have tested it with Xcelsius 2008 and I am able to get data back in Xcelsius. I found SAP note 1485601 that talks about Crystal Reports not being able to reading a WSDL generated by a SAP system.
           https://websmp230.sap-ag.de/sap/support/notes/1485601
Based on the error message from Crystal above I feel that Crystal is unable to read the WSDL URL, has anyone else encountered this issue, if so is there a possible work around.
We are running Crystal Reports 2008 V1 SP3 FP 3 and the SAP Integration Kit is also on the same service pack and patch level.
Any help or insight into the issue will be very helpful.
Thanks,
Kumar

Ingo,
I am using the "XML and Web Services" connection option in Crystal Reports, and using a HTTP WSDL.Here is a sample of how WSDL url generated by SAP BW.
http://servername:8000/sap/bc/srt/wsdl/bndg_DF6E553E117931F19C6B001560A1B616/wsdl11/allinone/ws_policy/document?sap-client=100
We have a two structure BW query (one for keyfigures and one as characteristic structure ), I know that this will cause the structure for the characteristics to show up as a single field and each element of the structure will result in a row of data, but we need the individual elements on the structure and we were hoping to get around the MDX driver limitation by using the web service connection.
The data in the Crystal Reports 2008 needs to be in a crosstab layout as shown below, but if we use the Crosstab expert the key figures are stacked one under the other and also we cannot get the labels from the KPI structure to show up on the Crystal Reports.
               Characteristic Structure
             Column1            Column2                     Column3
Label 1          KeyFigure 1          KeyFigure 2                    KeyFigure 3
Label 2          KeyFigure 1          KeyFigure 2                KeyFigure 3
Label 3          KeyFigure 1          KeyFigure 2                    KeyFigure 3
This layout is already built in a Web Template and therefore we were planning on using the WSDL to get the layout directly into Crystal report, but I keep running into the WSDL error when I try to consume the WSDL in Crystal.
Thanks,
Kumar

Error in Consuming external WSDL in ABAP

Dear Gurus,
I am trying to consume a WSDL in ABAP using enterprise services in SE80. After load the WSDL and making logical port, when i test the WSDL, it gives an error : (SOAP:1.008 SRT: Couldn't create Object: ("ICF Error when creating HTTP client object by Config for U )
Can any body tells what is the cause of this error? I tried but unable to resolve the problem. Help from integration and ABAP gurus is required. Thanks

Hello Imran,
Have you tried, or is it practicable for your situation, to create the consumer service and the logical port using the URL directly, instead of a local file? (as you have shown in your print, it looks to me that it's local file)
Maybe you can check if this WS has been used normally by other consumers, or even test it with SoapUI to guarantee it is functional (also to compare the requests). You could put this WSDL under a validation tool, i know that SAP does it when the WSDL is under processing, and it goes wrong when some elements/attributes aren't supported ... and i see you could upload it successfully, but despite of it is good to double check.
Good luck!
Renan

Error target namespace must be absolute URI when consuming external WSDL

Hi,
I'm trying to consume external WSDL which has relative target namespace.
Through SE80 transaction I select Create -> Enterprise Server -> Service Consumer.
I have tried with URL and local file options but the result is the following in both cases:
At the en of the wizard I receive the errors "exception in Error-Handler" and "Error target namespace must be absolute URI".
I'm on ECC 6.0 SP 18.
Anybody knows how to solve this problem? Maybe is not possible to consume external WSDL with relative URI?
Thanks
Regards

Hi,
I think the problem is that the WSDL is not WS-I compliant.
I have found note 1327511 (Limiations and common problems in ABAP WSDL processing) and with the report RSSIDL_DESERIALIZE_DEMOI have found the same error.
Anybody can confirm this?
Is there any other document or reference where SAP indicates this fact?
Thanks
Regards

Problem with RPC/encoded WSDL

I'm having trouble calling a web service that is based on an RPC-encoded WSDL. I've already made slight changes to the WSDL, so that I get a work-able message type for mapping purposes. These changes are based on <a href="http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16556272">soapenc:Array recommendations in WSDL 1.1 Section 2.2</a> for declaration of array types.
Here's a snippet of the WSDL:
<wsdl:definitions ...>
<wsdl:types>
 <schema ...>
 <complexType name="ArrayOf_tns1_ServiceOption">
 <complexContent>
 <restriction base="soapenc:Array">
 <attribute ref="soapenc:arrayType"
 wsdl:arrayType="tns1:ServiceOption[]"
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>
 </restriction>
 </complexContent>
 </complexType>
 </schema>
 <schema ...>
 <complexType name="ServiceOption">
 <sequence>
 <element name="key" nillable="true"
 type="xsd:string"/>
 <element name="value" nillable="true"
 type="xsd:string"/>
 </sequence>
 </complexType>
 </schema>
</wsdl:types>
</wsdl:definitions>
I've changed it to:
<wsdl:definitions ...>
<wsdl:types>
 <schema ...>
 <complexType name="ArrayOf_tns1_ServiceOption">
 <sequence>
 <element name="ServiceOption"
 type="tns1:ServiceOption"
 minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
 </complexType>
 </schema>
 </schema>
 <schema ...>
 <complexType name="ServiceOption">
 <sequence>
 <element name="key" nillable="true"
 type="xsd:string"/>
 <element name="value" nillable="true"
 type="xsd:string"/>
 </sequence>
 </complexType>
 </schema>
</wsdl:types>
</wsdl:definitions>
The above changes have allowed me to make message mappings. But the I still get an error when sending a request to the web service. It seems that it requires the xsi:type and soapenc:arrayType attributes for arrays.
How can I create these attributes? How does XI handle RPC-encoded WSDLs? I haven't encountered these problems with document-literal WSDLs.
Thanks in advance.

Hi Lorenzo,
the extended support of rpc-style does not include the support of soapenc:array. It just addresses the root of the message and its direct children (as discussed in the thread where I added this hint).
In the documentation of External Definitions you can find a hint where to find a list of supported XSD/DTD/WSDL-features. However, also there you will find no hint on the fact that soapenc:array is not supported. The reason for this is, that soapenc:array is specified in none of these standards. It is some artifact that SOAP smuggled into XSD. For good reasons WS-I prohibits the use of this artifact.
Hence, if you need support for argumentation I can only point out the WS-I document I already linked.
Greetings
Stephan

PI - Problem with a receive WSDL message with encode (envelope)

Hello,
I'm having a ploblem with a PI interface with the scenario below (synchronous):
ECC (proxy) <-> PI <-> 3rdParty (soap)
The WSDL provided has a kind of envelope (soapenc:arrayType). Here's the structure declaration:
 <xs:complexType name="TTUDResultArray">
 <xs:sequence>
 <xs:element name="Success" type="xs:boolean" />
 <xs:element name="ErrorDescription" type="xs:string" />
 <xs:element name="Count" type="xs:int" />
 <xs:element name="Accounts" type="ns1:TTUDInquiryResultArray" />
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="TTUDInquiryResultArray">
 <xs:complexContent>
 <xs:restriction base="soapenc:Array">
 <xs:sequence />
 <xs:attribute xmlns:n1="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType" n1:arrayType="ns1:TTUDInquiryResult[]" />
 </xs:restriction>
 </xs:complexContent>
 </xs:complexType>
When I import this WSDL as a External Definition, the field Accounts is displayed with error (in red), as the PI was incapable to read this kind of type definition.
Testing in SoapUI, the response message is displayed with a different structure than it's possible to see in the PI Operation Mapping:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
 <SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:NS2="urn:TUDIntf">
 <NS1:InquireDateRangeResponse xmlns:NS1="urn:TUDIntf-ITUD">
 <return href="#1"/>
 </NS1:InquireDateRangeResponse>
 <NS2:TTUDResultArray id="1" xsi:type="NS2:TTUDResultArray">
 <Success xsi:type="xsd:boolean">true</Success>
 <ErrorDescription xsi:type="xsd:string"/>
 <Count xsi:type="xsd:int">2</Count>
 <Accounts xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="NS2:TTUDInquiryResult[2]">
 <item href="#2"/>
 <item href="#3"/>
 </Accounts>
 </NS2:TTUDResultArray>
 <NS2:TTUDInquiryResult id="2" xsi:type="NS2:TTUDInquiryResult">
 <AvailableAmount xsi:type="xsd:double">49</AvailableAmount>
 <PaymentAmount xsi:type="xsd:double">49</PaymentAmount>
 <PaymentStatus xsi:type="xsd:string">AC</PaymentStatus>
 <PaymentNbr xsi:type="xsd:string">110201</PaymentNbr>
 <Success xsi:type="xsd:boolean">false</Success>
 </NS2:TTUDInquiryResult>
 <NS2:TTUDInquiryResult id="3" xsi:type="NS2:TTUDInquiryResult">
 <AvailableAmount xsi:type="xsd:double">50</AvailableAmount>
 <PaymentAmount xsi:type="xsd:double">50</PaymentAmount>
 <PaymentStatus xsi:type="xsd:string">AC</PaymentStatus>
 <PaymentNbr xsi:type="xsd:string">123456</PaymentNbr>
 <Success xsi:type="xsd:boolean">false</Success>
 </NS2:TTUDInquiryResult>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I`ve tried to map the WSDL inside my interface, but always I test (on SPROXY or Runtime Workbench) an error message is displayed:
Error While Sending Message: Error stack from response: Runtime exception occurred during application mapping com/sap/xi/tf/_mmInquireEZCashtoEcc_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:mtInquireEcc_response. Values missing in queue context. Targe~
Someone knows if that's some tip of how to use this kind of WSDL?

Hello,
Looks like an RPC style WSDL to me. Can you ask the third-party to provide you with a document-literal wsdl? You can refer to the points mentioned by Stephan in this thread.
Problem with RPC/encoded WSDL
Thanks to Raj for pointing out that I did not have the thread link
Hope this helps,
Mark
Edited by: Mark Dihiansan on Dec 12, 2011 2:34 AM

Process to consume a WSDL file in ABAP without using XI

Hi all,
I want to know if we can consume a WSDL file in ABAP without using XI?
I have developed a lot of web services and gave WSDL file to respective teams.
Now i need to consume a WSDL file in ABAP and i dont know how to do it.For creating a web service i use the web service wizard in SE37.
Now i need to consume a WSDL file in ABAP . The WSDL file is from a third party organization. how can i consume a WSDL file in ABAP without using XI. What is the process to consume a WSDL file in ABAP without using XI
Please help me with process and some sample code to consume a WSDL file in ABAP without using XI
Regards,
Jessica Sam.

Depending on your release the process is a little bit different.
For NW 2004, see these instructions.
http://help.sap.com/saphelp_NW04/helpdata/en/bf/d005244e9d1d4d92b2fe7935556b4c/frameset.htm
For NW 7.0 see these instructions, in NW 7.0, you will, use the SOAMANAGER transaction to configure logical ports and other stuff, this replaces transaction WSADMIN and LPCONFIG.
http://help.sap.com/saphelp_nw70/helpdata/EN/bf/d005244e9d1d4d92b2fe7935556b4c/frameset.htm
Regards,
Rich Heilman

Consuming Deployed WSDL

Hello,
I am new to BPEL, I have tried only hello world program in JDeveloper.
1) Now i want to consume a WSDL file which is deployed on stand alone OC4J application server.
How can i do that.
2) I am not able to run two server i.e; BPEL and oc4j at same time.
My web service need oc4j to run and to deploy or consume web service in BPEL i need BPEL server.
so how can i run both on same system, or what is the other solution.

Hi,
Welcome to the world of SOA !!!
Jdeveloper - This is an IDE to develope SOA composites.
OC4J Server - This server is used on SOA 10g.
Weblogic Server - This server is used in SOA 11g
Are you using SOA 10g or SOA 11g ?
To test your composite / bpel component you need to run either on 10g (OC4J with BPEL engine) or 11g (weblogic with BPEL engine).
You can also configure JDeveloper embedded server.
Which one u got ?
Thanks,
Vijay

Problem in consuming web service from esworkplace

Hello
I am useing CE7.2 evaluation version
I want to consume a web service from SAP workplace
I've built a process composer project then I tried to import a WSDL and chose the "service registry" option
However I keep getting the message "internal error in the services registry"
BTW u2013 I defined the "esworkplace" as the services registry in the Preferences.
Any ideas what can be the problem? Thanks.
Thanks

Hi Experts,
Please help me with this issue. I am really stuck up here.
Thanks,
Radhika

Problem at Consume WEB Service in ABAP

hello!!
I tell them my problem, is to create a web service from the SE80, which could be used properly.
Then there was a change of server, which migrated to the developments and the web service is recreation, but this can not be consumed.
now I need help, is where do I indicate that the basis so that they can return to consume web services, what services or settings should be activated.
any suggestion or help are welcome.
The ECC system is a 5 AS ABAP only.
from now, I appreciate any help or guidance I can get.

What is the problem? Are all the services active in SICF for web services and how is the web service being consumed is it through a wsdl file ?

Problem with consuming web services in Flex

So i'm trying to set up a basic flex application to consume a
web service (POJO exposed with axis2). Here's the WSDL:
<wsdl:definitions xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"
xmlns:axis2="
http://ws.apache.org/axis2"
xmlns:mime="
http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:http="
http://schemas.xmlsoap.org/wsdl/http/"
xmlns:ns0="
http://webservices.emailcenter.pas/xsd"
xmlns:soap12="
http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:ns1="
http://org.apache.axis2/xsd"
xmlns:xs="
http://www.w3.org/2001/XMLSchema"
xmlns:soap="
http://schemas.xmlsoap.org/wsdl/soap/"
targetNamespace="
http://ws.apache.org/axis2">
<wsdl:types>
<xs:schema xmlns:ns="
http://webservices.emailcenter.pas/xsd"
targetNamespace="
http://webservices.emailcenter.pas/xsd"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<xs:element name="getTime">
<xs:complexType />
</xs:element>
<xs:element name="getTimeResponse">
<xs:complexType>
<xs:sequence>
<xs:element type="xs:string" name="return" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>
<wsdl:message name="getTimeMessage">
<wsdl:part element="ns0:getTime" name="part1" />
</wsdl:message>
<wsdl:message name="getTimeResponse">
<wsdl:part element="ns0:getTimeResponse" name="part1"
/>
</wsdl:message>
<wsdl:portType name="SimpleServicePortType">
<wsdl:operation name="getTime">
<wsdl:input message="axis2:getTimeMessage" />
<wsdl:output message="axis2:getTimeResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding type="axis2:SimpleServicePortType"
name="SimpleServiceSOAP11Binding">
<soap:binding style="document" transport="
http://schemas.xmlsoap.org/soap/http"
/>
<wsdl:operation name="getTime">
<soap:operation style="document" soapAction="urn:getTime"
/>
<wsdl:input>
<soap:body namespace="
http://ws.apache.org/axis2"
use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body namespace="
http://ws.apache.org/axis2"
use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding type="axis2:SimpleServicePortType"
name="SimpleServiceSOAP12Binding">
<soap12:binding style="document" transport="
http://schemas.xmlsoap.org/soap/http"
/>
<wsdl:operation name="getTime">
<soap12:operation style="document"
soapAction="urn:getTime" />
<wsdl:input>
<soap12:body namespace="
http://ws.apache.org/axis2"
use="literal" />
</wsdl:input>
<wsdl:output>
<soap12:body namespace="
http://ws.apache.org/axis2"
use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding type="axis2:SimpleServicePortType"
name="SimpleServiceHttpBinding">
<http:binding verb="POST" />
<wsdl:operation name="getTime">
<http:operation location="getTime" />
<wsdl:input>
<mime:content type="text/xml" />
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SimpleService">
<wsdl:port binding="axis2:SimpleServiceSOAP11Binding"
name="SimpleServiceSOAP11port0">
<soap:address location="
http://10.1.1.149:8080/axis2/services/SimpleService"
/>
</wsdl:port>
<wsdl:port binding="axis2:SimpleServiceSOAP12Binding"
name="SimpleServiceSOAP12port0">
<soap12:address location="
http://10.1.1.149:8080/axis2/services/SimpleService"
/>
</wsdl:port>
<wsdl:port binding="axis2:SimpleServiceHttpBinding"
name="SimpleServiceHttpport0">
<http:address location="
http://10.1.1.149:8080/axis2/rest/SimpleService"
/>
</wsdl:port>
</wsdl:service>
the code for my application is very simple and
straightforward:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute" creationComplete="ss.getTime()">
<mx:WebService id="ss" wsdl="
http://10.1.1.149:8080/EmailCenter/services/SimpleService?wsdl">
<mx:operation name="getTime"/>
</mx:WebService>
<mx:DataGrid
dataProvider="{ss.getTime.lastResult}"></mx:DataGrid>
</mx:Application>
when I try to consume this in my flex application I keep
getting the following error:
[RPC Fault faultString="Required parameter 'getTime' not
found in input arguments." faultCode="Client.Input"
faultDetail="null"]
at
mx.rpc.soap::Operation/mx.rpc.soap:Operation::createFaultEvent()
at mx.rpc.soap::Operation/
http://www.adobe.com/2006/flex/mx/internal::invokePendingCall()
at mx.rpc.soap::Operation/
http://www.adobe.com/2006/flex/mx/internal::invokeAllPending()
at mx.rpc.soap::WebService/::unEnqueueCalls()
at mx.rpc.soap::WebService/
http://www.adobe.com/2006/flex/mx/internal::wsdlHandler()
at
flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.rpc.soap::WSDLParser/dispatchEvent()
at mx.rpc.soap::WSDLParser/::parseCompleted()
at mx.rpc.soap::WSDLParser/
http://www.adobe.com/2006/flex/mx/internal::httpResultHandler()
at
flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::resultHandler()
at mx.rpc::Responder/result()
at mx.rpc::AsyncRequest/acknowledge()
at ::DirectHTTPMessageResponder/completeHandler()
at
flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/flash.net:URLLoader::onComplete()
Any advice anyone could give would be wonderful. I'm pretty
new at this flex stuff but I feel like the problem may be with my
WSDL?

perhaps you missed this step:
--> Modify the code and add Credentials before calling the web method:
Public
SubMain()
Dim
ws As NewService1
ws.Credentials =
New System.Net.NetworkCredential("user name",
"password",
"domain name")
MsgBox("Square
of 2 = "& ws.Square(2))
Dts.TaskResult = Dts.Results.Success
End
Sub
Arthur
MyBlog
Twitter

How to Consume a WSDL file in Webdynpro JAVA Application 7.30

Hi Experts,
My requirement is,I have a wsdl file(Provided by the SAP PI) which i need to consume in Webdynpro Java 7.3(NWDS 7.30).
I has been tried in the follwing way
1.First click on the Model --> Adaptive Web Service Model -->Model Name--Package Name
2.Choose Remote Location/File System.
3.After that choose the WSDL file from my project which i added earlier.
4.After that I get the node in the context menu.But I am uneble to set some data into the node and also uneble to get data data from the node
After deploying my project I get the following error.
Error ::
The initial exception that caused the request to fail, was:
com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: Configuration not found for service reference with ID: c73e38ff-a4d8-4e4c-89c2-827fd5cf17ac from application demo.sap.com/mwebsrvc. Either you have not assigned the Service Group to a Provider System or the generation of the configuration has failed. Check the configuration details from SAP NetWeaver Administrator -> Application Communication. --> Details about the Service Reference: {urn://TestSOAPtoRFCSender}SI_TestSOAPtoRFCSender_OB; Service Group: com.tsecl.SITestSOAPtoRFCSender_OB.pidev_nerapdrp_gov_in; Service Group Software Component: demo.sap.com/mwebsrvc; Service Group Application: demo.sap.com/mwebsrvc; Configuration state: Not configured
 at com.sap.esi.esp.service.server.dynamic.DIIServiceRefConfigContextImpl.prepareContext(DIIServiceRefConfigContextImpl.java:275)
 at com.sap.esi.esp.service.server.dynamic.DIIServiceRefConfigContextImpl.<init>(DIIServiceRefConfigContextImpl.java:59)
 at com.sap.esi.esp.service.server.dynamic.DIIContextCreatorImpl.createDIIServiceRefConfigContext(DIIContextCreatorImpl.java:18)
 at com.sap.engine.services.webservices.espbase.client.dynamic.configuration.DIIContextFactory.createDIIConfigurationsContext(DIIContextFactory.java:12)
 at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:368)
 ... 67 more
Please help me about this.
Thanks and Regards,
Amit Basak

Hi Amit,
Create provider system in NWA -> SOA management -> System Connections. After ping is successful go to NWA -> Application Communication and select your DC and assign the provide system for your service configuration group.
I hope it will works fine as we also did the same.
- Pradeep

Problem while consuming external webservice

Hi,
I tried consuming webservice through se80->Enterprise Service->Service consumer.
For SAP webservices i am able to consume it. It is creating proper proxies.
But I tries it using with external WSDL url. It is saying error as
'Incorrect value: Unknown namespace http://www.w3.org/2001/XMLSchema'
Please help
Regards,
Dhana

Hi,
I have given this URL 'http://ws.cdyne.com/WeatherWS/Weather.asmx?WSDL'.
Now it is showing the following error
Exception occured in library handler.Not implemented.
Exception of class CX_SIDL_INTERNAL_ERROR
Please have a look into it
Regards,
Dhana

Error while consuming external WSDL file

Hi,
I have created the client proxy for the WSDL file(i.e. .Net webservice's WSDL file). While creating the logical port it is giving the error,
'Error: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL '. Please help to solve this problem.

Hi,
Thanks. I checked with program you have given, while executing it is displaing the WSDL file as inconsisten value as follows,
<sidl:DEFINITION xmlns:sidl="http://xml.sap.com/2006/08/esi/sidl/dump">
<sidl:consistencyCheck>Incorrect value:</sidl:consistencyCheck>
- <sidl:registry assigned="true">
- <sidl:entityContainer>
- <sidl:documentNamespace namespace="http://schemas.xmlsoap.org/wsdl/">
<sidl:entity targetNamespace="http://tempuri.org/" location="http://tedweb2k3.wipro.com/PublishCopy/TTWis/tt.asmx?wsdl" />
</sidl:documentNamespace>
- <sidl:documentNamespace namespace="http://www.w3.org/2001/XMLSchema">
<sidl:entity targetNamespace="http://www.w3.org/2001/XMLSchema" location="" />
<sidl:entity targetNamespace="http://tempuri.org/" location="" />
</sidl:documentNamespace>
</sidl:entityContainer>
</sidl:registry>
Please help me in this regard.

Problem in consuming a WSDL of ME in MII

Similar Messages

Maybe you are looking for