Comments on: Mission:Messaging: Migration, failover, and scaling in a WebSphere MQ cluster https://t-rob.net/2008/12/02/missionmessaging-migration-failover-and-scaling-in-a-websphere-mq-cluster/ A blog about securing and using WebSphere MQ Wed, 26 May 2010 13:01:59 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Michael Dag https://t-rob.net/2008/12/02/missionmessaging-migration-failover-and-scaling-in-a-websphere-mq-cluster/comment-page-1/#comment-201 Michael Dag Mon, 08 Dec 2008 09:35:50 +0000 http://t-rob.net/?p=177#comment-201 Hi T-Rob, hope you can change the text. To answer your questions, yes attributes that should not change or are not mentioned are preserved, the programs generate ALTER or DEFINE commands as required (DEFINE only when an object does not exist already). REPLACE is not used unless you specifically ask for it. Lastly the MQArchitect Implementation streamliner directly interacts at runtime with WebSphere MQ and even preserves the values of the changed attributes (so you can roll-back any changes!!!) There is also the option generate scripts in advance, but these scripts obviously do not have the capability to preserve previous values, more information can be found on: http://www.mqsystems.com :-) Hi T-Rob,
hope you can change the text.
To answer your questions, yes attributes that should not change or are not mentioned are preserved, the programs generate ALTER or DEFINE commands as required (DEFINE only when an object does not exist already). REPLACE is not used unless you specifically ask for it.
Lastly the MQArchitect Implementation streamliner directly interacts at runtime with WebSphere MQ and even preserves the values of the changed attributes (so you can roll-back any changes!!!) There is also the option generate scripts in advance, but these scripts obviously do not have the capability to preserve previous values, more information can be found on: http://www.mqsystems.com :-)

]]> By: T.Rob https://t-rob.net/2008/12/02/missionmessaging-migration-failover-and-scaling-in-a-websphere-mq-cluster/comment-page-1/#comment-195 T.Rob Sun, 07 Dec 2008 14:08:29 +0000 http://t-rob.net/?p=177#comment-195 Thanks, Michael! I will see if I can have that line deleted. Not sure how that snuck past us. :-) When you say your products work from a state point of view, does that mean they preserve all the attributes other than the ones you wish to change? Do they produce ALTER commands or DEFINE/REPLACE and does this happen at run time or can you prepare the scripts in advance? Thanks, Michael! I will see if I can have that line deleted. Not sure how that snuck past us. :-)

When you say your products work from a state point of view, does that mean they preserve all the attributes other than the ones you wish to change? Do they produce ALTER commands or DEFINE/REPLACE and does this happen at run time or can you prepare the scripts in advance?

]]> By: Michael Dag https://t-rob.net/2008/12/02/missionmessaging-migration-failover-and-scaling-in-a-websphere-mq-cluster/comment-page-1/#comment-193 Michael Dag Sat, 06 Dec 2008 11:05:31 +0000 http://t-rob.net/?p=177#comment-193 Hi T-Rob, great contribution as always! please update listing 2: ALTER CHANNEL(QM1.QM2) CHLTYPE(SDR) + CONNAME('host.of.qm2(1414)') Remove: PUT(DISABLED) as it is not an attribute of a Channel! The DEFINE/ALTER interface is not of this time, either for Point-to-Point or the SOA paradigm. Both MQDocument and MQArchitect work from a "state" point of view, just say "what you want" and they will make the appropriate MQSC commands for you and even execute them if needed! For more information see: www.mqsystems.com Hi T-Rob,
great contribution as always!

please update listing 2:
ALTER CHANNEL(QM1.QM2) CHLTYPE(SDR) +
CONNAME(‘host.of.qm2(1414)’)

Remove: PUT(DISABLED) as it is not an attribute of a Channel!

The DEFINE/ALTER interface is not of this time, either for Point-to-Point or the SOA paradigm.
Both MQDocument and MQArchitect work from a “state” point of view, just say “what you want” and they will make the appropriate MQSC commands for you and even execute them if needed!

For more information see: http://www.mqsystems.com

]]>