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 » General IBM MQ Support » how is MQseries integrator different From adapters

Post new topic  Reply to topic
 how is MQseries integrator different From adapters « View previous topic :: View next topic » 
Author Message
ividiva
PostPosted: Fri Nov 22, 2002 3:08 am    Post subject: how is MQseries integrator different From adapters Reply with quote

Newbie

Joined: 21 Nov 2002
Posts: 8

Hi,
am quite new to MQseries.. am a bit confused about MQseries ,Mqseries Integrator,and the adapters ..can ay one say wut exactly are they? and where do i use wut and in wut situation.

Mathews
Back to top
View user's profile Send private message
Wjbyczek
PostPosted: Fri Nov 22, 2002 6:10 pm    Post subject: Reply with quote

Newbie

Joined: 08 May 2002
Posts: 4
Location: Domain Systemix

MQ Series is a guaranteed delivery system that comprises the infrastructure for a message oriented middleware environment. It consists of the queuing components and mechanisms that deliver and store messages, which really are variable length datagrams up to 4Mb for a client side machine to up to 100Mb lengths for server to server interactions. Messages are stored on queues that can be accessed by application, and can also be configured to "trigger" applications to run when a message arrives. Information to bracket messages as part(s) of units of work is made available to application using the queues to ensure sequencing and identity are handled correctly.

MQSI, on the other hand, is a product that, running on an MQ Series infrastructure, can distribute, filter, condition, and "enhance" the data sent within messages. In short, it creates a workflow environment on top of message oriented middleware functions. It has the advantage of working directly with DB2 (and Oracle) datastores, has many forms of parsers (XML being just one of them) and can make use of plugins to perform a variety of tasks such as generating email based on messages received by one of the workflow nodes.

An adapter is an application component that allows a new or existing application to make use of MQ series API's to enable message interchange using the MQ infrastructure. adapters can be purchased for specific products such as SAP, etc, but the vast majority of adapters are "roll you own" varieties, usually created in the native language of the application involved as long as it is capable of working with the published API set for MQ. Languages that work with these API's are Cobol on all platforms, C, C++, Visual Basic, and even Perl. It can even work with "odd" PC languages such as Progress or Powerbuilder.


This is a really high level description of the products, but should give you at least a contrast of how they play in relation to each other. For detailed information, check out the IBM Websphere MQ product site.

Hope this helps.
Back to top
View user's profile Send private message Send e-mail Visit poster's website Yahoo Messenger
wmqiguy
PostPosted: Mon Nov 25, 2002 7:47 am    Post subject: Reply with quote

Centurion

Joined: 09 Oct 2002
Posts: 145
Location: Florida

I'll add two cents.

The word adapter is often abused and has come to mean all things to all people.

Adapters, as I refer to them, are basically the layer between the MQSeries queue and the sending/receiving applications. In the most simple scenario, this would consist of Put/Get calls. Let's call this the "thin" adapter. Easily reusable and does not require much reengineering, once built.

The problem historically was that these simple Put/Gets would not meet the interface requirements. Someone, either on the put or get, would need to transform the data as necessary. We can call this the "thick" adapter. Unfortunately, some poor programmer would need to modify this thing every time they would have to interact with a different application.

Enter the birth of the integration broker (WMQI). This product essentially moves this layer, the "thick" part of the adapter, into a centralized location between all the applications. Allows one group to worry about all the transformation algortihms that exist between the applications. The application programmers then only need to maintian a "thin" client and can concentrate on the business functions of the application.

Good luck.
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 » General IBM MQ Support » how is MQseries integrator different From adapters
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.