| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Strategy for Test and Roll Out of Updated Plug-In |
« View previous topic :: View next topic » |
| Author |
Message
|
| EddieA |
 Posted: Wed Mar 23, 2005 11:56 am Post subject: Strategy for Test and Roll Out of Updated Plug-In |
 |
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
I am using the Cache Node SupportPac, IA91. Recently this has been updated, so I grabbed the latest one to test it out on my laptop. This resolved a couple of issues I had with the previous one, so I decided that it was time to move it though the Dev, QA, Prod process.
So, I updated the jar file on the Dev box, and re-started to pick it up. Ooops:
| Quote: |
Mar 23 10:36:54 wbidevrk1p MQSIv500[31962]: (DWBIB01A.eCommerceREQ)[1]BIP2210E: Invalid configuration message: attribute name 'getOption' not valid for target object 'WSI_eCommerceHub.PutReplyToQ'. : DWBIB01A.6603a29d-ff00-0000-0080-a7c86037caa8: /build/S500_P/src/DataFlowEngine/ImbResource.cpp: 153: ImbResource::setAttribute: ComIbmJniNode: WSI_eCommerceHub#FCMComposite_1_14
|
Quickly back out the jar file to get things running, and to think about what happened.
Came down to the following conclusion. The difference between the 2 versions means that all the following must be updated in sync: Tooling, re-build bar files, and jar. Now, this isn't a problem if you are running discrete systems to support Dev, QA, and Prod. But, one of the joys of v5 is that you can support all of these environments from a single toolkit. Except when you want to do something like this.
So my question is: How do you guys handle changes like this. Remembering that even while you are happily developing away on your "new" version, there's always emergency changes that are needed to your current systems.
**Edit** Just spotted that Windoze is even more explicit about what the problem is:
| Quote: |
( EDDIEA.default ) Invalid configuration message: attribute name 'timeOut' not valid for target object 'ASBITSTREAM.CacheGet'.
The message broker received a configuration message containing the attribute name 'timeOut' which is not valid for the target object 'ASBITSTREAM.CacheGet'. 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 plug-in 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. |
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Thu Mar 24, 2005 12:35 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
I think this is a clear example of why you shouldn't (although you technically can) use single control of different environments...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 24, 2005 5:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Michael, the implication here is that one needs to install separate copies of the Toolkit for each environment, rather than having different domain connections from one Toolkit install.
That's a big waste, in my opinion. Why should an administrator have to log onto a particular computer to do deployments to Dev, and a different computer to deply to UAT?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Mar 24, 2005 5:18 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| jefflowrey wrote: |
| That's a big waste, in my opinion. Why should an administrator have to log onto a particular computer to do deployments to Dev, and a different computer to deply to UAT? |
in my "book" the dev admin and the uat/prod admin are not the same person, seperation of duties...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 24, 2005 5:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, that's a good point.
But it still doesn't seem necessary to force a separate console.
I think it can be cheated though, using copies of the eclipse/plugins folder, and naming the "right one" to be "plugins" before launch.
I just tried with WSADIE, and you can't use shortcuts on windows, unfortunately. So switching will have to involve renaming the folder, rather than changing where a shortcut points to.
_________________
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
|
|
|
|
