|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Modeling REST input output schema in WMB |
« View previous topic :: View next topic » |
Author |
Message
|
mehdiK |
Posted: Thu Mar 07, 2013 3:41 am Post subject: Modeling REST input output schema in WMB |
|
|
Acolyte
Joined: 07 Mar 2013 Posts: 53
|
Hello !
I'm working on Websphere message Broker Toolkit 8 and I try to create an Application on it to Get an XML file via HTTP (Rest Webservices) and compute it via Java and Output an XML file in the end.
I've tried to imagine how can the processus will be in SOA and REST, so Here's a screenshot of my design in the following link :
bit.ly/WMdD26
1- Is it true ? (Both of them).
2- And how can I set the XML file in the input instead of simple types (String, int etc...) by creating a WSDL file and Output (XML file not simple type) ?
3- Why is there difference between SOAP and REST and they are both transported by HTTP protocols ?
4- And Finally how can I set the input URL to get the XML file through the network ? (I think that I should configure a listener on a port but I don't know how)
Thank you a lot guys  |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Mar 07, 2013 4:02 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
SOAP uses WSDLs
REST doesn't.
It's not a file if it's not a block of disk space sitting on a disk being accessed by a file system. It's an XML document being transported by something - HTTP in the case of both REST and SOAP.
SOAP requires that all messages being exchanged must be described by XML data and match the XML schema.
REST doesn't.
SOAP is a message exchange protocol.
REST is an HTTP programming pattern.
You are lacking a lot of basic, crucial knowledge to accomplish the task you are trying to do. You don't really appear to understand the exchanges you are trying to make, and you don't really appear to understand the way Broker works.
It's going to be very very hard to try and learn both at the same time.
I would recommend that you start trying to learn how Broker works, and from how you have spoken, I would suggest you start by using actual real files.
Make a flow that is FileInput->Trace->FileOutput.
Then try and understand what that does and how it works, using different models and parsers.
Then change the flow to use FileInput->Trace->JavaCompute->Trace->FileOutput.
Instead of JavaCompute you can use Compute, .NETCompute, PHPCompute, or Mapping. It depends on what programming skills you are most comfortable with at this point. |
|
Back to top |
|
 |
mehdiK |
Posted: Thu Mar 07, 2013 5:11 am Post subject: |
|
|
Acolyte
Joined: 07 Mar 2013 Posts: 53
|
Thank you a lot, I'll do this  |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|