| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Apps running with MQ v6 -any unexpected problems? |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqrules |
 Posted: Fri Jan 12, 2007 3:17 pm Post subject: Apps running with MQ v6 -any unexpected problems? |
 |
|
Centurion
Joined: 01 Jun 2005
Posts: 100
Location: US
|
Hi all,
Has anyone encountered any application related problems going from MQ 5.3 to 6.0.2 on Windows, Linux and Solaris? As far as I know apps don't need to be re-compiled (except for the channel exit pgms to run with 64 bit).
Any feedback would be much appreciated.
thx and have a nice weekend!
mr |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Mon Jan 15, 2007 1:20 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
As you said, only exit programs must have to be changed and compiled.
We didn't get any issues as far as from any other apps like SAP, SIEBEL etc.
The customized script (the one you build earlier for MQ V5.3) might shows some issues.
The entire format/structure of displaying the Local queue, process, channel status etc are different from MQ V5.3
Couple of new entries have been introduced in MQ V6.0, even some couple of new MQ processes also.
This you have to take care, if you are handling it separetely.
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jan 15, 2007 7:37 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you use linear logging ms0l in java make sure you get the latest support pack as things have somewhat changed between V5 and V6 (format in AMQERRXX.LOG).
Check out your client connections in java / JMS as they have changed a little.
I believe you can no longer use the default qcf.connect() on a client connection but have to provide for qcf.connect(username, passwd)...
Otherwise not much of a change...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqrules |
| Posted: Mon Jan 15, 2007 10:11 am Post subject: |
|
|
Centurion
Joined: 01 Jun 2005
Posts: 100
Location: US
|
Thanks for the responses. I am aware of the changes of the formats/structures...
When I tell the app teams about upgrading to v6, the first thing they ask me if their programs ( written in Java, JMS, C++, C#, VB, COBOL...) need to be re-compiled. My answer is "no". But I was not aware that in Java qcf.connect() did not work.
Any other comment, input would be much appreciated.
Thanks!
mr |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jan 15, 2007 12:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqrules wrote: |
Thanks for the responses. I am aware of the changes of the formats/structures...
When I tell the app teams about upgrading to v6, the first thing they ask me if their programs ( written in Java, JMS, C++, C#, VB, COBOL...) need to be re-compiled. My answer is "no". But I was not aware that in Java qcf.connect() did not work.
Any other comment, input would be much appreciated.
Thanks!
mr |
Let's be specific here. qcf.connect() works fine on a sever connection. We are only talking about the changes when using a client connection.
Either use the container supplied authentication or in a non J2EE environment use qcf.connect(user, passwd) when establishing a CLIENT connection.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
