mqsicreateconfigmgr command

Use the mqsicreateconfigmgr command to create a Configuration Manager and its associated resources.

Supported platforms

Purpose

The mqsicreateconfigmgr command:
  1. Checks that the specified WebSphere® MQ queue manager already exists.

    If it does not exist:

    • If you run this command on z/OS, it reports an error and fails.
    • If you run this command on Linux, UNIX, or Windows, this command creates a queue manager.

      If the queue manager is created on Windows by this command, it is not started as a service. The queue manager stops if you log off. Therefore 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 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.

  2. Starts the WebSphere MQ queue manager if it is not already running, except on z/OS.
  3. Connects to the associated queue manager.
  4. Creates the WebSphere MQ queues and channel that are specific to the Configuration Manager, if they do not already exist.
  5. 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.
  6. If you run this command using the -n parameter, and then delete the Configuration Manager by 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.

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

Authorization

On Windows systems, the user ID used to run this command must have Administrator authority on the local system.

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

On z/OS systems, the user ID used to run 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, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:22:37

an23000_