Use the mqsicreatebroker command to create an integration node.
For information on creating the required queues, see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager
Queues that are specified on event-driven processing nodes are created automatically when the flow is deployed, if the integration node has the required permissions to create the queues. If the queues are not created automatically, you can create them manually; see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager.
If the specified queue manager 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 and Installing WebSphere MQ.
On
z/OS, the specified queue
manager must exist locally, and the required queues are created
automatically. If the named queue manager does not exist, the
mqsicreatebroker command
fails, and an error is issued.
In IBM Integration Bus Version 10.0, the -4 integrationRegistryHostName parameter is deprecated. The ability to share an Integration Registry across a multi-instance integration node environment is now available without the need to designate an Integration Registry host name.
For details of this command on the operating system that your enterprise uses, see the appropriate topic.