IBM Middleware Design Solutions.

MQSeries Tree structure!!

.--- queue manager ------.
queue  
| | .--- local QL
| | .--- remote QR
| | .--- transmit QX
| | .--- alias QA
| | .--- model QM
| | .--- dynamic QD
| | .--- cluster QC    
message channels (uni-directional)
| | .--- sender
| | .--- receiver
| | .--- server
| | .--- requester
| | .--- cluster sender
| | .--- cluster receiver  
MQI channel (bi-directional)
| | .--- server-connection
| | .--- client-connection

MQSeries Tips and triks....

1. Channel names are restricted to 22 chars length !
2. Display listeners : use netstat -an | find "14".
3. You are advised to give the transmission queue the same name as the target queue manager so that the queue is found by default.
   When you define a Remote Queue, you can provide the name of a transmission queue. You do not have to specify this. If you do not, a transmission queue with the same name as the target queue manager is used, or, if this does not exist, the default transmission queue is used.
4. The XMITQ name must match the remote queue manager name in order for remote administration to work, unless you are using a queue manager alias.
5. You are advised to create a DLQ for any queue manager you define.
6. You are advised to know the name of the default queue manager and verify it exists.
7. To dump a queue to a file Use QLOAD (MO03) - it preserves Message ID.
8. MQVER - display MQ version and CSD level.
9. DSPMQ - display all queue manages names and status.
10. CRTMQM / STRMQM / ENDMQM / DLTMQM - create / start / stop / delete a queue manager.
11. AMQSPUT - *** 1 msg per line ***.
12. AMQSGET
13. AMQSGBR - browse all messages in queue - Data only.
14. AMQSBCG - browse all messages in queue - Data and Headers.
15. To connect the client to a (remote) Qmgr :
    qmn := 'CHANNEL.SVRCONN/TCP/17.16.16.19(1414)' ;
16. Input params : qMgr, qName, numConnect, delayConnect, numMsgs, delayMsgs, sizeMsg, fileMsg, verbose.
17. RUNMQLSR / ENDMQLSR - manage Listener.
18. STRMQCSV / ENDMQCSV / DSPMQCSV - manage Command Server.
19. 
    

1.Instead of defining a Receiver channel, define a Requester channel, so it can be initiated from the receiver end.

You have to specify the remote's site Listener port (and IP), as SYSTEM. REQUESTER channel will be used.

2.To allow Remote Administration, a Queue Manager must define a Server Connection Channel, ( SYSTEM.ADMIN/DEF.SVRCONN may be used ) have the Commans Server running, as well as the Listener.

DEFINE CHANNEL(MY.ADMIN) CHLTYPE(SVRCONN) DESCR('Admin connection
') MCAUSER('mqm') dspmqcsv = display Command Server status str
mqcsv = start Command Server ps -ef | grep runmqlsr runmqlsr -
m -t TCP -p alter channel(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN
) mcauser('mqm')

3.Como activar la Configuration / Administration Remota de un QMgr ? Hace falta :

QMgr function : dspqm/strmqm SUNQM1

Listener running : runmqlsr -m SUNQM1 -t TCP -p 1415

Command Server running : strmqcsv/dspmqcsv SUNQM1

canales (at FMCQM) FMCQM.SUNQM1 (sender) y SUNQM1.FMCQM (receiver)

 MQ remote :Show Queue Manager

Remote (not Local)

Name ( nom REAL del Qmgr )

Conexion ( @ IP  Listener Port !!! )

Command name	Purpose
amqccert	Check certificate chains
amqmdain	Configure or control WebSphere MQ services (Windows® systems only)
amqoamd	Output setmqaut commands
amqtcert	Transfer certificates
crtmqcvx	Convert data
crtmqm	Create a local queue manager
dltmqm	Delete a queue manager
dmpmqaut	Dump authorizations to an object
dmpmqlog	Dump a log [url]
dspmq	Display queue managers
dspmqaut	Display authorizations to an object
dspmqcsv	Display the status of a command server
dspmqfls	Display file names
dspmqras
dspmqrte	Display route application
dspmqtrc	Display formatted trace output (UNIX® systems only)
dspmqtrn	Display details of transactions [pareja de rsvmqtrn]
dspmqver	Display version number
endmqbrk
endmqcsv	Stop the command server on a queue manager
endmqdnm	Stop .NET monitor
endmqlsr	Stop the listener process on a queue manager
endmqm	Stop a local queue manager
endmqtrc	Stop tracing for an entity
ffstsummary
mqftapp	Run the File Transfer Application
mqftrcv	Receive file using the File Transfer Application (server)
mqftrcvc	Receive file using the File Transfer Application (client)
mqftsnd	Send file using the File Transfer Application (server)
mqftsndc	Send file using the File Transfer Application (client)
rcdmqimg	Write an image of an object to the log
rcrmqobj	Recreate an object from their image in the log
rsvmqtrn	Commit or back out a transaction [pareja de dspmqtrn]
runmqbrk
runmqchi	Start a channel initiator process
runmqchl	Start a sender or requester channel
runmqckm
runmqdlq	Start the dead-letter queue handler
runmqdnm	Run .NET monitor
runmqlsr	Start a listener process
runmqsc	Issue MQSC commands to a queue manager
runmqtmc	Invoke a trigger monitor for a client (AIX® clients only)
runmqtrm	Invoke a trigger monitor for a server
setmqaut	Change authorizations to an object
setmqcrl	Set certificate revocation list (CRL) LDAP server definitions (Windows® systems only)
setmqprd	Enroll production license
setmqscp	Set service connection points (Windows® systems only) Publish the client-connection channel definitions in Active Directory instead of using environment variables MQCHLLIB and MQCHLTAB
strmqcsv	Start the command server for a queue manager
strmqm	Start a local queue manager
strmqtrc	Enable tracing

MQSeries: Establishing Communication between two Queue Managers....

I want to put this question because most of the people who are just beginning working with mqseries may go wrong in some aspects.  Let me put those points here so that it won't be a big deal while trying this.

1) Suppose we are trying to establish communication between two queue managers sitting on two nt machines which are in different domain, then the necessary things to do are.....i) The user_id with which the sender has logged in has to appear in the receiver's machine.  This is irrespective of domain.  ii)  After doing this you have to give authorities to the user id to send messages to the receiving queue manager.  To achieve this you have to use the commands

setmqaut -m qmgr_name -n queue_name -t queue -p user_id +allmqi

by doing this you are giving permissions for all mqi calls

2) Make sure that the queue managers on different machines which are trying to communicate are listening at the same port.  For Example, if one queue manager on the first machine is listening at 1430, the second queue manager on the second machine should also listen at 1430.  Otherwise it the sender won't recognize the receiver queue manager and will throw an exception

MQSeries Adapters.

From IBM

–CICS Bridges, IMS Bridge, SAP Bridge, Notes Bridge, ...

•

From 75 other vendors

–

More than 150 adapters

–databases, ERP, CRM, MOM, message brokers, packaged

–applications, transaction managers

MQSeries message, Queue, Queue Manager..!!!

Version 6.0 offers improved support for Secure Sockets Layer (SSL), the Internet standard for secure communication.


MQSeries
MQSeries is a middleware product from IBM that runs on multiple platforms and enables applications to send messages to  other applications.  Basically, the sending  application PUTs a message on a Queue, and the receiving application GETs the message from the Queue. The sending and receiving applications do not have to be on the same platform, and do not have to be executing at the same time.

  MQSeries takes care of all the storage, logging and communications details required to guarantee delivery of the message to the destination queue. In most cases, it will take care of translating the data when the source and destination use different character sets (EBCDIC on MVS vs. ASCII on NT or Unix). All the applications have to do is know the name of the Queue and agree on the meaning of the message.


                                  Message = Header(s) + Application Data

A message consists of a header and the attached application data.

Headers typically contain elements like:

• Unique Message Id

• Routing information

• Message format

The following are examples of the data part of a message:

• A record from an indexed or flat file

• A row from a DB2 table

• Individual columns from DB2 tables

• Multiple rows or records

       A queue is simply a place to put data

This figure shows how messaging works in the simple case where the program putting the message and program getting the message are both on the same computer and connected to the  same queue manager.

A queue manager is the subsystem software which controls access to the individual queues assigned to it. The queue manager logs all activity with each individual queue thus creating an audit trail. Multiple queue managers can coexist with each other. The limiting factor is the availability of system resources.

Websphere MQ basic imortant questions.

To be able to browse or change these MQ Config properties, the WebSphere MQ Queue Manager on which the queue resides must be configured for remote administration and be running. You must also have installed the WebSphere MQ client. If you have not done this, the administrative console displays messages like the following:
The WMQQueueDefiner MBean has encountered an error.
WMSG0331E: The MQ Client is required for this functionality, but it is not installed.
These MQ Config properties can be used only to view or change the properties of local queues. You cannot use MQ Config to administer alias or remote queues.Some properties displayed are read-only and cannot be changed.  The property values that you specify must match the values that you specified when configuring WebSphere MQ JMS resources.
In WebSphere MQ, names can have a maximum of 48 characters, with the exception of channels which have a maximum of 20 characters.


1.Base Queue Name
The name of the local queue to which messages are sent, on the queue manager specified by the Base Queue Manager Name property.
                 Data type                                                                 String


2.Base Queue Manager Name

The name of the WebSphere MQ queue manager to which messages are sent.
This queue manager provides the queue specified by the Base Queue Name property.
                 Data type                                                                 String


3.Queue Manager Host


The name of host for the queue manager on which the queue destination is created.
                   Data type                                                                 String


4.Queue Manager Port

The number of the port used by the queue manager on which this queue is defined.
                Data type                   Integer    
                Range                         A valid TCP/IP port number. This port must be configured on the 
                                                                        WebSphere   MQ queue   manager.


5.Server Connection Channel Name

The name of the channel used for connection to the WebSphere MQ queue manager.
               Data type                                                 String
               Range                                       1 through 20 ASCII characters


6.User ID

The user ID used, with the Password property, for authentication when connecting to the queue manager to define the queue destination.
If you specify a value for the User ID property, you must also specify a value for the Password property.
                   Data type                                                                 String


7.Password


The password, used with the User ID property, for authentication when connecting to the queue manager to define the queue destination.
If you specify a value for the User ID property, you must also specify a value for the Password property.
                          Data type                                                                 String

8.Description

The WebSphere MQ queue description, for administrative purposes within WebSphere MQ.
                    Data type                                                    String
                   Default                                                                       Null
                   Range                                                                        1 through 64 ASCII characters.


9.Inhibit Put

Whether or not put operations are allowed for this queue.
               Data type            Enum
                     Default                Put Inhibited

Range

Put Allowed Put operations are allowed for this queue. Put Inhibited Put operations are not allowed for this queue.

10.Persistence

Whether messages on the queue are persistent or non-persistent.

Data type	Enum
Default	Persistent
Range	Persistent Messages on the queue are persistent. Non persistent Messages on the queue are not persistent.

11.Cluster Name

The name of the cluster to which the WebSphere MQ queue manager belongs.
If you specify a value for Cluster Name, you should not specify a value for Cluster Name List.

Data type	String
Default	Null
Range	A valid WebSphere MQ name for a queue manager cluster, as 1 through 48 ASCII characters

12.Cluster Name List

The name of the cluster namelist to which the WebSphere MQ queue manager belongs.
If you specify a value for Cluster Name, you should not specify a value for Cluster Name List. 

Data type	String
Default	Null
Range	A valid WebSphere MQ name for a list of queue manager clusters, as 1 through 48 ASCII characters

13.Default Binding

The default binding to be used when the queue is defined as a cluster queue.

Data type	Enum
Default	On Open
Range	On Open The queue handle is bound to a specific instance of the cluster queue when the queue is opened. Not Fixed The queue handle is not bound to any particular instance of the cluster queue. This allows the queue manager to select a specific queue instance when the message is put, and to change that selection subsequently should the need arise.

14.Inhibit Get

Whether or not get operations are allowed for this queue.

Data type	Enum
Default	Get Inhibited
Range	Get Inhibited Get operations are not allowed for this queue. Get Allowed Get operations are allowed for this queue.

15.Maximum Queue Depth

The maximum number of messages allowed on the queue.

Data type	Integer
Units	Number of messages
Default	0
Range	A value greater than or equal to zero, and less than or equal to 640 000. For more information about the maximum value allowed, see the WebSphere MQ MQSC Command Reference. If this value is reduced, any messages that are already on the queue are not affected, even if the number of messages exceeds the new maximum.

16.Maximum Message Length

The maximum length, in bytes, of messages on this queue.

Data type	Integer
Units	Number of bytes
Default	0
Range	A value greater than or equal to zero, and less than or equal to the maximum message length for the queue manager and WebSphere MQ platform. For more information about the maximum value allowed, see the WebSphere MQ MQSC Command Reference. If this value is reduced, any message that is already on the queue are not affected, even if the message length exceeds the new maximum.

17.Shareability

Whether multiple applications can get messages from this queue.

Data type	Enum
Default	Shareable
Range	Shareable More than one application instance can get messages from the queue. Not Shareable Only one application instance can get messages from the queue.

18.Input Open Option

The default share option for applications opening this queue for input

Data type	Enum
Default	Exclusive
Range	Exclusive The open request is for exclusive input from the queue. Shared The open request is for shared input from the queue.

9.Message Delivery Sequence

The order in which messages are delivered from the queue in response to get requests.

Data type	Enum
Default	FIFO
Range	FIFO Messages are delivered in first in first out (FIFO) order. Priority is ignored for messages on this queue. Priority Messages are delivered in first-in-first-out (FIFO) order within priority. This is the default supplied with WebSphere MQ, but your installation might have changed it.

20.Backout Threshold

The maximum number of times that a message can be backed out. If this threshold is reached, the message is requeued on the backout queue specified by the Backout Requeue Name property.

The WebSphere MQ queue manager keeps a record of the number of times that each message has been backed out. When this number reaches a configurable threshold, the connection consumer requeues the message on a named backout queue. If this requeue fails for any reason, the message is removed from the queue and either requeued to the dead-letter queue, or discarded.

Data type	Integer
Default	0
Range	0 Never requeue messages 1 or more The number of times that a message has been backed, at which the message is requeued on a named backout queue.

21.Backout Requeue Name

The name of the backout queue to which messages are requeued if they have been backed out more than the backout threshold.

The WebSphere MQ queue manager keeps a record of the number of times that each message has been backed out. When this number reaches a configurable threshold, the connection consumer requeues the message on a named backout queue. If this requeue fails for any reason, the message is removed from the queue and either requeued to the dead-letter queue, or discarded.

Data type	String
Default	Null
Range	1 through 48 characters.

22.Harden Get Backout

Whether hardening should be used to ensure that the count of the number of times that a message has been backed out is accurate.

Data type	Enum
Default	Hardened
Range	Hardened The count is hardened. Not Hardened The count is not hardened. This is the default supplied with WebSphere MQ, but your installation might have changed it.

23.Default Priority

The default message priority for this destination, used if no priority is provided with a message.

Data type	Integer
Default	0
Range	0 (lowest priority) through 9 (highest priority)