Skip to main content

IBM Websphere MQ Directory structure (Windows systems) - Middleware News

Directory structure (Windows systems)

Table 1 shows the directories found under the root c:\Program Files\IBM\WebSphere MQ\. If you have installed WebSphere® MQ for Windows under a different directory, the root is modified appropriately.

Table 1. WebSphere MQ for Windows directory structure\bin     Contains binary files (commands and DDLs).

\config     Contains configuration information.

\conv     Contains files for data conversion in folder \table.

\errors     Contains the system error log files:

    AMQERR01.LOG
    AMQERR02.LOG
    AMQERR03.LOG

These files contain information related errors that are not associated with a particular queue manager. AMQERR01.LOG contains the most recent error information.

This folder also holds any FFST™ files that are produced.

\exits     Contains channel exit programs.

\licenses     Contains a folder for each national language. Each folder contains license information.

\log     Contains a folder for each queue manager. The following subdirectories and files will exist for each queue manager after you have been using that queue manager for some time.

AMQHLCTL.LFH
    Log control file.
Active
    This directory contains the log files numbered S0000000.LOG, S0000001.LOG, S00000002.LOG, and so on.

\qmgrs     Contains a folder for each queue manager; the contents of these folders are described in Table 2. Also contains the folder \@SYSTEM\errors,

\tivoli     Contains the signature file used by Tivoli®.

\tools     Contains all the WebSphere MQ sample programs. These are described in WebSphere MQ for Windows Quick Beginnings.

\trace     Contains all trace files.

\uninst     Contains files necessary to uninstall WebSphere MQ.

Table 2 shows the directory structure for each queue manager in the
c:\Program Files\IBM\WebSphere MQ\qmgrs\ folder. The queue manager might have been transformed as described in Understanding WebSphere MQ file names.

Table 2. Content of a \queue-manager-name\ folder for WebSphere MQ for Windowsamqalchk.fil     Contains a checkpoint file containing information about the last checkpoint.

\authinfo     Contains a file for each authentication information object.

\channel     Contains a file for each channel object.


\clntconn     Contains a file for each client connection channel object.

\errors     Contains error log files associated with the queue manager:

    AMQERR01.LOG
    AMQERR02.LOG
    AMQERR03.LOG

AMQERR01.LOG contains the most recent error information.

\listener     Contains a file for each listener object.

\namelist     Contains a file for each WebSphere MQ namelist.

\Plugcomp     Directory reserved for use by WebSphere MQ installable services.

\Procdef     Contains a file for each WebSphere MQ process definition. Where possible, the file name matches the associated process definition name, but some characters have to be altered. There might be a directory called @MANGLED here containing process definitions with transformed or mangled names.

\Qmanager     Contains the following files:

Qmanager
    The queue manager object.
QMQMOBJCAT
    The object catalogue containing the list of all WebSphere MQ objects, used internally.
    Note: If you are using a FAT system, this name is transformed and a subdirectory created containing the file with its name transformed.
QAADMIN
    File used internally for controlling authorizations.


\Queues     Each queue has a directory here containing a single file called Q. Where possible, the directory name matches the associated queue name but some characters have to be altered. There might be a directory called @MANGLED here containing queues with transformed or mangled names.

\services     Contains a file for each service object.

\ssl     Contains SSL certificate stores.

\Startprm     Contains temporary files used internally.

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