Skip to main content

Uninstalling WebSphere MQ on Linux - Middleware News


Procedure

  1. Before starting to uninstall, end all WebSphere MQ activity.
    1. Log in as a user in group mqm.
    2. Use the dspmq command to display the state of all the queue managers on the system.
    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 the necessary WebSphere MQ processes, type:
      ps -ef | grep mq
    6. Check that there are no processes listed that are running command lines beginning amq orrunmq. Ignore any that start with amqi.
  2. Before you uninstall WebSphere MQ for Linux you must find out the names of the packages (components) currently installed on your system. To list all the packages with their version information, enter the following:
    rpm -q -a | grep MQSeries
rpm -q -a | grep gsk
    Note: If you have applied maintenance to the install, remove these maintenance packages before removing the base install.
  3. Some of the installed packages are dependent on others. The rpm command will not remove a package if others are dependent on it. For this reason you must uninstall the packages in such an order that each one you uninstall has no dependencies from other packages. To list all of the packages on which a named package (for example MQSeriesServer) depends, enter the following:
    rpm -q --requires MQSeriesServer
    Alternatively, remove all the components at the same time by appending all the package names to the rpm command arguments. For example, to remove the runtime, Server and SDK components, enter the following:
    rpm -ev MQSeriesRuntime MQSeriesServer MQSeriesSDK
  4. After uninstalling , you might want to delete the contents of /var/mqm, which is not removed by the uninstallation. Only do this if you do not need your queue manager data. For example, do not delete the content if you plan to migrate to a later version of WebSphere MQ.
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

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