on 12-28-2006 7:28 AM
Hello everybody,
we try to call a WebService in Microsoft CRM.
The microsoft developer gave us a WSDL. This one seems to be very dynamic.
Do you have any god links, tutorials?.
Thanks a lot
Regards Mario
null
Hi Mario,
Is it a Document literal WSDL or a RPC encoded one? Take a look at this note: 856597, where you have a question on the type of WSDL and also on converting from one style to another for compatibility.
>>The microsoft developer gave us a WSDL. This one seems to be very dynamic.
Could you elaborate on this.
Regards,
Chandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chandra & Bhavesh,
thanks for your reply.
Unfortunately this does not solve the problem.
Read this:
http://www.biztalk-adapter.de/biztalk_eng/faq_crm.asp?navid=4
Regards Mario
Mario,
Did u try to invoke a simple webservice first from XI? go to www.xmethods.com, there you can find lot of simple web services with wsdl file available. Just try executing one webservice from there, then u'll get an idea as how to invoke the Microsoft CRM web service. Technically any webservice should be same.
--Archana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mario,
SOAP adapter FAQ --> http://service.sap.com/notes --> note number : 856597
Not sure if it actually helps though!
<i>Does the RPC or Document style in WSDL play a role in the SOAP adapter?
A: No. These styles are used in WSDL to describe how the message is represented as a SOAP message. And this corresponds to how the XI payload is represented. You must make sure that your XI proxy is generating the valid payload according to the given WSDL in whatever the style. If this is not the case (e.g., your proxy is generated by another WSDL and there is a mismatch in how the payload must look), you need to configure some mapping to match the payload.
Related Questions "Can I convert an RPC styled WSDL to a document styled WSDL?"
Q: Can I convert an RPC styled WSDL to a document styled WSDL?
A: It is difficult to answer yes or no because the answer depends on the WSDL instance and the implementation of the code that binds the XML instance to some native object. The problem comes from the fact that these two styles describe web services in different layers. The document style WSDL describes how one can bind an XML document to the SOAP message format. In contrast, the RPC style WSDL describes how one can bind an object to the SOAP message format. One can imagine that this works in two steps: first representing the object as an XML document and then binding this XML document to the SOAP message format. How this first step works is controlled by the SOAP encoding name. For the standard encoding specified in the SOAP specification, most objects can be easily described in an equivalent XML schema. Some special objects such as references and arrays must be represented by some special rules and some additional meta information in XML. This implies that these additional attributes and elements must also be described in the XML schema and the document style based proxy must set these values in the instance appropriately.
One must however note that even if one has an equivalent document style WSDL, this does not automatically guarantees the interoperability. Some RPC styled service implementations have significant interoperability problems such as requiring the xsi:type attribute for every element or the SOAP encoding attribute at some particular element. If one has to call such non conformant SOAP service, one must adjust the message accordingly.
Attachment wsdl_style_samples. zip contains some examples of WSDL documents and sample SOAP messages that illustrate how one can write an equivalent WSDL in another style.
Related Questions "Does the RPC or Document style in WSDL play a role in the SOAP adapter?"</i>
Regards
Bhavesh
Hi,
Import that wsdl in XI in external definitions node.
Then create message type and message interface using this external definition.
Then use this message interface as ur outbound or inbound interface.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.