WebSphere MQ v5.3 and Microsoft Windows 2003

2004-04-15 Thread Joshi, A (Anant)
Hi,

The Configuring WebSphere MQ accounts section of
Windows Quick Beginnings states following in case
any domain controller is on Win2K

1 Create a domain group (a global or universal group) 
2 Give members of this group the authority to query the group membership
of any account 
3 Create one or more user accounts, and add them to the group 
4 Use the accounts to configure each installation of WebSphere MQ 
5 Set the password expiry periods 


I have two questions -

Does the group name HAVE TO BE domain mqm ?
(hard-coded ?)

AND

How important is 2 ?
That particular authority is not allowed under our security policy.



Thanks
_

This email (including any attachments to it) is confidential, legally privileged, 
subject to copyright and is sent for the personal attention of the intended recipient 
only. If you have received this email in error, please advise us immediately and 
delete it. You are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly prohibited. 
Although we have taken reasonable precautions to ensure no viruses are present in this 
email, we cannot accept responsibility for any loss or damage arising from the viruses 
in this email or attachments. We exclude any liability for the content of this email, 
or for the consequences of any actions taken on the basis of the information provided 
in this email or its attachments, unless that information is subsequently confirmed in 
writing. If this email contains an offer, that should be considered as an invitation 
to treat.
_

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: WebSphere MQ v5.3 and Microsoft Windows 2003

2004-04-15 Thread Neil Casey
My experience with this leads me to believe the following:

1, The group name does have to be 'domain mqm'. The mq code looks for this
as a special case. The manual says:
a.   Enter the name domain mqm (use this exact string, because it is
understood and used by WebSphere MQ). 

2. The authority to query group membership is required if you want users
who are logged on to the domain to be able to use MQSeries. If all of your
MQ users on that system are local users, then it may not be required. If
the server where MQ is itself a domain controller, then it is required as
there are no local userids on a domain controller.

Note: If all the MQ users are local, and the server is not a domain
controller, then you probably don't need a domain mqm group at all. You
can just use a local security group (mqm) and MUSR_MQADMIN, just like on
Windows NT.

Regards,

Neil Casey
National Australia Bank
Southern Star Technology
WebSphere MQ Support
1/122 Lewis Rd Wantirna South
office. +61 3 9886 2375 (x82375)
mobile. +61 414 615 334



  Joshi, A (Anant)
  [EMAIL PROTECTED]To:   [EMAIL PROTECTED]
  BOBANK.COMcc:
  Sent by: MQSeries  Subject:  WebSphere MQ v5.3 and 
Microsoft Windows 2003
  List
  [EMAIL PROTECTED]
  AC.AT


  16/04/2004 06:09
  Please respond to
  MQSeries List






Hi,

The Configuring WebSphere MQ accounts section of
Windows Quick Beginnings states following in case
any domain controller is on Win2K

1 Create a domain group (a global or universal group)
2 Give members of this group the authority to query the group membership
of any account
3 Create one or more user accounts, and add them to the group
4 Use the accounts to configure each installation of WebSphere MQ
5 Set the password expiry periods


I have two questions -

Does the group name HAVE TO BE domain mqm ?
(hard-coded ?)

AND

How important is 2 ?
That particular authority is not allowed under our security policy.



Thanks
_

This email (including any attachments to it) is confidential, legally
privileged, subject to copyright and is sent for the personal attention of
the intended recipient only. If you have received this email in error,
please advise us immediately and delete it. You are notified that
disclosing, copying, distributing or taking any action in reliance on the
contents of this information is strictly prohibited. Although we have taken
reasonable precautions to ensure no viruses are present in this email, we
cannot accept responsibility for any loss or damage arising from the
viruses in this email or attachments. We exclude any liability for the
content of this email, or for the consequences of any actions taken on the
basis of the information provided in this email or its attachments, unless
that information is subsequently confirmed in writing. If this email
contains an offer, that should be considered as an invitation to treat.
_

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive