Skip to main content

Configuring client connection to a IBM MQ Appliance queue manager using Client Channel Definition Table (CCDT) - Middleware News

Queue manager stores the client connection channel information in client channel definition table (CCDT). This table is updated whenever a client connection channel is defined or altered.  MQ client applications uses the client channel definition table (CCDT) to determine the channel definitions and authentication information to connect to a queue manager.  For a client application to use the CCDT , it must either be copied to the client machine or the file should be placed in a location from where the client can access it. However, there is no traditional file system available on the appliance. Hence the file needs to be copied to a directory from where it can be downloaded. 
Here are the steps to do it.
Run the below command on the appliance to create the required MQ objects and a user account under which the client connection will be established.
usercreate -u maya -p passw0rd
crtmqm QM1
strmqm QM1
runmqsc QM1
    DEFINE QLOCAL(‘Q1’)
    DEFINE CHANNEL(‘CLNTCHL’) CHLTYPE(SVRCONN) TRPTYPE(TCP)
    DEFINE CHANNEL(‘CLNTCHL’) CHLTYPE(CLNTCONN) QMNAME(‘QM1’) CONNAME(_ADDRESS>(2323)’) TRPTYPE(TCP)
    DEFINE LISTENER(‘L1’) TRPTYPE(TCP) PORT(2323)
    START LISTENER(‘L1’)
    END

Set channel authentication rule to accept connection from the IP address of your client system
    SET CHLAUTH ('CLNTCHL') TYPE(ADDRESSMAP) ADDRESS(9.109.242.213) MCAUSER('maya')
Grant access to the user account ‘maya’ so that it can connect to and inquire the queue manager and also has the authority to put , get , inq and browse the queue Q1
   SET AUTHREC OBJTYPE(QMGR) PRINCIPAL('maya') AUTHADD(CONNECT,INQ)
   SET AUTHREC PROFILE('Q1') OBJTYPE(QUEUE) PRINCIPAL('maya') AUTHADD(PUT,GET,INQ,BROWSE)

Steps to download CCDT to a client machine:
In order to download the CCDT to the client machine, it must be first copied to a location from where the file can be downloaded.
  • Run the following command on the appliance to generate the AMQCLCHL.TAB file in the      mqbackup:// URI.
rcrmqobj –m QM1 –t clchltab
This command creates a file with name rName>_AMQCLCHL.TAB in the mqbackup:// URI.
Example:
QM1_AMQCLCHL.TAB
Use webui  to download the CCDT file to the client machine to the directory of your choice.

Steps to run a sample application using the downloaded CCDT in client machine:
  • On the windows client machine set the MQSAMP_USER_ID environment variable to identify the user that is running the sample programs
  • set MQCHLLIB and MQCHLTAB environment variables to specify the location and name of the CCDT respectively.
Example:


Alternatively, client channel definition table can be generated on the MQ client machine by using runmqsc client.  
Create CLNTCONN channel definition on the client machine by using runmqsc command with –n option.
Example:
runmqsc -n
   DEFINE CHANNEL(‘CLNTCHL’) CHLTYPE(CLNTCONN) QMNAME(‘QM1’) CONNAME(_ADDRESS>(2323)’) TRPTYPE(TCP)
   END
The above command creates a channel definition table file in the MQ data directory. On Linux the default location is /var/mqm and on windows the default location is C:\ProgramData\IBM\MQ. This file can then be used for connecting to the appliance queue manager.


Comments

  1. great information sir...you are awesome...hat's up :-)

    ReplyDelete
  2. I really appreciate the information shared above. It’s of great help. If someone wants to learn Online (Virtual) instructor lead live training in IBM SECURITY ACCESS MANAGER, kindly contact us http://www.maxmunus.com/contact
    MaxMunus Offer World Class Virtual Instructor-led training on IBM SECURITY ACCESS MANAGER. We have industry expert trainer. We provide Training Material and Software Support. MaxMunus has successfully conducted 100000+ pieces of training in India, USA, UK, Australia, Switzerland, Qatar, Saudi Arabia, Bangladesh, Bahrain, and UAE etc.
    For Demo Contact us.
    Avishek Priyadarshi
    MaxMunus
    E-mail: avishek@maxmunus.com
    Skype id: avishek_2.
    Ph:(0) 8553177744 / 080 - 41103383
    http://www.maxmunus.com/

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

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