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

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

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201...

Adding SSL certificates to a mixed z/OS and Unix queue manager environment - Middleware News

Adding SSL certificates to a mixed z/OS and Unix queue manager environment - Middleware News 1. Security Considerations IBM advises customers who are using SSL, that the most secure way to do this is to use recognized Certification Authorities to sign their certificates. Ensuring secure transfer of information is the main purpose of SSL. This integrity must be properly observed when setting up SSL. You should always be certain who has signed each of your SSL certificates, who has had and who continues to have access to them. The first secure way to generate certificates is to generate a certificate request, on each system or machine that uses SSL. This request has to be signed by an external Certification Authority before it can be used. Getting certificate requests signed by a CA is secure, because during the signing process at no point do any files contain the certificate's Private Keys. This principle is vital to SSL security. Signing certificates in this way is covered...