| Author |
Message
|
| shubha_s |
 Posted: Tue Nov 03, 2009 8:20 pm Post subject: MB issue |
 |
|
Acolyte
Joined: 10 Mar 2009
Posts: 57
|
HI,
I am using MB5. I have the toolkit being installed in Windows machine and the broker is in AIX machine. Is it possible to monitor the windows machine i.e the MB Toolkit from some other windows machine?
So when the windows machine goes down, the flows are not affected and the we can make the broker communicate with the other Windows machine.
Is this possible?? If so how.
--
Thanks |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Nov 03, 2009 9:14 pm Post subject: Re: MB issue |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| shubha_s wrote: |
I am using MB5. I have the toolkit being installed in Windows machine and the broker is in AIX machine. Is it possible to monitor the windows machine i.e the MB Toolkit from some other windows machine?
So when the windows machine goes down, the flows are not affected and the we can make the broker communicate with the other Windows machine.
Is this possible?? If so how.
|
MB Toolkit is more over a client, so you can install it on different windows workstations and connect to your broker which is running in AIX server
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| shubha_s |
| Posted: Tue Nov 03, 2009 10:06 pm Post subject: MB issue |
|
|
Acolyte
Joined: 10 Mar 2009
Posts: 57
|
But I want the same configuration manager running on both windows machines and I want the broker to communicate to both the machines..So that when one windows machine goes down the broker should communicate with the other configuration machine..We need not have to configure everything again..
--
Thanks |
|
| Back to top |
|
|
| AkankshA |
| Posted: Tue Nov 03, 2009 11:34 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
one broker in v5 can communicate with only one configuration manager
however you can take regular back up of config mgr and recreate the same on another machine in case of mishap......
_________________
Cheers |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Nov 04, 2009 6:25 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Put the configmgr under MSCS control.
But really, whether the configmgr is running or not generally doesn't matter. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Wed Nov 04, 2009 8:32 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| mqjeff wrote: |
Put the configmgr under MSCS control.
But really, whether the configmgr is running or not generally doesn't matter. |
i will complete the sentence 
But really, whether the configmgr is running or not generally doesn't matter as long as you do not need to do new deployments..... We in fact keep our config manager down all the time as a security measure and get it running for deployments only...
_________________
Cheers |
|
| Back to top |
|
|
|
|
