WebSphere Message Brokers
File: an23000_
Writer: Bill Oppenheimer

Reference topic

This build: July 31, 2007 21:33:50

mqsicreateconfigmgr command

Supported platforms

Purpose

This command completes the following actions:
  • Creates a WebSphere MQ queue manager, except on z/OS, if one does not already exist.
    Notes:
    1. If a WebSphere MQ queue manager is created as a result of using the mqsicreateconfigmgr command, the default dead letter queue (DLQ) provided by WebSphere MQ (SYSTEM.DEAD.LETTER.QUEUE) is automatically enabled. The security settings are the same as those of other broker-specific WebSphere MQ queues.

      If you choose to create the queue manager separately, set up a dead-letter queue (DLQ); the DLQ is referenced by WebSphere Message 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).

    2. If you are using a WebSphere MQ queue manager that has been created independently of the mqsicreateconfigmgr command, you can define clusters if you choose. This option simplifies your configuration.
  • Starts the WebSphere MQ queue manager, if it is not already running.
  • Creates the WebSphere MQ queues and channel that are specific to the Configuration Manager, if they do not already exist.
  • Creates database tables for the Configuration Manager in its internal repository. If you need to transfer data from the configuration repository of an earlier release, you can use the db2DatabaseToMigrate, migrationDatabaseUserId, and migrationDatabasePassword parameters.
  • If you run this command using the -n parameter and then delete the Configuration Manager using mqsideleteconfigmgr, without specifying the -n parameter on that command, the new database containing the configuration repository is not deleted.

    If you run the mqsicreateconfigmgr command again in this situation, and specify the -n parameter, the parameter is ignored because the new database still exists.

  • (Windows only) - installs a Windows service, under which the Configuration Manager runs.
  • Creates a record for the component in the broker registry.
Select the appropriate link for details of this command on the platform, or platforms, that your enterprise uses:

Authorization

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.

On UNIX systems, the user ID used to invoke this command must be a member of the mqbrkrs group.

On z/OS systems, the user ID used to invoke this command must be a member of a group that has READ and WRITE access to the component directory and access to WebSphere MQ.

WebSphere MQ queues created

  • SYSTEM.BROKER.CONFIG.QUEUE
  • SYSTEM.BROKER.CONFIG.REPLY
  • SYSTEM.BROKER.ADMIN.REPLY
  • SYSTEM.BROKER.SECURITY.REPLY
  • SYSTEM.BROKER.MODEL.QUEUE

Access authority is granted for the WebSphere Message Broker group mqbrkrs to all these queues. If the DLQ is enabled, it also has the same authority.

WebSphere MQ channels created

  • SYSTEM.BKR.CONFIG

Database tables created

The database tables that this command creates are in a repository created by the Configuration Manager.
Related concepts
Configuration Manager
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:33:50

an23000_ This topic's URL is: