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 » Message Map vs. GDM

Post new topic  Reply to topic
 Message Map vs. GDM « View previous topic :: View next topic » 
Author Message
Gideon
PostPosted: Thu Jan 15, 2015 8:59 am    Post subject: Message Map vs. GDM Reply with quote

Chevalier

Joined: 18 Aug 2009
Posts: 403

With a Mapping node (which creates a Message Map), I can create a drag and drop between two message formats which is included directly into the flow palette as a Mapping Node

When I create a Data Map (GDM), I can not drop that into a message flow. I can however, create an XSLT from it

What is the central purpose of the GDM (Data Map), since it can not be transported into a Mapping node.

Is it's purpose to create XSLT or any other script that can be included into a XSLT or other node ?

Thanks
Back to top
View user's profile Send private message Send e-mail
Simbu
PostPosted: Mon Jan 19, 2015 12:52 am    Post subject: Reply with quote

Master

Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India

By going through this post(eventhough it is for WMB v7), Data Map is the IBM RAD new feature and so it is available in IIB.
It is different from the Message Map which is specific to IIB.
Back to top
View user's profile Send private message
martinb
PostPosted: Mon Jan 19, 2015 12:25 pm    Post subject: Reply with quote

Master

Joined: 09 Nov 2006
Posts: 210
Location: UK

Gideon does not state what version of teh product being used, so here's some background.

From WMB v8 a new Graphical Transformation technology has been implemented to exploit the new dedicated Mapping runtime engine and the IBM common Graphical Data Mapping editor.

In WMB v8 / IIB v9 the Graphical Data Mapping is entended to support the fact the flow provides a Message Assembly which provides access to the message data and other associated headers etc. Also things just as Database interaction transforms are provided.

The WMB / IIB Toolkit creates .map files when you double click a Mapping node in a flow or invoke the new Message map wizard. These .map artifacts created in this way are only sutable for use in WMB / IIB runtime.

The WMB / IIB Toolkit alos allows you to invoke the Graphical Data Mapper with no WMB / IIB product extension features. This is achieved by creating a .map artifact via the File New -> Other -> Xml -> Data Map wizard. A "main" (top level) map created in this way is suitable for use in IBM products that exploit the WAS XML feature pack and provide a runtime for executing XSLT.

Infact since thee .map files enabled the "Generate" action in the Graphical Data Map editor you can use them to generate standard Xquery or XSLT for use in any engine.

One of the practical uses of this is to provide reusable common Graphical Transforms for use in WMB / IIB and other products, for example BPM / IID etc. This is achieved by creating a submap for the message body data using the base "Data Map" , and then invoking this common submap in both a Main Message Map for WMB/IIB and a main Data map for other products.
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 » Message Map vs. GDM
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.