| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Toolkit not showing textual name of Execution Group |
« View previous topic :: View next topic » |
| Author |
Message
|
| anantha sreenivasan |
 Posted: Tue Oct 28, 2008 2:22 am Post subject: Toolkit not showing textual name of Execution Group |
 |
|
Acolyte
Joined: 26 Sep 2006
Posts: 72
|
I have connected to broker from toolkit to deploy message flows. THe toolkit displays the name of the broker correctly under the Broker Topology tree view, but instead of
When I connect to an AIX broker the toolkit, for any execution group name it shows as "DiscoverdEG_UUID". For example "DiscoveredEG_a53c7f42-1c01-0000-0080-fda1f5bdb82d"
I find all the SYSTEM.BROKER.* queues empty in the configuration manager queue manager.
What could be the problem? |
|
| Back to top |
|
 |
| hopsala |
| Posted: Tue Oct 28, 2008 3:05 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Hm. Maybe you lack authorities to view execution groups. search for "mqsicreateaclentry" and give yourself full cmp authorities. try then.
Another possibility is that the toolkit was improperly installed. You should try from another station with a different user and see if the same happens. Btw, can you see EGs on other brokers? Is this a new station? |
|
| Back to top |
|
|
| anantha sreenivasan |
| Posted: Tue Oct 28, 2008 3:09 am Post subject: |
|
|
Acolyte
Joined: 26 Sep 2006
Posts: 72
|
The necessary authorities are in-place. Otherwise I would not be able to connect to the broker topology, which I can in this case.
The toolkit installation is proper since other brokers which communicate with this configuration manager, display their respective EG names without any issues.
Also from wherever I connect, I'm facing this issue.
Also this is not a new station and it has been under use for more than 4 months. |
|
| Back to top |
|
|
| anantha sreenivasan |
| Posted: Tue Oct 28, 2008 3:53 am Post subject: |
|
|
Acolyte
Joined: 26 Sep 2006
Posts: 72
|
| Will the action of tracing the configuration manager provide any clue to this issue? |
|
| Back to top |
|
|
| hopsala |
| Posted: Tue Oct 28, 2008 5:28 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| anantha sreenivasan wrote: |
| The necessary authorities are in-place. Otherwise I would not be able to connect to the broker topology, which I can in this case. |
This is false. There are seperate authorities for viewing broker topology and for viewing execution groups.
| anantha sreenivasan wrote: |
| Will the action of tracing the configuration manager provide any clue to this issue? |
It might, but this is the last thing you should do, not the first. If I were you, i'd:
1. Create another EG and see if the same happens.
2. If it does't, delete the faulty EG, create another and hope for the best. |
|
| 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
|
|
|
|
