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 » difficulty promoting data source inside ESQL

Post new topic  Reply to topic
 difficulty promoting data source inside ESQL « View previous topic :: View next topic » 
Author Message
pcelari
PostPosted: Thu May 24, 2007 6:27 pm    Post subject: difficulty promoting data source inside ESQL Reply with quote

Chevalier

Joined: 31 Mar 2006
Posts: 411
Location: New York

I have a compute node that calls three stored procedures on three remote DB2 on mainframe. While I made the first database as the property data source of the compute node, I specify the DBs in subsequent my SP calls. like this:

call SP1(in1, in2, Environment.Result0[]); -- data source as property
call SP1(in1, in2, Environment.Result1[]) IN DB2DV_1; -- explicit
call SP2(in1, in2, Environment.Result2[]) IN DB2DV_2; -- explicit

since Dev, QA, and production use different set of databases, I end up having to alter code before each deployment, except the first database that I specified as a property of the compute node and which I promoted.

My question is, how can I avoid having to alter code each time I deploy the same flow to a different environment?

It makes me sweat each time I make such a back and forth deployment after the corresponding code change. I can afford a mistake when deploying to production, or letting the development environment accidentally updating a production database.
_________________
pcelari
-----------------------------------------
- a master of always being a newbie
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Thu May 24, 2007 11:05 pm    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi pcelari,

You can set the names of the database as UDPs and then set them at bar file level, thus not touching the code.

Else, from your entire project point of view, you should have a table in some application database which fetches these kind of values for every flow based on its unique name....something like a properties file in Java, implemented in Db.

Regards.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » difficulty promoting data source inside ESQL
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.