mqsicreateconfigmgr command

Supported platforms

Purpose

This command completed the following actions:
  • Creates a WebSphere MQ queue manager, 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 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 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).

    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 this 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.

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 requirement ensures 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.

Syntax

Windows

Linux and UNIX systems

z/OS

Parameters

configmgrName
(Optional - Windows. Required - Linux, UNIX systems, and z/OS) The name of the Configuration Manager that you want to create.

On Linux, UNIX systems and z/OS, this parameter must be the first specified. It is case-sensitive on Linux, UNIX systems and z/OS.

The default name on Windows, if this parameter is not specified, is 'ConfigMgr'.

-i ServiceUserID
(Required) The user ID under which the service runs.

This parameter can be specified in any valid username syntax for the platform.

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 Event Broker has been installed), and the working directory (if specified by the -w flag).

Start of changeThe security requirements for the ServiceUserID are detailed in Security requirements for Windows platforms for Windows, Security requirements for Linux and UNIX platforms for UNIX platforms, and Security requirements for z/OS for z/OS.End of change

If you use the unqualified form for the service user ID (username), Start of changeon WindowsEnd of change the operating system searches for the user ID throughout its domain, starting with the local system. This search might take some time to complete.

-a ServicePassword
(Required) The password for the ServiceUserID.

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.

-q QueueManagerName
(Required) The name of the queue manager associated with the Configuration Manager.

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 update is done whether or not the queue manager is created by this command.

-n db2DatabaseToMigrate
(Optional) The name of the database that you created at an earlier release to hold the configuration repository tables.

This database must already exist. You do not need to create an ODBC connection for this database, because access is provided by JDBC.

-u migrationDataBaseUserID
(Optional) The user ID with which the configuration repository database (created at an earlier release) is to be accessed.
-p migrationDataBasePassword
(Optional) The password of the user ID with which the configuration repository database (created at an earlier release) is to be accessed. If not specified, this parameter defaults to the ServicePassword specified by -a.

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.

-s UserNameServerQueueManagerName
(Optional) The name of the WebSphere MQ queue manager that is associated with the User Name Server. If this parameter is not specified, the Configuration Manager assumes that there is no User Name Server defined, and does not attempt to communicate with one.
-w Workpath
(Optional) The directory in which working files for the Configuration Manager are stored. If not specified, the default directory specified when the product was installed is used.
1
(Optional - z/OS only) The registry pass that creates only the Configuration Manager registry.
2
(Optional - z/OS only) The WebSphere MQ pass that creates only the Configuration Manager WebSphere MQ queues.
Note: This action can be performed only if the Configuration Manager registry exists.

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.

Start of changeOn UNIX systems, the user ID used to invoke this command must be a member of the mqbrkrs group. End of change

Start of changeOn 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.End of change

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 Event 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 administered by the Configuration Manager.

Responses

This command returns the following responses:
  • BIP8011 Unable to create configuration data
  • BIP8012 Unable to connect to system components
  • BIP8014 Component cannot be created
  • BIP8022 Invalid user ID/password
  • BIP8030 Unable to modify user ID privileges
  • BIP8048 Unable to start queue manager
  • BIP8050 Unable to create queue manager
  • BIP8051 Unable to create queue
  • BIP8053 Unable to set security for queue manager
  • BIP8054 Unable to set security for queue
  • BIP8055 Unable to load Java class
  • BIP8056 Unknown queue manager
  • BIP8074 Unable to create JVM
  • BIP8075 Java exception
  • BIP8076 Unable to set current directory
  • BIP8077 Error initializing configuration data
  • BIP8078 Error initializing configuration data
  • BIP8084 Unable to create directory
  • BIP8087 Component already exists
  • BIP8093 Queue manager being created
  • BIP8094 Queue manager stopping
  • BIP8097 Unable to create Java object

Examples

mqsicreateconfigmgr CMGR01 -i wbrkuid -a wbrkpw -q WBRK_CONFIG_QM
Related concepts
Configuration Manager