An execution group is a named grouping of message flows that have been assigned to a broker. The broker enforces a degree of isolation between message flows in distinct execution groups by ensuring that they execute in separate address spaces, or as unique processes.
Each execution group is started as a separate operating system process, providing an isolated runtime environment for a set of deployed message flows. A single default execution group is set up ready for use when you create a reference to a broker in the workbench. By setting up additional execution groups, 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.
Within an execution group, 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.
If you create additional execution groups, you must give each group a name that is unique within the broker, and assign and deploy one or more message flows to each one.
An execution group 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 execution group. If more
than one message flow runs within an execution group, multiple threads are
created within the DFE process.
You can create and deploy execution groups either in the workbench,
or using commands. When you create an execution group, you specify if you
want the process to run in 32-bit or 64-bit mode. When you deploy a 64-bit
execution group to a broker, the broker determines if a 64-bit process is
supported; if not, the deploy fails with error message BIP2825.
When you create a 64-bit execution group, it can support the processing
of very large messages. This option also supports WebSphere Event Broker applications
running in trusted (fastpath) mode if you have installed WebSphere
MQ Version
6.0, which provides 64-bit queue managers.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ae00270_ |