Skip to main content

WebSphere / IBM MQ Migration Guide - Middleware News

The WebSphere / IBM MQ Self-help Migration Guide is designed to help users choose, plan, and simplify the process of migrating from an older version of MQ to a new version. If you are running z/OS, see our related blog entry WebSphere / IBM MQ for z/OS Migration Guide.

You can click on Migration Guide to run it in your web browser or download the PDF using the "Download Now" button at the bottom of this blog entry.

This guide is broken down into the following parts:

Planning your Migration
This section contains guidelines and references to help you Check Pre-reqs for your planned target version to ensure compatibility. As shown in Figure 1, this section allows you to check pre-requisites that are specific to MQ as well as other related IBM products for your target version. This step is critical to ensure overall compatibility and support.
Figure 1

Determine your migration path
As shown in Figure 2, to determine your migration (or upgrade) path you may need to check the product documentation of your current release and review new features offered in the later releases to which you may be migrating. This will help you find specific features available in these releases and give you a better idea of which release you should migrate to. There is also a link to the planning guide for the target release that provides information on what is involved in the migration to that release, so that you can plan the order and extent of the migration of components and other resources. The potential impact covers any specific major effect or change that is associated with any of the releases, so as a user you are aware of the potential impact that the migration may have.
Figure 2

Preparing for your migration
As shown in Figure 3, this section details the migration options and considerations for each of the options. It also contains an explanation of the differences between the migration methods as they relate to MQ.
Figure 3

Executing your Migration
Once you have decided what target version you will be migrating to and planned for the migration option, you can review this section for executing your migration. As shown in Figure 4, this section lists the tasks of installation and executing the migration option.
Figure 4

Supplemental Info
The supplemental info section lists the useful migration resources including a compilation of all the links provided through the entirety of this guide into a single pdf file for your convenience. See Figure 5.
Figure 5

Case Studies
This section includes two sample scenarios.
Figure 6

Conclusion
The Migration Guide is built to walk users step by step through the MQ migration process, from planning to execution. The guide also contains a list of useful links and resources that migration users would typically need to follow, regardless of any environment distinction. Click the "Download Now" button below to download the interactive PDF.
Labels:

Comments

  1. HiFriendDecember 24, 2015 at 9:22 AM

    Please let me know if we have any article related to MB patching in AIX with response file.

    ReplyDelete

Post a Comment

adsrerrapop

Popular posts from this blog

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...
Post a Comment
Read more

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...
Post a Comment
Read more

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...
143 comments
Read more