Migration glossary

This glossary lists differences in terminology between WebSphere Business Integration Event Broker Version 5.0 and Version 2.1 products.

For a full list of terms and abbreviations used by the product documentation, and for definitions that are more complete, see Glossary of terms and abbreviations.

A
assigned message flow
In Version 2.1, a message flow that is assigned to an execution group. In Version 5.0, when you add a message flow to a broker archive (bar) file and deploy the bar file to an execution group, implicitly the message flow is assigned to the execution group.
assigned message flow properties
In Version 2.1, the properties of an assigned message flow. In Version 5.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 5.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, implicitly the message flows are assigned to the execution group.
B
built-in node
In Version 5.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 5.0, equivalent check in function might be provided by an external repository 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 5.0, equivalent check out function might be provided by an external repository associated with the workbench.
Configuration Manager
In Version 5.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 associated with the workbench.
connection
In Version 5.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 5.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 5.0, this function is provided, with enhancements, by the Message Brokers Toolkit for WebSphere Studio, which is also known as the workbench.
D
deploy
In Version 2.1 and Version 5.0, this term has the same meaning. However, when using rapid application development (RAD) in Version 5.0, the term publish is also used to mean deploy. This is for consistency with the equivalent function in WebSphere Application Server.

I
IBM Primitive node
In Version 2.1, a message processing node that is supplied by the product. In Version 5.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 5.0, this function is provided by the Input node.
M
Message Brokers Toolkit for WebSphere Studio
In Version 5.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 5.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 5.0, this function is provided by the Output node.
S
shared
In Version 2.1, configuration repository and message repository data that is shared by Control Center users. In Version 5.0, equivalent function might be provided by an external repository 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 5.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 5.0, the equivalent function might be provided by an external repository 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 5.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 for WebSphere Studio.