IBM MQ and IBM Integration Bus - from Migration and Maintenance to Continuous Enhancements, How and Why to Stay Current

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

Tags: Proceedings , SHARE in Orlando 2015 , 2015

Applying new versions and fix packs of any product can be fraught with danger. What is the best way to apply maintenance? What do I need to test? Do I need to make any configuration changes post installation? What are the risks? All perfectly valid questions which this session will attempt to answer in relation to the IBM MQ and IBM Integration Bus products.
It's not just a case of standing still though, what's the best way to find out about and take advantage of new features as you migrate.
IBM 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 IBM Integration Bus, in its previous guise as WebSphere Message Broker, has supported migration & co-existence and v10.0 is no different. We take a look at the various strategies for safely migrating your brokers up to version 10, and how to leverage the new v10.0 features for improved productivity.-David Coles-IBM Corporation

Back to Proceedings File Library