WebSphere Message Brokers
File: an07080_
Writer: Bill Oppenheimer

Reference topic

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

mqsicreatebroker command

Supported platforms

Purpose

The mqsicreatebroker command:
  • Windows platform Linux platform UNIX platform Creates a WebSphere MQ queue manager, except on z/OS, if one does not already exist.
    1. If a WebSphere MQ queue manager is created as a result of using the mqsicreatebroker 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 want to create the queue manager separately, you must set up a 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 want to back out the message onto the input queue, effectively halting the message flow until the problem is resolved, disable the DLQ.

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

    2. If you use a WebSphere MQ queue manager that has been created independently of the mqsicreatebroker command, you might want to define clusters, which simplifies your configuration in most cases.

  • Windows platform Linux platform UNIX platform Starts the WebSphere MQ queue manager, except on z/OS, if the WebSphere MQ queue manager is not already running.

    If the queue manager is created by using this command, it is not started as a Windows service; therefore the queue manager will stop if you log off. You must, 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.

  • Creates the broker-specific WebSphere MQ queues, if they do not already exist.
  • Creates database tables for the broker, if they do not already exist, or adds rows specific to this broker to existing database tables.
  • Windows platform Installs a service under which the broker runs (on Windows platforms only).
  • 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

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

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

z/OS platform On z/OS systems, the user ID used to start 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. The setting of LdapPrincipal and LdapCredentials options on mqsicreatebroker is not required 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.CONTROL.QUEUE
  • SYSTEM.BROKER.EXECUTIONGROUP.QUEUE
  • SYSTEM.BROKER.EXECUTIONGROUP.REPLY
  • SYSTEM.BROKER.INTERBROKER.QUEUE
  • SYSTEM.BROKER.INTERBROKER.MODEL.QUEUE
  • SYSTEM.BROKER.MODEL.QUEUE
  • SYSTEM.BROKER.WS.INPUT
  • SYSTEM.BROKER.WS.REPLY
  • SYSTEM.BROKER.WS.ACK

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.

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.

  • Windows platform 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 recreate 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.
  • Linux platform UNIX platform 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
User exits
Logs
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:25

an07080_ This topic's URL is: