ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SDO

Post new topic  Reply to topic
 SDO « View previous topic :: View next topic » 
Author Message
RocknRambo
PostPosted: Thu Jun 08, 2006 7:34 am    Post subject: SDO Reply with quote

Partisan

Joined: 24 Sep 2003
Posts: 355

we are having a philosophical debate goin...

Concept of SDO's are not new.. correct?

ESB & WPS have come up, that any data access is done with SDO.

technically, a SDO is an schema level .xsd. Correct ?

how can we co-relate the same in MB world. like in MB, we can import .xsd and create a message set and then its saved as .mxsd.

can anybody share some knowledge on SDO's in terms of MB ??

Thanks
-RR
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Jun 08, 2006 7:46 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

An SDO only makes sense and only exists inside a specific Java container. It's like an EJB that way.

One of the basic things that WPS/ESB do is this. When a consumer makes a WebServices Request over HTTP, the HTTP data is automatically converted into an SDO. The SOAP XML in the HTTP message is marshalled into the SDO.

Likewise, when a SOAP message comes in over JMS, then the SOAP XML in the JMS message is marshalled into the SDO.

The WSDL defines the interface, that is it strictly determines the contract between the consumer and the producer in that it says "A consumer of this service will make a request that is formatted like this. The response from the producer will be formatted like this."

The concepts behind an SDO are not new, I'm sure - but what "new" means is certainly up for philosphical debate...
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
RocknRambo
PostPosted: Thu Jun 08, 2006 8:14 am    Post subject: Reply with quote

Partisan

Joined: 24 Sep 2003
Posts: 355

so, SDO makes sense only in JAVA Container like WPS/ESB,

and MB is not a container, SDO doesnt come into picture ?

sorry, I'm still trying to visualize in MB World



Thanks
-RR
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Jun 08, 2006 8:31 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

As I understand it, SDO is two things - a standard and an implementation. As a SDO stands for "Service Data Object". I suppose in practice, it can be implemented in any object oriented language. AFAIK, though, IBM only supports SDO in Java.

You could, potentially, build a Java Compute Node that will create an SDO out of a message tree, or vice versa. But there is no native "SDO" implementation in the current version of MB.

But most particularly what SDO is not is a data description/interchange format - so it doesn't talk about what the object looks like when persisted in a file or in a message on a queue or in an HTTP request or etc. It only talks about what the object looks like as an object, an in-memory structure. Again, at least as far as I know. I'm not an expert on SDO.

In general, I would think about the SOA at the business level first. A Service in an SOA is after all only a "repeatable piece of business logic". What are the business transactions that are being performed, what data is required as input to each transaction, what data is produced as output of that transaction. The input and the output is then turned into an interface specification, and possibly then turned into WSDL. The WSDL defines the XML format of that data. This XML can then be exchanged over a variety of transports - MQ, JMS, HTTP, FTP, SMTP, etc (although the official WS standards only specify HTTP and JMS). Then, for example, a WPS web service implementation will receive that XML and transform it into an SDO, which the business logic in the service will interact with. And an MB flow will receive that XML and transform it into a logical message tree, which the integration logic in the flow will interact with.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SDO
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.