| Author |
Message
|
| SphereOfLove |
 Posted: Mon Mar 09, 2015 7:22 am Post subject: Using a Broker with an existing Windows CLuster (MSCS) |
 |
|
Apprentice
Joined: 13 May 2014
Posts: 38
|
Hi,
I have created a cluster of two nodes. I have successfully defined Queue Manager and put it under MSCS control by adding it to windows ( 2008 r2 data Center addition) Services and Applications( i am using Integration Bus 9.0.0.1).
Then i created a broker under it using mqsicreatebroker xxxxx -i username -a password -e sharedfolderpath.
I have also added broker info on the other node too, but the thing is broker service fails when switching over to the other node.
I goto the second node, stop QM and restarts QM with -si option. then i could start the broker, but still when i fail over the broker does not starts.
I could see the following error in logs;
| Code: |
AMQ6125: An internal WebSphere MQ error has occurred.
AMQ6118: An internal WebSphere MQ error has occurred (20800835)
AMQ9422: Repository manager error, RC=0
AMQ6184: An internal WebSphere MQ error has occurred on queue manager mblQMGR.
|
any Idea? anyone. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Mar 09, 2015 7:50 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What is the service userid for the qmgr? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Mar 09, 2015 9:30 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
you are missing an option on the mqsicreatebroker command
This post may help you move forward
http://www.mqseries.net/phpBB2/viewtopic.php?t=67168
don't forget that once to have the broker working you need to stop it, failover and then run the mqsiaddbrokerinstance command on the second node.
ONLY when the broker runs on both nodes shouls you add it to the MSCS as a generic service.
If you are new to this than be prepared to make a good few mistakes as you learn the way to do it. Script everything.
_________________
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 |
|
|
| SphereOfLove |
| Posted: Tue Mar 10, 2015 7:00 am Post subject: |
|
|
Apprentice
Joined: 13 May 2014
Posts: 38
|
| smdavies99 wrote: |
you are missing an option on the mqsicreatebroker command
This post may help you move forward
http://www.mqseries.net/phpBB2/viewtopic.php?t=67168
don't forget that once to have the broker working you need to stop it, failover and then run the mqsiaddbrokerinstance command on the second node.
ONLY when the broker runs on both nodes shouls you add it to the MSCS as a generic service.
If you are new to this than be prepared to make a good few mistakes as you learn the way to do it. Script everything. |
Excellent! and Thank you smdavies99.
Your TIPS and Link Fixed alot. Now the i can failover to both node successfully!
Great Help from YOU!
One more thing that needs to be clear as when i switch to the second node where I added mqsibrokerinstance, if i open explorer there, i can not see broker/integration node under the MQ, although i could see MQ (running) and if i query mqsilist, the broker is also running; the broker service is also up and running.
Is there i miss something?
NOTE:
I added three things for the cluster to work.
1: I created QM with ... crtmqm -a option.
2: I created broker with -B and -w option.
3: I followed the instructions from smdavies99. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Mar 10, 2015 10:50 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
This is a known 'sometimes happens' feature.
If you installed MBExplorer Fix pack into a different directory this may happen.
There are some posts here on the subject.
What I do is add the broker connection as a remote broker and using the Cluster IP address. Do the same for the QMGR
This way you can use the Explorer on either node.
You WILL however run into issues with MQ V8 security. There are a number of articles by Morag Hughson on this. There are links from a numer of posts in the Security Forum.
_________________
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 |
|
|
| SphereOfLove |
| Posted: Wed Mar 11, 2015 10:50 pm Post subject: |
|
|
Apprentice
Joined: 13 May 2014
Posts: 38
|
| smdavies99 wrote: |
This is a known 'sometimes happens' feature.
If you installed MBExplorer Fix pack into a different directory this may happen.
There are some posts here on the subject.
What I do is add the broker connection as a remote broker and using the Cluster IP address. Do the same for the QMGR
This way you can use the Explorer on either node.
You WILL however run into issues with MQ V8 security. There are a number of articles by Morag Hughson on this. There are links from a numer of posts in the Security Forum. |
Thank you! |
|
| Back to top |
|
|
|
|
