| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| WMQI architecture |
« View previous topic :: View next topic » |
| Author |
Message
|
| kwelch |
 Posted: Wed Mar 12, 2003 1:54 pm Post subject: |
 |
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi,
Thanks for the clarification. It's kind of a bummer for us though. Our environment is in constant change. We only wanted to change a promoted item on something in the messageflow. The subflow, where the bulk of the development coding is, went too. Usually we are only changing the subflow which can go on it's own. Just another thing to be aware of so we know to go in and delete and put the old one back whenever we change a messageflow and don't want the subflow to go.
As for the ALTERNATE config mgrs. interesting idea, we will have to think more on that one.
Karen |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Mar 12, 2003 8:32 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Karen,
We use supportPac IC01 to export message flows from the configuration manager. Unlike Control Center export, this supportPac export individual message flow/subflow into seperate XML file. We then version control this xml file using ClearCase and then migrate it to the higher region.
I personally don't like the idea of alternate config mgr as it builds lots of dependencies and at a given point of time you have access to single environment. As zpat said, It would be great to have this limitation removed.
_________________
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 Mar 13, 2003 10:59 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi Kirani,
Thanks for that info on the support pac.
As you were saying the alternate configmgr does have some dependancies. If it were only the WMQI that was involved in the production fix, it wouldn't be bad but if any of the other apps were involved, they would need a similar way to make their fixes. It seems like we just need another production fix path for these issues.
I am still interested in hearing others ideas on this though.
Karen |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
