| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Bar file WBIMB 5.0 comparison with assignment of MQSI2.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| pbravic |
 Posted: Thu Apr 08, 2004 3:17 pm Post subject: Bar file WBIMB 5.0 comparison with assignment of MQSI2.1 |
 |
|
Apprentice
Joined: 24 Nov 2003
Posts: 42
|
Hi we are in the process of migrating from MQSI 2.1 to WBIMB. In MQSI, we had logical execution groups(containing message flows) for messages comming from 2 inputs and both are grouped under a broker.
In WBIMB we find that the bar file contains both the message set and message flows which is then deployed in to the broker execution group
our question is how to have the same logical entity as that of MQSI 2.1 in WBIMB 5.0
Process 1
-----------
Is it fine if we create 2 execution groups and 2 bar files (A and B)
bar file A containing only message flows from input 1 and all the message sets (as these are common for most of the message flows)
bar file B containing only message flows from input 2 and all the message sets
deploy them into respective execution groups
or
Process 2
-----------
2 exection group with one bar file containing all the message sets and message flows
which one of the above process have better performance.
thanks and regards
ravi |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Apr 08, 2004 3:41 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
How many bar files you package things into does not, as far as I know, affect the performance of the broker.
It's only the packaging of stuff that's used to send things over MQ to the broker for parsing and storing in it's database.
This allows you to break up the things you need to deploy to a particular execution group or broker into smaller pieces in order to manage the performance of your deployments. So if you had a really really larger message set that didn't change much, you could put that in one bar file, and deploy it separately from the message flows that use it for better deployment efficiency.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| crgharm |
| Posted: Wed Jun 09, 2004 11:11 am Post subject: |
|
|
Novice
Joined: 25 Apr 2002
Posts: 21
Location: St. Louis, Missouri
|
Does this mean that if you have 2 (or more) message flows that reference a message set, then all those message flows and that one message set must be deployed to the same execution group?
Thanks,
Craig |
|
| Back to top |
|
|
| shanson |
| Posted: Thu Jun 10, 2004 3:02 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
To answer your last question, no it does not. You can if you want create A.bar containing msgFlow A and msgSet M, and B.bar containing msgFlow B and msgSet M, and deploy them to separate execution groups.
The principle I recommend is that, for a given execution group, you place in the same bar file a message set and all the message flows that use it. It's easier for change management to do this - remember that the broker only has one instance of a given message set per execution group, so if a message set appears in more than one bar file deployed to the same execution group you must remember to update all bar files when you update the message set.
So if you were deploying msgFlow A and B to the same execution group, I would place them in the same bar along with msgSet M. |
|
| 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
|
|
|
|
