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 IndexWebSphere Message Broker SupportUsing the Mapping node with ODBC tables as input

Post new topicReply to topic
Using the Mapping node with ODBC tables as input View previous topic :: View next topic
Author Message
leao
PostPosted: Fri Dec 21, 2018 4:22 am Post subject: Using the Mapping node with ODBC tables as input Reply with quote

Newbie

Joined: 06 Dec 2018
Posts: 4

Is there any way to use ODBC database tables as input to the mapping node? Can I for example use ESQL to put data from a DB into the environment tree, and then use the environment mapping functionality in the mapper?

Or is it simply better to use plain ESQL?

I would think that the more of the embedded functionality I can use (for example with the mapping node), the better, and that manual coding leaves more room for error and maintenance.

Any advice on this?
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Dec 21, 2018 5:54 am Post subject: Re: Using the Mapping node with ODBC tables as input Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 25685
Location: Ohio, USA

leao wrote:
Is there any way to use ODBC database tables as input to the mapping node? Can I for example use ESQL to put data from a DB into the environment tree, and then use the environment mapping functionality in the mapper?

Or is it simply better to use plain ESQL?


If you've got an existing OBDC connection that you want to exploit, then it's reasonable to use that. If it was me, I'd use plain ESQL but that's not cut and dried.

leao wrote:
I would think that the more of the embedded functionality I can use (for example with the mapping node), the better, and that manual coding leaves more room for error and maintenance.


I would disagree with that. It's a necessity to use embedded functionality for that which the embedded functionality is intended for (reading from queues or files for example). The use of Mapping v ESQL v Java has more to do with the complexity of transformation and the skill set of your site. I know of sites which use Java Compute Nodes exclusively because they have a large number of Java resources, write extensive amounts of non-IIB Java and have the processes to control them.

Speaking personally, I'd sooner use 2 lines of ESQL than a huge amount of hard to maintain maps, but then I'd use ESQL anyway. Over a decade of ESQL coding has left me mapping-challenged.

You must use what you think is best because it's your site and your code, but I wouldn't just use the Mapping node blindly. it's not more "embedded" than the code based transformation nodes.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportUsing the Mapping node with ODBC tables as input
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.