Integration servers
An integration server is a named grouping of message flows that have been assigned to an integration node. The integration node enforces a degree of isolation between message flows in distinct integration servers by ensuring that they run in separate address spaces, or as unique processes.
Each integration server is started as a separate operating system process, providing an isolated runtime environment for a set of deployed message flows. Within an integration server, the assigned message flows run in different thread pools. You can specify the size of the thread pool (that is, the number of threads) that are assigned for each message flow by specifying the number of additional instances of each message flow.
The mode that your integration node is working in can affect the number of integration servers that you can use; see Restrictions that apply in each operation mode.
A single default integration server is set up ready for use when you create a reference to an integration node in the IBM® Integration Toolkit. By setting up additional integration servers, you can isolate message flows that handle sensitive data such as payroll records, or security information, or unannounced product information, from other non-sensitive message flows.
If you create additional integration servers, you must give each group a name that is unique within the integration node, and assign and deploy one or more message flows to each one.
You can create and deploy integration servers either in the IBM Integration Toolkit, or using commands.
An integration server process is also known as a DataFlowEngine (DFE); this term is typically used in problem determination scenarios (trace contents, diagnostic messages, and so on). A DFE is created as an operating system process, and has a one-to-one relationship with the named integration server. If more than one message flow runs within an integration server, multiple threads are created within the DFE process.