If you choose to create the queue manager separately, set up a dead letter queue (DLQ). The DLQ is referenced by WebSphere Event Broker when errors occur processing messages in message flows.
If a message in either a user-defined message flow or in the publish/subscribe model cannot be processed, it is routed to this DLQ as a last resort. If you would prefer the message to be backed out onto the input queue, effectively halting the message flow until the problem is resolved, disable the DLQ.
The mqsideleteusernameserver command does not delete this queue (unless the queue manager is deleted).
If you are using a WebSphere MQ queue manager that has been created independently of the mqsicreateusernameserver command, you can define clusters. This simplifies your configuration.
If the queue manager is created by this command, it is not started as a Windows service; it stops if you log off. To avoid this happening, either remain logged on, or change the start up status of the queue manager service. (If you lock your workstation, the WebSphere MQ queue manager does not stop.)
If you use the unqualified form for this user ID (username) on Windows platforms, the operating system searches for the user ID throughout its domain, starting with the local system. This search might take some time to complete.
The ServiceUserID specified must be a member of the local group mqbrkrs. On Windows platforms, it can be a direct or indirect member of the group. The ServiceUserID must also be authorized to access the home directory (where WebSphere Event Broker has been installed).
The security requirements for the ServiceUserID are detailed in Security requirements for Windows platforms for Windows platforms and in Security requirements for Linux and UNIX platforms for Linux and UNIX systems.
For compatibility with existing systems, you can still specify <password>. However, if you do not specify a password with this parameter when you run the command you are prompted to enter a password during its invocation, and to enter the password a second time to verify that you have entered it correctly.
On Windows platforms, Linux, and UNIX systems, if the queue manager does not already exist, it is created by this command. It is not created as the default queue manager: if you want it to be the default queue manager on this system, you must create the queue manager before you issue this command.
The queue manager attribute MAXMSGL (maximum length of messages that can be put to queues) is updated to 100 MB. This is done whether or not the queue manager is created by this command.
Two samples, password.dat and pwgroup.dat, are provided in the examples/auth directory under the product home directory.
Access authority is granted for the WebSphere Event Broker group mqbrkrs to all these queues.
mqsicreateusernameserver -i wbrkuid -a wbrkpw -q WBRK_QM -r 1000
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an07200_ |