Middleware News

Dead Letter Queue - Dead Letter Messages - Middleware News Dead Letter Queue - When messages can not be delivered to the intended queue, the messages may be delivered to a Dead Letter Queue (DLQ) if the queue manager has one defined. - By default a queue manager does not have a DLQ but you should define one for every queue manager. Dead Letter Messages Messages can be placed on the DLQ by the queue manager, the channels (MCA) or by applications When the messages are put onto DLQ, they should have a Dead Letter Header (DLH). DLH will be generated by Queue manager and MCA. If application are putting the messages onto DLQ, applications must create the DLH. MQRC and MQFB Reason code in the MQDLH will be a value from either the MQRC reason codes or MQFB feedback codes Example MQDLH MQOPEN - 'SYSTEM.DEAD.LETTER.QUEUE' MQGET of message number 1 ****Message descriptor**** StrucId : 'MD ' Version : 2 Report : 0 MsgType : 8 Expiry : -1 Feedback : 0 Encod

Migration to WebSphere MQ V7.0.1 and WebSphere Message Broker V7.0 - Middleware News Wmq wmb dist migration v1 030310 View more documents from karthickmsit .

Multi instance Queue Managers - Middleware News The concept of these multi-instance queue managers is to share the queue manager data in a high available storage place (line SAN), which should be accessible by more than 1 queue manager. For example, we have QM1 and QM2 on different machine. For both these queue managers we keep the logs and QM data in a shared location /shared/QMdata. Now if you start the QM1 first, then QM2 becomes passive. When QM1 is not operational or crashed then QM2 will take over the proceedings. When you intend to use a queue manager as a multi-instance queue manager, create a single queue manager on one of the servers using the crtmqm command, placing its queue manager data and logs in shared network storage. On the other server, rather than create the queue manager again, use the addmqinf command to create a reference to the queue manager data and logs on the network storage. To create and use this multi-instance queue managers, we need: # Client

Communicating with a Queue Manager outside Cluster - Middleware News Assumptions: 1. You already have a Queue Manager cluster (named QMGRCLUS) setup with 2 Queue Managers with names QM1 and QM2 and all the requires channels are setup for communication between QM1 and QM2 2. You have QM3, which is outside the cluster 3. QM2 has a Queue [Q2] defined at cluster level. In this tutorial, let us send message from QM3’s Q3 to QM2’s Q2 and in the reverse path. In this case one of your Queue Managers should act as a gateway. Say for example, lets make QM1 as the gateway for cluster and QM3 is outside cluster. Steps: 1. The queue manager outside the cluster must have a QREMOTE definition for each queue in the cluster that it wants to put messages to. DEFINE QREMOTE(Q2) RNAME(Q2) RQMNAME(QM2) XMITQ(TQ1) [in this case Q2 is a cluster queue and i want to put message from QM3 -> QM2] 2. QM3 must have a SDR channel and TX queue to QM1 and QM1 should have corresponding RCVR cha

MQ commands fail after install of V6.0 - Middleware News Problem(Abstract) You install WebSphere MQ V6.0 and find that you are unable to run MQ commands such as: dspmqver, dspmq and so on. You receive an error like the following: dspmq exec(): 0509-036 Cannot load program dspmq because of the following errors: 0509-150 Dependent module /usr/lib/libmqmcs_r.a(shr.o) could not be loaded. 0509-103 The module has an invalid magic number. Cause The system picks 32 bit MQ libraries when It should select the 64 bit lib's. The most likely cause is that the $LIBPATH or $LD_LIBRARY_PATH is pointing to the 32 bit MQ libraries when It should select the 64 bit lib's. See Implications of a 64-bit queue manager in the Quick Beginnings Guide for your operating system. Resolving the problem Edit the LIBPATH or $LD_LIBRARY_PATH to remove the /usr/lib or /opt/lib. or Add /[usr|opt]/mqm/lib64 to the front of the $LIBPATH or $LD_LIBRARY_PATH export LIBPATH=/usr/mqm/lib64:

WebSphere MQ Bridge for http - Middleware News

IBM Sterling WebsphereMQ FTE 2-Minute Explainer - Middleware News MQ FTE V7.0.2: The Enterprise File Bridge - Middleware News WebSphere MQ File Transfer Edition - Middleware News

IBM WebSphere Commerce Demo - Middleware News

Install WebSphere Portal 7 Trial [Part 1 of 4] - Middleware News