| Author |
Message
|
| klabran |
 Posted: Fri Sep 30, 2005 8:59 am Post subject: Change qnames in flow/esql based on test/prod system? |
 |
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
Now that I have completed my move to WBIM5. I would like to rework some of my old flows.
In my 2.1 setup I had two flows that would be identical except that the OBDC DSN would be different and the ESQL code in my compute node would have a different queue name to go to based on if this was production or test and a different qname for the input queues IE - TEST_QL_INPUT or PROD_QL_INPUT.
IE - Two Flows, One Test, One Production. Both Flows are identical except that Test would use a DSN connecting to my test DB and my ESQL would point to a test QName. To move to production I would copy the Test flow rename to Prod_XYZ and then change the DSN and ESQL to reflect Prod info and release to broker.
I know this was cludgy but it worked for me at the time. Now I want to go to one flow if possible.
I know I can change the ODBC DSN via the Bar file so that is solved but how can I dynamically change the QNames?
Thanks,
Kevin |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Fri Sep 30, 2005 9:08 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| klabran |
| Posted: Fri Sep 30, 2005 12:50 pm Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
Oh Boy.... I must have slept through that part in the training session. 
Thanks. I'll have to check out the bar file a little more closely.
Kevin |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Sat Oct 01, 2005 2:25 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| happyj |
| Posted: Mon Oct 03, 2005 1:36 am Post subject: |
|
|
Voyager
Joined: 07 Feb 2005
Posts: 87
|
| I use alias queues to do this. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Mon Oct 03, 2005 1:43 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| happyj wrote: |
| I use alias queues to do this. |
true that is another way of achieving your goal, but then the Queue names are the same in your DEV and PROD environment right?
That was not what klabran was looking for.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| happyj |
| Posted: Mon Oct 03, 2005 2:11 am Post subject: |
|
|
Voyager
Joined: 07 Feb 2005
Posts: 87
|
|
| Back to top |
|
|
| Ian |
| Posted: Mon Oct 03, 2005 3:39 am Post subject: |
|
|
Disciple
Joined: 22 Nov 2002
Posts: 152
Location: London, UK
|
Hi Kevin,
This concept is not new to v5, it has been around since inception.
The mechanism that WMQI v2.1 and WBIMB v5 provide for dealing with different
user environments (such as DEV, TEST and PROD) is through promoted node properties.
In v5 you should start with topic "ac00640_"
In v2.1 it is covered in the following manuals :
Websphere MQ Integrator Version 2.1 : Using the Control Center
Chapter 5. Working with messageflows
Promoting message flow node properties
======================================================================
For example, you might want to set the name of a data source as a
property of the message flow, rather than a property of each
individual node in the message flow that references that data source.
You are creating a message flow that accesses a database called
SALESDATA. However, while you are testing the message flow, you want
to use a test database called TESTDATA. If you set the data source
properties of each individual node within the message flow to
reference TESTDATA, you will have to update all these references when
you put your message flow into production.
If you promote the data source property, you can set the properties
for all of the individual nodes to be SALESDATA, and set the value of
TESTDATA for the promoted property to override the node data source
values while you test the message flow (the promoted property always
takes precedence over the settings for the properties within any
relevant nodes).
======================================================================
Chapter 5. Working with messageflows
Promoting properties through a hierarchy of messages flows
======================================================================
The process of promoting message flow node properties can be repeated
as you construct a hierarchy of message flows. You can promote
properties from any level in the hierarchy to the next level above,
and so on through the hierarchy. The value of a property is propagated
from the highest point in the hierarchy at which it is set down to the
original message flow node when the message flow is deployed to a
broker. The value of that property on the original message flow node
is overridden.
======================================================================
_________________
Regards, Ian |
|
| Back to top |
|
|
| klabran |
| Posted: Wed Oct 05, 2005 6:30 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
Awesome. Thanks everyone for your suggestions. I will be using both promoted prop's and the bar file because I also have flows where the qnames are the same between systems but I like the promotion for my DB connections. 
Kevin |
|
| Back to top |
|
|
|
|
