| Author |
Message
|
| Michael Dag |
 Posted: Mon Aug 24, 2009 11:45 pm Post subject: WebSphere MQ V7.0.1 Refresh Pack Announced |
 |
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
 |
| zpat |
| Posted: Tue Aug 25, 2009 1:25 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Looks good, I wonder if the client auto-reconnect feature can be implemented without making any application coding changes for existing apps?
Any links or reference to the online manuals? |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Aug 25, 2009 1:26 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| zpat wrote: |
Looks good, I wonder if the client auto-reconnect feature can be implemented without making any application coding changes - otherwise it's much less useful?
Any link reference to the online manuals? |
Unlucky! From the summary:
| Quote: |
| To enable automatic client reconnection, client applications need to take advantage of new options available to existing commands that specify when and how reconnection attempts should be made. These options are available to MQI and JMS users. Both the WebSphere MQ clients and servers involved in any given connection need to be updated to WebSphere MQ V7.0.1 level to enable this automatic reconnection feature. |
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Aug 25, 2009 3:34 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
|
| Back to top |
|
|
| markt |
| Posted: Tue Aug 25, 2009 4:13 pm Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
| Quote: |
| I wonder if the client auto-reconnect feature can be implemented without making any application coding changes |
No code changes are required, but you do have to upgrade to use the 701 libs. And have the channels use SHARECNV >0.
To enable the function with no code changes, put the right entry in mqclient.ini. Alternatively, it can be enabled by a minor code change - set the appropriate MQCNO option on MQCONNX. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Aug 25, 2009 4:39 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Quote: |
Multi-instance queue managers
In today's 24 x 7 world, the business impact of outages to applications, networks, and hardware can be severe and far-reaching. Similarly, the SOA Messaging that connects these applications and services also needs to meet enterprise demands for high availability. High availability (HA) is a fundamental way to maximize the resilience of an SOA and requires that it can rapidly and completely recover from outages -- especially unplanned ones.
WebSphere MQ V7.0.1 can help increase the availability of messaging out-of-the-box. This software-based approach to increasing availability does not require specialist skills or hardware. Automatic failover is provided by multi-instance queue managers in the event of an unplanned outage. Controlled switchover is also provided for planned outages, such as applying software maintenance.
With this new availability option, the messages and data for a multi-instance queue manager are held on networked storage accessed via a modern network file system protocol, such as Network File System (NFS) version 4. Multiple instances of this queue manager can then be defined and started on different machines, with one active instance and one standby instance. The active queue manager instance processes messages and accepts connections from applications and other queue managers.
It holds a lock on the queue manager data to ensure that there is only one active instance of the queue manager. The standby queue manager instance periodically checks whether the active queue manager instance is still running. If the active queue manager instance fails or is no longer connected, the standby instance acquires the lock on the queue manager data as soon as it is released, performs queue manager restart processing, and becomes the active queue manager instance.
The multi-instance queue manager feature does not use an HA Coordinator and provides a simple alternative to platform-specific hardware-based facilities such as High Availability Cluster Multi-Processing (IBM HACMP™) on the IBM AIX® platform and similar HA Coordinators available for other hardware platforms.
For highest levels of messaging availability, use of platform-specific hardware-based mechanisms with HA Coordinators like HACMP is recommended. HA Coordinators provide more robust monitoring and more flexible coordination and restart capabilities.
WebSphere MQ V7.0.1 replaces the need for SupportPac™ MC91 -- High Availability for WebSphere MQ on UNIX® platforms -- which is planned for withdrawal.
|
Don't those last two statements contradict each other? Why pull MC91 if its still being recomended to use real H.A. when you need the "highest levels of messaging availability" ?
The new multi instance QMs look interesting...it will be a long time before we get every MQ Client and every connected QM up to 7.0.1 though. It seems we will be using traditional H.A. (MC91 + IC91 + VCS in our case) even if the QM goes to 7.0.1, which we plan on Q1 2010. But for brand new installations where every incoming connection will be 7.0.1 or greater, definitly a contender for the best solution. Wonder exactly how WMB plays with it.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| markt |
| Posted: Tue Aug 25, 2009 5:02 pm Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
| Quote: |
| Don't those last two statements contradict each other? |
No
| Quote: |
| Why pull MC91 if its still being recomended to use real H.A. when you need the "highest levels of messaging availability" ? |
Because you don't need MC91 to implement HACMP/VCS solutions. The "tricky" part of MC91 - playing with filesystem layouts and symlinks to ensure appropriate resource isolation - is now done by the core qmgr code automatically (albeit in a different way). Other aspects of MC91 are also improved in the base code, making it much simpler to integrate into ANY of the HA products.
Although MC91 is "withdrawn" that is different from "unavailable". It's been moved to a secondary page, but can still be downloaded if you need it. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Aug 25, 2009 11:10 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| PeterPotkay wrote: |
| ...Don't those last two statements contradict each other? Why pull MC91 if its still being recommended to use real H.A. when you need the "highest levels of messaging availability" ? |
Hopefully next week I'm off to a proof of technology demonstration, and it's a question I mean to ask. In the meantime, if anybody already has the answer, please share it!
| markt wrote: |
| Quote: |
| Don't those last two statements contradict each other? |
No
| Quote: |
| Why pull MC91 if its still being recomended to use real H.A. when you need the "highest levels of messaging availability" ? |
Because you don't need MC91 to implement HACMP/VCS solutions. The "tricky" part of MC91 - playing with filesystem layouts and symlinks to ensure appropriate resource isolation - is now done by the core qmgr code automatically (albeit in a different way). Other aspects of MC91 are also improved in the base code, making it much simpler to integrate into ANY of the HA products.
Although MC91 is "withdrawn" that is different from "unavailable". It's been moved to a secondary page, but can still be downloaded if you need it. |
Can you expand on this please? I'm with PeterPotkay on this one being somewhat contradictory - until I can get my hands on the RefreshPack and try it at least!
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Aug 25, 2009 11:23 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| It's not so easy to upgrade a critical business installation as a development lab one so MC91 should remain supported until WMQ v6 is out of support. |
|
| Back to top |
|
|
| markt |
| Posted: Wed Aug 26, 2009 7:11 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
MC91 has always been a Cat2 SupportPac - ie NOT SUPPORTED. So the support position has not changed.
And as I've already said, it's still available for people who want to use it and have not downloaded it yet. Recognise that it will never be updated in future - so you also can keep your own archive copy safe in the knowledge that it won't change. There are no plans to remove it from the "withdrawn" page of SupportPacs at
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27007149
The end of service of V6 might be an appropriate time to remove it completely, but that discussion won't even start to take place for a long time.
And also I've already said, V7.0.1 contains all of the difficult stuff that MC91 provided. In particular: defining data and log directories, resource isolation, a status command for simple healthchecking, building stanzas in mqs.ini on standby machines, internal self-checking/suiciding ... |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Aug 26, 2009 3:19 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
FYI, I just spotted this:
http://www-01.ibm.com/support/docview.wss?uid=swg21398427
Multi-instance queue manager function delivered in WebSphere MQ V7.0.1 is not currently supported on i5/OS or Solaris.
Due to issues identified late in the test cycle, the new multi-instance queue manager function delivered in WebSphere MQ v7.0.1 will not be supported on any version of the following operating systems until the issues have been resolved:
* i5/OS
* Solaris on SPARC
* Solaris on x86-64
_________________
Glenn |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Aug 27, 2009 6:54 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| markt wrote: |
| And also I've already said, V7.0.1 contains all of the difficult stuff that MC91 provided. In particular: defining data and log directories, resource isolation, a status command for simple healthchecking, building stanzas in mqs.ini on standby machines, internal self-checking/suiciding ... |
MQ 7.0.1 does this for the multi-instance QMs. But does it also do it if you want to use a traditional QM under VCS or HACMP while running MQ 7.0.1? Will there be documentation helping a customer who wants to use MQ 7.0.1 with traditional H.A. solutions? MC91, while never officially supported as a Cat 2, was still officially there. It was a huge help. Now that its withdrawn, just wondering where we go for this type of info for MQ 7.0.1 and newer. Or do we just use the withdrawn MC91?
Apologies if this will all be in the 7.0.1 Info Center, I keep getting "Bad Gateway" errors when clicking on the new links.. I'm just thinking about this as we will be migrating from MQ 6.0.2.7 to 7.0.1 in Q1 2010 and I am interested in how this will work as almost all my QMs are running under hardware clusters. I'm assuming that unless we specifically set up a QM to be multi instance, anything that MC91 has you set up should still be valid.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Aug 27, 2009 7:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| PeterPotkay wrote: |
| Will there be documentation helping a customer who wants to use MQ 7.0.1 with traditional H.A. solutions? |
It does seem like an excellent topic for a devWorks article. |
|
| Back to top |
|
|
| Jonasli |
| Posted: Sun Aug 30, 2009 11:08 pm Post subject: Re: WebSphere MQ V7.0.1 Refresh Pack Announced |
|
|
Apprentice
Joined: 24 Apr 2003
Posts: 34
Location: Beijing
|
I can not find any detail information about the multi-instance from the info-center of MQ V7.0.1. and any configuration and requirement for Network storage, i want to try this feature, but i do not how to do it,,, wow
who can help me send a link about the material and sample? thanks very much! |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Aug 31, 2009 12:10 am Post subject: Re: WebSphere MQ V7.0.1 Refresh Pack Announced |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| contact admin wrote: |
...I can not find any detail information about the multi-instance from the info-center of MQ V7.0.1. and any configuration and requirement for Network storage, i want to try this feature, but i do not how to do it,,, wow
who can help me send a link about the material and sample? thanks very much! |
Search the InfoCentre, and you'll find a lot of detail in regard to multi-instance queue managers, including examples of how to set up test systems on Linux and Windows. Embedded within the pages are links to the requirements for shared file systems etc.
Seek, and ye shall find 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
|
|
