- BrokerName
- (Required) The name of the broker that you are creating.
This parameter must be the first parameter, and if you create a broker
with an uppercase name, the name must be specified in uppercase in
the workbench.
For restrictions on the character set that you can
use, see Characters allowed in commands.
- -q QueueManagerName
- (Required) The name of the queue manager that is associated
with this broker. Use the same name for your broker and the queue
manager to simplify the organization and administration of your network.
Queue manager names are limited to 48 characters in length, and they
are case sensitive.
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 MAXMSGLEN (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.
- -n DB2Location
- (Required) The location of the database in which the broker tables
are created.
- -u DB2TableOwner
- (Required) The user ID with which databases that contain broker
tables and user data are to be accessed.
This user ID must have
authority to create tables within this database, and read from and
write to those tables.
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.
- -s UserNameServerQueueManagerName
- (Optional) The name of the WebSphere MQ queue manager that is associated
with the User Name Server.
Specify this parameter if you require either authentication
services or publish/subscribe access control.
If you do not specify this parameter, the broker assumes that no User Name Server is defined. To enable publish/subscribe access control, specify the -s and -j parameters.
- -j
- (Optional) If you require publish/subscribe access control, specify this
parameter. You must also specify the -s parameter.
- -l UserLilPath
- (Optional) A list of paths (directories) from which
the broker loads 32-bit loadable implementation libraries (LILs) for
user-defined message processing nodes. Use the -l flag
for 32–bit LILs.
This name is case sensitive; enclose the names in
single quotation marks if they are in mixed case.
Do not include
environment variables in this path; WebSphere Message
Broker ignores
them.
- You must create your own directory for storing your .lil or .jar files.
Do not save these files in the WebSphere Message
Broker install
directory.
- -P HTTPListenerPort
- (Optional) Enter the number of the port on which the
Web services support is listening.
The broker starts
this listener when a message flow that includes HTTP nodes or Web
services support is started; the default is 7080. 
Ensure that
the port that you specify has not been specified for any other purpose.
- -g ConfigurationChangeTimeout
(Optional) The maximum time (in seconds) that
is allowed for a user configuration request to be processed. It defines
the length of time taken within the broker to apply to an execution
group a configuration change that you have initiated. For example,
if you deploy a configuration from the workbench, the broker must respond to
the Configuration
Manager within this time.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.
Specify the value in seconds, in
the range 10 to 3600. The default is 300.
For information about
how to set the value for this timeout, see Setting configuration timeouts.

- -k InternalConfigurationTimeout
(Optional) The maximum time (in seconds)
that is allowed for an internal configuration change to be processed.
For example, it defines the length of time taken within the broker
to start an execution group.
The response time of each execution group differs
according to system load and the load of its own processes. The value
must reflect the longest response time that any execution group takes
to respond. If the value is too low, the broker returns a negative
response, and might issue error messages to the local error log.
Specify
the value in seconds, in the range 10 to 3600. The default is 60.
For
information about how to set the value for this timeout, see Setting configuration timeouts.
- -v StatisticsMajorInterval
- (Optional) Specify the interval (in minutes) at which WebSphere Message
Broker statistics and accounting is
notified that archive records are to be output. The valid range is
from 10 to 14400 minutes.
An interval of zero minutes indicates that the operating
system has an external method of notification and is not using an
internal timer within WebSphere Message
Broker.
- -1
- (Optional) The registry pass, which creates only the broker registry.
- -2
- (Optional) The WebSphere MQ pass,
which creates only the broker WebSphere MQ queues.
- -3
- (Optional) The DB2 pass,
which creates only the broker DB2 tables
and indexes.
- -y LdapPrincipal
- (Optional, but mandatory when ldapCredentials is
provided.) The user principal for access to an optional LDAP directory
that holds the JNDI administered Initial Context for the JMS provider.
- -z LdapCredentials
- (Optional, but mandatory when ldapPrincipal is
provided.) The user password for access to LDAP.
- -c ICUConverterPath
- (Optional) A delimited set of directories to search
for additional code page converters.
The code page converters must be either of the form icudt32_codepagename.cnv,
or in an ICU data package called icudt32.dat.
- Do not use this parameter to set
the converter path if you are using a converter that matches one of
the built-in converters that are provided with Version 6.0, and that converter is the local
code page for the broker. Use the ICU_DATA environment
variable instead.
- -x UserExitPath
- (Optional) The path that contains the location of all
user exits to be loaded for 32-bit execution groups in this broker.
This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH)
for the execution group process only.