mqsicreateconfigmgr command

Supported platforms

  • Windows 2000, Windows XP

Purpose

This command:
  • Creates a WebSphere MQ queue manager, if one does not already exist.
    Note:
    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 Business Integration 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 simplifies your configuration.
  • Starts the WebSphere MQ queue manager, if this is not already running. Note that the Configuration Manager always runs as a WebSphere MQ trusted application.
  • Creates the Configuration Manager-specific WebSphere MQ queues and channel, if they do not already exist.
  • Creates database tables for the Configuration Manager in the configuration repository, if they do not already exist.
  • 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 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.

Syntax

Parameters

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

This can be specified in any valid Windows username syntax:

  • domain\username
  • \\server\username
  • .\username
  • username

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

-a ServicePassword
(Required) The password for the ServiceUserID.
-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 is done whether or not the queue manager is created by this command.

-n DataBaseName
(Required) The name of the database that you created to hold the configuration repository tables. This database is the configuration repository for the whole broker domain, and contains configuration information for all resources, as well as data internal to the Configuration Manager.

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

-u DataBaseUserID
(Optional) The user ID with which the configuration repository database is to be accessed. If this is not specified, the value set in ServiceUserID is used.

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.

-p DataBasePassword
(Optional) The password of the user ID with which the configuration repository database is to be accessed. If not specified, this defaults to the ServicePassword specified by -a.
-d SecurityDomainName
(Optional) This parameter must be set to null. When you create the configuration manager, omit this parameter.

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.

-s UserNameServerQueueManagerName
(Optional) The name of the WebSphere MQ queue manager that is associated with the User Name Server. If this 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.
-l 2, 0, or 1
(Optional) This parameter must be set to 2. When you create the configuration manager, omit this parameter. Refer to Considering security for the workbench for more information on this option.

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.

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 Business Integration Message 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 Message Broker groups mqbrdevt, mqbrasgn, mqbrops, and mqbrtpic to the queues SYSTEM.BROKER.CONFIG.QUEUE and SYSTEM.BROKER.CONFIG.REPLY.

Websphere MQ channels created

  • SYSTEM.BKR.CONFIG

Database tables created

The database tables that this command creates are described in Database contents.

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 -i wbrkuid -a wbrkpw -q WBRK_CONFIG_QM
-n WBRKCMDB 
Related concepts
Configuration Manager