| Are you running version 5 in production? |
| Yes - working OK |
|
100% |
[ 6 ] |
| Tried and failed |
|
0% |
[ 0 ] |
|
| Total Votes : 6 |
|
| Author |
Message
|
| markneil |
 Posted: Mon Jul 12, 2004 7:11 am Post subject: WBIMB 5 in production - anyone? |
 |
|
Apprentice
Joined: 09 Sep 2003
Posts: 26
|
I'm trying to get a feel for how many people are running production systems with WBIMB 5. My boss wants some reassurance before we start down that road. I'd be very grateful if anyone who is doing so could post a quick reply or answer the poll...
Thanks
Mark |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jul 12, 2004 7:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you start down the road, then you will find out whether your particular applications can be supported in production on version 5.
In other words, the best assurance that WBIMB is production ready for your environment is to actually test it for your needs in your environment.
If you take a develop - test -production approach, then you should have ample time to identify the risks and fixes before you hit production. And can then address any issues with IBM.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Lisa |
| Posted: Mon Jul 12, 2004 7:37 am Post subject: WBIMB |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
I think you should have three options?
Yes
Tried and Failed
No
We plan to move WBIMB CSD03 to production by the end of this year.
Lisa  |
|
| Back to top |
|
|
| jensinaus |
| Posted: Mon Jul 12, 2004 5:37 pm Post subject: |
|
|
Newbie
Joined: 04 May 2004
Posts: 5
|
For each message flow we have in production, we also have a suite regression tests. In following the process that Jeff outlined, we have identified and raised with IBM the following fix pack 3 defects.
* APAR IY58478 -- BIP5461E due to Dict gen of Nillable global elements
When a global element is created in v5, the Nillable option
can be set. However when added to a type as an element reference the
Nillable property option is missing and has not been applied to the CWF Element References.
* APAR IC41402 -- No Exception when parsing invalid chars in MRM DateTime field.
WBIMB MRM DateTime Parsing Error defaults to 19700101
Where previously the parsing of WMQIv2.1 MRM DateTime errors would
generate error message 5509, Version 5 is now defaulting to 19700101 in
the failing field.
For example, 9999XXXXXXXXZZZZ is output as 999919700101ZZZZ
Our tests not only cover the happy path scenario, but also the expected exceptions. In the case of an invalid date, we're expecting error/log message 5509. WBIMBv5, however, returns 19700101.
* APAR IC41257 -- BIP5004E error does not include the element name.
Error Message 5004 (Invalid XML), returns an empty ExceptionList insert 6 text field. In WMQI 2.1 CSD05 it contained the invalid element name.
These fixes are scheduled for fix pack 5. We plan to go into production in October this year.
Jens |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Jul 12, 2004 5:52 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Mark,
Are you starting a new project or migrating existing WMQI 2.x project to V5?
From migration perspective you might come across whole set of different issues. There are many threads in this forum that talks about such issues.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| markneil |
| Posted: Tue Jul 13, 2004 11:49 pm Post subject: |
|
|
Apprentice
Joined: 09 Sep 2003
Posts: 26
|
It's a migration that we're doing. Thanks for all the tips, we'll certainly take them into account. It looks like nobody on this board is actually in production yet though.
Mark |
|
| Back to top |
|
|
|
|
