|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Broker and Execution Group Processes |
« View previous topic :: View next topic » |
Author |
Message
|
deepnair |
Posted: Tue Feb 07, 2012 2:18 pm Post subject: Broker and Execution Group Processes |
|
|
Apprentice
Joined: 07 Feb 2012 Posts: 35
|
Hi - I'm just trying to understand how exactly the broker works (im from java background) i.e. how the execution groups, broker and MQ are aligned (is broker server or an eg is a server ? is jvm at broker level or eg level ? who manages threads, stack and heap ?)
I did search in infocentre but the info i could get is at a very high level but not detailed to explain the architecture...
I was reading in infocentre and there it says
Quote: |
Each execution group is started as a separate operating system process, providing an isolated runtime environment for a set of deployed message flows. |
If this is the case then each EG is like an app server hosting multiple apps (as flows + msg sets) - then why do we need a "broker" component on top of it - can the "MQ Engine" not handle it by itself ?
Thoughts ....?
Thanks,
Deep Nair |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Feb 07, 2012 3:04 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
The queue manager knows nothing about Broker.
Broker is just another MQ application, as far as the queue manager is concerned.
You can think of the 'Broker' as the equivalent to a WAS Deployment Manager.
It's also responsible for starting and stopping EG processes, and restarting them if it notices that they've crashed. |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue Feb 07, 2012 10:26 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
As you are from a Java background, some of your points are very relevant
Each EG is a separate process therefore it stands to reason that there will be a JVM per EG.
The other thing to understand right from the beginning is that
Broker is NOT a J2EE Application Server.
If you want an App Server then use WAS, JBoss etc.
Don't try to program a JCN in the same way you program Java in an App Server. IF you do then you will get nowt but a whole load of grief.
Finally,
If you don't understand what is happening then by all means come back here and ask. All we ask of you is that you have at least tried a few things out and importanlty that you are willing to try out some of our suggestions. It is all about learning and sharing that learning. If you are willing to help yourself then we will help you. Keep on reading the documentation! _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
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
|
|
|
|