Use the mqsicreatebroker command to create a broker and its associated resources.
If WebSphere MQ Version 7.1, or later, has been selected for the queue manager, the channel auth security is automatically disabled.
The queues that are created include a dead letter queue (DLQ), SYSTEM.DEAD.LETTER.QUEUE. The security settings are the same as for other broker-specific WebSphere MQ queues.
If a message received by a message flow cannot be processed, it is typically backed out onto the input queue. If it cannot be backed out, or the message flow is not configured to back out messages, or to complete alternative error processing, the broker puts the message to the DLQ.
The mqsideletebroker command does not delete the default DLQ (unless the queue manager is deleted).
If you use WebSphere MQ clusters in your domain, define the queue manager before you run this command, and configure the queue manager in the cluster to benefit from reduced administration and increased availability.
If the command creates the queue manager on Windows, the queue manager is not started as a service. If you log off, the queue manager stops. Therefore, you must either remain logged on, or change the startup status of the queue manager service. If you lock your workstation, the WebSphere MQ queue manager does not stop.
If you enable administrative security, the queues required for this support are also created by this command.
Brokers can access only local queue managers, so you cannot create a broker on a queue manager that is on a remote system.
If you have migrated from Version 6.1, the following restrictions apply.
In previous versions of IBM® Integration Bus, parameters that you specified on this command were used by the broker to provide default authorization for database access: either the database user ID and password (if specified) or the service user ID and password. Because the Version 9.0 broker does not use a database for its own purposes, the database user ID and password parameters have been deprecated. The broker service ID and password parameters have also been deprecated, except on Windows.
If you migrate a broker from a previous release, the associated values are stored and used for default database access as though you had entered these values by using the mqsisetdbparms command.
When you create a Version 9.0 broker, you must use the mqsisetdbparms command to set up database access authorization.
When you create a multi-instance broker, the resources are stored on a shared file system. The user that issues the mqsicreatebroker command must have the correct permissions on the shared file system to create these resources.
For details of this command on the operating system that your enterprise uses, see the appropriate topic.
Access authority is granted for the IBM Integration Bus group mqbrkrs to all these queues. If the DLQ is enabled, it also has the same authority.