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 » Mssage Tanpost Mchanism

Post new topic  Reply to topic
 Mssage Tanpost Mchanism « View previous topic :: View next topic » 
Author Message
jeevan
PostPosted: Thu Sep 07, 2006 7:56 am    Post subject: Mssage Tanpost Mchanism Reply with quote

Grand Master

Joined: 12 Nov 2005
Posts: 1432

While working on MQ as an admin, I have never tried to go beyond the solving problem into the when a message what exactly format it comes in. I can imagine what a message systems may exchange ? Definitely some text message with number. Does a messaging system ever exchange an image ?

As I went through the many discussionsin this forum and understand that mq is not a system to transfer file. That means, I can imagine, mq generally exchange test message with some numeric data.

My questions ( curiousity- as I have never work as appl guy) is a message may be a single paragraphs ( text) or sometime it may be details of a person ( database record - taken out from a database) but it should be consistence. Is that correct? how can we devise a system which can process ( i am thinking in term of message broker) any type of message?

Is the message body always in xml format when it is transported? if we can sending a person record as a message, should not it be converted in xml format before the system sends it ?

I would really appreciate if some one can clarify this.

thanks a lot
Back to top
View user's profile Send private message
jeevan
PostPosted: Thu Sep 07, 2006 8:06 am    Post subject: Reply with quote

Grand Master

Joined: 12 Nov 2005
Posts: 1432

sorry for typo, i mean message transport mechanism
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Sep 07, 2006 8:16 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

An MQ message holds a stream of bytes.

Those bytes can represent anything that can be described with bytes.

This includes files.

There is nothing wrong with MQ as a transport for file transfer.

MQ by itself is not a file transfer solution, at least for the enterprise. The File Transfer applications that come with MQ v6 are fine for individual file transfers, but not for enterprise level managed file transfers.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
CMF
PostPosted: Thu Sep 07, 2006 8:20 am    Post subject: Reply with quote

Novice

Joined: 18 Apr 2006
Posts: 10
Location: Nashville

jefflowrey wrote:
...MQ by itself is not a file transfer solution, at least for the enterprise...


Why not?

A file is just a bunch of bytes, right?



edit: and yes I've read the other posts.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Sep 07, 2006 8:23 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

CMF wrote:
jefflowrey wrote:
...MQ by itself is not a file transfer solution, at least for the enterprise...


Why not?

A file is just a bunch of bytes, right?


What's the difference between a solution and a transport?

Also, I've made this same rant many many times. I'm not going to repeat it here.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
jeevan
PostPosted: Thu Sep 07, 2006 3:23 pm    Post subject: Reply with quote

Grand Master

Joined: 12 Nov 2005
Posts: 1432

Thank you Jeff. My question is mainly from the point of message processing - in that also from MB point of view. As I understood, there are 3/4 different kinds of inputs for MB. I did not get an answer ( may be I have not read thoroughly all the documentations) that how the message is parsed. Specially, I am interested how body of the message, in case of when the input is mq queue, is parsed - when the body is a single block of text, and when it is a database record.

What i am trying to understand is that how the message actually is processed, how they arrive in MB, how parsed and processed. Any clarification would be appreciative.

thanks
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Sep 07, 2006 3:31 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

In Message Broker, you can process the message any way you want, including by hand.

Usually, though, most people use either a self-describing data format (XML or MIME) or a modelled format from a message set - MRM-CWF, MRM-TDS or MRM-XML.

But any more detail than that would simply be more confusing.

If you want to learn broker, then you need to get training.

If your company won't pay for it, then it's obviously not worth their time for you to know what you're doing, or it's worth them paying you for six months of downtime doing nothing other than learning Broker.
_________________
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 » Mssage Tanpost Mchanism
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.