| Author |
Message
|
| hs |
 Posted: Fri Jun 03, 2005 2:31 am Post subject: WBIMB - Debgugger not working |
 |
|
Novice
Joined: 03 Jun 2005
Posts: 17
|
I am using WBIMB V5 on XP Professional. It has been setup on a standalone machine. I am currently trying to use the debug facility but experiencing some problems.
hostname=harry
The steps are:
1. Select "Attach" after clicking on Flow debug perspective.
2. Double click on localhost, then click on "Next" button
I then get a "Security Message" window, where it asks for:
User name, Password. Once the information has been given, it just hangs and eventually comes back with the following error:
"Information you exchange with this Agent controller cannot be viewed or changed by others.
However, it cannot be determined whether this Agent Controller is the intended target on host harry.
Inorder to verify the target Agent Controller is correct, you must import the certificate of the Agent Controller on host harry."
Reason:
IWAT0017E Security certificate not available for host harry
Make sure that you have the correct security certificates imported into the workspace.
Does anyone know why I am getting this error ? All I want to do is debug a message flow on a standalone machine.  |
|
| Back to top |
|
 |
| hs |
| Posted: Fri Jun 03, 2005 4:42 am Post subject: |
|
|
Novice
Joined: 03 Jun 2005
Posts: 17
|
I have made some progress so far....
I no longer get the Security Message window, after specifying account details in the IBM Agent Controller service. This was initially missing...
In the "Attach to the Flow Engine" window, there is no list of flow engines from the list. It is blank !
Why can't I select a flow engine ?
IBM Certified Specialist - MQSeries 5.3 |
|
| Back to top |
|
|
| JT |
| Posted: Fri Jun 03, 2005 7:25 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| The Agent Controller must be started prior to starting any brokers. So, if you haven't already done so, stop the broker & Agent Controller, and restart them in their correct sequence. |
|
| Back to top |
|
|
| chibban |
| Posted: Sun Jun 05, 2005 8:15 am Post subject: |
|
|
Novice
Joined: 01 Jun 2005
Posts: 14
|
I beleive stop RAC service -> Start RAC service -> mqsireload for all the data flow engines is also good.
I had a missing execution group on the debugger and that solved this in my case.
_________________
Thanks,
Sivan |
|
| Back to top |
|
|
| hs |
| Posted: Mon Jun 06, 2005 12:37 am Post subject: |
|
|
Novice
Joined: 03 Jun 2005
Posts: 17
|
Thanks for all the suggestions so far:
JT: I checked that the agent controller does start before any broker service.
Sivan: I am not sure what RAC service looks like in the SERVICES. By what name are you referring to ?
I tried MQSIRELOAD but I am still getting a blank list for selecting the flow engine.  |
|
| Back to top |
|
|
| Nick Lethbridge |
| Posted: Mon Jun 06, 2005 2:52 am Post subject: |
|
|
Voyager
Joined: 13 Aug 2001
Posts: 88
Location: Santander, UK
|
I guess that you are running IBM Agent Controller (RAC) Version 5.0.2. build 20040205_1459 - required if you have Fix Pack 3 or later installed ?
I have also encountered similar problems with the WBIMB debugger, it seems to be a case of stopping the RAC, stopping the broker, closing the Toolkit and then restarting them in the order RAC, broker, Toolkit.
The debugger is good when it all "comes together", but it does seem a bit inconsistent.....
I am running with Fix Pack 4, so perhaps this has been fixed in Fix Pack 5 ?
Have you had a look at the RAC servicelog.log - it might give some clue as to why you cannot see the flow engines ? |
|
| Back to top |
|
|
| hs |
| Posted: Tue Jun 07, 2005 6:04 am Post subject: |
|
|
Novice
Joined: 03 Jun 2005
Posts: 17
|
Thanks Nick.
IT'S WORKING !!!!! 
I looked in the registry and it showed that I was running IBM Agent Controller (RAC) Version 5.0.1.
I upgraded to RAC 5.0.2 and now it works ! |
|
| Back to top |
|
|
| NSJ |
| Posted: Fri Jul 15, 2005 1:53 am Post subject: |
|
|
Novice
Joined: 06 Jul 2005
Posts: 12
|
Hi All
I am having the same problem of the debugger not displaying the flow engine.Eventhough i am using Agent controller version 5.0.2 i am not able to debug. I am running message broker 5.0 Fix pack 5 on WIN XP. Is there any other prerequisites or configuration that needs to be done. I tried reinstalling Agentcontroller but i still cant debug the message flows. Tried restarting the config manager , broker and agent controller in the correct sequence too.
Any suggestions??.
Thanks
NSJ |
|
| Back to top |
|
|
|
|
