This glossary lists differences
in terminology between WebSphere® Event Broker Version 6.0 and
previous versions of the product.
A- assigned message flow
- In Version 2.1, a message flow that
is assigned to an execution group. In Version 6.0,
when you add a message flow to a broker archive (bar) file and deploy
the BAR file to an execution group, the message flow is assigned implicitly
to the execution group.
- assigned message flow properties
- In Version 2.1, the properties of
an assigned message flow. In Version 6.0,
you specify the equivalent properties in the deployment descriptor
of a broker archive (bar) file.
- Assignments view
- In Version 2.1, the user interface
in the Control Center that is used to assign
message flows to an execution group. In Version 6.0, the
equivalent function is provided by the Broker
Administration perspective of the workbench. When you add message flows to a broker archive (bar) file
and deploy the BAR file to an execution group, the message flows are assigned implicitly to the
execution group.
B- Broker Administration perspective
- In Version 6.0, a broker administration
console that communicates with one or more Configuration
Managers. Administrators work in this
perspective to manage the resources (also referred to as domain objects)
in the broker domain that are defined on one or more Configuration
Managers. In Version 2.1, the equivalent function is
provided by the Assignments
view.
- built-in node
- In Version 6.0, a message processing
node that is supplied by the product. In Version 2.1, this is referred to as an IBM Primitive node.
C- check in
- In Version 2.1, a Control Center action that stores a new or
updated resource in the Configuration
Manager.
In Version 6.0, the equivalent check-in
function might be provided by an external repository that is associated
with the workbench.
- check out
- In Version 2.1, a Control Center action that extracts a resource
from the Configuration
Manager and locks it for
local modification by a user. In Version 6.0,
the equivalent check-out function might be provided by an external
repository that is associated with the workbench.
- Configuration
Manager
- In Version 6.0, the Configuration
Manager does not store message flow definitions. Instead, these definitions
are stored in the local file system or in an external repository that
is associated with the workbench.
In addition in Version 6.0 the Configuration
Manager no longer uses an external database
to store the domain configuration, but uses an internal repository
instead.
- connection
- In Version 6.0, this represents
the flow of control and data between two message processing nodes.
In Version 2.1, this is referred to
as a connector.
- connector
- In Version 2.1, this represents
the flow of control and data between two message processing nodes.
In Version 6.0, this is referred to
as a connection.
- Control Center
- In Version 2.1, the graphical user
interface that provides the function to define, configure, deploy,
and monitor resources. In Version 6.0,
this function is provided, with enhancements, by the Message Brokers Toolkit, which is also known as the workbench.
I- IBM Primitive node
- In Version 2.1, a message processing
node that is supplied by the product. In Version 6.0, this is referred to as a built-in node.
- Input Terminal node
- In Version 2.1, an IBM Primitive
node through which a message is received by a subflow. In Version 6.0, this function is provided by
the Input node.
M- Message Brokers Toolkit
- In Version 6.0, the development
and operational management environment for a broker domain. It is
also referred to as the workbench.
In Version 2.1, the Control Center provides this function.
O- Operations view
- In Version 2.1, the Control Center view
that is used to manage and monitor the brokers in a broker domain.
In Version 6.0, the equivalent function
is provided by the Domains and Alerts views in the Broker Administration perspective of
the workbench.
- Output Terminal node
- In Version 2.1, an IBM Primitive node through which
a message is propagated by a subflow. In Version 6.0, this function is provided by
the Output node.
S- shared data
- In Version 2.1, configuration repository
and message repository data that is shared by Control Center users.
In Version 6.0, the equivalent functionality
might be provided by an external repository that is associated with
the workbench.
T- traffic light status icon
- In Version 2.1, an icon next to
a message flow, execution group, or broker in the Domain Topology
pane of the Operations view in the Control Center.
A green traffic light indicates that the resource is running, and
a red traffic light indicates that it is not running. In Version 6.0, an alert appears in the Alerts
view in the Broker Administration perspective of the workbench only when the resource is not
running.
U- unlock
- In Version 2.1, the action to end
the checked-out state of a resource in such a way that any changes
made to the resource since it was checked out are not stored in the Configuration
Manager.
In Version 6.0, the equivalent function
might be provided by an external repository that is associated with
the workbench.
V- view
- In Version 2.1, a user interface
in the Control Center that enables a user to
perform a specified task. There are eight views: Message Sets, Message
Flows, Topology, Assignments, Topics, Operations, Subscriptions, and
Log. In Version 6.0, a view is a component
of a perspective in the workbench.
To perform a specified task, the user selects the appropriate perspective
and then uses a combination of one or more views and an editor.
W- workbench
- See Message Brokers Toolkit.