| Author |
Message
|
| DevNYC1 |
 Posted: Wed Aug 22, 2012 7:33 am Post subject: Properties for queue/mgr info for different envs in V7 |
 |
|
Apprentice
Joined: 22 Aug 2012
Posts: 32
|
I am new to WebSphere Message Broker (using V7). I have a basic question regarding the property file configuration to define the queues/queue managers/channels that my flow will be reading from and writing to in diff. environments (DEV, QA, etc). I searched this forum and it is my understanding that UDP (User Defined Properties) is the best way to provide static configuration properties to the flow(s).
I will be using my local Windows desktop's MB for flow development but will connect to the queues running on the Unix environments and deploy to the Unix environments (they are on the internal network).
What is most flexible way to maintain and access these properties?
Last edited by DevNYC1 on Wed Aug 22, 2012 9:18 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Aug 22, 2012 7:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There is no property file.
You posted in the wrong topic on this forum. This topic is for Java and JMS questions, not for Broker questions.
You're demonstrating that you are misunderstanding a number of fundamental points about Message Broker.
You should review the learning material you've already been provided again, and you should discuss this material and your own understanding with local resources - people sitting next to you at the office. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 22, 2012 7:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Moved to more relevant section
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 22, 2012 7:55 am Post subject: Re: Using UDP to define queue info for different envs in V7 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| DevNYC1 wrote: |
| I searched this forum and it is my understanding that UDP (User Defined Properties) is the best way to provide static configuration properties to the flow(s). |
Search again; they're not. You might also want to give the product documentation another shot. What you want is in the first link I got when I typed "properties" in the search box on the InfoCenter.
| DevNYC1 wrote: |
| What is most flexible way to maintain and access these properties? |
The one provided by the product.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| DevNYC1 |
| Posted: Wed Aug 22, 2012 9:14 am Post subject: Re: Using UDP to define queue info for different envs in V7 |
|
|
Apprentice
Joined: 22 Aug 2012
Posts: 32
|
| Vitor wrote: |
| Search again; they're not. You might also want to give the product documentation another shot. What you want is in the first link I got when I typed "properties" in the search box on the InfoCenter. |
That is what I did before posting this question and here where I was looking: http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fbe10200_.htm
I see UDP as the one most applicable option for the scenario that I described. I may be wrong, and it looks like I was wrong. Would appreciate any thoughts on the question.
Thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 22, 2012 9:22 am Post subject: Re: Using UDP to define queue info for different envs in V7 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Not in that specific topic for your specific question I hope.
| DevNYC1 wrote: |
| I see UDP as the one most applicable for the scenario that I described. |
I wouldn't see them as the most applicable for the scenario you described; one key weakness is they can't do what you're describing. A UDP is a valid method of passing properties to code running inside a flow. That code can't override or modify many of the properties used by the supplied nodes, and certainly can't override the queue name used by the MQInput node.
You should also re-review the documentation (and possibly the WMQ documentation) if you think you need to supply channel information to WMB. There are 2 possible uses for a channel:
- to communicate queue manager to queue manager (which no application ever does)
- to establish a client connection to a queue manager (which WMB never does).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Aug 22, 2012 10:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Again, you are missing the connection between and understanding of several basic concepts.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/aa40070_.htm
A message flow runs on a given Broker. That broker is tightly coupled to a specific queue manager.
When you create a message flow, you choose what Broker to deploy that message flow to. When you choose to move a message flow from, for example, test into production, you do this by deploying the flow again.
When you choose to deploy a broker application, you are not able to cause changes to be made to the queue manager as part of the deployment process. This can be done as part of an overall process, but the Broker will not do this for you. |
|
| Back to top |
|
|
|
|
