MQSeries.net :: View topic

jfluitsm · Posted: Wed Oct 12, 2005 12:34 am Post subject:

Matt,

I think that the migration has two different areas.

There is the technical migration, that is not too difficult although might be some work. Indeed V6 and especially the co-existence will help a lot as it is now feasible to migrate bit-by-bit without the need for extra servers. Also that the ConfigMgr doesn't need Windows and DB2 anymore is of much help.

However the most difficult part is implementing the new development environment. Here are a lot of issues to solve, just to mention a couple:

Work-in-progress and related resources are stored locally per developer, most likely this needs larger home-dirs on the workstations.

Resources have to be organized into projects, as projects are stored in repositories the organisation of projects is not personal.

Deployment procedures will change because of the use of the .bar files, including a decision on what will be put in a single .bar file.

Subflows can no longer be deployed, all containing main flows have to be deployed (I regard this as a good thing, now it is possible to control when a flow uses the new version of the subflow)
This is not a complete list. These issues are not solved by the V6 software, and it can't be as the best solutions might be different for each site. These issues are also the reason why we advice our customers to do a Proof-of-Concept.

For some this might look scaring but you might find yourself in one of the two situations:

You don't have many flows and don't have much development. Then simple pragmatic solutions can be chosen.

You have many flows and do much development. Then V5/V6 will improve development. Developers are mostly pleased with the new UI and debugging flows is now feasibly.
_________________
Jan Fluitsma

IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6