| Author |
Message
|
| my_mqseries |
 Posted: Mon Jun 05, 2006 5:19 am Post subject: WBIMB Getting Started |
 |
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
I am new to WBIMB. I have been trying to start off with a simple examples. But I am heading nowhere. I just cant deploy the sample. Here are the list of steps I am doing. Could anyone please tell me if there is anything missing or doing wrong. I really appreciate your help on this.
1. Created two separate databases in DB2. One for Broker (WBIMB_BROKER) and another for Configuration Manager (default ConfigMgr).
2. Created new Queue Manager (WBIMB.queue.manager on Port 1420) which is going to be used by Broker, Configuration Manager and Application.
3. Created two local queues. One named IN and another one OUT, to be used in application development.
4. Created two System DSNs. One for Broker (WBRKBKDB) and another for Configuration Manager (WBRKCMDB).
5. Created Broker WBIMB_BROKER with the following command.
mqsicreatebroker WBIMB_BROKER -i MyLogin -a password -q
WBIMB.queue.manager -n WBRKBKDB -u MyLogin -p password
6. Create Configuration Manager with the following command.
mqsicreateconfigmgr -iMyLogin -apassword -qWBIMB.queue.manager
–nWBRKCMDB -uMyLogin –ppassword
7. Started both WBIMB_BROKER and ConfigMgr. No problems in start up. Verified Event Viewer.
8. Now, in Broker Application Development Perspective and created new Message Flow Project.
9. Add a Message Flow to this project. Added three nodes (MQInput, MQOutput and Compute). Set the Properties of MQInput (IN Queue), MQOutput (Out Queue) and Compute (generated esql and saved it).
10. In Broker Administration Perspective, added new Domain to Domain Connections which created a configmgr.
11. Then added Broker to the Domain by selecting New  Broker  from File Menu.
12. Now deploying the Message Flow Project to the newly created Domain. Right click on Message Flow Project and click on Run on Server and complete the rest. With this it is deployed to Domain.
13. Deploy Topology to the Config Mgr. Right click on Broker Topology and click on Deploy Topology Configuration  Complete.
Thank You very much |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jun 05, 2006 5:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I guess you're using v5.
You don't explain what goes wrong.
I wouldn't use "run on server", myself. I'd build a bar file and deploy that. But that's mostly personal preference.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pottas |
| Posted: Mon Jun 05, 2006 5:39 am Post subject: |
|
|
Disciple
Joined: 27 Oct 2005
Posts: 185
Location: South Africa
|
What version of MQ and Broker are you running?
What errors do you get in your Application Logs?
And check your Event Log in you Broker Administration Perspective in the Domains pane - do you get any errors when you deploy your bar file?
Please post the errors you're getting.
pottas |
|
| Back to top |
|
|
| my_mqseries |
| Posted: Mon Jun 05, 2006 6:13 am Post subject: |
|
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
Sorry.. I haven't provided enough details.
I am using WBIMB V 5.0 (also tried after applying FixPack 7) on Windows XP. IBM DB2 V8.2. WebSphere MQ V5.3 with CSD10.
I did try to create a BAR file and deploy it. Afte any of these tries, gives me an alert "Execution Group is not running".
I wanted to know whether the steps which I am following are right or wrong? So that I try in a different way.
From Application Log I get an error
( WBIMB_BROKER ) Broker WBIMB_BROKER (UUID f49f959f-0b01-0000-0080-99c5942f0c26) was unable to retrieve an internal configuration response message for execution group 'MyLogin' within the 360 second Configuration Timeout.
I did increase the configuration time out to 500 secs.
Cheers |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Jun 05, 2006 11:24 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
In the broker admin perspective, do you see this "MyLogin" execution group under the topology you created?
_________________
-wayne |
|
| Back to top |
|
|
| my_mqseries |
| Posted: Mon Jun 05, 2006 1:30 pm Post subject: |
|
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
| Yes. I can see MyLogin in Topology alongwith default Execution Group. However, when I right click on it, I cannot see the option Start. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jun 05, 2006 1:39 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You don't mention that you did this or not.
You need to establish a sender/receiver pair for the configmgr going to broker, AND a sender/receiver pair for the broker going to the config manager.
So you would need the following objects on your broker queue manager:
Sender pointing to configmgr queue manager
Transmission queue named after configmgr qmgr name
Receiver channel from configmgr queue manager
and these on your configmgr queue manager:
Sender channel pointing to broker queue manager.
Transmissions queue named after broker qmgr name
Receiver channel from broker
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| my_mqseries |
| Posted: Mon Jun 05, 2006 2:13 pm Post subject: |
|
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
Oh.. I didn't have a clue about these Queues which you are talking about. This looks like I need to create two separate Queue Managers. One for Broker and another one for Configuration Manager and then create the queues which are mentioned above?
Thank You |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jun 05, 2006 5:06 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Not if you pointed them both at the same queue manager.
Which I guess you said you did. 
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| my_mqseries |
| Posted: Tue Jun 06, 2006 5:55 pm Post subject: |
|
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
Hi jefflowrey
I did create channels and queues as you mention. Channels did start fine. Now I did create another sample msg flow project did create a BAR file and deployed it. Still I have same problem. "Execution Group is not running". Now I have two separate Queue Managers. One for Configuration Manager and another one for Broker.
This problem is just haunting me. Can you please let me know whether the steps I am following are right.
Thanks a lot. |
|
| Back to top |
|
|
| SpitFire |
| Posted: Tue Jun 06, 2006 10:16 pm Post subject: |
|
|
Acolyte
Joined: 01 Aug 2005
Posts: 59
Location: India
|
| my_mqseries wrote: |
Now I did create another sample msg flow project did create a BAR file and deployed it. Still I have same problem. "Execution Group is not running".
|
Check if the following services are running in your task manager
1) bipservice.exe (2 instances)
2) bipbroker.exe
3) bipconfigmgr.exe
4) dataflowengine.exe
And before you deploy any project, try to deploy(complete) just the topology configuration and check if that happens successfully.
[/quote]
_________________
...: 5|71+ph1|23 :... |
|
| Back to top |
|
|
| my_mqseries |
| Posted: Wed Jun 07, 2006 3:58 am Post subject: |
|
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
This is getting interested. I appreciate all the replies to my problem.
I did check the Processes and I can see all except for dataflowengine. I tried to start it from bin but I get this error in Event Viewer.
(default. ) Administrative agent to execution group communication error: invalid value '' supplied for execution group parameter 'ExecutionGroupUUID'.
The invalid value '' was supplied for the execution group parameter 'ExecutionGroupUUID'.
Stop and restart the broker. If the problem persists, stop, delete, recreate and then restart the broker.
I did do what has been suggested in error like stopped, deleted and recreated broker. Still I cant start DataFlowEngine.
When and how does it is started please?
Thank You |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 07, 2006 4:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Each dataflowengine.exe is an execution group. You can't start them manually, they are started by bipbroker.exe (which is started by bipservice.exe).
Please stop and restart the broker.
Please try spitfire's suggestion of deploying the complete Topology again.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| my_mqseries |
| Posted: Wed Jun 07, 2006 11:30 am Post subject: |
|
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
I tried doing as suggested. Now the error is
BIP1533E: Unable to deploy configuration data: unknown WebSphere MQ queue manager WBIMB_BROKER.queue.manager associated with broker TestMsgBroker.
An attempt was made to deploy configuration data to one or more brokers. The WebSphere MQ queue manager WBIMB_BROKER.queue.manager associated with broker TestMsgBroker is not known to the Configuration Manager's WebSphere MQ queue manager. The deploy operation was not performed.
Check that the name of the queue manager is spelled correctly. Note that WebSphere MQ queue manager names are case-sensitive. If the spelling is correct, make sure that either a queue manager alias definition for queue manager WBIMB_BROKER.queue.manager, or a transmission queue called WBIMB_BROKER.queue.manager, is defined to the Configuration Manager's queue manager. For more information on this error see the WebSphere MQ Application Programming Reference manual, code 2087.
I did read in forum somewhere that
[color=blue]do not forget to create the transmission queue that has the same name as the queue you are going to.[/color]
What does this mean please?
Thank You |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Jun 07, 2006 12:47 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Quote: |
| 2. Created new Queue Manager (WBIMB.queue.manager on Port 1420) which is going to be used by Broker, Configuration Manager and Application. |
I don't think you need to worry about communication between the two qmgrs since you only have one.
As far as what the xmitq having the same name as the qmgr, it helps WMQ do the routing between the two qmgrs without have to create specific QREMOTEs for everything. Details can be found in the Intercommunications Manual. |
|
| Back to top |
|
|
|
|
