ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQSI 2.0.1 & MQSI 2.0.2 compability

Post new topic  Reply to topic
 MQSI 2.0.1 & MQSI 2.0.2 compability « View previous topic :: View next topic » 
Author Message
MVO
PostPosted: Tue Nov 20, 2001 6:39 am    Post subject: Reply with quote

Centurion

Joined: 09 Sep 2001
Posts: 131

Can a 2.0.1 broker run with a 2.0.2 configuration manager ? Our client does not want to upgrade to 2.0.1 until next year but we want to use 2.0.2 features to build another broker for another application.
Back to top
View user's profile Send private message
Segs
PostPosted: Tue Nov 20, 2001 7:33 am    Post subject: Reply with quote

Voyager

Joined: 04 Oct 2001
Posts: 78
Location: Zurich Financial Services

I'm pretty sure the answer to this is no. We're in the process of upgrading to v2.0.2 and have a global config manager that looks after all our production brokers, we are going to upgrade the config manager after all the brokers in its topology have been upgraded to v2.0.2 My advice to you on this would be to be very careful indeed.
Back to top
View user's profile Send private message Send e-mail
Outdesign
PostPosted: Tue Nov 20, 2001 9:25 am    Post subject: Reply with quote

Apprentice

Joined: 16 Sep 2001
Posts: 38
Location: Hampshire, UK

You can successfully run with a mixed environment where you have a v2.0.2
ConfigMgr and Control Center and a v2.0.1 Broker.

However, when deploying from a v2.0.2 ConfigMgr and Control Center to a v2.0.1 Broker,
the Control Center log will indicate a successful deploy, but then be followed by a
"BIP1536S ConfigMgr unable to register subscriptions" message.
This has already been raised as a defect with IBM but should not affect any processing
on your v2.0.1 Broker.

What you have to be aware of is the 'new' functionality included in v2.0.2 can not
be deployed to a v2.0.1 Broker (MQe ,SCADA, new NEON nodes or Publication node) as this
WILL cause errors at deploy time
Back to top
View user's profile Send private message Visit poster's website
zpat
PostPosted: Mon Nov 26, 2001 5:55 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5849
Location: UK

Generally one level back and forward is supported for coexistence although you may need the compatibility PTFs applied.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQSI 2.0.1 & MQSI 2.0.2 compability
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.