Migration and Maintenance, the Necessary Evil. Into the Dark for MQ and Message Broker [z/OS & Distributed]

Project and Program: Application Architecture Development and Integration, MQ (Messaging and Queuing along with Integration Bus)

Tags: Proceedings , SHARE in Boston 2013 , 2013

Applying new versions and fix packs of any product can be fraught with danger. What is the best way to apply maintenance? What do we need to test? Do I need to make any configuration changes post installation? What’s my risk? All perfectly valid questions which this session will attempt to answer in relation to the WebSphere MQ and Message Broker products. WebSphere MQ itself has historically had a single migration path for applications and queue manager data on non-zOS platforms. A big enhancement was made in MQ 7.1 on distributed platforms to allow the ability to install new versions of MQ alongside existing releases greatly increasing migration and co-existence options. This session will cover what this means to you and the new co-existence options open for the future. For several releases now WebSphere Message Broker has supported migration & co-existence and v8.0 is no different. We take a look at the various strategies for safely migrating your brokers up to version 8. David Coles; Neil Johnston; Dave Gorman IBM Corporation

David Coles; Neil Johnston; Dave Gorman , IBM Corporation

Back to Proceedings File Library