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 » Mapping

Post new topic  Reply to topic
 Mapping « View previous topic :: View next topic » 
Author Message
aradha
PostPosted: Tue Feb 23, 2010 2:47 am    Post subject: Mapping Reply with quote

Apprentice

Joined: 16 Dec 2008
Posts: 45

Hi

I am doing mapping XML to TDS.
Is there any advantage of using ESQL for mapping instead of Mapping Node any ideas which is best?????
Back to top
View user's profile Send private message
MrSmith
PostPosted: Tue Feb 23, 2010 2:56 am    Post subject: Reply with quote

Master

Joined: 20 Mar 2008
Posts: 215

One thing i have always noticed between levesl is that Mappings seem always to need migrating whereas ESQL code rarely has. If the values are not manipulated much or conditioned then mapping would be a easy option but i would say ESQL has more flexibility. Unless you have a time constraint then do it in both see what gives!!!
Back to top
View user's profile Send private message
aradha
PostPosted: Tue Feb 23, 2010 3:04 am    Post subject: Reply with quote

Apprentice

Joined: 16 Dec 2008
Posts: 45

Thanks for reply just want to what exactly advantage of using ESQL
for mapping cases.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Feb 23, 2010 5:08 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

aradha wrote:
Thanks for reply just want to what exactly advantage of using ESQL
for mapping cases.


The mapping node uses ESQL under the covers. If you have all the message sets you need and straightforward mapping requirements the mapping node is a good choice. For everything else use ESQL.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
aradha
PostPosted: Tue Feb 23, 2010 7:28 pm    Post subject: Mapping Reply with quote

Apprentice

Joined: 16 Dec 2008
Posts: 45

For every thing else means?? for understanding can you give example
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Feb 23, 2010 7:47 pm    Post subject: Re: Mapping Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

aradha wrote:
For every thing else means??


For all those cases where you don't have all the message sets you need and/or have complex transformation requirements.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Bartez75
PostPosted: Wed Feb 24, 2010 7:20 am    Post subject: Reply with quote

Voyager

Joined: 26 Oct 2006
Posts: 80
Location: Poland, Wroclaw

If you know ESQL then use it. If not then perhaps mapping is a good start.

I use always esql even if mapping is very simple because simply I don't feel comfortably with mapping node.
Since there is no performance differences between them (maybe I'm here) then the choice is rather simple.
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 » Mapping
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.