Skip to main content

Migrating to WebSphere MQ for AIX Version 7.0

Migrating to WebSphere MQ for AIX Version 7.0
=================================================

Instructions for migrating to WebSphere® MQ Version 7.0.

About this task

If you want to migrate to WebSphere MQ Version 7.0, complete this task.

If you migrate from a previous level of this product without first backing up your system, you cannot revert to your previous level, so back up your system before you install WebSphere MQ Version 7.0. You can then back out the upgrade if necessary. If you back out the upgrade, however, you cannot recover any work, such as changes to messages and objects, performed by WebSphere MQ Version 7.0.
Procedure

1. Stop all MQ applications on the machine and the applications accessing remote machines.
2. End all WebSphere MQ activity.
1. Log in as a user in group mqm.
2. Start of changeUse the dspmq command to display the state of all the queue managers on the system.End of change
3. Use the endmqm command to stop all running queue managers.
4. Stop any listeners associated with the queue managers, using the command:

endmqlsr -m QMgrName

5. To check that you have stopped all of them, enter the following:

ps -ef | grep mq

Check that there are no processes listed that are running command lines beginning amq or runmq. Ignore any that start with amqi.
3. Log in as root.
4. Function supplied by the SupportPacs in Table 1 has been superseded by function in WebSphere MQ Version 7.0. Remove these SupportPacs before installing WebSphere MQ Version 7.0.
Table 1. SupportPacs superseded by WebSphere MQ Version 7.0SupportPac Number Description
MA0Y WebSphere MQ Bridge for HTTP
Note: If you installed SupportPac MACS, remove the directory /usr/mqm/inc64 and its contents.
Review any other installed SupportPacs for their applicability to WebSphere MQ Version 7.0.
5. Start of change If you are migrating from WebSphere MQ Version 5.3 to WebSphere MQ Version 7.0, you must uninstall WebSphere MQ Version 5.3. If you are migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0, you do not have to uninstall WebSphere MQ because the installation process does it for you. However, when migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0, before installing you must ensure that you manually remove the file sets which have been retired from WebSphere MQ Version 7.0.
* Remove the following file sets before migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0:
o mqm.msg.De_DE
o mqm.msg.Es_ES
o mqm.msg.Fr_FR
o mqm.msg.It_IT
End of change
6. Install WebSphere MQ Version 7.0 by following the tasks set out in Start of changeInstalling a WebSphere MQ serverEnd of change.
7. Restart WebSphere MQ.

* Migrating from an earlier version of WebSphere MQ for AIX client
If you want to migrate to a WebSphere MQ for AIX®, Version 7.0 client from an earlier version of the WebSphere MQ client, you must perform certain tasks.
* Changes to the installation path
The current version of the WebSphere MQ for AIX client installs into a different directory to versions earlier than Version 5.3. If you are migrating from an early version, you need to take action.
* Removal of obsolete code pages from WebSphere MQ for AIX
IBM-850 code pages are no longer supported.
* Defining a transaction program
* After you have migrated to WebSphere MQ Version 7.0
Perform these tasks immediately after you migrate to WebSphere MQ Version 7.0.
Labels:

Comments

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

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

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