mqsicreatebroker command

Use the mqsicreatebroker command to create a broker and its associated resources.

Supported platforms

Purpose

The mqsicreatebroker command:
  1. Checks whether 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.

        The queues that are created include a dead letter queue (DLQ), SYSTEM.DEAD.LETTER.QUEUE. The security settings are the same as those of other broker-specific WebSphere MQ queues.

        If a message received by a message flow cannot be processed, it is typically backed out onto the input queue. If it cannot be backed out, or the message flow is not configured to back out messages, or to perform alternative error processing, the broker puts the message to the DLQ.

        The mqsideletebroker command does not delete the default DLQ (unless the queue manager is deleted).

    • If it does exist, check that the queue manager has a DLQ defined; it is not created by this command on an existing queue manager, The broker puts messages that cannot be processed to the DLQ.

      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 not already running, except on z/OS.

    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.

  3. Connects to the associated queue manager.
  4. Creates the WebSphere MQ queues that are required by the broker, if they do not already exist.
  5. Start of changeCreates database tables for the broker in the relevant schema in the specified database. If the schema, determined by user ID, or the tables, do not exist, they are created. If the tables already exist, the command adds rows specific to this broker to the existing tables.

    If the parameters that you specify on this command result in this broker sharing tables within a database schema with other brokers, you must ensure that all these brokers are at the same version of the product.

    End of change
  6. On Windows only, installs a service under which the broker runs.
  7. 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 both the mqbrkrs group and the mqm group.

On z/OS systems, the user ID used to run this command must be a member of a group that has both READ and WRITE access to the component directory. The user ID must also have access to WebSphere MQ resources, and DB2®.

Using LDAP: Ensure that the registry is appropriately secured to prevent unauthorized access. You do not have to set the LdapPrincipal and LdapCredentials options on mqsicreatebroker for correct operation of the broker. The password is not stored in clear text in the file system.

WebSphere MQ queues created

  • SYSTEM.BROKER.ADMIN.QUEUE
  • SYSTEM.BROKER.AGGR.CONTROL
  • SYSTEM.BROKER.AGGR.REPLY
  • SYSTEM.BROKER.AGGR.REQUEST
  • SYSTEM.BROKER.AGGR.TIMEOUT
  • SYSTEM.BROKER.AGGR.UNKNOWN
  • SYSTEM.BROKER.CONTROL.QUEUE
  • SYSTEM.BROKER.EXECUTIONGROUP.QUEUE
  • SYSTEM.BROKER.EXECUTIONGROUP.REPLY
  • SYSTEM.BROKER.INTERBROKER.MODEL.QUEUE
  • SYSTEM.BROKER.INTERBROKER.QUEUE
  • SYSTEM.BROKER.MODEL.QUEUE
  • SYSTEM.BROKER.TIMEOUT.QUEUE
  • SYSTEM.BROKER.WS.ACK
  • SYSTEM.BROKER.WS.INPUT
  • SYSTEM.BROKER.WS.REPLY

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.

Database tables created

The database tables that this command creates, or adds to, are described in Database contents.

Responses

In some circumstances, you might see the following error message issued by DB2:
    (51002)[IBM][CLI Driver][DB2/NT]SQL0805N
    Package "NULLID.SQLLF000" was not found.  SQLSTATE=51002.

This error occurs when the bind to the database is not successful.

  • On Windows platforms, binding is not needed for broker databases, but is required for user databases. If you create the database using the DB2 Control Center, the bind is completed for you. If you use the command interface, the bind is not completed for you. For example, to create or re-create a bind for the database MYDB enter the following commands at the command prompt:
    db2 connect to MYDB user db2admin using db2admin
    db2 bind X:\sqllib\bnd\@db2cli.lst grant public
    db2 connect reset
    where X: is the drive on which DB2 is installed.
  • On Linux and UNIX platforms, binding is necessary for all databases. For example, to create binding for database WBRKBKDB, you must enter the following commands at the command prompt (where <user_name> is the user ID under which the database instance was created):
    db2 connect to WBRKBKDB user db2admin using db2admin
    db2 bind ~<user_name>/sqllib/bnd/@db2cli.lst grant public CLIPKG 5
    db2 connect reset

If you do not use the default DB2 user ID and password (db2admin), you must replace the values in the db2 connect command with the correct values.

If you run the mqsicreatebroker command and it fails, resolve the problem that caused the failure: When you run the same command again you might receive a series of messages indicating any items that cannot be created. Receiving these messages does not indicate a problem with the mqsicreatebroker command itself.
Related concepts
Broker domains
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:40:43

an07080_