Use the mqsicreatebroker command to create a broker on a Linux or UNIX systems.
>>-mqsicreatebroker--brokerName-- -q --queueManagerName---------> >--+----------------+--+------+--+------+-----------------------> '- -w --workPath-' '- -t -' '- -m -' >--+-------------------+----------------------------------------> '- -l --userLilPath-' >--+----------------------------------+-------------------------> '- -g --configurationChangeTimeout-' >--+------------------------------------+-----------------------> '- -k --internalConfigurationTimeout-' >--+------------------------+-----------------------------------> '- -P --httpListenerPort-' >--+-------------------------------+----------------------------> '- -v --statisticsMajorInterval-' >--+--------------------------------------------+---------------> '- -y --ldapPrincipal-- -z --ldapCredentials-' >--+------------------------+--+--------------------+-----------> '- -c --icuConverterPath-' '- -x --userExitPath-' >--+---------------------+--+--------------------+--------------> '- -o --operationMode-' '- -s --+-active---+-' '-inactive-' >--+----------------------+--+---------------------+------------> '- -e --sharedWorkPath-' '- -d --+-defined---+-' '-undefined-' >--+-------------------+--+----------------------+--------------> '- -b --cachePolicy-' '- -r --cachePortRange-' >--+-----------------------------------+----------------------->< '- -4 --integrationRegistryHostname-'
For restrictions on the character set that you can use, see Characters allowed in object names.
The default behavior is to create a queue manager using the default mqm path, if the queue manager does not already exist on the same server.
crtmqm –md /<broker sharedWorkPath>/mqm/qmdata
-ld //<broker sharedWorkPath>/mqm/qmlog queueManagerName
If this shared queue manager path is not appropriate, create the multi-instance queue manager on the server before you run this command.
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 object names.
When a broker has been enabled for multi-instance mode using the –e flag, the broker workPath is divided between data that is specific to this broker instance, and that which is shared between this broker and any of its instances created using the mqsiaddbrokerinstance command. Data specific to the multi-instance enabled broker is stored in the workPath directory on the local server, whereas the shared data is held in a directory on network storage at the location specified using the –e flag.
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 ends abnormally are stored in this directory.
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.
Specifying this parameter creates a separate working directory for the broker. This working directory is a subset of the default working directory structure that contains fewer subdirectories and no common\profiles subdirectory.
If you specify this parameter on HP-UX and Solaris, specify the serviceUserId as mqm.
For more details about using WebSphere MQ trusted applications, see the Intercommunication section of the WebSphere MQ Version 7 product documentation online.
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 IBM® Integration Bus installation directory.
If you specify more than one directory, separate directories by using a colon (:).
A message flow cannot respond to a configuration change while it is processing an application message. An integration server 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 - 3600. The default is 300.
For information about how to set the value for this timeout, see Setting configuration timeout values.
The response time of each integration server differs according to system load and the load of its own processes. The value must reflect the longest response time that any integration server 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 - 3600. The default is 60.
For information about how to set the value for this timeout, see Setting configuration timeout values.
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.
If you have purchased a license for the Standard Edition, you are entitled to run your brokers in either standard or scale mode.
If you specify -s active, administration security is enabled. Only user IDs that you authorize are permitted to complete actions on the broker. Read, write, and execute authority is always granted on the security queue SYSTEM.BROKER.AUTH to all user IDs that belong to the security group mqbrkrs. When the broker has been created, you can add further user ID authorizations to this queue.
When you create an integration server on a broker for which administrative security is enabled, the queue SYSTEM.BROKER,AUTH.egroup_name is created. Populate the queue with the appropriate user authorization.
If you specify -s inactive, or omit this parameter, broker administration security is not enabled. All users are able to complete all actions against the broker and all integration servers.
If broker administration security is not enabled, web users can access the web user interface as the default user, with unrestricted access to data and broker resources.
This option is an alternative to starting a multi-instance broker in standby mode using the mqsistart command.
If you specify -d defined, the WebSphere MQ service is defined to the queue manager and the broker starts and stops when the queue manager starts and stops.
If you specify -d undefined, the WebSphere MQ service is not defined to the queue manager and the broker does not start and stop when the queue manager starts and stops. This is the default setting.
mqsicreatebroker IB9NODE
-q IB9QMGR -t
mqsicreatebroker IB9NODE
-q IB9QMGR -x /opt/3rdparty/wmbexits
mqsicreatebroker IB9NODE
-q IB9QMGR -s active
mqsicreatebroker IB9NODE
-q MyQmgr -e MyNetworkSharedWorkpath -d defined
mqsicreatebroker IB9NODE -q IB9QMGR -o scale