Partilhar via

Integration - Bridging Microsoft MSMQ and IBM WebSphere MQ on 64-bit Windows

  • Artigo

The MSMQ-MQSeries Bridge, which ships with Host Integration Server 2006 (HIS 2006) and earlier, is a well-established way to integrate the messaging worlds of Microsoft and IBM.

The Bridge is essentially a Windows application written to use the MQSeries (or more accurately WebSphere MQ) APIs to manage message flow to and from IBM hosts (that is, mainframes or servers running Windows, Solaris, Linux, etc.). Messages can be pulled from local MSMQ queues and sent through the MQSeries client to remote MQSeries queues, or pulled from those same remote MQSeries queues and placed in the local MSMQ queues.

Being dependent on the WebSphere MQ client, the Bridge can only be installed on operating systems where there could be a Windows client to work with. For example, IBM does not currently supply a true 64-bit client for Windows so HIS 2006 will not provide the option to select the Bridge when setup is run on 64-bit operating systems. (Note: setup detects the operating system and not the presence of the WebSphere MQ client so the introduction of a true 64-bit client will not cause setup to do anything different).

According to:

System Requirements for WebSphere MQ 6.0 Windows 

    1. WebSphere MQ V6 64-bit Windows (toleration) support:
      - WebSphere MQ V6 64-bit Windows (toleration) is applicable at WebSphere MQ V6.0.2.1 or later.
      - WebSphere MQ V6.0.2.0 or lower versions only support 32-bit operating systems.
      - Only 32-bit versions of programming languages are supported.

 and

939202 An update is available that enables you to install the client-based BizTalk Adapter for WebSphere MQ on 64-bit versions of Windows

"Starting with version 6.0.2.1, WebSphere MQ for Windows is also supported as a 32-bit application on 64-bit versions of Windows."

it is possible to install the more recent WebSphere MQ clients on 64-bit Windows but they cannot be treated as 64-bit applications.

So, in summary, if you wish to integrate MSMQ with WebSphere MQ using HIS 2006's Bridge then you need to test and deploy on x86 operating systems.

[[24th March, 2009 - Host Integration Server 2009 will not be adding 64-bit support for the MSMQ-MQSeries Bridge. The requirement to deploy on x86 operating systems still stands.]]

Comments

  • Anonymous
    April 01, 2008
    Hi, Hope to get help from you. We implement a messaging systems. The server receives message from clients and stores it in MSMQ. It then forward the message to another destination. The program of routing message first enable the MSMQ: MQAutoReceive(q2) MQAutoReceive (MessageQueue objQName, //) {...// //......            objQName = new MessageQueue(".\Private$&quot; + qNameToPtTo);            objQName.Formatter = new XmlMessageFormatter(new Type[] { typeof(byte[]) });            objQName.ReceiveCompleted += new ReceiveCompletedEventHandler(nameOfHandler);            objQName.UseJournalQueue = useJournal;            objQName.MessageReadPropertyFilter.ArrivedTime = true;            objQName.BeginReceive(); //......} The handler of completed message receiving like this: q2ReceiveCompleted(object p_source, ReceiveCompletedEventArgs p_objAsyncResult) { //.......... try{                q2 = ((MessageQueue)(p_source));                m2 = q2.EndReceive(p_objAsyncResult.AsyncResult);                if (m2.ArrivedTime.AddSeconds(msgValidity) < DateTime.Now)                {                    q2.Refresh();                    q2.BeginReceive();                    return;                }                m2.TimeToReachQueue = new TimeSpan(0, 0, TIME_TO_REACH_Q);                m2.AdministrationQueue = q2AdminQ;                m2.AcknowledgeType = AcknowledgeTypes.FullReachQueue;                m2.UseJournalQueue = true;     //.........................  } catch { } finally {                q2.Refresh();                q2.BeginReceive(); } We have very serious problem of memory leaking. We dont really comprehend it as the message in queue is removed (EndReceive), but still memory is growing. Hope to get help from you. Thank you.

  • Anonymous
    September 07, 2008
    The comment has been removed

  • Anonymous
    January 06, 2010
    Hi I run the setup of HIS 2009 and all features  including MSMQ-MQSeries Bridge. Open the MSMQ-MQSeries Bridge Manager. Click on Enterprise->Computers Open the system node (where I just installed the MSMQ-MQSeries Bridge) It shown red cross on that system. and Node were not opened. Enviroment: 32 bit Windows Server 2008 EE SP2, MSMQ Enabled with Routing Support and Webspehere MQ 7.0.1 Server installed. Addtional Information: Microsoft MSMQ-MQSeries Bridge Service is runnig.

  • Anonymous
    January 06, 2010
    Hi Syed, Is running setup the only step you have taken? Installing the Bridge requires a lot of configuration work before and after. MSMQ-MQSeries Bridge Setup and Configuration http://msdn.microsoft.com/en-us/library/aa744955(BTS.10).aspx Cheers John Breakwell (MSFT)

  • Anonymous
    January 07, 2010
    Hi John, Yes I refrered the same link while configured the MSMQ-MQseries Bridge and successfully done installation on Windows Server 2003. And MSMQ-MQSeries work as expected. But my concern is about installtion of MSMQ-MQSeries Bridge on 32 bit Windows Server 2008 SP2, Is it supported platform ?? Yes, I done all requires configuration work before and after MSMQ-MQSeries Bridge. I followed the same Instruction given for 32 bit windows server 2008 platform. Thanks Ahsan

  • Anonymous
    January 08, 2010
    Hi Syed, The Product Support Compatibility Matrix at http://support.microsoft.com/gp/lifecompmatrix#H and http://support.microsoft.com/gp/lifecompmatrix#B shows the currently supported platforms: "HIS 2009 requires one of the following operating systems (32-bit x86 or 64-bit x64): •  Windows XP SP2 Professional SP2 •  Windows Server 2003 SP2 •  Windows Server 2003 R2 SP2 •  Microsoft Windows Vista SP1 •  Windows Server 2008 •  Windows Server 2008 R2 •  Windows 7 •  Virtualization with Hyper-V" 32 bit Windows Server 2008 SP2 is supported. Cheers John Breakwell (MSFT)

  • Anonymous
    January 08, 2010
    The comment has been removed