This glossary lists differences
in terminology between WebSphere® Message 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.
- assigned message set
- In Version 2.1, a message set that
is assigned to a broker. In Version 6.0,
when you add a message set to a broker archive (bar) file and deploy
the BAR file to an execution group, the message set is assigned implicitly
to the execution group.
- Assignments view
- In Version 2.1, the user interface
in the Control Center that is used to assign
message flows to an execution group and message sets
to a broker. In Version 6.0, the
equivalent function is provided by the Broker
Administration perspective of the workbench. When you add message flows and message sets to a broker archive (bar) file
and deploy the BAR file to an execution group, the message flows and message sets are assigned implicitly to the
execution group.
B- base message set
- In Version 2.1, a finalized message
set upon which another message set is based. The two message set definitions
are linked and the definition of the base message set can never be
modified. In Version 6.0, when you base
a message set on another message set, the workbench makes a copy of the definition
of the base message set. Subsequently, the two message set definitions
are completely separate from each other and can be modified independently.
- base type
- In Version 2.1, a compound type
as a whole can have a simple value. The type of this simple value
is called the base type. In Version 6.0,
a base type is the simple type or complex type upon which another
type is based.
- 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.
- C language binding
- See language binding.
- COBOL language binding
- See language binding.
- complex type
- In Version 6.0, a type that has
structure. In Version 2.1, this role
is performed by a compound type.
- compound type
- In Version 2.1, this has two roles:
- A type that has structure. In Version 6.0,
this is referred to as a complex type.
- A collection of elements. In Version 6.0,
this is referred to as a group.
- Composition
- In Version 6.0, a property that
describes how a message tree is structured. In Version 2.1, the equivalent property of
a compound type is Type Composition.
- Configuration
Manager
- In Version 6.0, the Configuration
Manager does not store message flow and message set 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.
- Connection pane
- In Version 2.1, a pane that is used
to specify certain properties of an element or compound type. In Version 6.0, these properties are specified
as the logical properties of an element reference or group reference.
- 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.
- Content Validation
- In Version 6.0, a property of a
group. In Version 2.1, the equivalent
property applies to a compound type and is called Type Content.
- context tag
- See element qualifier.
- 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.
- customizer
- In Version 2.1, a means of specifying
complex properties of a message processing node. In Version 6.0, you use an editor to perform
this task.
D- debugger
- In Version 2.1, a tool that is accessed
from the Message Flows view in the Control Center and
enables message flows to be debugged. In Version 6.0, similar but enhanced function
is provided by the flow debugger.
- Description pane
- In Version 2.1, a pane that is associated
with every object and that is used to specify the Short Description
and Long Description properties of the object. In Version 6.0, some objects still have short
and long descriptions, but message model objects have a documentation property instead.
- documentation property
- In Version 6.0, the documentation
property of an object allows you to add information to enhance the
understanding of that object's function. In Version 2.1, the equivalent information
is provided using the Description
pane.
E
- element member
- In Version 2.1, an object that represents
the membership of an element within a compound type. In Version 6.0, the object that represents the
membership of a global element within a complex type or group is called
an element reference.
- element qualifier
- In Version 2.1, an object that is
associated with an element in a message to enable that element to
be treated differently in different contexts. It is also known as
a context tag. In Version 6.0, element
qualifiers are no longer used.
- element reference
- In Version 6.0, an object that represents
the membership of a global element within a complex type or group.
In Version 2.1, the object that represents
the membership of an element within a compound type is called an element
member.
- element value
- In Version 2.1, a named value that
you can use to specify a value constraint on an element. In Version 6.0, element values are no longer
used. Instead, you associate value constraints with a simple type.
- extended decimal
- In Version 2.1, a Custom Wire Format
(CWF) physical representation of a number. In Version 6.0, this is referred to as external
decimal.
- external decimal
- In Version 6.0, a Custom Wire Format
(CWF) physical representation of a number. In Version 2.1, this is referred to as extended
decimal.
F- finalize
- In Version 2.1, the action to put
a message set into a finalized state. When a message set is in this
state, you can never modify its definition again. In Version 6.0, a message set cannot be finalized.
- flow debugger
- In Version 6.0, a facility to debug
message flows that is provided in the Debug perspective in the workbench.
In Version 2.1, the equivalent function
is provided by the debugger .
- freeze
- In Version 2.1, the action to put
a message set into a frozen state to prevent further modification
to its definition. See also unfreeze.
In Version 6.0, a message set cannot
be frozen.
G- glossary
- In Version 2.1, a form of documentation
in HTML format that you can generate from a message set definition.
In Version 6.0, this has been replaced
by message set documentation,
which is also in HTML format.
- group
- In Version 6.0, a structure that
can be included in a complex
type or another group. In Version 2.1,
this role is performed by a compound
type.
H- History pane
- In Version 2.1, a pane that is used
to specify additional documentation for certain MRM objects such as an element,
a message, and a compound type. In Version 6.0,
the Documentation property of an object is used to specify this information.
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.
- identifier
- In Version 2.1, an identifier that
identifies each object uniquely within a message set. You use the
identifier to reference the object in an ESQL statement. In Version 6.0, an object is identified by its
name only. When you migrate a message set, the name of an object is
formed from its Version 2.1 identifier.
- Input Compression Technique
- In Version 2.1, a Tagged Delimited
String (TDS) property of a message set. In Version 6.0, this property does not exist.
- 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.
L- language binding
- In Version 2.1, a set of properties
associated with a message set that enable you to generate a C header
or COBOL copybook from the message set definition. In
Version 6.0, this set of properties
does not exist, and you cannot generate a C header or COBOL copybook
from a message set definition.
- Level
- In Version 2.1, a property of a
message set that specifies the version of the message set. In Version 6.0, this property does not exist.
- Long Description
- See Description pane.
M- message book
- In Version 2.1, a form of documentation
in HTML format that you can generate from a message set definition.
In Version 6.0, this has been replaced
by message set documentation,
which is also in HTML format.
- 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.
- message category
- In Version 6.0, a way of grouping
messages, perhaps for documentation or convenience purposes, or for
assisting in the generation of Web Services Description Language (WSDL)
files. This replaces the Version 2.1 transaction and transaction category.
- Message Domain
- In Version 6.0.2, a message set property that specifies the message
domain of messages in the message set. It replaces the Runtime
Parser property of earlier releases.
- message repository
- In Version 2.1, the set of database
tables used by the Configuration
Manager to store
message set definitions. In Version 6.0,
there is no message repository, and message set definitions are stored
in the local file system or in an external repository that is associated
with the workbench.
- Message Repository Manager
- In Version 2.1, the component of
the Configuration
Manager that manages message
set definitions in the message repository. In Version 6.0, there is no Message Repository
Manager.
- message set documentation
- In Version 6.0, documentation in
HTML format that you can generate from a message set definition. In Version 2.1, the equivalent documentation
is provided by a glossary and
a message book.
- MRM
- In Version 2.1, the name of a message
domain and the abbreviation for Message
Repository Manager. In Version 6.0,
it is the name of only a message domain.
N- name
- In Version 2.1, a descriptive name
of an object in a message set. This name is not used to identify the
object in an ESQL statement; the identifier of
the object is used instead. In Version 6.0,
the name is used to identify an object and must be a valid XML Schema
identifier. When you migrate a message set, the name of an object
is formed from its Version 2.1 identifier.
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 Compression Technique
- In Version 2.1, a Tagged Delimited
String (TDS) property of a message set. In Version 6.0, this property does not exist.
- 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.
P- plug-in
- In Version 2.1, a user-written extension
to the broker that provides a message processing node or message parser
in addition to those supplied with the product. In Version 6.0, this is referred to as a user-defined extension.
- prefixed identifier
- In Version 2.1, an identifier that
contains a prefix to ensure that the identifier is unique within a
message set. Use prefixed identifiers in situations where different
elements have the same name so that the element is defined globally
even though it is considered to be local to a compound type of which
it is a member. In Version 6.0, prefixed
identifiers are no longer required because an element can be defined
locally. When you migrate a message set, an element with a prefixed
identifier becomes a local element, and the prefix is discarded when
the identifier is used to form the Version 6.0 name.
R- Run Time pane
- In Version 2.1, the pane that is
used to specify the runtime parser for a message set. In Version 6.0, this information is specified
as a general message set property.
- Runtime Parser
- See Message Domain.
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.
- Short Description
- See Description pane.
- simple type
- In Version 2.1, one of seven types
defined by the MRM to describe an item of data. In Version 6.0, a simple type is one of the
44 XML Schema simple types or a user-defined simple type.
- Simple Unordered Set
- In Version 2.1, one of the permissible
values of the Type Composition property
of a compound type. It is intended for the modelling XML DTD attribute
list declarations. In Version 6.0, this
value is not required because XML Schema attribute groups are modelled
as objects in their own right. If the Type Composition property of
a compound type has this value when you migrate a message set, the
Composition property of the group that is formed from the compound
type has the value All, if the Type Content property of the compound
type has the value Closed, or the value Unordered Set otherwise.
- suspended from use
- In Version 2.1, certain MRM objects
in a message set that is based on another message set can be suspended
from use. When suspended from use, an object cannot be used. In Version 6.0, an object cannot be suspended
from use.
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.
- transaction
- In Version 2.1, a group of messages
that are considered to be part of a single business transaction. In
Version 6.0, transactions are no longer
used. When you migrate a message set, a transaction is replaced by
a message category that
contains the same messages as the original transaction.
- transaction category
- In Version 2.1, a group of transactions
within a message set. In Version 6.0,
transaction categories are no longer used. When you migrate a message
set, a transaction category is replaced by a message category. This message
category contains all the messages in all the transactions that were
members of the original transaction category.
- Type Composition
- In Version 2.1, a property of a
compound type. In Version 6.0, the equivalent
property applies to a group and is called Composition.
- Type Content
- In Version 2.1, a property of a
compound type. In Version 6.0, the equivalent
property applies to a group and is called Content Validation.
U- unfreeze
- In Version 2.1, the action to remove
a message set from a frozen state to allow further modification to
its definition. In Version 6.0, a message
set cannot be frozen.
- 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.
- user-defined extension
- In Version 6.0, a user-written extension
to the broker that provides a message processing node or message parser
in addition to those supplied with the product. In Version 2.1, this is referred to as a plug-in.
V- value constraint
- In Version 2.1, the use of an element
value to specify a constraint on the value of an element. In Version 6.0, a value constraint is represented
by an XML schema facet that is applied to a simple type.
- 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.