mqsiaddbrokerinstance command

Use the mqsiaddbrokerinstance command to create a multi-instance integration node on a server where IBM® Integration Bus has been installed.

Supported platforms

  • Windows
  • Linux® and UNIX systems

Purpose

Use the mqsiaddbrokerinstance command to add an integration node instance to any additional server on which you require multi-instance support. You must first create a multi-instance enabled integration node on one server by using the mqsicreatebroker command.

If you add an integration node instance with the mqsiaddbrokerinstance command, you cannot use this command to start and stop a multi-instance integration node as a WebSphere® MQ service; you must use the mqsichangebroker command instead.

Select the appropriate link for details of this command on the platform, or platforms, that your enterprise uses:

Authorization

For information about platform-specific authorizations, see the following topics: If you have enabled administration security, you must also set the permissions that are detailed in Tasks and authorizations for administration security.
On all Windows platforms, you must install WebSphere MQ on a domain server, and create a user to own WebSphere MQ resources. The user must either be a member of domain group mqm or a member of another global domain group which is directly or indirectly a member of mqm. Make this user the owner of the shared queue manager and log files. The sid of the user who owns the queue manager and log files is then the same as the sid of the user that runs instances of the queue manager.

On Linux and UNIX systems, the user ID used to run this command must be a member of both the mqbrkrs group and the mqm group. Additionally, you need to make the uid and gid for this user ID the same on all the systems, and the user ID needs to be the same one that created the first instance of the multi-instance integration node, using the mqsicreatebroker command.

You might need to edit the /etc/passwd file on each system to set a common uid and gid for the user ID being used to create and add integration node instances; then reboot your systems.

You should change the uid and gid in the Linux and UNIX environments with caution, as it affects the permission levels of files on the system.

Changing a uid or gid causes the ownership of all the files previously owned by that user or group to change to the actual integer of the previous owner of the file. Therefore, you must ensure that your system administrator manually restores the ownerships of the affected files and directories.