This glossary defines WebSphere® Message
Broker terms and abbreviations that
are used in this online information center.
The
migration
glossary lists differences in terminology between
WebSphere Message Broker Version 6.0 and previous versions of the
product.
A- access control list (ACL)
- In computer security, a list associated with an object that identifies
all the subjects that can access the object that it is associated
with. The list also defines their access rights. Subjects are principals that have explicit
permissions (to publish, to subscribe to, and to request persistent
delivery of, a publication message)
against a topic in the topic
tree. The ACLs define the implementation of topic-based security.
- ACL
- See access control list.
- active working set
- The logical collection of application projects that is currently
displayed in the Broker Application Development perspective. See also working set.
- aggregation
- See message element
aggregation.
- AMI
- See Application Messaging Interface.
- Application Messaging Interface (AMI)
- The programming interface, provided by WebSphere MQ, that defines a high level
interface to message queuing services. See also Message Queue Interface (MQI) and Java™ Message
Service (JMS). Applications that use the AMI connect to the
broker using WebSphere MQ Enterprise
Transport.
attribute
A characteristic or trait of an entity that describes the entity. In
XML, a name-value pair within a tagged element that modifies certain
features of the element.

- attribute group
- A set of attributes that
can appear in a complex type.
TOP
B- BAR file
- See broker archive file.
- bend point
- A point that is introduced in a connection between two message flow nodes at which the
line that represents the connection changes direction. A bend point
can be used to make node alignment and processing logic clearer and
more effectively displayed.
- binary large object (BLOB)
- A block of bytes of data (for example, the body of a message)
that has no discernible meaning, but is treated as one solid entity
that cannot be interpreted.
- BLOB
- See binary large object.
- BLOB domain
- The message domain that includes all messages with content that
cannot be interpreted or subdivided into smaller sections of information.
Messages in this domain are processed by the BLOB parser. See also IDOC domain, JMS domain, MIME domain, MRM domain, XML domain, XMLNS domain, and XMLNSC domain.
- BLOB parser
- A program that interprets a message that belongs to the BLOB domain, and generates the
corresponding tree from the bit stream on input, or the bit stream
from the tree on output.
- broker
- A set of execution processes that host one or more message flows. Also known as message
broker.
- broker archive file
- The unit of deployment to
the broker; also known as
a BAR file. The broker archive file contains a number of different
files, including compiled message
flows (.cmf) and message sets (.dictionary and .xsdzip files),
that are used by the broker at run time. It can also contain additional
user-provided files that your message flows might need at run time,
provided that the file extension does not overlap with extensions
that are used by the broker.
- broker domain
- A collection of brokers that
share a common configuration, together with the Configuration
Manager that
controls them.
- broker schema
- A symbol space that defines the scope of uniqueness of the names
of resources that are defined
within it. The resources include message flows, ESQL
files, and mapping files.
- built-in node
- A message flow node that
is supplied by the product. Some of the supplied nodes provide basic
processing such as input and output.
TOP
C- callback function
- See implementation function.
- cardinality
- See mapping cardinality.
- category
- An optional grouping of messages that
are related in some way. For example, messages that relate to a particular
application might be included in a single category.
- cmf
- See compiled message flow.
- collective
- A set of brokers that
are fully interconnected and form part of a multi-broker network for publish/subscribe applications.
- compiled message flow (cmf)
- A message flow that has
been compiled to prepare it for deployment to the broker. A cmf file
is sent to the broker within a BAR
file.
- complex element
- A named structure that contains simple
elements within the message.
Complex elements can contain
other complex elements, and can also contain groups. The content of a complex
element is defined by a complex
type. See also simple
element.
complex type
A type that can contain elements, attributes, and groups organized
into a hierarchy.A complex type structure
within a message contains elements, attributes, and groups organized into a hierarchy.
See also simple type.

- component
- A set of runtime processes that perform a specific set of functions.
A component is a broker, a Configuration
Manager,
a Database Instance Manager,
or a User Name Server.
- component directory
- In z/OS®, the root directory
of the component's runtime
environment.
- component name
- The external name of a component.
Each component requires a name, which is used, for example, in the workbench and
in commands.
- component PDSE
- In a z/OS environment, a PDSE that contains jobs to define
resources to DB2, WebSphere MQ, and the WebSphere Message Broker started task. See partitioned data set.
- configuration
- In a broker domain, the brokers, execution groups, deployed message sets, deployed message flows, and defined topics
and access control lists.
- Configuration Manager
- The component that provides an interface between the workbench
and a set of runtime brokers.
It provides brokers with their initial configuration, and updates
them with any subsequent changes. It maintains the broker domain configuration.
- Configuration Manager Proxy
- An application programming interface that your applications can
use to control broker domains through a remote interface to the Configuration
Manager.
- connection
- See message flow node connection.
For broker-to-broker connections, see publish/subscribe
topology.
- content-based filter
- In publish/subscribe, an expression that is included as part of
a subscription to determine
whether a publication message
is received based on its content. The expression can include wild cards.
- Custom Wire Format
- The physical representation of a message in
the MRM domain that
is composed of a number of fixed format data structures or elements, which are not separated
by delimiter characters.
- CWF
- See Custom Wire Format.
TOP
D- Database Instance Manager
- On Windows®, a network server
that supports the creation, maintenance, and deletion of databases
used by brokers in all installations on a single computer. Database
support is limited to Derby and DB2®. The Database Instance Manager
is associated with a Windows service.
- data element separation
- For a complex type,
defines to the MRM parser TDS physical format which
method of identifying data elements is to be used, and how the data
elements are constructed. The following separation types are supported:
data pattern separation, delimited separation, fixed length separation,
and tagged separation
- DataFlowEngine (DFE)
- See execution group.
- datagram
- A form of asynchronous messaging in which an application sends
a message, but does not want a response. Also known as send-and-forget.
Contrast with request/reply.
- debugger
- See flow debugger.
deploy
To place files or install software into an operational environment.The
process of transferring data to an execution
group on a broker so
that it can take effect in the broker
domain. For deploying message
flows and associated resources, the data is packaged in a broker archive (BAR) file before
being sent to the Configuration
Manager, from where it is unpackaged
and distributed appropriately.

- Derby
- The database based on the Apache Derby open source project from
Apache Software Foundation. Derby database support is embedded in
the broker component on Windows only.
- destination list
- See local environment.
- distribution list
- A list of WebSphere MQ queues to which a message can be
put with a single statement.
- document type definition (DTD)
- The rules that specify the structure for a particular class of
SGML or XML documents. The
DTD defines the structure with elements, attributes, and notations,
and it establishes constraints for how each element, attribute, and
notation can be used within the particular class of documents. A DTD
is analogous to a database schema in that the DTD completely describes
the structure for a particular markup language.
- DTD
- See document type definition.
TOP
E- editor area
- The area in the workbench window where files are
opened for editing.
- element
- A named piece of information, or a field, within a message, with a business meaning
agreed by the applications that create and process the message. See
also simple element and complex element.
- embedded message
- See multipart message.
- environment
- A structure within the message
tree that is user-defined and can contain variable information
that is associated with a message while it is being processed by a message flow.
- ESM
- See external security manager.
- ESQL
- See Extended SQL.
- ESQL data type
- A characteristic of an item of data that determines how that data
is processed. ESQL supports
six data types (Boolean, datetime, null, numeric, reference, and string).
Data that is retrieved from a database or is defined in a message model is mapped to
one of these basic ESQL types when it is processed in ESQL expressions.
- ESQL field reference
- A sequence of values, separated by periods, that identify a specific
field (which might be a structure) within a message tree or a database table.
An example of a field reference is Body.Invoice.InvoiceNo.
- ESQL function
- A single ESQL expression
that calculates a resultant value from a number of given input values.
The function can take input parameters but has no output parameters;
it returns to the caller the value that results from the implementation
of the expression. The ESQL expression can be a compound expression
such as BEGIN END.
- ESQL module
- A sequence of declarations that define MODULE-scope variables
and their initialization, and a sequence of subroutine (function and
procedure) declarations that define a specific behavior for a message flow node. A module must
begin with the CREATE node_type MODULE statement
and end with an END MODULE statement. The node_type must
be one of Compute, Database, or Filter. The entry point of the ESQL code is the module scope
procedure named MAIN.
- ESQL procedure
- A subroutine that has no return value. It can accept input parameters
from and return output parameters to the caller.
- ESQL variable
- A local temporary field that is used to assist in the processing
of a message.
- exception list
- A list of exceptions, with supporting information, that has been
generated during the processing of a message.
- execution group
- 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.
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.
- Extended SQL (ESQL)
- A specialized set of SQL functions
and statements that are based on regular SQL, and extended with functions
and statements that are unique to WebSphere Message Broker.
- Extensible Markup Language (XML)
- A standard metalanguage for defining markup languages that is
based on Standard Generalized Markup Language (SGML).
- Extensible Stylesheet Language (XSL)
- A language for specifying style sheets for XML documents. Extensible
Stylesheet Language Transformation (XSLT) is used with XSL to describe
how an XML document is transformed into another document.
- External Security Manager (ESM)
- In a z/OS environment, a
security product that performs security checking on users and resources. RACF® is an example of an ESM.
TOP
F- field reference
- See ESQL field reference
filter
An ESQL expression
that is applied to the content of a message to determine how the message
is processed.The filter expression can be applied by a Filter node or to determine
whether a publication matches certain criteria set by a subscriber.

- flow debugger
- A facility to debug message
flows that is provided in the Debug perspective in the workbench.
- format
- The definition of the internal structure of a message, in terms of the fields
and the order of those fields. A format can be self-defining, in which case
the message is interpreted dynamically when it is read.
TOP
G- graphical user interface (GUI)
- A type of computer interface that presents a visual metaphor of
a real-world scene, often of a desktop, by combining high-resolution
graphics, pointing devices, menu bars and other menus, overlapping
windows, icons, and the object-action relationship.
- group
- A list of elements with
information about how those elements can appear in a message. Groups can be ordered,
unordered, or selective.
- GUI
- See graphical user interface.
TOP
I- IBM® Runtime Environment
for Java
- A subset of the IBM Developer Kit for the Java Platform that contains the core
executable files and other files that constitute the standard Java platform. The IBM Runtime Environment includes the Java virtual machine (JVM), core classes, and
supporting files.
- IBM Software
Developer Kit for Java
- A software package that can be used to write, compile, debug,
and run Java applets and applications.
- IDOC domain
- The message domain that includes all messages that are exchanged
between the broker and SAP R3 clients by the MQSeries® link for R/3. Messages in this
domain are processed by the IDOC
parser. See also BLOB
domain, JMS domain, MIME domain, MRM domain, XML domain, XMLNS domain, and XMLNSC domain.
- IDOC parser
- A program that interprets a message that belongs to the IDOC domain, and generates the
corresponding tree from the bit stream on input, or the bit stream
from the tree on output.
- implementation function
- A function written for a user-defined
node or message parser;
also known as a callback function.
- input node
- A message flow node that
represents a source of messages for a message
flow or subflow.
See also output node.
install_dir
The location in the local file system in which product components
have been installed. For example, the default location for runtime
components on Windows XP is C:\Program Files\IBM\6.0.
- installation directory
- In a z/OS environment, a
file system into which all product data is installed, and from which
it is referenced and retrieved during the customization phase.
TOP
J- Java Database
Connectivity (JDBC)
- An industry standard for database-independent connectivity between
the Java platform and a wide
range of databases. The JDBC interface provides a call-level API for
SQL-based and XQuery-based database access. See also Open Database Connectivity.
- Java Message
Service (JMS)
- An application programming interface that provides Java language functions for handling messages.
See also Application Messaging
Interface (AMI) and Message
Queue Interface (MQI). Applications using JMS connect to the
broker using either WebSphere MQ Real-time Transport or WebSphere MQ Multicast Transport.
- JCL
- See Job Control Language
- JDBC
- See Java Database Connectivity.
- JMS
- See Java Message Service.
- JMS domain
- The message domain that includes all messages that are produced
by the WebSphere MQ implementation
of the Java Message Service standard. These
messages, which have a message type of either JMSMap or JMSStream,
are supported in the same way as messages in the XML domain, and are parsed
by the XML parser. See
also BLOB domain, IDOC domain, MIME domain, MRM domain, XML domain, XMLNS domain, and XMLNSC domain.
- Job Control Language (JCL)
- Job Control Language (JCL) comprises a set of Job Control Statements
that are used to define work requests called jobs. JCL tells the operating
system what program to run, and defines its inputs and outputs.
TOP
L- LIL
- See loadable implementation
library.
- loadable implementation library (LIL)
- The implementation module for a node or parser written in C. This library
file is implemented in the same way as a dynamic link library, but
has a file extension of .lil not .dll.
- local environment
- A structure within the message
tree that contains broker and, optionally, user information
associated with a message while it is being processed by a message flow.
In previous releases,
the local environment structure was known as the Destination list;
the latter term is retained for compatibility.
- local error log
- A generic term that refers to the logs to which WebSphere Message Broker writes records on the
local system. Also known as the system log.
TOP
M- map
- (1) A complete transformation that has source objects that define
the structure of the inputs and target objects that define the structure
of the outputs. A map is represented as a .msgmap file.
- (2) To associate a source to a target in a message map.
- mapping
- A target value expression.
- mapping cardinality
- The granularity of the way in which message elements are mapped
from message source to message target. For example:
- One-to-one: associates a single source with a single target
- One-sided: associates a value with a target
- Many-to-one: associates multiple sources with a single target
- message
- A communication that is sent from a person or program to another
person or program. In WebSphere Message Broker, a message format can
be modeled by a message definition that
describes the structure and content of the message. Messages must
have a structure and format that
is agreed by the sending and receiving applications.
- message broker
- See broker.
- Message Brokers Toolkit
- A component that integrates with Rational® Application Developer and is based
on the Eclipse platform. This component provides the workbench development environment.
- message definition
- An annotated XML Schema model of a message format. A message definition
is a structured collection of elements, types, and groups.
- message definition file
- A file in a message set that
contains one or more message
definitions.
- message dictionary
- A data structure that describes all of the messages in a message set in a form suitable
for use by the MRM parser.
- message domain
- A grouping of messages that share certain characteristics. A message
domain has an associated parser that interprets messages that are
received and generated by a broker. WebSphere Message Broker supports messages in the BLOB domain, IDOC domain, JMS domain, MIME domain, MRM domain, XML domain, XMLNS domain, and XMLNSC domain. You can create
additional parsers known as user-defined
parsers to support messages that do not conform to the supported
domains.
- message element aggregation
- A mapping in which all the repeatable elements in one instance
are mapped to another instance. It is not possible to map the repeatable
elements themselves, only the instances. This aggregation is useful
when mapping all possible inputs to one or more outputs, and can be
used for copying an array, or for assigning a scalar, such as a summation.
Use message element aggregation when the following conditions are
met:
- A single source and target are selected.
- Source and target are of simple numeric type.
- The source repeats.
- message flow
- A sequence of processing steps that run in the broker when an
input message is received. A message flow is created in the workbench by
including a number of message flow
nodes that each represents a set of actions that define a processing
step. The connections in the flow determine which processing steps
are carried out, in which order, and under which conditions. A message
flow must include an input node that
provides the source of the messages that are processed. Message flows
are then ready to deploy to
a broker for execution. See also subflow.
- message flow node
- A processing step in a message
flow, also called a message processing node. A message flow
node can be a built-in node,
a user-defined node, or
a subflow node.
- message flow node connection
- An entity that connects an output terminal of one message flow node to an input
terminal of another. A message flow node connection represents the
flow of control and data between two message flow nodes.
- message model
- See message definition.
- message parser
- A program that interprets an incoming message and creates an internal
representation of the message in a tree structure, and that regenerates
a bit stream for an outgoing message from the internal representation.
- message processing node
- See message flow node.
- Message Queue Interface (MQI)
- The programming interface that is provided by WebSphere MQ queue managers. Application programs
use the programming interface to access message queuing services.
See also Application Messaging
Interface (AMI) and Java Message Service (JMS).
Applications that use the MQI, connect to the broker using WebSphere MQ Enterprise
Transport.
- message set
- A folder in a message set
project that contains one or more message definition files.
It can be deployed to a broker in
a broker archive file.
- message set project
- The eclipse container for a message
set.
- message template
- A means of identifying a message format within the broker. It
consists of four parts: message
domain, message set, message type, and physical format.
- message tree
- The logical tree structure that represents the content and structure
of a message in the broker.
The message tree is created by a message
parser from the input message received by a message flow, according
to a message template.
- message type
- The name given to a message
definition in a message definition file.
- metadata
- The data that describes the characteristic of stored data.
- MIME
- See Multipurpose Internet
Mail Extensions.
- MIME domain
- The message domain that includes all messages that conform to the
MIME standard. See also BLOB
domain, IDOC domain, JMS domain, MRM domain, XML domain, XMLNS domain, and XMLNSC domain.
- MIME parser
- A program that interprets a message that belongs to the MIME domain, and generates
the corresponding tree from the bit stream on input, or the bit stream
from the tree on output.
- MQI
- See Message Queue Interface.
- MQIsdp
- See SCADA device protocol.
- MQRFH
- An architected message header that is used to provide metadata for the processing of
a message. This header is supported by the WebSphere MQ (MQSeries) Publish/Subscribe SupportPac™.
- MQRFH2
- An extended version of MQRFH,
providing enhanced function in message processing.
- MRM domain
- The message domain that can parse, and write, a wide
variety of message formats. This domain is primarily intended for
non-XML message formats, but it can also parse and write XML messages.
Message models are created in the workbench, with one or more physical
formats. Messages in the MRM domain are processed by the MRM parser. See also BLOB domain, IDOC domain, JMS domain, MIME domain, XML domain, XMLNS domain, and XMLNSC domain.
- MRM parser
- A program that interprets a message that belongs to the MRM domain, and generates
the corresponding tree from the bit stream on input, or the bit stream
from the tree on output. Its interpretation depends on the physical format that you have
associated with the input or output message.
- multilevel wild card
- A wild card that can
be specified in subscriptions to match any number of levels in a topic.
- multipart message
- A message that contains one or more other messages within its structure.
The contained message is sometimes referred to as an embedded message.
- Multipurpose Internet Mail Extensions
- An Internet standard that defines different forms of data, including
video, audio, or binary data, that can be attached to e-mail without
requiring translation into ASCII text.
TOP
N
namespace
In XML and XQuery, a uniform
resource identifier (URI) that provides a unique name to associate
with the element, attribute, and type definitions in an XML schema,
or with the names of elements, attributes, types, functions, and errors
in XQuery expressions. XML instance
documents, XML Schemas,
and message definitions can
use namespaces.

- node
- (1) An endpoint or junction used in a message flow. See message flow node.
- (2) An element in a message mapping tree. See tree node.
TOP
O- ODBC
- See Open Database Connectivity.
- Open Database Connectivity (ODBC)
- A standard application programming interface (API) for accessing
data in both relational and non-relational database management systems.
Using this API, database applications can access data stored in database
management systems on a variety of computers even if each database
management system uses a different data storage format and programming
interface.
- output node
- A message flow node that
represents a point at which messages leave the message flow or subflow. See also input node.
TOP
P- parser
- See message parser.
- partitioned data set (PDS, PDSE)
- In a z/OS environment, a
data set in direct-access storage that is divided into partitions,
which are called members. A partitioned data set (extended) (PDSE)
is an extension to a PDS that contains an indexed directory in addition
to the members.
- PDS, PDSE
- See partitioned data set.
- perspective
- A group of views that show various aspects of the resources in
the workbench. See also view.
- physical format
- The physical representation of a message within
the bit stream. The supported physical formats are Custom Wire Format, XML Wire Format, and Tagged/Delimited String Format. Physical format information is used only by the MRM parser
and the IDOC parser.
- point-to-point
- A style of messaging application in which the sending application
knows the destination of the message. Contrast with publish/subscribe.
- predefined element and message
- An element or message for which a matching
definition exists in the message
model. See also self-defining
element and message.
- principal
- An individual user ID (for example, a login ID) or a group. A
group can contain individual user IDs and other groups, to the level
of nesting that is supported by the underlying facility.
property
A characteristic of an object that describes the object. A property
can be changed or modified. Properties can describe an object's name,
type, value, or behavior, among other things.Resources that are
created and maintained in the workbench and components have properties;
for example, message flow nodes,
deployed message flows, and
brokers.

- publication
- A piece of information about a specified topic that is available to a broker in a publish/subscribe system.
- publication node
- An end point of a specific path through a message flow to which a client
application subscribes, identified to the client by its subscription point.
- publisher
- An application that makes information about a specified topic available to a broker in a publish/subscribe system.
- publish/subscribe
- A style of messaging application in which the providers of information
(publishers) are de-coupled
from the consumers of that information (subscribers) using a broker. See also topic. Contrast with point-to-point messaging.
- publish/subscribe topology
- The brokers, the collectives,
and the connections between them, that support publish/subscribe applications
in the broker domain.
TOP
Q- queue
- A WebSphere MQ object to which
message queuing applications can put messages, and from which message
queuing applications can get messages.
- queue manager
- A system program that provides queuing services to applications.
A queue manager provides an application programming interface (the MQI) that enables programs to
access messages on the queues that
the queue manager owns.
TOP
R- request/reply
- A type of messaging application in which a request message is
used to request a reply from another application. Contrast with datagram.
- resource
- The collective term for projects, folders, subfolders, and files
that can be manipulated in the Eclipse workbench.
- Resource Recovery Services (RRS)
- A z/OS facility that provides
two-phase sync point support by participating resource managers.
- retained publication
- A published message that is kept at the broker for propagation to clients
that subscribe in the future.
- RRS
- See Resource Recovery Services.
TOP
S- SCADA
- See Supervisory, Control,
And Data Acquisition.
- SCADA device protocol (MQIsdp)
- A protocol that implements the WebSphere MQ Telemetry Transport to connect SCADA devices to the broker.
- schema
- See XML Schema.
- self-defining element and message
- An element or message for which no matching
definition exists in a message
model, but which can be parsed without reference to a model.
For example, a message that is coded in XML can be self-defining. See
also predefined element and
message.
- send-and-forget
- See datagram.
- simple element
- A field in a message that
is based on a simple type.
A simple element can repeat,
and it can define a default or a fixed value. See also complex element.
- simple type
- A characteristic of a simple
element that defines the type of data within a message (for example, string,
integer, or float). A simple type can have value constraints which place
limits on the values of any simple elements based on that simple type.
See also complex type.
- single-level wild card
- A wild card that can
be specified in subscriptions to match a single level in a topic.
- SOAP
- An XML based language defined by the World Wide Web Consortium
(W3C) for sending data between applications. SOAP is transport and
platform neutral.
- SQL
- See Structured Query Language.
- SQLJ
- A Java extension that supports
static Structured Query Language statements
embedded within Java code.
- stream
- A method of topic partitioning
that is used by applications that connect to WebSphere MQ Publish/Subscribe brokers.
- Structured Query Language (SQL)
- A standardized programming language that is used to define and
manipulate data in a relational database. ESQL, the language that is used
by WebSphere Message Broker, is based on SQL,
and has many similar constructs.
- style sheet
- A specification of formatting instructions that, when applied
to structured information, provides a particular rendering of that
information (for example, online or printed). Different style sheets
can be applied to the same piece of structured information to produce
different presentations of the information.
- subflow
- A sequence of processing steps, implemented by message flow nodes,
that is designed to be embedded in a message
flow or in another subflow. A subflow must include at least
one Input or Output node. A subflow can be started by a broker only
as part of the message flow in which it is embedded, and therefore
cannot be deployed.
- subflow node
- A message flow node that
represents a subflow.
- subscriber
- An application that requests information about a specified topic from a publish/subscribe broker.
- subscription
- A record that contains the information that a subscriber passes to its local broker to describe the publications that it wants to receive.
- subscription filter
- A predicate that specifies the subset of messages that are to
be delivered to a particular subscriber.
- subscription point
- The name that a subscriber uses
to request publications from
a particular set of publication
nodes. It is the property of a publication node that differentiates
that publication node from other publication nodes in the same message flow.
- substitution group
- An XML Schema feature
that provides a means of substituting one element for another in an XML message. A substitution group
contains a list of global elements that can appear in place of another
global element, called the head element.
- Supervisory, Control, And Data Acquisition
(SCADA)
- A term used to describe any form of remote telemetry system that
is used to gather data from remote sensor devices (for example, flow
rate meters on an oil pipeline) and for the near real time control
of remote equipment (for example, pipeline valves). These devices
communicate with the broker using the SCADA
device protocol (MQIsdp).
- system log
- See local error log.
TOP
T- Tagged/Delimited String (TDS) Format
- The physical representation of a message in
the MRM domain that
has a number of data elements
separated by tags and delimiters.
- TDS Format
- See Tagged/Delimited String
Format.
- terminal
- The point at which one node in
a message flow is connected
to another node. You can connect terminals to control the route that
a message takes, dependent on the outcome of the operation that is
performed on that message by the node.
- topic
- A character string that describes the nature of the data that
is published in a publish/subscribe system.
- topic based subscription
- A subscription specified
by a subscribing application that includes a topic that filters publications.
- topic security
- The application of ACLs to
one or more topics to control subscriber access to published
messages.
- topology
- See publish/subscribe topology.
- transform
- A defined way in which a message of one format is converted into one or
more messages of another format.
- tree node
- An element in a mapping tree; a container for the mapping type
such as a message, database table, a column, or a basic element.
- type
- A characteristic of an element that
describes its data content. See also simple type and complex type.
TOP
U- Unicode Transformation Format, 8-bit encoding
form (UTF-8)
- A transformation format that is designed for ease of use with
existing ASCII-based systems. UTF-8 is an encoding of Unicode character
strings that optimizes the encoding of ASCII characters in support
of text-based communication.
- uniform resource identifier (URI)
- An encoded address that represents any resource, such as an HTML
document, image, video clip, or program, on the Web; a URI is an abstract
superclass compared with a Uniform
resource locator or a Uniform
resource name, which are concrete entities.
- uniform resource locator (URL)
- A sequence of characters that represent information resources
on a computer or in a network such as the Internet. This sequence
of characters includes:
- The abbreviated name of the protocol that is used to access the
information resource
- The information that is used by the protocol to locate the information
resource
A Web server typically maps the request portion of the URL to
a path and file name. Also known as universal resource locator.
- uniform resource name (URN)
- A name that uniquely identifies a Web service to a client.
- URI
- See uniform resource identifier.
- URL
- See uniform resource locator.
- URN
- See uniform resource name.
- user-defined extension
- An optional component that is designed by the user to extend the
functions of WebSphere Message Broker. A user-defined
extension can be either a node or
a message parser. See also user-defined
node and user-defined parser.
- user-defined node
- An extension to the broker that provides a new message flow node in addition
to those that are supplied with the product. See also implementation function and utility function.
- user-defined parser
- An extension to the broker that provides a new message parser in addition to those
that are supplied with the product. See also implementation function and utility function.
- User Name Server
- A component that interfaces
with operating system facilities to determine valid users and groups.
- UTF-8
- See Unicode Transformation
Format.
- utility function
- A function provided by the broker that can be used by developers
who write user-defined nodes or parsers.
TOP
V- value constraint
- A limit that sets a restriction on the values that a simple type can represent.
- view
- In Eclipse-based user interfaces, a pane that is outside the editor
area, which can be used to look at or work with the resources in the workbench.
For example, you can view and edit your project files in the Broker
Development view (previously called the Resource Navigator view).
See also perspective.
TOP
W- warehouse
- A persistent, data store for historical events (or messages).
The Warehouse node within
a message flow supports the
recording of information in a database for subsequent retrieval and
processing by other applications.
- Web service
- A self-contained, self-describing modular application that can
be published, discovered, and invoked over a network using standard
network protocols. Typically, XML is used to tag the data, SOAP is
used to transfer the data, WSDL is used for describing the services
available, and UDDI is used for listing what services are available.
- Web Services Description Language (WSDL)
- An XML-based specification for describing networked services as
a set of endpoints that operate on messages that contain either document-oriented
or procedure-oriented information. A WSDL document enables a Web services
client to invoke a Web service using
the messages defined in a message
definition.
- WebSphere MQ Enterprise
Transport
- A transport protocol supported by WebSphere Message Broker that enables WebSphere MQ application clients to
connect to brokers.
- WebSphere MQ Everyplace
- A generally available WebSphere MQ product
that provides proven WebSphere MQ reliability
and security for mobile and wireless devices. WebSphere MQ Everyplace® applications connect to the
broker using WebSphere MQ Mobile Transport.
- WebSphere MQ Mobile Transport
- A transport protocol supported by WebSphere Message Broker that enables WebSphere MQ Everyplace application
clients to connect to brokers.
- WebSphere MQ Multicast Transport
- A transport protocol supported by WebSphere Message Broker that enables dedicated JMS application clients to connect
to brokers. This protocol is optimized for high volume, one-to-many publish/subscribe topologies.
- WebSphere MQ Real-time Transport
- A transport protocol supported by WebSphere Message Broker that enables dedicated JMS application clients to connect
to brokers.
- WebSphere MQ Telemetry Transport
- A transport protocol supported by WebSphere Message Broker that enables SCADA devices to connect to
brokers. This protocol is a lightweight publish/subscribe protocol that
flows over TCP/IP that uses a subset of UTF-8.
- WebSphere MQ Web Services Transport
- A transport protocol supported by WebSphere Message Broker that enables HTTP compliant
application clients to connect to brokers.
- wild card
- A character that can be specified in subscriptions to match a
range of topics. See also multilevel
wild card and single-level
wild card.
- workbench
- The user interface and integrated development environment (IDE)
in Eclipse and Eclipse-based tools such as IBM Rational Application
Developer.
work_path
The location in the local file system in which the component stores
internal and working data. For example, the default location on Windows systems
is C:\Documents and Settings\All Users\Application Data\IBM\MQSI\.
- working set
- A logical collection of application projects, that you can use
to limit the number of resources that are displayed in the Broker
Application Development perspective. See also active working set.
- World Wide Web Consortium (W3C)
- An international industry consortium set up to develop common
protocols to promote the evolution and interoperability of the World
Wide Web.
- WSDL
- See Web Services Description
Language.
- W3C
- See World Wide Web Consortium.
TOP
X- XML
- See Extensible Markup Language.
- XML domain
- The message domain that includes all messages that conform to
the W3C XML standard. Messages in this domain are processed by the XML parser. See also BLOB domain, IDOC domain, JMS domain, MIME domain, MRM domain, XMLNS domain, and XMLNSC domain.
- XML parser
- A program that interprets a message that belongs to the XML domain and JMS domains, and generates
the corresponding tree from the bit stream on input, or the bit stream
from the tree on output. The bit stream is a representation of an
XML file.
- XMLNS domain
- An extension of the XML
domain that contains messages that conform to the W3C XML standard,
and that can also exploit the namespaces specification.
Messages in this domain are processed by the XMLNS parser. See also BLOB domain, IDOC domain, JMS domain, MIME domain, MRM domain, XML domain, and XMLNSC domain.
- XMLNS parser
- A program that interprets a message that belongs to the XMLNS domain , and generates
the corresponding tree from the bit stream on input, or the bit stream
from the tree on output. The bit stream is a representation of an
XML file.
- XMLNSC domain
- An extension of the XML domain that provides high-performance
XML parsing and offers optional XML Schema validation. Messages in
this domain are processed by the XMLNSC
parser. You can create a message
model for messages that you process in this domain, but a model
is only necessary if you want to validate the message. See also BLOB domain, IDOC domain, JMS domain, MIME domain, MRM domain, XML domain, and XMLNS domain.
- XMLNSC parser
- A program that interprets a message that belongs to the XMLNSC domain , and generates
the corresponding tree from the bit stream on input, or the bit stream
from the tree on output. The bit stream is a representation of an
XML file.
- XML Path Language (XPath)
- A language designed to uniquely identify or address parts of a
source XML document, for use with XSLT. It can also be used by Java programs within a JavaCompute
node, or as the expression language within a Mapping node , or by
the properties of several other nodes, to provide basic facilities
for the manipulation of strings, numbers, and Boolean values.
- XML Schema
- An international standard that defines a language for describing
the structure of XML documents.
An XML Schema formally describes and constrains the content of XML
documents by indicating which elements are valid and in which combinations.
(An XML Schema is an alternative to a document
type definition (DTD), and can be used to extend functionality
in the areas of data typing, inheritance, and presentation.) The XML
Schema language is ideally suited to describing the messages that
flow between business applications, and is widely used in the business
community for this purpose. Message definitions are annotated XML
Schema.
- XML Schema Definition Language (XSD)
- A language for describing XML files that contain XML Schema.
- XML Wire Format
- The physical representation of a message in
the MRM domain that
can be parsed as XML.
- XPath
- See XML Path Language.
- XSD
- See XML Schema Definition
Language (XSD).
- XSL
- See Extensible Stylesheet Language.
TOP