The user ID under which components run. You can specify the ServiceUserID in any valid user name syntax. On Windows systems, valid formats are:
On Linux and UNIX systems, only the last format, username, is valid.
If you use the unqualified form for this user ID (username) on Windows systems, the operating system searches for the user ID throughout its domain, starting with the local system. This search might take some time to complete.
The ServiceUserID that you specify must be a member of the mqbrkrs local group. On Windows systems, the ID can be a direct or indirect member of the group. The ServiceUserID must also be authorized to access the home directory (where WebSphere Message Broker has been installed), and the working directory (if specified by the -w parameter).
On Windows systems, if you specify that the broker is to run as a WebSphere MQ trusted application (-t parameter), you must also add the service user ID to the mqm group. On Linux and UNIX systems, specify the ServiceUserID as mqm if you set the -t parameter.
The security requirements for the ServiceUserID are described in Security requirements for Windows platforms, and in Security requirements for Linux and UNIX platforms.
Each broker must have its own unique queue manager. A broker cannot share a queue manager with another broker.
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 this queue manager to be the default queue manager on this system, either create the queue manager before you issue this command, or change the settings of this queue manager to make it the default after it has been created. Use either the WebSphere MQ Explorer, or the WebSphere MQ Services snap-in, depending on which version of WebSphere MQ you are using.
The queue manager attribute MAXMSGLN (the maximum length of messages that can be put to queues) is updated to 100 MB. This attribute is updated regardless of whether the queue manager is created by this command.
For restrictions on the character set that you can use, see Characters allowed in commands.
This database must already exist. You must create a System DSN ODBC connection for this DSN, if you have not already done so.
If
you have a DB2 database on Linux,
enter the appropriate DB database alias name; an ODBC DSN is not required.
This user ID must have authority to create tables within this database, and read from and write to those tables.
On Windows systems, if your broker database exists in DB2, and this user ID is not known to DB2, it is created for you within DB2.
On Linux and UNIX systems, the service user must have been granted the correct privilege before entering this command. If your database is SQL Server, you must create this user ID as a SQL Server login ID and give it the correct access before you create the broker.
If you have an application database in DB2 that was created by this user ID, or to which this user ID has appropriate read, write, or create authority, message flows that run in this broker can access and manipulate the application data that is held within it, without having to specify explicit schema names (see Security requirements for Linux and UNIX platforms and Security requirements for Windows platforms for further details).
For compatibility with existing systems, you can 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.
For DB2 on Linux and UNIX systems, you can specify -u and -p as empty strings (two quotation marks "") . In this case, DB2 grants WebSphere Message Broker the privileges of the ServiceUserID, which results in a database connection as "already verified". If you specify -a as an empty string as well as -u and -p, WebSphere Message Broker stores no passwords, creating the most secure configuration.
This directory is also used for trace records that are created when tracing is active. These records are written to a subdirectory, log, which you must create before you start the broker.
Error logs that are written by the broker when a process terminates abnormally are stored in this directory. On Windows systems, use this parameter to specify a directory on a drive other than the one on which the product is installed.
The error log is unbounded and continues to grow. Check this directory periodically and clear out old error information.
You cannot change this parameter using the mqsichangebroker command. To specify or change the work path, delete and re-create the broker.
If you specify this parameter on Windows systems, add the ServiceUserID (identified by -i parameter) to the mqm group.
If you specify this parameter on HP-UX and Solaris, specify the ServiceUserID as mqm.
A message flow cannot respond to a configuration change while it is processing an application message. An execution group that has been requested to change its configuration returns a negative response to the deployed configuration message if any one of its message flows does not finish processing an application message and apply the configuration change within this timeout.
The value that you set for this timeout depends on the system load (including CPU utilization), and on each execution group's load. You can make an initial estimate by deploying the broker's entire configuration. The time taken for this to complete successfully gives an indication of the minimum value to set.
Specify the value in seconds, in the range 10 to 3600. The default is 300.
The sum of the ConfigurationTimeout and the ConfigurationDelayTimeout represents the maximum length of time that a broker can take to process a deployed configuration message before it generates a negative response.
This parameter represents the time that it takes for a broker and its execution groups to process a minimal deployed configuration message; it depends on queue manager network delays, the load on the broker's queue manager, and system load.
The broker starts this listener when a message flow that includes Web Services support is started; the default is 7080.
Ensure that the port that you specify has not been specified for any other purpose.
mqsicreatebroker WBRK_BROKER -i wbrkuid -a wbrkpw -q WBRK_QM -s WBRK_UNS_QM -n WBRKBKDB
mqsicreatebroker WBRK_BROKER -i wbrkuid -a wbrkpw -q WBRK_QM -n WBRKBKDB -t
mqsicreatebroker WBRK_BROKER -i wbrkuid -a wbrkpw -q WBRK_QM -n WBRKBKDB -x /opt/3rdparty/wmbexits
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an28130_ |