| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WBI Message Broker First Impression - A Problem Report |
« View previous topic :: View next topic » |
| Author |
Message
|
| mcfennek |
 Posted: Sun Oct 31, 2004 2:50 am Post subject: WBI Message Broker First Impression - A Problem Report |
 |
|
Newbie
Joined: 31 Oct 2004
Posts: 8
|
Hallo,
first of all I have to ask: Is this just me, or is it really a problem to install and work with the WBI Message Broker (using the WBI Toolkit v5.1) the first time?
Usually I would call myself quite intelligent - I have nearly 10 years of professional experience in software development working with tons of different tools. I worked for several years with the eclipse platform, I also worked with MQ Series Integrator before, but I never had such problems getting something to work...
I'm struggling with this piece of software for over a week now. I use Windows XP service pack 2 (as I cannot find service pack 1 anymore), DB2 8.1 (Fixpack 7a), Websphere MQ 5.3 CSD 8 (which is registered in my system as version 5.30.0 instead of 5.3.8 - do not know why), Agent Controller 5.0.1, Message Broker 5.0.1.2 and the WBI Toolkit 5.1.0.3.
The first thing I was struggling with for a long time was the fact that Websphere MQ would complain that no JRE is installed even though I installed the IBM JRE 1.4.0 which came with Websphere MQ.
Then I had to figure out that Websphere MQ JMS support is 100% necessary for installing the Business Integration Message Broker Suite, but it is not included in the typical installation process of MQ.
After everything was installed, I had huge problems creating a default configuration with the Toolkit. Even though the toolkit created a new user (wbiuser), granted all rights and groups to the user, created a ConfigMgr and a broker (including all queues and database tables) I could not connect to the Config-Manager ('Could not connect to MQ Queue Manager WBRK_QM (reason code = 2009)' ). When I finally managed to solve this problem - I still do not know how - I thought I could finally start working with the system. (The one thing I found out: if something goes wrong, delete the broker and the configmgr using the mqsideletebroker and mqsideleteconfigmgr command, delete the database tables and the queue manager before you try anything else - this way chances to succeed are higher when you try it again....)
So I imported the first example (GettingStartedExample) and deployed it on the server - everything worked 
After this huge success I tried the second example (XML Airline Reservation) which ended up in an database command error "... WBIUSR.XMLFLIGHTTB is an undefined name. SQLSTATE=42704". Creating the table manually from the cmd prompt (with the script airlinedb2.sql) solved this problem. The next problem I had, was deploying this message flow. I got an error BIP2066E which I solved using this post.
Within the next hours (days) I played with the sample apps, I tried to work through the tutorial "Using WebSphere Business Integration Brokers Toolkit V5.02" (unfortunately the source code is not downloadable because of a broken link), and found the really good redbook "WebSphere Business Integration Message Broker Basics" - I always had problems deploying stuff, running sample etc....
Now I'm in a state where some things are working others not. For example I still cannot debug (So I guess something is wrong with my Agent Controller). When I deploy a message flow or want to start a new message set, I might have to restart the broker or even reboot my system. I still get tons of strange error messages and sometimes a new message flow seems to be up and running but when I put a message on the queue nothing is happening....
So I can only repeat the question I asked in the beginning: Is this product (which is listed in the $100.000 range) so bad and buggy, or am I really too stupid to use it? My biggest problem is: I do not know what questions to ask (in this forum or at the IBM customer support), because I have problems everywhere.....
I'm really happy if people would post their comments and/or give some suggestions what I'm doing wrong.
Thanks,
Michael |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Sun Oct 31, 2004 6:03 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Michael, I am not a WBIMB expert, but I can answer some of your questions. The rest I leave to the experts.
| Quote: |
I use Windows XP service pack 2...
|
To my knowledge, this is unsupported. XP SP1 is supported. This can be the source of who knows how many of your problems. Or none of them.
| Quote: |
Websphere MQ 5.3 CSD 8 (which is registered in my system as version 5.30.0 instead of 5.3.8 - do not know why),...
|
Issue mqver at the command line to know what MQ version you are at. 5.3 with CSD08 is really 5.3.0.8.
| Quote: |
Message Broker 5.0.1.2 and the WBI Toolkit 5.1.0.3.
|
You should get yourself to 5.0.4 (CSD04), the latest version, for both the Toolkit and the Broker. I am assuming the 5.1.0.3 is a typo in your message.
| Quote: |
would complain that no JRE is installed even though I installed the IBM JRE 1.4.0 which came with Websphere MQ.
|
Annoying isn't it? A bug in the MQ install program I guess that's been around forever. If you know you got the JRE, ignore the "error".
| Quote: |
I could not connect to the Config-Manager ('Could not connect to MQ Queue Manager WBRK_QM (reason code = 2009)' ).
|
When you made a new Broker connection, you most likely spelled the channel name wrong (they are case sensitive). This is why Java apps get a 2009 on the initial connection attempt, a misspelled channel name. A 2009 after a connection has been established means you got disconnected for any number of reasons.
| Quote: |
(The one thing I found out: if something goes wrong, delete the broker and the configmgr using the mqsideletebroker and mqsideleteconfigmgr command, delete the database tables and the queue manager before you try anything else - this way chances to succeed are higher when you try it again....)
|
Seems a bit drastic. But for someone new, this may be helpful, as your initial set up steps may have contained errors.
The rest of the questions I am not knowledgable enough to answer. WB-IMB is a complicated program. Having no expirience with MQ on top of no expirience with any MQ Integrator/program means you have a tough road ahead of you if you are trying to do this alone and with no formal training. You came to the right place so you are not alone, but if your goal is to be profecient with this tool, get yourself some training. The aggravation it will save you is priceless.
And you need to work with it consistently. There is to much to know to take a class in November and expect to pick it up in June and run with it.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| nathanw |
| Posted: Mon Nov 01, 2004 12:04 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
Peter is right
I ahve to say that having used integartor in all its forms 1.0, 1.1 2 and now 5, it is not a simple program too pick up.
Documentation is getting alot better these days but to use an example, when 2.0 first came out the installation documentation was terrible and i found the routines used in the training manuals worked fiorst time everytime. This was probably due to the fact that non experienced people were in the training classes and to avoid delays etc the docs were written as idiot proof as possible (apologies to all). As a consultant / trainer / troubleshooter / support person i found that this helped alot.
V5 has alot of areas where if no experience is available it will drive you mad.
I have worked with "Broker" for getting on for 5 years now and when I first installed V5 I had alot of the same problems as you.
Get the latest updates and fixes and start again. Alot of the "buggy" problems have been sorted. But my best advice is to get on a course ASAP.
We are all willing to help here, however, the course will solve alot of initial problems. |
|
| Back to top |
|
|
| javaforvivek |
| Posted: Mon Nov 01, 2004 1:02 am Post subject: |
|
|
Master
Joined: 14 Jun 2002
Posts: 282
Location: Pune,India
|
| Quote: |
| For example I still cannot debug (So I guess something is wrong with my Agent Controller). |
Michael,
AS everyone here has suggested, use the latest VSD levels.
You may download the latest version of Agent Controller from
http://www6.software.ibm.com/dl/wbimb/wbimb-p
Select the proper platform and download the agent controller.
| Quote: |
| My biggest problem is: I do not know what questions to ask (in this forum or at the IBM customer support), because I have problems everywhere..... |
Search for the countless posts regarding installation and default configuration in this forum.
(Many of them were posted by me (and many others) who were novice at that time on WBIMB..!!  and faced numerous problems!!)
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Nov 01, 2004 7:33 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| PeterPotkay wrote: |
| Quote: |
I could not connect to the Config-Manager ('Could not connect to MQ Queue Manager WBRK_QM (reason code = 2009)' ).
|
When you made a new Broker connection, you most likely spelled the channel name wrong (they are case sensitive). This is why Java apps get a 2009 on the initial connection attempt, a misspelled channel name. A 2009 after a connection has been established means you got disconnected for any number of reasons.
|
Also, if everything is set up right, but your SYSTEM.BKR.CONFIG channel on your Configuration Manager is STOPPED, you will see this error code.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mcfennek |
| Posted: Fri Nov 05, 2004 6:16 am Post subject: |
|
|
Newbie
Joined: 31 Oct 2004
Posts: 8
|
Hallo,
thanks for all your relies,
as suggested I switched to the latest CSDs, including Toolkit Version 5.0.4 (CSD04). I found out that WBI Toolkit Version 5.1.0.3. is only suggested for users of the Websphere Studio 5.1 (see link).
After these changes everything went much smoother. Also with my debugging problems, I found out that my Agent Controller pointed to the wrong JRE (Eclipse comes with its own JRE).
Now I still have minor problems, but at least I can work and have a chance to solve my problems.
As I worked with MQSI 2.1 before I just was really surprised in how many problems you can run with WBIMB 5.0.
Thanks again,
Michael |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Nov 05, 2004 4:44 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Mike, thanks to Jeff's reply in another post, I decided to look at the read me for CSD04. CSD04 ships with a whole bunch of defects!!! All come with known manual fixes, but if you applied CSD04 and did not go thru and follow up with what the read me suggests, more problems would follow.
I find it kinda odd that a CSD would ship with so many issues built into it...
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Nov 06, 2004 6:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| PeterPotkay wrote: |
| I find it kinda odd that a CSD would ship with so many issues built into it... |
Yes, me too. IBM usually reserves that kind of behavior for GA, not for FixPacks...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nathanw |
| Posted: Mon Nov 08, 2004 3:52 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
| jefflowrey wrote: |
| PeterPotkay wrote: |
| I find it kinda odd that a CSD would ship with so many issues built into it... |
Yes, me too. IBM usually reserves that kind of behavior for GA, not for FixPacks...
|
RIGHTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT  |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Nov 08, 2004 5:03 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Redbooks can be a good way to get going with unfamilar products.
It's my subjective impression that IBM have cut back on their testing of the Websphere MQ family of products.
Certainly defects are occuring that I would have expected to have been picked up at the labs. |
|
| 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
|
|
|
|
