If you choose to create the queue manager separately, set up a dead letter queue (DLQ). The DLQ is referenced by WebSphere Business Integration 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 mqsideleteconfigmgr command does not delete this queue (unless the queue manager is deleted).
If you have installed VisualAge for Java, and selected the WebSphere MQ Connector as part of that installation, ensure that the CLASSPATH entry for VisualAge for Java appears after the CLASSPATH entries for WebSphere MQ for the Windows platform that you are using (server or Java client). This is to ensure that the Configuration Manager accesses the correct WebSphere MQ classes (not the VisualAge classes) when it is started by the mqsistart command. If the Configuration Manager detects an error in this area, it writes message BIP1004 to the Windows System Event log.
This can be specified in any valid Windows username syntax:
The ServiceUserID specified must be a member (either direct or indirect) of the local group mqbrkrs, and must be authorized to access the home directory (where WebSphere Business Integration Event Broker has been installed), and the working directory (if specified by the -w flag). This user ID must also be a member (either direct or indirect) of the local group mqm or of the local Windows Administrators group.
The security requirements for the ServiceUserID are detailed in Security requirements for Windows platforms.
If you use the unqualified form for this user ID (username), the operating system searches for the user ID throughout its domain, starting with the local system. This search might take some time to complete.
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, 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.
This database must already exist. You do not need to create an ODBC connection for this database, because access is provided by JDBC.
This user ID must have the authority to create tables in the database identified by the DataBaseName, and to read from and write to that database.
The -u and -g options on the mqsicreateaclgroup command refer to users and groups within the domain that the Configuration Manager uses for its security. This domain is by default the machine on which the Configuration Manager resides, but is different if you use this option.
This command changes security privileges for the ServiceUserID; the user ID used to invoke this command must be a member of the Windows Administrators group on this local system.
Access authority is granted for the WebSphere Business Integration Event Broker group mqbrkrs to all these queues. If the DLQ is enabled, it also has the same authority.
Access authority is granted for the WebSphere Business Integration Event Broker groups mqbrdevt, mqbrasgn, mqbrops, and mqbrtpic to the queues SYSTEM.BROKER.CONFIG.QUEUE and SYSTEM.BROKER.CONFIG.REPLY.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an07150_ |