Chapter 3. Mediation with WebSphere Message Broker 25
3.2.1 Broker
The broker is a set of application processes that host and run message flows.
When a message arrives at the broker from a business application, the broker
processes the message before passing it on to one or more other business
applications. The broker routes, transforms, and manipulates messages
according to the logic that is defined in their message flow applications. Each
broker uses a database to store the message flows, configuration data, and the
message sets deployed to it.
3.2.2 Execution groups
Execution groups are processes that host message flow threads. The execution
groups facilitate the grouping of message flows within the broker with respect to
functionality, load balancing, or other qualifications that are determined to be
necessary. Each broker contains a main execution group. Additional execution
groups can be created as long as they are given unique names within the broker.
Each execution group is a separate operating system process. Therefore, the
contents of an execution group remain separate from the contents of other
execution groups within the same broker. This separation can be useful for
isolating pieces of information for security, because the message flows execute in
separate address spaces or as unique processes.
Message flow applications are deployed to a specific execution group. To
enhance performance, you can deploy additional message flow instances to an
execution group. Each additional instance allocates an additional thread to host
the message flow application. Therefore, more threads will be available in the
execution group to process the incoming message at run time.
3.2.3 Configuration Manager
The Configuration Manager is the interface between the Message Brokers
Toolkit and the brokers in the broker domain. The Configuration Manager stores
configuration details for the broker domain in an internal repository, providing a
central store for resources in the broker domain.
The Configuration Manager is responsible for deploying message flow
applications to the brokers. The Configuration Manager also reports on the
progress of the deployment and on the status of the broker. When the Message
Brokers Toolkit connects to the Configuration Manager, the status of the brokers
in the domain is derived from the configuration information stored in the internal
repository of the Configuration Manager.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.