Creating an integration node
You can create integration nodes on every software platform that is supported by IBM® App Connect Enterprise.
Before you begin
- Ensure that your user ID has the correct authorizations to perform the task. Refer to Security requirements for administrative tasks.
- On distributed systems, you must set up your command line environment before you create an integration node by running the product profile or console; refer to Setting up a command environment.
About this task
Create an integration node by using the command line on the computer on which you installed IBM App Connect Enterprise.
You must give the integration node a name that is unique on the local computer. Integration node names are case-sensitive on all supported platforms except Windows.
Optionally, on all distributed systems you can specify a queue manager to be associated with the integration node. This queue manager is used by default for IBM MQ processing in the message flow if no queue manager has been specified explicitly on the MQ node. Some message flow nodes such as CD and FTE nodes, and event-driven processing nodes used for aggregation, timeout, message collections, and message sequences, require a queue manager to be specified for the integration node. These nodes use system queues, which are owned by the queue manager, to store information about in-flight messages. For information about creating the system 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, provided that 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. For more information about using IBM MQ with IBM App Connect Enterprise, see Installing IBM MQ and Interaction between IBM App Connect Enterprise and IBM MQ.
Multiple integration nodes can specify the same queue manager, but deploy issues can occur if an attempt is made to reuse a unique endpoint suffix when two different integration nodes share a queue manager and use the integration node listener. You can also specify a queue manager to be used by an existing integration node, by modifying the node.conf.yaml configuration file for the integration node. You must then restart the integration node for the changes to take effect.
The mode in which IBM App Connect Enterprise is running can affect the number of integration servers and message flows that you can deploy. For more information, see Operation modes.
To create an integration node, complete the steps in Creating an integration node by using the command line.
If you want to configure the integration node as an IBM MQ trusted application, see Using IBM MQ trusted applications.