mqsicreatebroker command - Linux and UNIX systems

The queue manager specified on the integration node is also required for message flow nodes that use system queues to store state information about messages, such as the CD and FTE nodes, and for event-driven processing nodes that are used for aggregation and timeout flows, message collections, and message sequences. These nodes require a queue manager to be specified on the integration node, and they also require a set of system queues to be created. For information about creating the system queues, see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager. For more information about the IBM Integration Bus features that require system queues, see Installing WebSphere MQ.

You cannot use a secured queue manager as the local default queue manager for an integration node.

If you specify a queue manager that does not exist, you must create it before the flow is deployed.

If the -q parameter is not specified, some features that require access to WebSphere MQ will be unavailable. For more information about using WebSphere MQ with IBM Integration Bus, see Enhanced flexibility in interactions with WebSphere MQ.

  crtmqm -md /<integration node sharedWorkPath>/mqm/qmdata
         -ld //<integration node 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. For more information, see Creating a multi-instance integration node.

For restrictions on the character set that you can use, see Characters allowed in object names.

When an integration node has been enabled for multi-instance mode using the -e flag, the integration node workPath is divided between data that is specific to this integration node instance, and that which is shared between this integration node and any of its instances created using the mqsiaddbrokerinstance command. Data specific to the multi-instance enabled integration node 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 that is specified using the -e flag.

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 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 integration node 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 integration nodes in either standard or scale mode.

Specify the administrative security status for the integration node. If you specify -s active, administration security is enabled. Only user IDs that you authorize are permitted to complete actions on the integration node. Read, write, and execute authority is always granted on the integration node to all user IDs that belong to the security group mqbrkrs. When the integration node has been created, you can add further user ID authorizations.

If you are using queue-based security, the queue SYSTEM.BROKER.AUTH.integration_server_name is created when you create an integration server on an integration node for which administrative security is enabled. Populate the queue with the appropriate user authorization.

If you specify -s inactive, or omit this parameter, integration node administration security is not enabled. All users are able to complete all actions against the integration node and all integration servers.

If integration node administration security is not enabled, web users can access the web user interface as the default user, with unrestricted access to data and integration node resources.

This option is an alternative to starting a multi-instance integration node in standby mode using the mqsistart command.

If you specify -d undefined, the MQ Service is not defined to the queue manager, and the integration node does not start and stop when the queue manager starts and stops. This is the default setting.

For more information about running the integration node as an MQ Service, see Creating a multi-instance integration node.

• If you specify default, the default cache policy is used.
• If you specify disabled, the global cache components in the integration node are disabled. The cache is disabled by default.
• If you specify none, the cache manager in each integration server uses the values that you set. The integration server properties that were set most recently by the broker-level policy are retained as a starting point for customization.
• If you specify the fully qualified name of a policy file, the integration nodes listed in the policy file are configured to share the data in the global cache. The path must be absolute, not relative.

• If you specify a range of ports, the value of this parameter must be in the format xxxx-yyyy, and the range must contain at least 20 ports.
• If you specify generate, the integration node generates a range of ports that are not being used by another integration node on that computer. The integration node chooses a range that starts from 2800. If, for example, another integration node is using ports 2800 to 2819, the integration node generates a range from 2820 to 2839.