| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WB-IMB 5.0 to WMB 6.0 - Toolkit |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Tue Jul 31, 2007 12:24 pm Post subject: WB-IMB 5.0 to WMB 6.0 - Toolkit |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I've searched and its pretty clear that a v6 Toolkit can deploy a v6 or v5 bar file to a v5 Config Manager to a v5 Broker.
What I can't find in black and white is if a new flow can be developed in a v6 Toolkit, or a v5 flow edited in v6 Toolkit, then saved as a v6 bar, and then deployed to a v5 CM to a v5 Broker. (Obviously the new edited / flow does not include v6 specific features)
By v5 I mean 5.0.4 in my shop. I found this puzzler in the online help:
| Quote: |
| If you want to use a Version 6.0 Message Brokers Toolkit and a Version 5.0 Configuration Manager to deploy to a Version 5.0 broker that is part of a WebSphere Business Integration Message Broker Version 5.0 installation at service level Fix Pack 3 or earlier, apply Fix Pack 5 to the WebSphere Business Integration Message Broker Version 5.0 installation of which the Version 5.0 Configuration Manager is part. |
OK, I am at 5.0.4. That's not Fix Pack 3 or earlier, but its also not at Fix Pack 5 that they recommend to go to. I'm in the middle. ????
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jul 31, 2007 12:36 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If your v5 configMgr is part of a separate installation than your Brokers, just apply the FP5 to the configMgr.
I'd consider it otherwise risky to try to use FP4 of v5 with Broker v6 components.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jul 31, 2007 12:40 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Our Config Managers are on seperate servers than the Brokers.
So the following should work?
6.0.2 Toolkit develops a flow, saves the bar, then deploys to:
5.0.5 Config Manager taliking to 5.0.4 Brokers
Thanks Jeff.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 31, 2007 12:52 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'd guess so.
I mean, I'd be surprised if it didn't.
And you might as well push the ConfigMgrs to the most recent FP, rather than just FP5.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Aug 01, 2007 6:43 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| PeterPotkay wrote: |
So the following should work?
6.0.2 Toolkit develops a flow, saves the bar, then deploys to:
5.0.5 Config Manager taliking to 5.0.4 Brokers
|
Yep, that's fine. However, I'd always recommend having the toolkit deploy to the same [version+release] of broker. That way, there's no possibility of you trying to deploy "new" capability to an old broker.
Given that the different versions can co-exist on the same machine, that shouldn't cause too much of a problem.
-Matt |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Aug 01, 2007 9:44 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Hi Matt.
I'm OK with the Config Managers at 5.0.4 if my Toolkits are at 6.0.2? Or should my migration path be the following given my versions (All Windows 2003 SP1, MQ 6.0.2.1, WB-IMB 5.0.4):
Upgrade the Config Managers first to 6.0.0.4
Upgrade the Tool Kits to 6.0.2
Upgrade the Brokers to 6.0.0.4
The developer is using a 6.0.2 Toolkit to deploy to a 5.0.4 Config Manager / Broker and getting the following error: The flow is a bare bones Input Node to Output Node flow. Real Simple.
| Code: |
----------------------------------------------------------------------------------------------------
BIP2211E: Invalid configuration message containing attribute value '' which is not valid for target attribute 'validateMaster', object 'basic.MQInput'; valid values are 'none, content, value, contentAndValue, inherit'
The message broker received a configuration message containing the attribute value '' which is not valid for the target attribute 'validateMaster', on object 'basic.MQInput'. Valid values are 'none, content, value, contentAndValue, inherit'. This can be caused by a mismatch in levels between the Message Brokers Toolkit, the Configuration Manager and the Broker, or as a result of a user or third party written user-defined node where the implementation library installed at the broker does not match the node definition held at the Configuration manager and Message Brokers Toolkit.
Ensure that the levels of code installed at the Message Brokers Toolkit, Configuration Manager and Broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this is IBM, contact your IBM support center.
----------------------------------------------------------------------------------------------
|
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| newbee_wmb |
| Posted: Tue Apr 15, 2008 8:26 am Post subject: Can we deploy messages coded in V6 toolkit on V5 broker |
|
|
Newbie
Joined: 04 Oct 2007
Posts: 3
|
Hi
We are planning to migrate our message broker from WMB V5.0.8 to WMB V6.0 and it was mentioned in most of online docs that V6(toolkit, cfgmanager) and V5(toolkit, cfgmanager) can co exist on the same machine.
I want to know (which is very crucial fro us) that Can we develop message flows on Toolkit of V6 (this developed code wont have any new new features that are available only on V6 ) and deploy on Broker V5?
can any body kindly help me in this please.
Thanks in advance |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 15, 2008 8:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes, you can use the V6 Toolkit for development with v5 brokers and configmgrs. This is not true of v6.1 Toolkit, though.
You should avoid coexistance in production as much as possible. It significantly complicates the upgrade/migration/troubleshooting situation.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
