- BrokerName
- (Required) This parameter must be the first parameter. Specify
the name of the broker to modify.
- -a servicePassword
- (Optional) The password for the serviceUserId.
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.
On Linux® and UNIX® systems, -a is
required for compatibility with Windows® systems,
but is not used in relation to serviceUserId. -a is
used as a default only if -p is not specified.
See the -p parameter description for further
details.
If you have created your broker to use the
serviceUserId and
servicePassword for
database access, ensure that you update both instances of the password
on this command by specifying the
-p dataSourcePassword parameter.
Specify the
-p dataSourcePassword parameter
in the following circumstances:
- You omitted the -u dataSourceUserId and -p dataSourcePassword parameters.
- You included the -u dataSourceUserId and -p dataSourcePassword parameters,
but provided the same user ID and password for the service user ID
using -a servicePassword and -i serviceUserId.
To complete a password change successfully:
- Stop the broker.
- Change the password using the appropriate operating system function.
- Use the mqsichangebroker command
to update all parameters that reference this same password.
- Restart the broker.
- -i serviceUserId
- (Optional) The user ID under which the broker runs. You must also
change the password (-a) if you change this value.
-
The user ID under which components run. You can
specify the serviceUserId in any valid user name
syntax.
On Windows systems,
valid formats are:

- \\server\username
- .\username
- username
On Linux and UNIX systems, only the last format, username,
is valid.
Do not use a domain name as part of the serviceUserId parameter.
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® Event
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.
- -p dataSourcePassword
- (Optional) The password of the user ID with which the databases
that contain broker tables and user data are to be accessed.
For
compatibility with existing systems, you can still 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 -p as
an empty string (two double quotation marks, ""). In this case, DB2 grants WebSphere Event
Broker the privileges of the serviceUserId,
which results in a database connection as "already verified". If you
specify an empty string for -a and -p,
no passwords are stored by WebSphere Event
Broker,
creating the most secure configuration.
Ensure that you change
all instances of the use of this password. If you have created (or
changed) the broker to use the same user ID and password for its service
user ID, as well as its database access, update both instances at
the same time. (See the description of the -a parameter
for further details.)
- -s unsQMgrName
- (Optional) The name of the WebSphere MQ queue manager that is associated
with the User Name Server.
To remove topic-based security, specify an empty
string (two quotation marks, "").
- -j
- (Optional) Publish/subscribe access
is enabled for the broker. This parameter is valid only with the -s parameter.
- -d
- (Optional) Publish/subscribe access
is not enabled for the broker.
- -t
- (Optional) The broker runs as a WebSphere MQ trusted application.
For more details about using WebSphere MQ trusted applications, see WebSphere MQ Intercommunication.
- -n
- (Optional) The broker ceases to run as a WebSphere MQ trusted application.
- -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.
On Linux and UNIX systems, directory names are
case sensitive, and you must include the names in single quotation
marks if they contain mixed case characters.
Do not include
environment variables in the path; the broker ignores them.
-
Create your own directory for storing your .lil or .jar files.
Do not save them in the WebSphere Event
Broker installation
directory.
If you specify more than one additional directory,
each directory must be separated by the default platform-specific
path separator.
- -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.
- -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.
- -v statisticsMajorInterval
- (Optional) The time interval (in minutes) at which WebSphere Event
Broker statistics and accounting is
told to output archive records. For internal accounting, 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 Event
Broker.
- -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 ICU converter path
- (Optional) A delimited set of directories to search
for additional code page converters. On Windows systems, the delimiter is
a semicolon (;). On UNIX and Linux systems, the delimiter is
a colon (:).
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.
To change other broker properties,
first delete and re-create the broker, and then use the workbench to redeploy the broker's configuration.
To change the user ID that is used for database access, see Administering the broker domain.