| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Newbie Adventures with WBIv5. Help Requested. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Osaka |
 Posted: Sun Jan 29, 2006 5:23 pm Post subject: Newbie Adventures with WBIv5. Help Requested. |
 |
|
Newbie
Joined: 29 Jan 2006
Posts: 5
Location: IBM - Houston, TX
|
I am new completely new to WBI. I am using v5. I have read the online docs and red book 24-7090. I picked up this work for a collegue pulled away on a Sev-1 problem.
I am trying to deploy a fairly simple Message Flow Project.
One MQInput node linked to a queue named "TEST.TO.COURTS".
The MQInput node has an Out->In link to a Compute node.
The Compute node has ESQL that checks an input value and changes "OutputLocalEnvironment.Destination.MQ.DestinationData[1]" queue manager and queue name to various values.
The Compute node has an Out->In link to a MQOutput node.
The MQOutput node has Queue Manager and Queue Name blank since they should be set by the Compute node. It has Destination Mode set to "Destination List".
The idea is for an application to send MQ messages to only one Queue named "TEST.TO.COURTS" and they get automatically routed to the proper remote system Queues according to a value set in the input XML message.
All of our servers are Windows 2003 Servers. The application will be running on a separate box from the "MQ Router" box. One problem confusing me is that there is already a Configuration Manager and Broker defined on the Router box being used by another contact admin project. We each have our own Queue Managers defined. All the documentation I have found never mentions multiple Configuration Managers on the same Windows box. When I run the mqsicreateconfigmgr.exe command, I get the following error message "BIP8087E: ConfigMgr already exists and cannot be created.". I am passing the command a different userid, Queue Manager, and database than the original one would have been created with.
I decided to see if I could just use the same Config Manager, and create my own Broker. I used the Message Broker Toolkit to create a new Broker under the exising Config Manager connection (the one tied to the other projects Q manager) listed in the "Domains" window. I noticed that even though it would let me create the broker, when I run the mqsilist command, the new broker is not listed. So I deleted the broker from the Toolkit, and first created the broker using the mqsicreatebroker.exe command, which was successful. I could start new broker with the mqsistart command. Adding the broker with the toolkit still gives the same result, I get a "Broker is not running" alert in the toolkits Alerts window.
Can anyone offer me some advice on what path I should try?
Can multiple Config Managers exist on the same windows box?
Can two brokers use different Queue Managers when associated with the same Config Manager?
Any help is greatly appreciated. Ive already overrun the schedule. 
_________________
-Steve |
|
| Back to top |
|
 |
| wschutz |
| Posted: Sun Jan 29, 2006 6:02 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
Can multiple Config Managers exist on the same windows box?
Can two brokers use different Queue Managers when associated with the same Config Manager? |
(1) Only V6 of broker allows two config managers on the same physical machine.
(2) Yes, if you want more than one broker per machine, you need to have a seperate qmgr for each broker ... and, you need to
(a) put both qmgrs (the configmgr qmgr and the broker qmgrs) in the same qmgr cluster so they can communicate with each other or
(b) set up MQ channels between the qmgrs so they can communicate (see the Intercommunication Manual)
_________________
-wayne |
|
| Back to top |
|
|
| Osaka |
| Posted: Sun Jan 29, 2006 9:19 pm Post subject: |
|
|
Newbie
Joined: 29 Jan 2006
Posts: 5
Location: IBM - Houston, TX
|
Thanks for the info.
I think I see that I need to create some transmission queues and sender/receiver channels between the two Queue Managers so the new broker can talk to the Config Manager.
Now I think I have somehow gotten the Config Manager into an inconsistent state. I created the channels and queues, and physical broker but when I added the broker in the toolkit, I got an error saying something to the effect that I did things in the wrong order.
So I tried to delete everything and start over, but no matter what I do, the toolkit gives me an error. I select Complete Broker Topology Deploy, and get:
"BIP1510E: Unable to deploy configuration data.
An attempt was made to deploy configuration data to one or more brokers, but the Configuration Manager is already deploying to broker ETIX_BROKER"
After reading some more online, I checked the CBROKER table, and there is a row with CSECTION = 'GRAVEY' and CNAME = 'ETIX_BROKER'. I have completly deleted all reference to ETIX_BROKER broker everywhere else, so I guess this row needs to be deleted. Just wanted to confirm that since the other post said CSECTION would be equal to 'DPLING'.
Thanks again for all the help.
If its something anyone knows like the back of your hand, could you please post me the proper order of steps to create broker. Right now I still have the queues and channels defined in MQ, they are just all stopped. Everything else is deleted except the row in CBROKER table.
_________________
-Steve |
|
| Back to top |
|
|
| Osaka |
| Posted: Sun Jan 29, 2006 9:37 pm Post subject: |
|
|
Newbie
Joined: 29 Jan 2006
Posts: 5
Location: IBM - Houston, TX
|
Sorry for being long winded, just trying to supply as much info as possible.
After I do the 'Cancel Deployment', I get a successful message:
"BIP1520I: Deploy operations successfully initiated.
The Configuration Manager has processed the deploy request and initiated the deploy of configuration data to the following brokers. Active brokers: DBROKER . Deleted brokers: ETIX_BROKER."
The CBROKER table has one row with CSECTION = 'GRAVEY' at this point.
Then, if I do a 'Complete Deployment', I get a successful message:
"BIP1520I: Deploy operations successfully initiated.
The Configuration Manager has processed the deploy request and initiated the deploy of configuration data to the following brokers. Active brokers: DBROKER . Deleted brokers: ETIX_BROKER ."
The CBROKER table has two rows, one with GRAVEY and one with DPLING at this point.
Then, if I do another 'Complete Deployment', I get an error message:
"BIP1510E: Unable to deploy configuration data.
An attempt was made to deploy configuration data to one or more brokers, but the Configuration Manager is already deploying to broker ETIX_BROKER. You can not deploy to a set of brokers if there is an earlier deploy outstanding to any broker in the set. The deploy operation was not performed."
The CBROKER table still has two rows, one with GRAVEY and one with DPLING.
This pattern repeats...
_________________
-Steve |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sun Jan 29, 2006 9:45 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Osaka,
Please keep your posts short and simple. Thx.
Just tell us what have u created as of now, i.e
ConfigMgr, its database = ? (Does it start)
Broker(s), its database = ? (Does it start)
Config Queue Manager = ?
---- Transmission Queue = ?
---- Channels = ?
Broker Queue Manager = ?
---- Transmission Queue = ?
---- Channels = ?
After all this tell us where you are currently, is it connected or not, u are able to not able to deploy etc.
Regards. |
|
| Back to top |
|
|
| Osaka |
| Posted: Sun Jan 29, 2006 10:36 pm Post subject: |
|
|
Newbie
Joined: 29 Jan 2006
Posts: 5
Location: IBM - Houston, TX
|
| elvis_gn wrote: |
Hi Osaka,
Please keep your posts short and simple. Thx.
Just tell us what have u created as of now, i.e
ConfigMgr, its database = ? (Does it start) YES, YES
Broker(s), its database = ? (Does it start) YES, YES
Config Queue Manager = ? YES
---- Transmission Queue = ? YES
---- Channels = ? YES
Broker Queue Manager = ? YES
---- Transmission Queue = ? YES
---- Channels = ? YES
After all this tell us where you are currently, is it connected or not, u are able to not able to deploy etc.
When I try to do "New -> Broker" in the Toolkit, I get an error saying "BIP1511E: Queue manager 'WASETIX' cannot be associated with broker 'ETIX_BROKER'; it is already associated with broker 'ETIX_BROKER'. " I am assuming this is resulting from the row that exists in the CBROKER table even after I delete all references to ETIX_BROKER. I wont have access to delete that row till tomorrow at work, and wanted to make sure deleting the row was a good idea and wouldnt hose the whole system.
Regards. |
_________________
-Steve |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sun Jan 29, 2006 10:55 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Osaka,
I have not fooled around with the ConfigMgr or Broker tables....I dont mean that u should not try it or it wont work, it will work and I have noticed many here doing the same...its just that the need has not arrived for me yet.
If your broker is created newly, then I would just drop the ConfigMgr, its database, and then recreate it...its a 5min work.
This would definitely solve the problem.
Ofcourse you should NOT do it if you have multiple Brokers.
In MB v6.0 the configMgr database in on Derby or so, I dont know what will happen to our tricks of removing rows there.
Regards. |
|
| Back to top |
|
|
| Osaka |
| Posted: Mon Jan 30, 2006 1:46 pm Post subject: |
|
|
Newbie
Joined: 29 Jan 2006
Posts: 5
Location: IBM - Houston, TX
|
Unfortunately there will be no v6 for me.
I got the DBA to delete the row from the database. So at this point there are no references to my broker anywhere.
I created sender/receiver channels on each Queue Manager to eachother. I created Queues on each one named after eachother.
I ran mqsicreatebroker
I ran mqsistart
I loaded up the Toolkit, and created the broker in the Domains window pane and did a Delta deploy with no errors.
It STILL gives me a yellow alert symbol on the new broker and reports "Broker is not running". (I checked the services and it is running, the Windows Event Viewer reports successful startup messages for the broker process also). Somehow the toolkit doesnt know the broker is running...
Now when I look in the CBROKER table there are two lines... one has CSECTION='SHARED' and the other has 'DPLING'. So somehow it is getting stuck in the middle of the deployment???
_________________
-Steve |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Jan 30, 2006 8:49 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Osaka,
Are any flows deployed under any Execution group under the broker ?
If not then the Broker will show as not running.
Regards. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Jan 31, 2006 3:59 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
For most tables in the Config Manager (including CBROKER), a row with a CSECTION column of SHARED means that the entry describes the set of properties as entered in the toolkit.
A CSECTION of DEPLED means that the entry describes the deployed object - e.g. what the broker has reported its state as being to the CM.
A CSECTION of GRAVEY refers to a broker that has been deleted in the toolkit, but either this has not been deployed to the broker, or the broker has not yet told the CM that it has tidied up successfully.
There are also CSECTIONS called GENRAL and TECHNO, but are not important here.
The CM repository is a linked hierarchy; for example, the topology (CTOPOLOGY) contains UUID references to rows in the CBROKER table, the data for which contains UUID references to rows in the execution groups table (CEG) and so on. Therefore, it is not usually sufficient just to delete rows - you have to unlink them from the parent document too.
Which is why messing around with the database is usually a bad idea. ...And is also why I went to great pains to (a) hide the repository and (b) provide database tidyup through the CMP API in v6 |
|
| 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
|
|
|
|
