- When WebSphere MQ is running, it must check that only authorized
users can access queue managers or queues. Whenever any user attempts such
access, WebSphere MQ uses its own local account to query information about
the user.
- Domain controllers that are running Windows 2000
Server, Windows 2003 Server, or later, are, by default, set up in such a way
that WebSphere MQ cannot use local accounts to check that users defined on
those domains are authorized to access queue managers or queues. In this case,
you must provide WebSphere MQ with a special domain user account to use. If
you are unsure whether this case applies to you, you should consult your domain
administrator.
- If a special domain user account is required, send the Configuring Windows Accounts page to your
domain administrator, and ask for one of the special accounts it describes.
- Enter the account details into the Prepare WebSphere MQ Wizard.
This wizard runs automatically at the end of installation; the wizard can
also be run at any time from the Start menu.
If the special user account is required but you carry on anyway and
configure WebSphere MQ without it, many or all parts of WebSphere MQ will
not work, depending upon the particular user accounts involved. In particular,
if you are currently logged on with a domain user account, you might not be
able to complete the Default Configuration, and the Postcard and API Exerciser
might not work.