| Author |
Message
|
| siri |
 Posted: Tue Dec 15, 2009 2:13 am Post subject: MB: Bar file deployment |
 |
|
Newbie
Joined: 15 Dec 2009
Posts: 6
|
Hello,
I have created mb components on Red hat linux:
BIP8099I: ConfigMgr: mbconfig - mbqm
BIP8099I: Broker: mbbroker - mbqm
Both the components are using the same queue manager mbqm with a listener defined on port 1818. The components have started successfully. The user name is 'mqm' and has access to mb.mq and IBM DB2.
Now i am trying to deploy a bar file and I am facing the following issue:
---------------------------------------------------------------------------------------------------------------------------------------------
./mqsideploy -i IP_Address -p 1818 -q mbqm -b mbbroker -e default -a sample.bar
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1045I: Connecting to the Configuration Manager...
BIP1037S: Broker not found.
Broker 'mbbroker' was not found in the Configuration Manager repository.
Reissue the command specifying an existing broker.
---------------------------------------------------------------------------------------------------------------------------------------------
Please suggest me,
Thanks,
Siri. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Tue Dec 15, 2009 2:36 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
does the config manager KNOW about the broker?
Does the Broker appear in the Toolkit Admin perspective when you connect the toolkit to the ConfigMgr?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| siri |
| Posted: Tue Dec 15, 2009 3:38 am Post subject: |
|
|
Newbie
Joined: 15 Dec 2009
Posts: 6
|
Hello,
The broker is setup in a remote box and I am accessing the broker machine using putty to deploy the BAR files.
Thanks,
Siri |
|
| Back to top |
|
|
| fschofer |
| Posted: Tue Dec 15, 2009 3:59 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Dec 15, 2009 3:59 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
My two questions still apply.
The configmgr HAS to be associated with the broker(s) it controls otherwise, how can it know where to deploy the things you want to deploy to?
This is done via the toolkit or via the CMP exerciser.
Once this is done then you can deploy from the commandline.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Dec 15, 2009 4:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| If you use mqsicreateexecutiongroup with the... -f? ... flag? one of the flags, it will register the Broker with the configmgr. |
|
| Back to top |
|
|
| siri |
| Posted: Tue Dec 15, 2009 5:28 am Post subject: |
|
|
Newbie
Joined: 15 Dec 2009
Posts: 6
|
Hello smdavies99,
I have added a new domain connection in Tool Kit and connected to remote configuration manger suuccessfuly but now I am not able to see any brokers in the Brokers List.
Hello mqjeff,
I also tried to create a new execution group, the error is as follows:
----------------------------------------------------------------------------------------------------------------------------------------------
./mqsicreateexecutiongroup -i localhost -p 1818 -q mbqm -b mbbroker -e mbeg -f mbqm
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1045I: Connecting to the Configuration Manager...
BIP1145I: Defining broker 'mbbroker' on 'mbqm' in the Configuration Manager...
BIP1124I: Creating execution group 'mbeg' on broker 'mbbroker'...
BIP1125E: The execution group could not be created.
The utility was asked to create execution group 'mbeg' on broker 'mbbroker', but it was not completed successfully by the Configuration Manager. The Configuration Manager reported the following error(s): [{message=BIP1712W, detail=BIP1712W: Broker not found
An attempt was made to view or modify the Broker with UUID '9482bd94-2501-0000-0080-853017ac5468', but it does not exist in the Configuration Manager's repository.
If you are trying to manipulate an object immediately after submitting a request to create it, it is likely that there was a problem creating the object. An example of this is if you attempt to create a default execution group without first ensuring that the parent broker was created successfully; this error suggests that there was a problem creating the broker.
Check the Configuration Manager's logs to see why the Broker could not be found. If the object has previously been available, the receipt of this error may indicate corruption in the Configuration Manager's repository; if this is the case, you may need to use mqsirestoreconfigmgr to restore the Configuration Manager's repository, or if this is not possible, contact your IBM support center for advice., source=ConfigMgr, timestamp=Tue Dec 15 18:47:46 EST 2009}]
-------------------------------------------------------------------------------------------------------------------------------------------
Thanks,
Siri |
|
| Back to top |
|
|
| nathanw |
| Posted: Tue Dec 15, 2009 5:32 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
I would sugegst that you read through the basic set up of Brokers etc in GUI
You have not added your broker to your configmgr which has been stated several times previously in this thread
| Code: |
| An attempt was made to view or modify the Broker with UUID '9482bd94-2501-0000-0080-853017ac5468', but it does not exist in the Configuration Manager's repository. |
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Dec 15, 2009 6:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
nathanw - the mqsicreateexecutiongroup command would have handled registering the broker with the configmgr if it had completed successfully.
It didn't end successfully. So all the usual, documented, methods for determining why a Broker couldn't be registered with a ConfigMgr apply.
For which methods siri now should go review the basic set up of Broker. |
|
| Back to top |
|
|
| siri |
| Posted: Tue Dec 15, 2009 7:36 am Post subject: |
|
|
Newbie
Joined: 15 Dec 2009
Posts: 6
|
Hello,
I have successfully deployed the bar files. Added the broker to broker domain in the tool kit and now able to deploy using the command promt.
Thank you all for your suggestions.
Thanks,
Siri |
|
| Back to top |
|
|
|
|
