| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| multiple environments on one system in OS390 |
« View previous topic :: View next topic » |
| Author |
Message
|
| shalabh1976 |
 Posted: Thu Apr 17, 2003 6:42 am Post subject: multiple environments on one system in OS390 |
 |
|
Partisan
Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India
|
In an earlier post the following statement was made:
Each broker CAN have a different .odbc.ini file - just change the $ODBCINI environment parameter to point to a customized version before running the mqsistart broker-name command
In our current environment, our broker is running on OS390. Is there an analagous solution for ODBC?
We have multiple brokers running on the same system, and would like to have a separate user data database for each broker. We do not want to have to change the datasource when we promote between environments.
If all of the different brokers are operating under different id's and the user data table used by each broker is created under an id equal to the broker id, it seems like all the code could use the same datasource by not specifying the table owner. The drawback here is that all environments would be using the same database. |
|
| Back to top |
|
 |
| migstr |
| Posted: Thu Apr 24, 2003 6:00 am Post subject: |
|
|
Apprentice
Joined: 05 Jun 2002
Posts: 34
Location: New York
|
Hi, I'm not sure if I'm answering your question but I will tell you what we are doing. We also have two different brokers on a 390 (dev and test) but they each use the same DB2 subsystem. We create two sets of application tables, one has dev table owner, second has test table owner. We then create ALIASes for each set using the BROKER id. For example,
DEVBROKER.APPTABLE1 for DEVTABLEOWNER.APPTABLE1
TESTBROKER.APPTABLE1 for TESTTABLEOWNER.APPTABLE1
Our ESQL only refers to Database.APPTABLE1,therfore, when you run under dev broker it will access your dev tables; run under test broker accesses you test tables. The DATASOURCE is the same because it is the same DB2 subsystem. So no chages required.
Our production broker is on a different DB2 subsystem, so we create a datasource promote property, and when we promote to prod, we change this to the production db2 subsystem.
I hope this helps and if you are doing something different/better, please let me know.
_________________
Thanks, Margaret
-------------------------------------------------------
IBM Certified Specialist - MQSeries, Websphere MQ Integrator
IBM Certified Solutions Expert - MQSeries, Websphere MQ Integrator
IBM Certified Developer - MQSeries |
|
| Back to top |
|
|
| shalabh1976 |
| Posted: Mon May 12, 2003 10:44 am Post subject: |
|
|
Partisan
Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India
|
Thanks for your reply,
Actually thats what we are also discussing :
1. Modifying the ODBC file
2. Using the promote property
I will post the implemented solution once that is done. |
|
| 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
|
|
|
|
