| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSI in NT with multiple domains |
« View previous topic :: View next topic » |
| Author |
Message
|
| Miriam Kaestner |
 Posted: Mon Sep 24, 2001 7:08 am Post subject: |
 |
|
Centurion
Joined: 26 Jun 2001
Posts: 103
Location: IBM IT Education Services, Germany
|
Has anybody experience with MQSI in an NT multi-domain environment? I am not an NT domain expert, and am not sure I understand the MQSI manuals correctly.
What I want to achieve is to separate Development domain from Test domain and Production domain(each on a separate NT domain, and also MQSI domain, so 3 Config mgrs.)The 3 NT domains have mutual trust relationship, and all users log on to the Primary domain controller.
If I understand the MQSI Planning Guide correctly, it should be possible to define the mqbrks, mqm, mqdevt etc. groups as
-global group on Primary Controller DOMPRIM (users: MQSIADMIN1),
-local groups in each NT domain (DOMTEST, DOMDEV, DOMPROD) - so in each local mqbr... group, there are other users, as well as the global group. For example, to DOMDEVdomain mqbrks group belong users DEVELOPER1 and DEVELOPER2 (+ MQSIADMIN1 from the global mqbrk group). To DOMPRODdomain mqbrks group belongs only user MQSIBRK1P (+ MQSIADMIN1 from the global mqbrk group).
So when I create the brokers and configuration managers, I specify -d parameter as DOMDEV for development broker, and DOMPROD for the production broker.
So my unser DEVELOPER2 will be able to do any broker action on the test broker, but not on the production broker.
Has anybody a running scenario such as this?
|
|
| Back to top |
|
 |
| camenzind |
| Posted: Wed Jan 09, 2002 1:21 am Post subject: |
|
|
Novice
Joined: 13 Sep 2001
Posts: 10
|
| Unfortunatly MQSI doesn't support nested domains. The control center connection passes only the userid to the configmgr, which adds the domain name from the -d parameter (like a prefix) to check authorizations. It means, that you can't administer all users in one domain and than connect the local groups. You also need exactly these group names in your domains (name and case), i.e. if you have naming conventions for global groups you are on a bad end. |
|
| 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
|
|
|
|
