| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Database connections |
« View previous topic :: View next topic » |
| Author |
Message
|
| lppgronw |
 Posted: Tue Sep 11, 2007 11:33 am Post subject: Database connections |
 |
|
Newbie
Joined: 11 Sep 2007
Posts: 2
|
I am trying to use a DataInsert node and have created the data definition and data map. I have created the data conncetion using JDBC and have successfully connected. I am using MB toolkit on a Windows XP machine and will eventually deploy to an AIX machine for production. My question is the Data Source property of the DataInsert Node. What should go there, connection URL? Based on some of the answers I've seen do I have to create a windows ODBC connection and use that as the data source? If so, what happens when I deploy to AIX, will I have to create the ODBC definition there as well?
What's the point of creating the database connection in the data perspective if it can't be used with a esql compute node or the database nodes? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Sep 11, 2007 11:37 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The only reason to create a Database connection in the Toolkit is so that the Toolkit knows about the database. To, for example, not throw warnings when you write ESQL that references database structures.
It's not very much use at all, as long as you know how to ignore warnings.
Broker runtime and Toolkit are entirely separate environments.
Broker runtime only uses ODBC for connections - unless you specifically write java code to create JDBC connections.
All of that should have been covered in your Broker training.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jsware |
| Posted: Wed Sep 12, 2007 3:42 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
How do people overcome the problem of databases in different environments would have different names? For example I might have 3 environments, DEV, TEST and PROD. I have 3 brokers: DEV_BRK, TEST_BRK and PROD_BRK. DEV & TEST brokers are on TEST_HOST and PROD is on its own host.
Each environment has its own application database I need to access; DEV_DB, TEST_DB and PROD_DB.
I have say 6 flows, each with 3 nodes that access the relevant database. How can I deploy the flows between environments without accidentally connecting to the wrong database in an environment.
Promoting properties to be changed in the bar file is not foolproof because I have 9 properties to change each time I do a deploy. Using "aliased" names in the ODBC.INI file does not help because DEV & TEST brokers are on the same host (but need to access different databases).
What do other people do (if anything more than be careful)?
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 12, 2007 3:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There are a lot of ways to "overcome" this "problem".
One is to create the ODBC DSNs to all have the same name.
One is to use mqsiappplybaroverrides - which may be problematic for some properties, but is fine for this situation.
One is to write scripts or use scripts that do the same thing as mqsiapplybaroverrides - change the properties in the broker.xml file.
There are a couple of articles on devworks about this - some are about using Ant and one is about a Java tool for changing BAR properties (it's by Boris Lublinsky).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
