| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Best paractices for WMQI |
« View previous topic :: View next topic » |
| Author |
Message
|
| kb |
 Posted: Fri May 16, 2003 12:17 am Post subject: Best paractices for WMQI |
 |
|
Newbie
Joined: 26 Nov 2002
Posts: 5
|
Hi,
I have been asked to construct some best-practice processes/standards around developemnt work using WMQI.
I have looked at the support pacs, but have have the following quesitons/ideas.
1) I would like to be able to use a tool to create a design do retrospectively from an XML file export of a messae Flow?. IS this possible? Has anyone written a stylesheet to do this?
2) What is the best way of specifiying queue manager and queue names, so that when you move from dev-->test-->production, the changes can be made cleanly? I have though to using ALIASes, environment variables, or apply a change to exported XML file. ANy ideas??
3) Similarly to 2) if a database conenction is to be used, where should the connection and login information be stored so that it can be accessed within WMQI, and easily changed as we migrate from dev to test etc.
4) Does anyone have any ideas on a suitable dev process for WMQI, so that it takes advantage of its quick developemnt potential, while allowing it to maintain the quality approach of a traditonal devlopment process?
Any ideas/suggestions/pointers very welcome.
Thanks
KieranB |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri May 16, 2003 5:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Quote: |
| 1) I would like to be able to use a tool to create a design do retrospectively from an XML file export of a messae Flow?. IS this possible? Has anyone written a stylesheet to do this? |
It's possible, yes. I know other people have done it for their own internal purposes. However, if IBM changes the format of the exported XML file, you will have to change your stylesheet.
| Quote: |
| 2) What is the best way of specifiying queue manager and queue names, so that when you move from dev-->test-->production, the changes can be made cleanly? I have though to using ALIASes, environment variables, or apply a change to exported XML file. ANy ideas?? |
Leave queue manager blank. Use the same queue name on dev, test, and production - or get used to changing it. If you are doing an import/export between environments, then yes you could change the XML file.
This is supposed to be much more flexible in the next release (if the technology preview is reliable.. which it should be). There will be deployment descriptors, like with WAS, that will allow these to be changed during deployment.
| Quote: |
| 3) Similarly to 2) if a database conenction is to be used, where should the connection and login information be stored so that it can be accessed within WMQI, and easily changed as we migrate from dev to test etc. |
You can't change login information, since it's not stored with the message flow. You only need to change connection information in your message flows if the ODBC connection names are different in each enviornment. If they are, you have the same options as 2.
| Quote: |
| 4) Does anyone have any ideas on a suitable dev process for WMQI, so that it takes advantage of its quick developemnt potential, while allowing it to maintain the quality approach of a traditonal devlopment process? |
Follow your traditional development processes. If those processes take so much time that you have lost the quick development potential of WMQI, you need to address that separately from WMQI. |
|
| 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
|
|
|
|
