| Author |
Message
|
| SireeSharu |
 Posted: Mon Nov 12, 2012 9:00 am Post subject: Need MQ client software v6.0 for windows 2003 server |
 |
|
Newbie
Joined: 07 Nov 2012
Posts: 5
|
Hi all,
In our project we are trying to replace MQ v6.0 Server CSD 3 exisitng on on windows 2003 server with a MQ v6.0 client connection and to make this client conenction point to SUSE Linux Enterprise Server 10 CSD 2. In this way we can save licensing costs of MQ by removing an MQ server from the windows 2003 system .
I am new to the MQ Adminstration world.
So i need  regarding how to proceed and where can i get MQ client software v6.0 for windows 2003 server.
Please help me regarding this.
Thanks & Regards |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon Nov 12, 2012 9:19 am Post subject: Re: Need MQ client software v6.0 for windows 2003 server |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| SireeSharu wrote: |
| So i need regarding how to proceed and where can i get MQ client software v6.0 for windows 2003 server. |
No you don't, you need to use a supported version of WMQ in both cases - WMQ V6.0 is no longer in support (although for some strange reason the V6.0 Client is still available for download). You can download the WMQ V7.x Client from the SupportPac website, and I'd like to say I have checked whether W23K is a supported platform for WMQ V7.x but I can't as some elements of the IBM site have gone postal.
_________________
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.
Last edited by exerk on Tue Nov 13, 2012 12:49 am; edited 1 time in total |
|
| Back to top |
|
|
| SireeSharu |
| Posted: Mon Nov 12, 2012 2:25 pm Post subject: |
|
|
Newbie
Joined: 07 Nov 2012
Posts: 5
|
Hi exerk,  for the quick response
I cannot beacuse we are using message broker v 6.0 and we have MQ 6.0 on all the MQ servers we have. I Know they are not supported but our project is not going to upgrade in near soon. we are planning to remove MQ on the windows 2003 server and the only option is to install MQ v6.0 client to refer to MQ server on SUSE Linux Enterprise Server 10 CSD 2.
So Is MQ v6.0 available for download? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 12, 2012 5:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| SireeSharu wrote: |
Hi exerk, for the quick response
I cannot beacuse we are using message broker v 6.0 and we have MQ 6.0 on all the MQ servers we have. I Know they are not supported but our project is not going to upgrade in near soon. we are planning to remove MQ on the windows 2003 server and the only option is to install MQ v6.0 client to refer to MQ server on SUSE Linux Enterprise Server 10 CSD 2.
So Is MQ v6.0 available for download? |
Don't quite understand you. MQ client V7 will work with MQ V6.
If you have WMB on the windows server you cannot replace MQ server with MQ client as the broker needs an MQServer..., so no it's not your only option, it may be a chosen one, but you have not given any reason for the choice. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Nov 13, 2012 12:54 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| SireeSharu wrote: |
| ...So Is MQ v6.0 available for download? |
| exerk wrote: |
| ...WMQ V6.0 is no longer in support (although for some strange reason the V6.0 Client is still available for download)... |
And WMQ V7.x is supported on W23K so there is no excuse for not using the Client 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 |
|
|
| SireeSharu |
| Posted: Wed Nov 14, 2012 10:16 am Post subject: |
|
|
Newbie
Joined: 07 Nov 2012
Posts: 5
|
Hi exerk and fjb_Saper,
Thanks fo the response
I now undertand that thet MQ client 7.0 is backward compatable to MQ 6.0 server. Though i knew it before i was not 100% sure.Thanks for clarifying.
The WMB 6.0.2 we have is using a MQ 6.0and we are not replacing that.
There is another independent Q manager which we want to replace with the client connection.
I just wanted to know overview the steps i need to perform after i install the 7.xclient.
Thanks in advance |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 14, 2012 11:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SireeSharu wrote: |
| The WMB 6.0.2 we have is using a MQ 6.0and we are not replacing that. |
Despite it being out of support?
And this exercise being a good oppertunity to deal with all of these old elements in a single operation rather than revisit this later in a more pressured environment when the WMBv6.0 finally breaks?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| SireeSharu |
| Posted: Thu Nov 15, 2012 11:02 am Post subject: |
|
|
Newbie
Joined: 07 Nov 2012
Posts: 5
|
Hi Vitor,
Migration is being planned for next year. So it might take few more months/year. |
|
| Back to top |
|
|
| SireeSharu |
| Posted: Thu Nov 15, 2012 12:19 pm Post subject: |
|
|
Newbie
Joined: 07 Nov 2012
Posts: 5
|
| For now i just need regarding an overview of what needs to be performed after MQ client 7.0 installation. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 15, 2012 1:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SireeSharu wrote: |
| For now i just need regarding an overview of what needs to be performed after MQ client 7.0 installation. |
It's called "configuring the client" and is fully documented in the product documentation.
You can legitimately push this onto the application people to do within their code.
You may have to push this onto the application people if their code assumes that it's running on it's own queue manager. Code changes could range from recompiling to use client libaries not binding librairies all the way through to reworking their code because the transactionality works differently.
You know, all the stuff you documented in the discovery phase of your project when you started out on this plan to move from server to client when you documented the implications.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
