| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| One Config Manager with two brokers |
« View previous topic :: View next topic » |
| Author |
Message
|
| Yanghui |
 Posted: Tue Oct 29, 2002 6:42 am Post subject: One Config Manager with two brokers |
 |
|
Disciple
Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland
|
Hi,
I've got an awkward situation of using one config manager for both my development and systest brokers. We want to use the two brokers this way. When one messagflow is done and tested by developers in the development broker, then it is promoted to the systest broker for further testing. Since we are using one config manager for both brokers, we found it's impossible to seperate two versions of same one msgflow within one config manager. Yes, we can use different name for different version since config manager is not working as a file system in which a file with same name can be kept in different directories but it's very easy to mix them up especially when a lot subflows are used and each of them keeps change. We have Message Flow Category in control center but it's only for grouping purpose. In config manager, all message flows are stored flatly.
My question is that in one config manager, is it possible to have two or more complete seperated areas for keeping different msgflow with same name? Any idea about how to achieve this is highly appreciated. We just don't like the idea of having another extra NT box for this simply msgflow promotion. BTW, does anybody know how to install more than one config manager on one NT box? I heard it can be done but never figure out how.
Many thanks in advance.
Best regards
-Yanghui |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Oct 30, 2002 5:46 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| Yanghui wrote: |
My question is that in one config manager, is it possible to have two or more complete seperated areas for keeping different msgflow with same name? Any idea about how to achieve this is highly appreciated. We just don't like the idea of having another extra NT box for this simply msgflow promotion. BTW, does anybody know how to install more than one config manager on one NT box? I heard it can be done but never figure out how.
|
current configuration doesn't support this.
_________________
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 |
|
|
| jsware |
| Posted: Fri Nov 01, 2002 12:29 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
I would recommend you have three configuration managers, one for development, one for systest and another for production. When you want to promote, export the flow out of the dev config manager and import it into the systest.
You can also save the flow in a version control system (CVS, Sourcesafe, PVCS etc. etc) and label it so that you have a history of changes, without cluttering up any config mgrs with multiple versions of the same thing.
Keeping separate versions can also cause problems because if you have sub-flows, then they can end up being referenced by the wrong parent flow/ vica-versa.
Also we found that when developers started trying to use the config mgr to hold multiple version of the same thing, they ended up copying the flow and renaming/using the copy as the new version. When we exported and imported these flows into production, the config mgr complained that the flow being imported had the same name as one that already exists. Each flow has an internal unique identifier and the copy which they made into version 2 had a different id but the same readable name... |
|
| Back to top |
|
|
| Yanghui |
| Posted: Mon Nov 04, 2002 3:15 am Post subject: |
|
|
Disciple
Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland
|
Thanks for the response.
The problem to us is that we have too many different WMQI enviornments. Besides the three you mentioned, we also have two extra, UAT (User Acceptance Test) and contingency. Too many NT boxes have been setup only for msgflow deployment.
Actually I have been thinking of the SupportPac IC01 but now I am almost certain that it won't help either. Two reasons. A) it doesn't support any UNIX platform. All our brokers are runing on Solaris. B). even it supports UNIX, the commands mqsiassign and mqsideploy still need to communicate with ConfigMgr somewhere.
I think it could be much nicer if a broker could be managed without configmgr. If that's the case, we could save at least 4 NT boxes. Hope IBM will think about this option. |
|
| Back to top |
|
|
| tchagan |
| Posted: Mon Nov 04, 2002 6:19 am Post subject: |
|
|
Apprentice
Joined: 10 Feb 2002
Posts: 31
|
Hi,
IC01 is used to communicate with your config manager, there would be no use having the utility on UNIX as config managers are NT based. Use IC01 to split your exported message flows into individual flows and sub-flows and then code control them (CVS, PVCS etc).
We have had the same problem but did manage to use a single config manager for dev and systest although with few developers and strict controls for who had what code. Basically by the time we got to systest we had put everything into PVCS so we controlled code access through this mechanism by enforcing the process.
Terry |
|
| Back to top |
|
|
| dougie |
| Posted: Thu Nov 14, 2002 2:40 am Post subject: Our Solution |
|
|
Newbie
Joined: 12 Nov 2002
Posts: 6
|
| We use exactly the same situation as yourselves. The way we have coped is to prefix each messageflow with DV and then copy and rename the messageflow with the prefix ST before moving it to the ST broker. We also have a version number suffix that remains constant when promoting the flow through the environments thus being a link to the original M/F. Sub flows make things a bit more difficult in our case the DV prefix remains in dev but the prefix is dropped when moving into systems testing - not great but it works!. |
|
| 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
|
|
|
|
