Glossary of terms and abbreviations

This glossary defines WebSphere Message Broker terms and abbreviations used in this online information.

There is also a migration glossary that lists differences in terminology between WebSphere Message Broker Version 6.0 and previous versions of the product.

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z

A
access control list (ACL)
In computer security, a list associated with an object that identifies all the subjects that can access the object and 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.
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
In XML, a name-value pair within a tagged element that modifies certain features of the element. In other message domains, a simple element within a message. An attribute requires special treatment when used with XML messages. In messages that are not XML, an attribute is treated exactly like a simple element based on the same simple type.
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 that have content that cannot be interpreted and subdivided into smaller sections of information. Messages in this domain are processed by the BLOB parser. See also IDoc domain, JMS domain, MRM domain, and XML domain.
BLOB parser
A program that interprets a bit stream or message tree that represents a message that belongs to the BLOB domain, and generates the corresponding tree from the bit stream on input, or a 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. It contains any number of compiled message flows (.cmf), message sets (.dictionary), and a single deployment descriptor. It can also contain any additional files you might need as long as the extension does not overlap the .cmf and .dictionary extensions.
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 defined within it. The resources are message flows, ESQL files, and mapping files.
built-in node
A message flow node that is supplied by the product. A number of 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 are 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 transmission to the broker. A cmf 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 structure within a message. A complex type 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. It is used, for example, in the workbench and in commands. Each component requires a name.
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, and deployed message flows, and the 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.
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 system. Database support is limited to Derby and DB2. The Database Instance Manager is associated with a Windows service.
data element separation
A delimiter sequence that defines how a TDS message is to be parsed. The following separation types are supported: data pattern separation, delimited separation, fixed length separation, and tagged separation
Start of changeDataFlowEngine (DFE)End of change
Start of changeSee execution group.End of change
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. See also request/reply.
debugger
See flow debugger.
deploy
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 delivered by IBM Cloudscape Version 10.0, which is built on the Derby database from the Apache Software Foundation. Cloudscape does not modify Derby in any way, but provides additional function including installers. 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 period-separated values that identify a specific field (which might be a structure) within a message tree or a database table. The path from the root of the information to the specific field is traced using the parent/child relationships. An example of a field reference might be something like 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 the value that results from the implementation of the expression to the caller. 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 that has been generated during the processing of a message, with supporting information.
execution group
A named process or set of processes within a broker in which message flows are run. The broker is guaranteed to enforce some degree of isolation between message flows in distinct execution groups because it ensures that they run in separate address spaces, or as unique processes.

Start of changeAn 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.End of change

extended SQL (ESQL)
A specialized set of SQL functions and statements based on regular SQL, extended with functions and statements unique to WebSphere Message Broker.
extensible markup language (XML)
A standard metalanguage for defining markup languages that was derived from and is a subset of Standard Generalized Markup Language (SGML).
extensible stylesheet language (XSL)
A language for specifying style sheets for XML documents. XSL 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
(1) An ESQL expression that is applied to the content of a message in a Filter node to determine how the message is processed.
(2) An ESQL expression that is applied to the content of a publication message to determine if the message matches certain criteria.
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 across the MQSeries link for R/3. Messages in this domain are processed by the IDoc parser. See also BLOB domain, JMS domain, MRM domain, and XML domain.
IDoc parser
A program that interprets a bit stream or tree that represents a message that belongs to the IDoc domain, and generates the corresponding tree from the bit stream on input, or 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.
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 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, MRM domain, and XML domain.
Job Control Language
Job Control Language (JCL) comprises a set of Job Control Statements, which 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 is implemented in the same way as a dynamic link library, but has a file extension of .lil rather than .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 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 by creating a target value expression.
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 sent from a person or program to another person or program. In WebSphere Message Broker, a message can be modeled by a message definition which describes the structure and content of the message. Messages must have a structure and format which is agreed by the sending and receiving applications.
message broker
See broker.
Message Brokers Toolkit
The WebSphere Message Broker development environment that integrates with IBM Rational Application Developer which is based on the IBM WebSphere Eclipse Platform. Also known as the workbench.
message definition
A logical description of a message. A message definition is a structured collection of simple elements.
message definition file
A file that contains the messages, elements, types, and groups that make up a message set.
message dictionary
A data structure that describes all of the messages in a message set in a form suitable for deployment to a broker.
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, and XML 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 message element aggregation occurs when 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. A message flow node can be either a built-in node, a user-defined node, or a subflow node. Also called message processing node.
message flow node connection
An entity that connects the output terminal of one message flow node to the input terminal of another. A message flow node connection represents the flow of control and data between two message flow nodes.
message model
A definition of a message format that is used by applications. You define a message model in the workbench.
message parser
A program that interprets the bit stream of 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 provided by WebSphere MQ queue managers. The programming interface allows application programs to access message queuing services. See also Application Messaging Interface (AMI) and Java Message Service (JMS). Applications using the MQI connect to the broker using WebSphere MQ Enterprise Transport.
message set
A container; a logical grouping of messages and associated message resources (elements, types, groups).
message set documentation
A human-readable form of message definitions that you have created in the workbench.
message set project
A specialized container in which you create and maintain all the resources associated with one message set.
message template
A named and managed entity that represents the format of a particular message. Message templates represent a business asset of an organization.
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.
message type
The logical structure of the data within a message; for example, the number and location of character strings.
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.
MIME parser
A program that interprets a bit stream or tree that represents a message that belongs to the MIME domain, and generates the corresponding tree from the bit stream on input, or 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 MQSeries Publish/Subscribe SupportPac.
MQRFH2
An extended version of MQRFH, providing enhanced function in message processing.
MRM
The name given to the domain and parser associated with messages that are modeled in the workbench. MRM stands for Message Repository Manager and is used only to identify the MRM parser and MRM domain.
MRM domain
The message domain that includes all messages that are modeled in the workbench. Message models can be created to represent a wide range of message types, with one or more optional physical formats. Messages in this domain are processed by the MRM parser. See also BLOB domain, IDoc domain, JMS domain and XML domain.
MRM parser
A program that interprets a bit stream or tree that represents a message that belongs to the MRM domain, and generates the corresponding tree from the bit stream on input, or 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 allows different forms of data including video, audio, or binary data to be attached to e-mail without requiring translation into ASCII text.

TOP

N
namespace
In XML, a uniform resource identifier (URI) that provides a unique name to associate with all the elements and type definitions in a schema. XML instance documents and XML schemas can make use of 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. ODBC is based on the call level interface (CLI) specification of the X/Open SQL Access Group.
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. The user can switch perspectives, depending on the task at hand, and customize the layout of views and editors within the perspective. 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.
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 with an appropriate set of properties and in the correct context. 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 supported by the underlying facility.
property
A characteristic that, as one of a set of characteristics, defines the values and behaviors of objects in the workbench. For example, message flow nodes and deployed message flows have properties.
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 they can get messages.
queue manager
A system program that provides queuing services to applications. It provides an application programming interface (the MQI) to enable 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. See also datagram.
resource
A file of any type that exists in the workbench. You can view and edit a resource in the Resource Navigator view in the workbench.
Resource Recovery Services (RRS)
A z/OS facility that provides two-phase sync point support across participating resource managers.
retained publication
A published message that is kept at the broker for propagation to clients that subscribe at some point 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 the message model. For example, a message coded in XML is 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.
SQL
See Structured Query Language.
stream
A method of topic partitioning that is used by applications that connect to MQSeries Publish/Subscribe SupportPac brokers.
Structured Query Language (SQL)
A standardized programming language that is used to define and manipulate data in a relational database. ESQL, the language 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 a 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 performed by the node on that message.
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 for filtering of 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 an MRM message, RDB 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. As opposed to a Uniform resource locator or a Uniform resource name, which are concrete entities, a URI is an abstract superclass.
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 (a) the abbreviated name of the protocol used to access the information resource and (b) the information 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 node
An extension to the broker that provides a new message flow node in addition to those 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 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
A display are in the workbench in which you can navigate and edit your information and resources. For example, the Resource Navigator view enables you to view and edit your project files. See also perspective.

TOP

W
warehouse
A persistent, historical data store for 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 modular application that performs specific tasks and is accessible through open protocols like HTTP and SOAP.
Web Services Description Language (WSDL)
An XML-based specification for describing networked services as a set of endpoints operating on messages containing 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
See Message Brokers Toolkit
World Wide Web Consortium (W3C)
An international industry consortium set up to develop common protocols to promote 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. The XMLNS domain is an extension of the XML domain and contains messages that conform to the same standard and that can exploit the namespaces feature of the XML specification. Messages in this domain are processed by the XML parser. See also BLOB domain, IDoc domain, JMS domain, and MRM domain.
XML parser
A program that interprets a bit stream or tree that represents a message that belongs to the XML domain and JMS domains, and generates the corresponding tree from the bit stream on input, or bit stream from the tree on output. The bit stream is a representation of an XML file.
XML Path Language
An XSL sublanguage designed to uniquely identify or address parts of a source XML document, for use with XSLT. XPath also provides basic facilities for 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 allowed 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 which flow between business applications, and it is widely used in the business community for this purpose.
XML Wire Format
The physical representation of a message in the MRM domain that can be parsed as XML.
XPath
See XML Path Language.
XSL
See extensible stylesheet language.

TOP