| Author |
Message
|
| Rocket |
 Posted: Wed Apr 24, 2002 8:28 pm Post subject: |
 |
|
Newbie
Joined: 23 Apr 2002
Posts: 5
|
what do you all see as the best way to set up the mqsi development environment when there are many developers on one project. should each developer have a configuration manager and a broker on their individual workstation? or, should all developers share one central configuration manager on a shared server and only have a broker on their workstation? we will share a broker/config mgr in system test, i'm only interested in the build/unit test environment.
thanks. |
|
| Back to top |
|
 |
| vedbhat |
| Posted: Wed Apr 24, 2002 8:49 pm Post subject: |
|
|
Disciple
Joined: 19 Mar 2002
Posts: 186
Location: Singapore
|
Hi,
It is better to have a Single Broker and Multiple Execution Server for each of the User.
Regards
Ved
_________________
IBM Certified Solutions Expert - MQSeries Workflow
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| Rocket |
| Posted: Wed Apr 24, 2002 8:58 pm Post subject: |
|
|
Newbie
Joined: 23 Apr 2002
Posts: 5
|
| when you say Multiple Execution Server are you referring to the config manager? |
|
| Back to top |
|
|
| vedbhat |
| Posted: Wed Apr 24, 2002 9:08 pm Post subject: |
|
|
Disciple
Joined: 19 Mar 2002
Posts: 186
Location: Singapore
|
Sorry, I mean Execution Group.
_________________
IBM Certified Solutions Expert - MQSeries Workflow
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Apr 24, 2002 9:33 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
You may have licensing issues if you decide to install Broker/Configuration manager on multiple machines. In a typical development environment you will have one configuration manager shared by all developers and one or more brokers either on the same server or different server.
Creation of Execution groups on any broker is directly related to number of CPU's on that box. Each Execution group is a seperate OS process. If you have a 4 CPU box and you create more than 4 execution groups, you many have performance issues.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| kwelch |
| Posted: Thu Apr 25, 2002 3:44 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Kiran,
I am confused about your comment if you have 4 cpu box and create more than 4 execution groups you may have a problem. Are you saying that we shouldn't have more than 4 execution groups?i.e. only 1 exec group per cpu??? Currently in our environment( we are still fairly new) we have an execution group for each project. To date we have not had any problems but as I said we are fairly new and don't have a lot of volume as of yet but we anticipate more in the near future. Are we headed for trouble? Could you clarify or explain please?
Thanks!
Karen |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Apr 25, 2002 8:18 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Karen,
To explain further I will give you an example. Lets say if you have 4 CPU box and you define 6 Execution groups. Out of 4 CPUs, 2 of the CPU's will be shared by total 4 Execution grups (assuming there are no other major processes running on that box). Message flows running in shared CPU execution groups will be sharing resources, which may result into performance problems. Within an execution group, the assigned message flows run in different thread pools.
Defining many Execution groups in development environment is not a problem at all. But when you go into production or do volume testing, it is recommended that we create proper number of EGs depending on the number of CPUs on that box. This will give better throughput.
Hope I answered all your questions.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
