Skip to main content

Uninstalling IBM WebSphere MQ on AIX - Middleware News


Uninstalling WebSphere MQ on AIX

On AIX, you can uninstall theWebSphere MQ server or client using the System Management Interface Tool (SMIT) or the installp command.

Before you begin

If any updates have been applied, remove them before starting this uninstallation procedure. For more information, see AIX: Restoring the previous maintenance level on WebSphere MQ version 7.1.

Procedure

  1. Stop all WebSphere MQ applications associated with the installation you are uninstalling.
  2. For a server installation, end any WebSphere MQ activity associated with the installation you are uninstalling:
    1. Log in as a user in the group mqm.
    2. Set up your environment to work with the installation you want to uninstall. Enter the following command:
      . MQ_INSTALLATION_PATH/bin/setmqenv
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.
    3. Display the state of all queue managers on the system. Enter the following command:
      dspmq -o installation
    4. Stop all running queue managers associated with the installation you want to uninstall. Enter the following command for each queue manager:
      endmqm QMgrName
    5. Stop any listeners associated with the queue managers. Enter the following command for each queue manager:
       endmqlsr -m QMgrName
  3. Log in as root.
  4. Uninstall WebSphere MQ using either installp or smit. If WebSphere MQ was installed in a non-default location, you must use installp to uninstall.
    • Uninstall using installp by entering one of the following commands:
      • For an installation in the default location /usr/mqm
        installp -u mqm
      • For an installation in a non-default location:
        installp -R usil -u mqm
        where usil is the path of the User Specified Install Location (USIL) specified when the product was installed.
    • Uninstall using smit:
      1. Select the required smit window using the following sequence:
          Software Installation and Maintenance
            Software Maintenance and Utilities
              Remove Installed Software 
      2. List the software in the SOFTWARE name field:
        1. Enter .
        2. Press F4
      3. Select the file sets to uninstall from the list (those beginning with mqm), and pressEnter. There is an option at this stage to do a preview. Leave the option set to the default value of Yes to preview the file sets you are uninstalling, or select No to not preview these file sets.
      4. Press Enter on the Remove Installed Software panel, it asks whether you are sure, press Enter.

What to do next

  • If the product successfully uninstalled, you can delete any files and directories contained in the/usr/mqm directory under the User Specified Install Location (USIL) specified in the installpuninstallation command.
  • Use the lslpp command to check for other products installed in the USIL. If there are no other products installed in the USIL and you do not intend to use it again, you can delete the USIL using the rmusil command.
  • If there are no other WebSphere MQ installations on the system, and you are not planning to reinstall or migrate, you can delete the /var/mqm and /etc/opt/mqm directory trees. Deleting these directories destroys all queue managers and their associated data.

Comments

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...

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...

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 ...