X

News, tips, partners, and perspectives for the Oracle Solaris operating system

WebSphere MQ V6.0 and WebSphere Message Broker V6.0

Guest Author
With support being withdrawn by IBM for WebSphere MQ V5.3 and WebSphere Integration Message Broker V5.0 on 28th Sept 2007. I suspect at lot of IBM WebSphere customers will be looking to migrate to WebSphere MQ V6.0 and WebSphere Message Broker V6.0.
To ease the migration it maybe be useful to know the following:
1. Both WebSphere MQ V6.0 and WebSphere Message Broker V6.0 can be deployed on Solaris 10 SPARC and Solaris 10 x86-64, and also within Solaris Containers.
2. IBM have produced performance reports for WebSphere MQ V6.0 and WebSphere Message Broker V6.0 on Sun Solaris, the former was performed on Sun Fire T2000 systems running Solaris 10.
WebSphere Message Broker V6.0 for Solaris - Performance Report (ip6e.pdf)
WebSphere MQ V6.0 for Solaris - Performance Evaluations (mp6m-SunFire.pdf)
However, did you also know that with Sun Cluster 3.2 you can achieve high availability for WebSphere MQ V6.0 and WebSphere Message Broker V6.0 on Solaris 10 SPARC and Solaris 10 x86-64, also within Solaris Containers by using the following Sun Cluster 3.2 Agents:
SunPlex(TM) High Availability (HA) Agent for IBM WebSphere MQ
SunPlex(TM) High Availability (HA) Agent for IBM WebSphere Message Broker
This means you could deploy multiple instances of WebSphere MQ V6.0 and WebSphere Message Broker V6.0 in separate Solaris Containers all underpinned by Sun Cluster 3.2. For example, wouldn't it be nice to consolidate your workload on a T2000 or X6400 servers (to name just two) knowing you'll also be delivering high availability.
Neil Garthwaite
Sun Cluster Engineering

Join the discussion

Comments ( 8 )
  • przemol Thursday, December 7, 2006
    Could you please add RSS feed to the existing ATOM feed ?
    Thanks in advance
    przemol
  • zoram Monday, December 11, 2006
    Done! Please click on the RSS icon to subscribe to the RSS feed.
  • przemol Tuesday, December 19, 2006
    Thank you !
  • Palle Simonsen Thursday, December 21, 2006
    What degree of HA is delivered?
    I.e. when doing a failover of an MQM what will happen with undelivered messages in the queue(s) of the failed MQM? Are they transparently taken over by the surviving MQM's or will they pend a restart of the failee?
  • andyp Friday, December 29, 2006
    Hi Palle, a queue manager's storage (queues) cannot be taken over by another queue manager. So, in order to process any undelivered messages, you have to recover / restart the queue manager on another node with access to the same shared storage. This is quite straightforward to achieve using GFS or some failover filesystem, and Sun Cluster.
    If your filesystem supported it, you could replicate the data across sites and restart the queue manager in a remote location, although then you get into all kinds of latency issues.
    If you want to have multiple queue managers accessing a single physical queue, you would need to look at the shared queue feature which is available on the mainframe (z/OS).
  • guest Monday, February 5, 2007
    Hi Neil,
    We are in the process of setting up
    WebSphere Message Broker V6.0
    WebSphere MQ V6.0 (HA) for Solaris.
    The customer currently is on SUN Cluster 3.1.
    Wanted confirmation if the (HA) Agent for IBM WebSphere MQ 6
    and (HA) Agent for IBM WebSphere Message Broker 6 are supported on SUN Cluster 3.1.
    Regards,
    Sunita(sunita@sg.ibm.com)
  • Sunita thaniyan Monday, February 5, 2007
    Hi Neil,
    We are in the process of setting up
    WebSphere Message Broker V6.0
    WebSphere MQ V6.0 (HA) for Solaris.
    The customer currently is on SUN Cluster 3.1.
    Wanted confirmation if the (HA) Agent for IBM WebSphere MQ 6
    and (HA) Agent for IBM WebSphere Message Broker 6 are supported on SUN Cluster 3.1.
  • Neil Garthwaite Thursday, February 8, 2007
    Hi Sunita, yes the Sun Cluster agents for WebSphere MQ and WebSphere Message Broker supports WMQ v6 and WMB v6 on Sun Cluster 3.1. Please just be sure to have the latest agent patch applied.
    Current SC 3.1 agent patch for WebSphere MQ is 116392-13 (SPARC) and 124855-01 (x86-64).
    Current SC 3.1 agent patch for WebSphere Message Broker is 116728-06 (SPARC).
    Please note that we only support the agent for WebSphere Message Broker on Solaris 10 x86-64 with Solaris Cluster 3.2.
    All patches are available on SunSolve.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.