Use the mqsicreatebroker command to create an integration node.
- On distributed systems, if the optional -q parameter is
specified, the named local queue manager is associated with the integration node. This queue manager
is used by default for MQ processing in the message flow if no queue manager has been specified
explicitly on the MQ node.The queue manager that is specified on the integration node is also required for message flow nodes that use system queues to store state information about the messages, such as the event-driven processing nodes that are used for aggregation and timeout flows, message collections, and message sequences. The following IBM App Connect Enterprise features require a queue manager to be specified for the integration node, and they also require a set of system queues to be created:
- Event-driven processing nodes
- Publish/subscribe (if you are using IBM MQ rather than MQTT)
- An integration node listener
- SAP nodes (for high availability)
- Record and replay
- Accounting and statistics using the web user interface (if you are using IBM MQ rather than MQTT)
- FTEInput and FTEOutput nodes
- CDInput and CDOutput nodes
For information on creating the required queues, see Creating the default system queues on an IBM 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 system queues on an IBM 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 IBM MQ will be unavailable. For more information about using IBM MQ with IBM App Connect Enterprise, see Enhanced flexibility in interactions with IBM MQ and Installing IBM MQ.
- On Windows only, the command installs a service under which the integration node runs.
- The command creates the integration node in one of the available operation modes. If the full package is installed, the default mode is advanced. If the Developer Edition is installed, the default mode is developer. For more information, see Operation modes.
- The command creates a record for the component in the registry.
- On Windows, Linux, and AIX systems, the command allows you to specify whether the integration node can be started and stopped as an IBM MQ service.
- When you create an integration node, the default port that is used for the first integration node is 4414. You can disable the web user interface or change the port on which it runs by using the mqsichangeproperties command. If administration security is not enabled, web users can access the web user interface as a default user with unrestricted access to data and integration node resources.
- If the --node-conf-yaml parameter is set, the command copies a node.conf.yaml configuration file for the integration node to the workdir/components/integrationNodeName directory. If the --node-conf-yaml parameter is not specified, the default node.conf.yaml file is copied.
- If either the --vault-key or --vaultrc-location parameter is specified on the command, an App Connect Enterprise vault is created to hold the credentials used by the integration node when accessing secured resources.
- Check responses; see Responses to commands.
- Check the error logs; see Local error logs.
- Check the error messages in the error log; you can search for more information about error messages in the product documentation.