| Author |
Message
|
| JYama |
 Posted: Wed Mar 02, 2005 12:08 am Post subject: How can I call Web Services? |
 |
|
Master
Joined: 27 Mar 2002
Posts: 281
|
Hi all,
I'm trying to call a Web Service from WBI Message Broker v5.
Now I've got a WSDL file from a service provider, but I have no idea how I can implment a message flow which enables to invoke an external web services.
How can I build a message set to call a Web Service?
On WAS, I know we can easily build interfaces for Web Services by GUI(Administrator console) once we've got WSDL files, but I'm not sure WBIMB toolkit has similar user interface.
Is there anybody who is familar with this issue?
(I checked IA81 support pack but I'm still not sure about a way to call external web services.)
Many thanks in advance,
JY |
|
| Back to top |
|
 |
| EKhalil |
| Posted: Wed Mar 02, 2005 5:18 am Post subject: |
|
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
There is a very detailed description in the WBIMB Application Programming manual on how to invoke WS from within the WBIMB. (offers examples of messages, etc) Check out other manuals as they offer help on building message sets. (personally I would import a DTD)Download them all and have them handy
Also check out write ups on each of the http nodes (understand their use:) I found the manuals extremely helpful  |
|
| Back to top |
|
|
| JYama |
| Posted: Wed Mar 02, 2005 6:02 pm Post subject: |
|
|
Master
Joined: 27 Mar 2002
Posts: 281
|
Thank you very much for useful and helpful information.
I'm checking the document now...
Anyway, my question is how we can use WSDL files when we build a message flow as a service requester.
Does WBIMB Toolkit read and understand WSDL files provided by the others?
In my understanding so far, we have to be familiar with the structure of the WSDL when we build a message flow as a service requester(not provider), right?
In other words, when we build a message flow as a requester, Message Broker Toolkit does nothing and the only one we can do with a WSDL file provided by a service provider is to manually read it and code ESQL by ourselves. (The toolkit doesn't read and understand such WSDL files provided by the others.)
Also I'm sure that building a message flow as a service 'provider' is much easier because its WSDL is automatically created by the toolkit and it doesn't require to write WSDL manually.
Cheers, |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 03, 2005 5:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay.
Let's take a step back, and look at what WebServices really are.
WebServices are just HTTP Requests and Replies (unless you're using a different transport than HTTP).
So you "invoke" a WebService by making an HTTP Request, and you get back an HTTP Reply.
What makes it a "Web Service" instead of a simple HTTP Request/Reply is that ... the DATA in the Request and in the Reply is XML.
The XML data is described by the, get this, Web Services Description Language document.
In WBIMB, data is described using Message Sets (or treated as self-defining). The process is described using Message Flows.
In order to get back the right information that you actually want, you have to understand the XML structure as defined by the WSDL, and you have to CREATE the right XML document (that matches the WSDL) so that it SPECIFIES the right thing.
IN other words, in *any* environment, you have to know the WSDL in order to know what information to put in and how.
In WBIMB, you should be able to create a Message Set from the WSDL, and use the Mapping Node to populate fields in a message of the right message type WITHOUT writing ESQL.
But you still have to know what to put into the XML document.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| K_A |
| Posted: Thu Mar 03, 2005 7:03 am Post subject: A support pac can help? |
|
|
Apprentice
Joined: 10 Nov 2004
Posts: 32
|
There is a supporrt pac around this : IA81.
It contains both the theory and a bunch of code examples. |
|
| Back to top |
|
|
| JYama |
| Posted: Thu Mar 03, 2005 9:22 pm Post subject: Summary |
|
|
Master
Joined: 27 Mar 2002
Posts: 281
|
Hi all,
Thank you very much for your supports, all.
Let me summarize the issue.
To build a message flow as a service requester, we need
1. (at least) a WSDL file provided by the web service provider,
2. to manually build a meesage set by ourselves by reading and understanding the WSDL file because there's no way to automatically build the message set from the WSDL file with the WBIMB Toolkit,
3. to build HTTP Request massage (based on the message set) on a mapping node,
4. to send the request message through a HTTPRequest Node to invoke the service.
If there're any misunderstandings, I would appreciate if you could point it out.
Cheers, |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Mar 04, 2005 5:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If the Web Service is defined in a UDDI, there appears to be a Wizard for Importing a Web Service.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nmaddisetti |
| Posted: Thu Mar 17, 2005 10:44 am Post subject: |
|
|
Centurion
Joined: 06 Oct 2004
Posts: 145
|
Hi
I am not clear that
should i create message set manually or using WSDL file
Thanks
Maddisetti |
|
| Back to top |
|
|
|
|
