Glossary

 

This glossary defines terms that are used in the documentation for BEA WebLogic Integration.^TM Text in blue indicates terms that are included in this glossary. For definitions of BEA WebLogic Server^TM terminology, see the WebLogic Server Glossary at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs61/glossary/index.html

Click a letter in the glossary index. Or use the Page Down key, the Page Up key, the arrow keys, or the scroll bar to navigate. Please contact us if you know of a relevant term that is not defined in this glossary.

 

— A —

access control list (ACL)

Data structure used to authorize or deny access to resources by principals. Human users of WebLogic Integration can be authorized to access three types of resources: Java Server Pages (JSPs) for administrative and configuration purposes; administration consoles; and the JDBC connection pool. You can authorize trading partners to access the transport servlet and the WebLogic Server JDBC connection pool. WebLogic Integration is authorized to access the transport servlet.

ACL

See access control list (ACL).

action

Basic unit of work performed by the business process management component of WebLogic Integration. Actions define workflow and task behavior, and can be defined as part of tasks, decisions, and events. Numerous actions are shipped with WebLogic Integration.

adapter

A software component that provides an interface between an enterprise information system and an integration server.

Administration Console

See WebLogic Integration B2B Console and WebLogic Server Administration Console.

Apache XML Parser

Third-party parser, provided by the Apache Software Foundation, that implements the W3C XML, DOM, and SAX standards.

application adapter

A software component that provides an interface between an enterprise information system and an integration server. An application adapter represents a system-level interface to all of the functionality in the application.

application integration

A JCA standards-based integration broker developed by BEA Systems, Inc. for inter- and intra-enterprise integration. Application integration is a component of WebLogic Integration.

application server

A server that provides sharing and processing of application logic, and connections to back-end resources. Resources include databases, ERP applications, and traditional mainframe applications. Application servers also provide user interface development mechanisms. Additionally, they usually provide mechanisms to deploy an application to the platform of the Web.

application view

A business-level interface to the functionality in an application. An application view is configured for a single business purpose, and contains only services related to that business purpose. Additionally, an application view represents both events and services that support a business purpose, allowing the business user to interact with the application view for all communication with an application.

attachment

Information that is sent with a business message.

authentication

Process by which WebLogic Integration establishes the identity of a principal.

authorization

Permission granted to WebLogic Integration principals to access certain resources.

Trading partner authorization is a role-based security feature whereby a trading partner is allowed to send and receive certain types of messages as defined by the trading partner's subscription in a specific conversation. Trading partners are authorized to access the transport servlet and the JDBC pool.

Human users can be authorized to access JSPs and, indirectly, the JDBC pool. A WebLogic Server access control list (ACL) can be configured selectively to allow or deny a user access to a resource.

WebLogic Integration is authorized to access the transport servlet in order to send messages to trading partners.

— B —

B2B

See business-to-business (B2B) e-commerce.

B2B integration

The WebLogic Integration feature that provides business-to-business integration functionality. See also business-to-business (B2B) e-commerce.

B2B plug-in

WebLogic Integration Studio component that extends business process management (BPM) for use with B2B integration.

binary data

A file format for data encoded as a sequence of bits, but not necessarily consisting of a sequence of printable characters (text). The term is often used to describe executable machine code.

big endian

Binary format in which the most significant byte has the lowest address. This format is used on IBM 370 systems and most RISC designs.

BizTalk

BizTalk^TM is an industry initiative started by Microsoft and supported by a wide range of organizations, including technology vendors such as SAP, CommerceOne, and Ariba, and technology users such as BASDA. BizTalk is not a standards body, but a community of standards users that is defining the BizTalk Framework, a set of guidelines for publishing XML schemas and using XML messages. See also http://www.biztalk.org.

BPM

See business process management (BPM).

browser client

Trading partner that uses a Web browser to communicate with other trading partners.

BTP

See business transaction protocol (BTP).

Bulk Loader

The WebLogic Integration utility that exports repository data to an XML file, imports XML data into the repository, and deletes data from the repository. The Bulk Loader can also be used to migrate repository data from one environment to another; for example, from one supported database to another. The Bulk Loader supports several JDBC databases.

business document

XML part of the payload of a business message.

business message

Basic unit of communication exchanged between trading partners in a conversation. A business message is a multipart MIME message that consists of business documents, attachments, and message headers.

business operation

Method of adding user-defined operations in WebLogic Integration by invoking EJBs or calling Java classes.

business process management (BPM)

The WebLogic Integration automation tool that enables you to define and monitor workflows.

business protocol

Set of rules that governs the electronic exchange of business information between enterprises across a network. A business protocol specifies the structure of business messages, the mehtod for processing the messages, and the method for routing them to the appropriate recipients. WebLogic Integration trading partners can use the XOCP, RosettaNet, and cXML business protocols to send and receive business messages.

business protocol definition

Set of logic plug-ins that implements a business protocol.

business protocol XPath filtering expression

XPath expression that can block messages passed by previous XPath filtering expressions. A business protocol XPath filtering expression is part of an XOCP filter logic plug-in, is specified in the repository by an administrator, and is defined for a particular WebLogic Integration instance. A business protocol XPath filtering expression applies to all messages that the WebLogic Integration instance receives for all trading partners. Each expression can examine different parts of the message-context XML document and return True or False, using different selection criteria. The business protocol XPath filtering expressions make up the final set of XPath expressions that evaluate messages before those messages are finally received by trading partners.

business protocol XPath routing expression

XPath expression that specifies all messages that can be sent from the WebLogic Integration instance. A business protocol XPath routing expression is part of an XOCP router logic plug-in, is specified in the repository by an administrator, and is defined for a particular WebLogic Integration instance. A business protocol XPath routing expression is evaluated after the interaction specifications and trading partner XPath routing expressions are evaluated, and thus can modify or override the list of trading partners selected by those expressions.

business service

Interface to a conversation definition. A trading partner offers a business service to other trading partners who may want to interact with the trading partner that is offering the business service.

business-to-business (B2B) e-commerce

The practice of buying and selling among companies through electronic transactions.

business-to-business (B2B) integration

Inter-enterprise application integration that includes supply-chain integration between enterprises.

business-to-consumer integration

The process of exposing information within an enterprise to people or entities, known and unknown, that exist outside of the enterprise.

business transaction protocol (BTP)

Standard that provides an open and well-defined method for managing long-running, complex transactions common in B2B e-commerce. BTP is an XML-based vocabulary protocol for representing and seamlessly managing complex, multistep B2B transactions over the Internet. BTP enables trading partners to manage complex XML message exchanges as long-running, loosely coupled conversations.

— C —

certificate authenticator

Standard interface defined in WebLogic Server to map digital certificates to WebLogic Server users. After verifying an incoming certificate, the certificate authenticator maps the incoming trading partner associated with the certificate to the corresponding WebLogic Server user, based on the certificate.

certification authority

Well-known and trusted organization, such as VeriSign, that issues digital certificates for the purpose of authenticating a certificate holder's identity to another party.

chain

Multiple logic plug-ins that share the same business protocol and are processed in a predefined sequence at run time. A chain may be either a router or a filter. A router consists of multiple router logic plug-ins and a filter consists of multiple filter logic plug-ins. In other words, router logic plug-ins form one chain, and filter logic plug-ins form another chain.

WebLogic Integration executes each router logic plug-in as a business message passes through the router. Then WebLogic Integration executes each filter logic plug-in as a business message passes through the filter. In other words, the logic plug-ins in the router chain are executed before the logic plug-ins in the filter chain.

After one logic plug-in has been executed, the next one in the sequence (in the chain) is activated. Each successive logic plug-in can access the shared message information as the business message passes through WebLogic Integration. A logic plug-in can modify or override the changes made by preceding logic plug-ins in the chain.

If logic plug-ins are supplied by a customer, they must be part of a router logic plug-in chain or a filter logic plug-in chain, even if they do not perform routing or filtering functions.

CLASSPATH

A list of file system directories or Java archive files that are to be searched by a Java Virtual Machine (JVM) to locate executable class files required at run time. The list may be supplied via an operating system environment variable (CLASSPATH) or a command-line switch (-classpath) sent to the virtual machine. Application server containers, such as servlet engines and EJB containers, may contain additional levels of classpath information.

client connector interface (CCI)

An interface that allows a J2EE-based application to connect to and access back-end systems. The CCI manages the flow of data between the client application and the back-end system, and does not have any visibility into what either the container or the application server are doing with the adapter.

cluster

Group of servers that work together to provide an application platform that is more powerful and reliable than a single server. A cluster appears to its clients as a single server but it is, in fact, a group of servers acting as one. If properly designed and configured, a cluster can provide both availability and scalability. Furthermore, it should be possible to dynamically add new processes and machines to a cluster to handle increased load without shutting down the cluster. It should also be possible to remove individual servers from the cluster, periodically, in order to perform maintenance.

COBOL Copybook Importer

Reads a COBOL Copybook and generates a message format reflecting the data structure of the COBOL Copybook.

code page

In the context of this documentation, the character encoding of the field data.

collaboration agreement

Definition of the interactions that trading partners agree to carry out, along with a specification for the methods through which these interactions are conducted. This specification includes details about transport, messaging, security constraints, and bindings to a process specification.

collaborative workflow

Workflow used by trading partners to implement a role while conducting business with the B2B integration component of WebLogic Integration.

CollaboratorMBean

MBean interface that represents trading partners in a run-time environment. WebLogic Integration management applications can use CollaboratorMBean objects to monitor trading partners.

commerce XML (cXML)

A business protocol for the consistent exchange of business documents between procurement applications, e-commerce networks, and suppliers.

Confirmed_Delivery_to_Destination

Quality of Service (QoS) option that verifies receipt of a message by all recipient trading partners. Delivery can be made more reliable by use of options such as Retry Attempts and Durability (Persistent option). Confirmed_Delivery_to_Destination can also provide additional information to the sender and administrators, including delivery status from recipients, complete message tracking for administrators, and confirmation from the B2B integration component of WebLogic Integration upon completion of delivery. Availability depends on the business protocol that is used.

Confirmed_Delivery_to_Hub

Default Quality of Service (QoS) option that verifies receipt of a message by the B2B integration component of WebLogic Integration. This option is often used when system performance is an issue. It does not provide delivery status from recipients, nor does it provide message tracking. Because the selection process for trading partners is performed after confirmation reaches the sender, no information about potential recipients is available. Availability depends on the business protocol that is used.

Confirmed_Routing

Quality of Service (QoS) option for XOCP that verifies delivery when a message reaches the router component. This option provides a list of the trading partners selected by the router to receive the message. The administrator for the sending trading partner receives message tracking information repeatedly until the message reaches the router. Availability depends on the business protocol that is used.

conversation

Series of message exchanges between trading partners. A conversation is defined by a collaboration agreement. The choreography of the message exchanges is determined by the conversation definition, which is part of the collaboration agreement.

conversation coordinator

Service that manages conversation life cycles, according to the rules of the corresponding business protocols, and supports long-living, durable conversations that span multiple organizational boundaries. The conversation coordinator generates conversation IDs; registers trading partners in a conversation; delivers business and system messages to clients; maintains status information about conversations; and provides the conversational context for execution of the business protocol.

conversation definition

Collection of values that specifies the parameters of a conversation.

ConversationHandler

Interface that enables a trading partner to send and receive business messages in conversations. A conversation handler must be registered for one or more conversation types in order for the associated trading partner to participate in conversations.

conversation initiator

Trading partner that initiates and terminates a conversation.

conversation life cycle

The period during which messages are exchanged between trading partners.

ConversationMBean

MBean interface that represents a conversation. WebLogic Integration management applications use ConversationMBean objects to monitor conversations in a run-time environment.

conversation participant

Trading partner that receives and processes business messages.

conversation termination

Intelligent and controlled cessation of message exchanges performed by the B2B integration or business process management (BPM) component of WebLogic Integration. For BPM clients, a conversation is terminated when the conversation initiator reaches a done state, as defined by the conversation termination property (Success or Failure) for the done node. A conversation participant can end its own participation in a conversation, but only conversation initiator workflows can terminate a conversation. For B2B integration clients, conversation termination is initiated by the Conversation.terminate() operation, which is performed by the conversation initiator. As a result of this operation, each conversation participant receives a ConversationHandler.onTerminate() message.

copybook

A common piece of source code designed to be copied into many source programs; used mainly in IBM DOS mainframe programming. In mainframe DOS (for example, DOS/VS and DOS/VSE), the copybook was stored as a book in a source library. A library comprised of books, the name of each of which began with a letter prefix designating a programming language (for example, A.name for Assembler, C.name for COBOL) because DOS did not support multiple or private libraries. This term is mainly used by COBOL programmers, but it is supported by most mainframe languages. The IBM OS series did not use the term copybook; instead, it referred to such files as libraries implemented as partitioned data sets or PDSs. A copybook is functionally equivalent to a C or C++ include file.

Correlation ID

Quality of Service (QoS) option that contains the message identification string. It can be used to correlate different business messages within an application. Availability depends on the business protocol that is used.

cXML

See commerce XML (cXML).

cXML filter

A logic plug-in chain that consists of the following logic plug-ins in this order:
(1) a cXML filter logic plug-in, which is provided by WebLogic Integration; and
(2) optional customer-supplied logic plug-ins.

cXML filter logic plug-in

A logic plug-in that determines which cXML business messages a trading partner will receive. The cXML filter logic plug-in is one of the logic plug-ins in the cXML filter.

cXML router

A logic plug-in chain that consists of the following logic plug-ins in this order:
(1) a cXML router logic plug-in, which is provided by WebLogic Integration;
(2) optional customer-supplied logic plug-ins; and
(3) a cXML router enqueue logic plug-in.

cXML router enqueue logic plug-in

A logic plug-in that queues a cXML message for potential delivery to a recipient.

cXML router logic plug-in

A logic plug-in that assigns the recipient for a cXML message.

— D —

data integration

The WebLogic Integration component that translates XML files to non-XML format, and vice-versa.

data integration plug-in

WebLogic Integration Studio component that extends business process management (BPM) for use with data integration.

data privacy

An SSL-based security feature in WebLogic Integration that provides link-level encryption of messages in communications between trading partners. Human users do not have data privacy (SSL) when their names and passwords are used for identification. A digital certificate is required to provide data privacy.

data transformation

In the context of WebLogic Integration documentation, data transformation refers to the mapping of data provided in one XML format to another XML format. For example, data transformation is performed when a RosettaNet document is mapped to an ebXML document.

data translation

In the context of WebLogic Integration documentation, data translation is the process of converting binary data to or from XML.

data universal numbering system (DUNS)

Standard for assigning nine-digit strings, as internationally-recognized identifiers, to companies that engage in global electronic commerce transactions. Business identifiers are assigned to trading partners for external use by some business protocols; they differ from internal WebLogic Integration trading partner names. Implementations of the RosettaNet business protocol must use DUNS numbers. Implementations of the cXML or XOCP business protocols have the option of using DUNS numbers.

decision

The business process management (BPM) term for a workflow component that contains a condition to be evaluated when a transition occurs. The result of the evaluation is either true or false, and it determines the appropriate dependent node to which subsequent flow control passes.

decoder

Component that processes the protocol-specific message headers, identifies the sending trading partner, enlists the sending trading partner in a conversation, prepares a reply for the sender, and forwards the message to the scheduling service.

deferred synchronous message delivery

Message delivery method whereby control is returned to the application once a message is sent. A message token is returned to the application, which the application can access later to check the status of message delivery. After the token is accessed, the application waits for a specified time or until one of the following events occur: acknowledgments are received from all potential destinations; the message times out; or the conversation in which the message was sent terminates.

delimiter

A sequence of bytes that denotes the end of a field or group of data.

delivery channel

Specification for delivering business messages to one trading partner. Each trading partner has a delivery channel for each business protocol that the trading partner supports.

digital certificate

Digital equivalent of an ID card that WebLogic Integration uses, with a public key encryption system, to authenticate trading partners. The digital certificate contains the owner's public key, which has been digitally signed by a certification authority.

digital signature

Security feature that establishes the identities of communicating entities. A digital signature can be trusted only to the extent that the public key used to verify the digital signature can be trusted.

document definition

Schema, such as a document type definition (DTD), that specifies the prerequisites for a valid document. WebLogic Integration document definitions are provided in XML DTDs. Each document definition includes two attributes: System ID (a DTD system identifier); and URL, which specifies the location of the document definition.

document exchange

Definition of the method through which a document is exchanged. A document exchange defines a business protocol and some run-time parameters.

document type definition (DTD)

File that specifies the format (grammar and syntax) to be used for associated XML messages or XML files. Defines what content can exist in an XML document. DTDs are part of the W3C XML specification.

done

A business process management (BPM) term for a workflow component that marks an entire workflow as complete. No further processing for any task occurs after this term is issued.

DTD

See document type definition (DTD).

DUNS

See data universal numbering system (DUNS).

Durability

Quality of Service (QoS) option that specifies whether a durable message store is used to guarantee message delivery in case of node failures. The options are namespace (default) and Persistent. Availability depends on the business protocol that is used.

— E —

ebXML

See electronic business XML (ebXML).

EDI

See Electronic Data Interchange (EDI).

EDI VAN

See Electronic Data Interchange Value-Added Network (EDI VAN).

EIS

See Enterprise Information System (EIS).

electronic business XML (ebXML)

Set of specifications for a modular electronic business framework. ebXML is a joint initiative of the United Nations (UN/CEFACT) and OASIS, developed for global usage.

Electronic Data Interchange (EDI)

Industry standard for the format of business messages used in e-commerce, and for the legal terms governing the use of such messages.

Electronic Data Interchange Value-Added Network (EDI VAN)

Third-party intermediary that routes EDI messages between trading partners.

end point

URL for a trading partner.

encoder

Component that transforms a message, as necessary, to support the required business protocol, and then forwards the message to the transport service.

Enterprise Application Integration (EAI)

The unrestricted sharing of information by two or more enterprise applications. A set of technologies that allow the movement and exchange of information between processes within and between organizations. (Linthicum 2000, p. 354)

Enterprise Information System (EIS)

A software system that provides the information infrastructure for an enterprise. An EIS offers a set of services to its clients. These services are made available to clients through local and/or remote interfaces. EIS examples include: an ERP system (for example, SAP R/3 or PeopleSoft), a Mainframe transaction processing system (for example, CICS), and a Legacy database system (for example, Oracle).

Enterprise JavaBeans (EJB)

A component architecture for the development and deployment of object-oriented, distributed, enterprise-level applications. Applications written using the Enterprise JavaBean architecture are scalable, transactional, and secure.

event

An occurrence within a software system (generally an EIS). If an event is of interest to an external party, it will cause the generation of an event object that is delivered to interested parties as an event notification.

event node

A business process management (BPM) term for a workflow. To execute an event node, the workflow waits for an XML message to trigger the event. When that trigger occurs, various sub-actions defined within the event node can be executed or workflow variables can be set.

event notification

A one-way asynchronous notification of an event within a system (generally an EIS). An event notification is achieved by delivering an event object representing the event to a subscriber for that type of event.

event object

A data object that represents an event within a system (generally an EIS). Event objects generally contain data sufficient to describe the event and the context in which it occurred. Event objects are often referred to simply as events. This is because event objects are the only representation of an event possible after the event has passed, and therefore are the lasting outcome of an event. An event object has a type that is a name used to refer to all events with the same cause. An event object contains an XML document that contains the data for the event.

extended property

User-defined element, attribute, or text that can be associated with entities in the repository. For this release, extended properties can be associated with trading partners only, through the WebLogic Integration B2B Console, or the Bulk Loader utility. These properties provide application extensions to the standard predefined attributes of trading partners. XPath routing expressions and XPath filtering expressions can reference these extended properties.

extensible markup language (XML)

Subset of SGML that is rapidly becoming a universal standard for defining, validating, and sharing data formats and documents. Because XML is text-based (that is, it is not written in binary format), and it uses syntax rather than binary markers to organize data, it can be deployed across heterogeneous and potentially incompatible systems and platforms. Its extensibility derives from markup symbols that are unlimited and self-defining, unlike those of HTML. Like HTML, XML can describe how a file is displayed. Unlike HTML, XML enables you to specify how a file is displayed. XML is a crucial component of the WebLogic Integration solution.

extensible open collaboration protocol (XOCP)

Default business protocol used by WebLogic Integration for B2B integration activities. Trading partners can use XOCP to send and receive message. XOCP provides support for conversation life cycle tracking, dynamic routing of messages, and the management of business interactions.

extensible style sheet language (XSL)

Language for specifying the format of an XML document.

eXtensible Stylesheet Language: Transformation (XSLT)

An XML language designed for transforming one XML document into another. An XSLT document, or stylesheet, describes data transformations that are to be performed on nodes of an XML document. Using XSLT, an XML document can be transformed into a variety of text formats (for example, XML, HTML, or PDF).

— F —

failover

Transfer of control to a backup component when a fault occurs.

field

A sequence of bytes that is interpreted by an application as an atomic unit of data.

file-sharing client

Trading partner that uses FTP to communicate with other trading partners.

filter

Set of one or more logic plug-ins for a specific business protocol. A filter determines which messages a trading partner will receive. To support B2B integration activities, WebLogic Integration provides an XOCP filter, a RosettaNet filter, and a cXML filter.

filter chain

See chain.

filtering expression

XPath expression in an XOCP filter logic plug-in.

filter logic plug-in

A logic plug-in in a filter. See RosettaNet filter logic plug-in, XOCP filter logic plug-in, and cXML filter logic plug-in.

FIX

The Financial Information Exchange (FIX) protocol is a messaging standard developed specifically for real-time electronic securities transactions.

— G —

GlobalConversationMBean

MBean interface that represents a conversation definition. B2B integration management applications use GlobalConversationMBean objects to monitor conversations in a run-time environment.

group

A set of fields (or groups) that is treated as a single unit.

group choice

A group made up of fields or other groups, of whichone is required. All the fields (or other groups) must be mutually exclusive in the terms of actual binary data they contain.

— H —

HTML

See Hypertext Markup Language (HTML).

HTTP proxy

Intermediary that represents the Internet for outgoing HTTP requests and represents many IP destinations for incoming requests.

hop timestamp

Facility through which each message is time-stamped upon its arrival in the B2B integration component of WebLogic Integration. No input is required from the application. A timestamp can be useful for debugging and measuring performance. Availability depends on the business protocol that is used.

Hypertext Markup Language (HTML)

The set of symbols in a file that governs the format of that file when it is displayed on a World Wide Web browser.

— I —

I18N

See internationalization (I18N).

interaction specification

A static XML document that contains secondary metadata about a service; for example, for a DBMS service adapter, the interaction specification would contain the SQL statement used to invoke a process on the database.

internationalization (I18N)

The tailoring of a software application to the customs and languages of specific locales, without recompilation or the use of binaries other than the originals.

Internet

The worldwide computer network of smaller, distributed networks that communicate via the TCP/IP protocols.

— J —

J2EE

See JAAS.

JAAS

See Java Authentication and Authorization Service (JAAS).

Java 2 Enterprise Edition (J2EE)

The Java^TM 2 Platform, Enterprise Edition (J2EE) defines the standard for developing multitier enterprise applications. J2EE simplifies enterprise applications by basing them on standardized, modular components, by providing a complete set of services to those components, and by handling many details of application behavior automatically, without complex programming.

Java Authentication and Authorization Service (JAAS)

The Java^TM Authentication and Authorization Service (JAAS) is a Java package that enables services to authenticate and enforce the use of access controls upon users.

Java Connector Architecture (JCA)

The Java Connector Architecture defines a standard architecture for connecting the J2EE platform to heterogeneous enterprise information systems. JCA defines a set of functionality that application service vendors must provide, and which back-end system vendors (for example, SAP, PeopleSoft, Siebel, Oracle, and third-party connector developers) can use to plug in to J2EE.

Java Database Connectivity (JDBC)

Java Database Connectivity is a Java specification for access to relational databases. JDBC is published by Sun Microsystems, Inc. For more information, see http://java.sun.com/products/jdbc/index.html.

Java Management Extensions (JMX)

Basis of the WebLogic Integration administration API. JMX, which is published by Sun Microsystems, Inc, is the standard API for management applications.

Java Message Service (JMS)

A standard application programming interface (API) and provider framework that enables the development of portable, message-based applications in the Java programming language.

Java Server Page (JSP)

A J2EE component that extends the Servlet class, and allows for rapid server-side development of HTML interfaces that can be comingled with Java.

Java Transaction API (JTA)

An API that allows applications and J2EE servers to access transactions.

Java Transaction Service (JTS)

Specifies the implementation of a transaction manager that supports JTA, and implements the Java mapping of the OMG Object Transaction Service (OTS) 1.1 specification at the level below the API.

JCA

See Java Connector Architecture (JCA).

JDBC

See Java Database Connectivity (JDBC).

JMS

See Java Management Extensions (JMX).

JMX

See Java Management Extensions (JMX).

join

Term for a workflow component that links business process management (BPM) events, tasks, and decisions, thus controlling the transitions between them. A join can be one of two types: AND or OR. If the join is an AND, all components linked by it must be satisfied before the successor to the join can be activated. If the join is an OR, only one of the components linked by that join must be satisfied in order to activate the successor to the join and continue the flow.

Joy

A user interface toolkit developed by BEA Systems, Inc. that takes XML documents as input, and creates an application's graphical user interface from the documents' content. Joy allows for the construction of extensible and highly customizable user interfaces.

JSP

See Java Server Page (JSP).

JTA

See Java Transaction API (JTA).

JTS

See Java Transaction Service (JTS)

— K —

(No terms begin with the letter "K")

— L —

L10N

See localization (L10N).

large message support

Feature that enables a WebLogic Integration administrator to request the storage of all messages above a certain size on disk rather than in memory, which is the default location. Unless otherwise specified, a message must be at least 3 kilobytes long to qualify for large message support.

legacy application

Stovepipe applications that may exist with many other similar stovepipe applications in a centralized environment. While most legacy applications run on mainframes, minicomputers and some large UNIX systems can be considered legacy systems using internally developed legacy applications.

little endian

Binary format in which bytes at lower addresses have lower significance. This format is used on Intel and VAX processors.

localization (L10N)

The application of the principles of internationalization to remove hard-coded values for items such as text, numbers, and icons from source code, replacing them with resource bundles that provide appropriate versions for specific locales.

logging

See log message and system log message.

logic plug-in

Value-added software that is installed on WebLogic Integration to provide additional processing of the information that passes through WebLogic Integration, and that is subject to guidelines and interfaces imposed by WebLogic Integration. WebLogic Integration provides router logic plug-ins and filter logic plug-ins for each business protocol that it supports.

WebLogic Integration customers can provide additional functionality by creating custom logic plug-ins that conform to the standards for the business protocol that is being used. Customer-provided logic plug-ins can provide functionality other than routing and filtering, such as billing. See cXML filter logic plug-in, cXML router logic plug-in, RosettaNet filter logic plug-in, RosettaNet router logic plug-in, XOCP filter logic plug-in, and XOCP router logic plug-in.

logic plug-in chain

See chain.

log message

Notification of a particular occurrence that is recorded in the local log. WebLogic Integration generates four different types of log messages based on the level of severity of the occurrence being reported: fatal, error, warning, and info. The log contains the complete message and the timestamp.

— M —

managed bean (MBean)

Java object (JavaBean) that, as part of the Instrumentation level in JMX architecture, contains attributes for management operations. In WebLogic Integration, MBean classes are used to monitor run-time information. MBeans are registered with the MBean server that runs inside WebLogic Integration. When MBeans are created, their attributes are populated from the repository. At run time WebLogic Integration updates MBean attributes to reflect the state of the running system. MBeans are implemented as Standard MBeans; that is, each class implements its own MBean interface. See CollaboratorMBean, ConversationMBean, and GlobalConversationMBean.

MBean

See managed bean (MBean).

message

See business message, log message, system log message, system transport message, and transport message.

message context

Information that enables recipients of a message to determine the structure and content of the message, as well as the conversation in which the message was sent. Specifically, the message context identifies the following: the relevant conversation, the message definition, the message parts, a content-type for each message part, and a document definition for each message part.

message-context XML document

File containing data used by XPath routing expressions and XPath filtering expressions to identify the trading partners intended to receive a message. A file of this type is generated by the B2B integration feature of WebLogic Integration from each XOCP message and associated information in the repository. A message-context XML document contains information carried in the message header and payload. Because a message-context XML document contains XPath expressions, and because XOCP is the only business protocol that supports XPath, XOCP is the only business protocol that uses message-context XML documents.

message definition

Specification of the business content, or payload (business documents and attachments) of a business message. A message definition consists of ordered message parts, the contents of which may be binary or XML. An XML message part defines a business document and requires a document definition. A binary message part defines an attachment and requires no other information.

message delivery method

See deferred synchronous message delivery and synchronous message delivery.

message envelope

Container for a business message as it travels through the B2B integration feature of WebLogic Integration. As the business message enters, B2B integration creates a message envelope for each intended recipient. In addition to the business message, the message envelope contains high-level routing and processing information, such as URLs for the sender and the recipient.

message filtering

Process used for one of several purposes: to restrict the type of messages received by a specific trading partner through the use of routers and filters; to restrict messages to a specified set of trading partners; or to implement matching algorithms so that information flows to the correct trading partners. See also logic plug-in.

message format

The description of a binary format produced by Format Builder.

message format language (MFL)

An XML language created by BEA Systems, Inc. that describes the native representation and hierarchy of binary data. MFL is an XML description of binary data.

message header

Part of a business message that contains attributes, such as information that identifies the sender and recipient, the conversation, and the Quality of Service (QoS).

message manipulator

Java class that implements the message manipulator interface com.bea.b2b.wlpi.MessageManipulator and that helps integrate B2B integration and business process management (BPM). A message manipulator uses BPM variables to create and process B2B integration business messages.

message token

Token that is returned to an application after the application sends a message. The token provides the following information: the message ID; the ID of the conversation in which the message was sent; whether the message was sent successfully; the amount of time that elapsed before all recipients sent acknowledgments, whether the Quality of Service (QoS) delivery option allows this information to be sent; the number of recipient destinations after the initial selection (router specifications applied); and the number of recipient destinations after the final selection (filter specifications applied).

message tracking

Feature that provides information about the status of a message as the message progresses through various predefined message-tracking locations in the B2B integration messaging system. WebLogic Integration administrators can use message-tracking information for debugging and to identify bottlenecks in the system. The availability of message-tracking locations depends on the configuration of the WebLogic Integration system, the Quality of Service (QoS) for the message, and the business protocol.

message XPath routing expression

XPath expression that specifies the initial list of recipient trading partners for a message. A message XPath routing expression is part of the XOCP router logic plug-in, is dynamically specified by the sending trading partner, and can support references to extended property in the message-context XML document that is generated for the message. Message XPath routing expression specifications can be modified or overridden by trading partner XPath routing expressions and business protocol XPath routing expressions.

metadata

Data used to indicate the purpose, meaning, or location of other data. Database schemas and XML DTDs are examples of metadata.

multicast

Broadcast of an XOCP message from one trading partner to many trading partners.

— N —

namespace

An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.

nonpersistent

Default Durability Quality of Service (QoS) option whereby a message is not stored anywhere in the WebLogic Integration system. A message sent with this option is not recoverable in the event of a whole or partial system failure that occurs while the message is enroute to its destination. Messages delivered with this option use fewer system resources and thus provide better throughput.

nonrepudiation

Mechanism that provides legal proof that a message was sent or received. Nonrepudiation of origin provides legal proof that a message was sent; it links a received message to the sender of the message. Nonrepudiation of receipt provides legal proof that a message was received; it links a processed message to the recipient of the message.

— O —

OASIS

See Organization for the Advancement of Structured Information Standards (OASIS).

OBI

See Open Buying on the Internet (OBI).

Open Buying on the Internet (OBI)

A consortium of companies, including BEA Systems, that develops and deploys open, platform-neutral standards for Internet-based procurement.

Organization for the Advancement of Structured Information Standards (OASIS)

International consortium dedicated to the rapid adoption of product- and platform-independent formats based on public standards, such as XML. OASIS operates www.xml.org, a site that offers resources, and that functions as a repository for XML specifications, such as vocabularies, DTDs, schemas, and namespaces.

— P —

packaged application

Any type of application that is purchased rather than developed. Such applications contain reusable business processes that represent best-of-breed business models, and do not require a full-scale development effort.

parser

See Apache XML Parser.

partner interface process (PIP)

One of a set of RosettaNet protocols that specify the choreography of messages. A PIP is the RosettaNet equivalent of a conversation definition.

party

Entity that binds a role in a conversation definition to a trading partner in a collaboration agreement.

payload

Business content of a business message, consisting of one or more business documents and attachments.

Persistent

Durability Quality of Service (QoS) option whereby a message is stored at, and forwarded from multiple locations between its source and destination, during the course of its delivery, as a safeguard in case of machine failures. This process is called persisting a message. An application can direct the system to persist messages on a per-message or per-conversation basis. However, the B2B integration component of WebLogic Integration must be recoverable in order for the message to persist. Persistence is achieved at the expense of system throughput. A persistent message travels more slowly and consumes more resources than a message that is namespace.

PIP

See partner interface process (PIP).

plug-in

See logic plug-in and B2B plug-in.

principal

Entity that requires access to the WebLogic Integration system. Principals include trading partners, human users, and B2B integration.

private process

Business process conducted within a business organization. The definitions and designs for a private process are specific to the organization and are not visible outside it. A private process can interface with process engines and with back-end business systems.

process engine

See WebLogic Integration Studio.

public process

Business process conducted between trading partners. A public process is part of a formal contract between trading partners that specifies the content and semantics of message interchanges between them. When the RosettaNet business protocol is used, the business process is a partner interface process (PIP). For all business protocols, a public process is implemented by means of collaborative workflows.

— Q —

QoS

See Quality of Service (QoS).

QPA

See Query for Price and Availability (QPA).

Quality of Service (QoS)

Class of options used by WebLogic Integration to define levels of reliability in message deliveries performed as part of B2B integration activities. QoS provides options for reliable delivery of messages in the event of network-link and node failures.The WebLogic Integration options improve reliability by using a persistent data store that enables WebLogic Integration to recover B2B integration operations in case of node failures.

Query for Price and Availability (QPA)

Message that is broadcast to one or more supplier trading partners, who respond to the buyer trading partner with quotes.

— R —

realm

Domain for a set of security features that provide access to ACLs, names of principals, and related security services. A realm provides a context in which the range of security operations and other security-related information governing WebLogic Integration users is defined. It determines how users are authenticated. The security features available for WebLogic Integration are built on the security functionality provided by WebLogic Server.

recovery

Restoration of a system to the most recently committed and consistent state.

reference

A group or field that relies on a prior definition to determine its name, type, and termination attributes.

registration

Request by a trading partner to receive business messages for a given role in a conversation definition. Registration requests are sent to WebLogic Integration and require the trading partner to have a subscription.

reliable messaging

Process of delivering messages with various Quality of Service (QoS) options that guarantee the safe arrival of those messages at their destinations, even when machine failures occur. When reliable messaging is used, the following functionality is available: confirmation of receipt of messages; message logging and tracking; correlation of messages; retry attempts; and a choice of message delivery methods.

repository

Database in which the following types of information are stored: trading partners, conversations, document definitions, XML schemas, and XSLT mappings. The primary store is a relational database accessed through JDBC. The repository can be configured and accessed through an HTML interface, the WebLogic Integration B2B Console. The Bulk Loader utility supports the updating and processing of repository data, and the deletion of data.

resource adapter

A system-level software driver used by an application server or an applicatoin client to connect to an EIS.

restricted trading partner

Trading partner that runs a license-restricted version of B2B integration.

Retry Attempts

Quality of Service (QoS) option whereby B2B integration attempts to resend a message a specified number of times at any delivery point in order to mask intermittent network failures. B2B integration waits for a predefined interval before attempting to resend a message. Availability of this option depends on the business protocol that is being used.

RNIF

See RosettaNet Implementation Framework (RNIF).

role

In B2B integration, a role is a definition of activities, such as buying and selling, that can be performed by a trading partner during a conversation. A role is defined in terms of the documents that can be sent or received by a trading partner in the conversation. Each conversation has two or more roles, and each role is defined by a collaborative workflow.

In business process management (BPM), a role is one of the following: an area of responsibility, an ability, or an authorization level that is shared by a group of users. A user can belong to one or more roles.

RosettaNet

(1) Non-profit consortium of high-technology companies whose purpose is to define and standardize business interfaces for e-commerce.

(2) Business and transport protocol specified by the RosettaNet consortium.

RosettaNet filter

A logic plug-in chain that consists of the following logic plug-ins in this order:
(1)a RosettaNet filter logic plug-in, which is provided by WebLogic Integration to support B2B integration; and
(2) optional customer-supplied logic plug-ins.

RosettaNet filter logic plug-in

A logic plug-in that determines which RosettaNet business messages a trading partner will receive. The RosettaNet filter logic plug-in is one of the logic plug-ins in the RosettaNet filter.

RosettaNet Implementation Framework (RNIF)

Guidelines for creating interoperable software application components that execute PIPs.

RosettaNet router

A logic plug-in chain that consists of the following logic plug-ins in this order:
(1) RosettaNet router logic plug-in, which is provided by WebLogic Integration to support B2B integration;
(2) optional customer-supplied logic plug-ins; and
(3) RosettaNet router enqueue logic plug-in.

RosettaNet router enqueue logic plug-in

A logic plug-in that queues a RosettaNet message for potential delivery to a recipient.

RosettaNet router logic plug-in

A logic plug-in that assigns the recipient for a RosettaNet message. Unlike XOCP and cXML, RosettaNet enables a trading partner to send only one message to one trading partner at a time. Therefore, the RosettaNet router logic plug-in assigns only one recipient.

router

Set of one or more logic plug-ins for a specific business protocol. A router determines the trading partners to which a message is sent. B2B integration provides an XOCP router, a cXML router, and a RosettaNet router.

router chain

See chain.

router logic plug-in

A logic plug-in in a router. See cXML router enqueue logic plug-in, cXML router logic plug-in, RosettaNet router enqueue logic plug-in, RosettaNet router logic plug-in, XOCP router enqueue logic plug-in, and XOCP router logic plug-in.

routing expression

XPath expression in an XOCP router logic plug-in.

routing service

B2B integration component that provides a list of recipients for a message, performs the final validation of message recipients, and stores the message for delivery to trading partners.

— S —

schema

A document that defines valid contents for an XML document. A schema definition is more specific than a DTS, and provides much finer-grained control over content.

scheduling service

B2B integration component that helps ensure proper routing, queuing, and sequencing of messages.

secure sockets layer (SSL)

Internet transport security protocol that provides data privacy between applications. In WebLogic Integration, two-way SSL requires digital certificates from both communicating applications.

security

Set of mechanisms available to prevent corruption or theft of data. See authentication, authorization, data privacy, and secure sockets layer (SSL).

security realm

A WebLogic Server component that contains user, role, and organization information.

servlet

A Java^TM program that extends the functionality of a Web server by generating dynamic content and making it possible for users to interact with Web clients using a request-response paradigm.

service

A named business function within an Enterprise Information System (EIS), implemented in terms of interactions provided by the adapter for the EIS. Services provide a two-way sychronous or asynchronous communication mechanism to an EIS.

service provider interface

A program that contains objects that provide and manage connectivity to the Enterprise Information System (EIS), establish transaction demarcation, and provide a framework for event listening and request transmission. All J2EE Connector Architecture-compliant adapters must provide an implementation for such interfaces in the javax.resource.spi package.

shape

Graphical representation, in the WebLogic Integration Studio drawing area, of a workflow node.

SSL

See secure sockets layer (SSL).

start

First component of a workflow. The triggering properties of the workflow are specified in the start node. The first shape after the start node is the first active component in the workflow.

stylesheet

An XSLT document that describes data transformations (or mappings) to be performed on an XML document. A stylesheet specifies which nodes of an XML document are to be manipulated (using XPath), and which manipulations are to be performed.

subscription

Permission for a trading partner to participate in a specific role in a specific conversation definition. To send business messages for a role in a conversation, a trading partner must have a subscription to that role. To subscribe, a trading partner must specify its own name, the name and version of the desired conversation, and the role to which the trading partner is subscribing.

supply chain

Sequence of processes for producing, shipping, and distributing products.

SWIFT

Society for Worldwide Interbank Financial Telecommunications (SWIFT) is the industry-owned cooperative that supplies secure global messaging services and interface software to approximately 7,000 financial institutions in more than 190 countries. See also http://www.swift.com.

synchronous message delivery

Message delivery method whereby B2B integration returns control to the application once the outcome of the message transmission is known. Control is returned to the application after any of the following events occur: acknowledgments are received from all potential destinations; the message times out; or a conversation in which the message was sent terminates.

systematic collaboration

Type of cooperative work among multiple trading partners in which all participants are aware of all other participants from the beginning of the business relationships. In such an arrangement, the business relationship is ongoing and process changes occur infrequently.

System Error Handler

A business process management (BPM) error handler available to every workflow template definition. Unless overridden by a workflow template definition, BPM invokes the System Error Handler whenever an exception occurs. When called, the System Error Handler rolls back the specified transaction and throws an exception to the client application.

system log message

Message placed in the local log to record WebLogic Integration activity. An example is a system log message indicating the inability to deliver a transport message because B2B integration terminated.

system transport message

Type of XOCP transport message exchanged between trading partners that causes system activity; for example, notification of conversation termination.

— T —

tag library

Collection of custom tags available to a JSP author.

task

One of a series of discrete activities that make up a workflow. Tasks are performed automatically by WebLogic Server or by a workflow user. Task behavior is determined by various task properties and by the task actions that define the processing to be performed as certain task events occur.

task event

Execution, during the life cycle of a task, of an action programmed by a workflow analyst. B2B integration supports four task events: Created, Activated, Executed, and Marked Done.

Timeout

Quality of Service (QoS) option that specifies the length of time that a sender waits for acknowledgment of a message before the message times out. After a timeout occurs, the message, acknowledgment processing, and retries are abandoned. Availability of this option depends on the business protocol being used.

token

See message token.

trading partner

Business entity that is authorized to send and receive business messages in a conversation. The configuration for a trading partner includes multiple delivery channels.

trading partner XPath filtering expression

XPath expression that reduces the set of messages that a trading partner receives by selectively passing certain messages to the targeted trading partner and blocking other messages before they are sent from B2B integration. A trading partner XPath filtering expression is part of an XOCP filter logic plug-in, is specified in the repository by an administrator, and is associated with a particular recipient trading partner. A trading partner XPath filtering expression can examine different parts of the message-context XML document, return True or False, using different selection criteria, and thereby potentially block a message that was passed by an earlier expression.

trading partner XPath routing expression

XPath expression that specifies the list of recipients for each message sent from a trading partner. A trading partner XPath routing expression is part of an XOCP router logic plug-in, is specified in the repository by an administrator, and is defined for a particular sending trading partner. A trading partner XPath routing expression can examine different parts of the message-context XML document and select a different set of recipient trading partners. The trading partners produced by each expression can replace or add to the previously generated set of recipients.

transaction

An atomic unit of work that modifies data. The code for a transaction encloses one or more program statements, all of which either complete or roll back. Transactions enable multiple users to access the same data concurrently.

transport

Properties for a delivery channel's transport level.

transport message

Data exchanged between trading partners. WebLogic Integration supports two types of transport messages: system transport messages and business messages.

transport service

B2B integration component that reads incoming messages to be passed to a decoder and writes outgoing messages from an encoder for delivery to a recipient. The decoder and encoder components must use the same business protocol, such as XOCP, RosettaNet, or cXML. The transport component is based on the HTTP/HTTPS transport protocol.

transport servlet

Entry point into the WebLogic Integration system for HTTP/HTTPS communication between trading partners that use XOCP, and between WebLogic Integration and nonXOCP trading partners. Access control at this entry point is set to allow access only by relevant non-human WebLogic Integration principals.

— U —

UDDI

See universal description, discovery, and integration (UDDI).

universal description, discovery, and integration (UDDI)

Specification for distributed Web-based information registries of Web services. The specification defines a method for publishing and researching information about Web services. UDDI is defined primarily to support Web services description language (WSDL). The main component of UDDI is the UDDI business registration, an XML file that describes a business entity and its Web services. Programs and programmers use the UDDI Business Registry to locate information about services.

— V —

value-added service

Logic that a trading partner adds to the services provided by WebLogic Integration. Credit checking and shipping are examples of value-added services.

— W —

W3C

See World Wide Web Consortium (W3C).

WebLogic Integration

Open, standards-based, software platform that delivers application server, application integration, business process management, and business-to-business integration functionality to an enterprise. WebLogic Integration runs on the EJB platform WebLogic Server and is implemented entirely in Java. Central to WebLogic Integration is XML, which provides an open data interchange format between loosely coupled participants. WebLogic Integration also leverages J2EE and workflow technologies (business process management) and supports leading e-commerce business protocols, such as RosettaNet, XOCP, and cXML.

WebLogic Integration B2B Console

HTML interface that an administrator uses to configure and monitor the B2B integration functions of WebLogic Integration.

WebLogic Integration Messaging API

API that enables you to create Java-based XOCP messaging applications as an alternative to using workflows.

WebLogic Integration process engine

Run-time component of WebLogic Integration that monitors and controls business process management (BPM) workflows.

WebLogic Integration repository

See repository.

WebLogic Integration Studio

The business process management client application that is used to define and monitor workflows.

WebLogic Server

Award-winning J2EE-compliant application server developed by BEA Systems, Inc.

WebLogic Server Administration Console

HTML interface that an administrator uses to configure and monitor WebLogic Server.

Web service

Business functionality made available by one company, usually through an Internet connection, for use by another company or software program.

Web services description language (WSDL)

Specification for an XML-based grammar that defines and describes a Web service. A WSDL is necessary if two different online systems need to communicate without human intervention.

WLC

Name of the root element in the repository.

workflow

Business process, such as order processing, that is automated in whole or in part. When a workflow is executed, information is passed to a particular participant at a particular time, according to a set of intelligent business rules that enable computers to perform most of the work, leaving humans to deal only with exceptions.

workflow expression

A calculation or an evaluation that WebLogic Integration performs at run time. The syntax of workflow expressions is comparable to that of SQL.

workflow node

Component of a WebLogic Integration Studio workflow, consisting of starts, tasks, events, joins, decisions, and dones.

workflow template

Folder or container in the WebLogic Integration Studio. A workflow template represents a workflow and has a meaningful name, such as Order Processing or Billing. The workflow template combines various workflow template definitions (versions) of its implementation. A workflow template controls which organizations can use the contained workflow template definitions.

workflow template definition

Definition or version of a workflow, distinguished by the dates on which it becomes effective and expires. At run time, WebLogic Integration starts an instance (or session) of a workflow template definition, selecting the most effective (or current and active) definition.

World Wide Web Consortium (W3C)

International organization that establishes standards for client and server protocols in order to facilitate Internet-based communications and commerce.

WSDL

See Web services description language (WSDL).

— X —

X.509

Widely used specification for digital certificates.

XML

See extensible markup language (XML).

XML schema

File that specifies the structure, content, and semantics of XML documents; replacement for the XML DTD.

XML service

One of several Apache XML services provided for WebLogic Integration. These services include the Apache XML Parser, DOM implementation, and the XSLT style sheet processor.

XML vocabulary

Set of XML tags that define the elements that may be included in a DTD. An XML vocabulary can be developed for a particular industry or business function.

XOCP

See extensible open collaboration protocol (XOCP).

XOCP filter

A logic plug-in chain that consists of the following logic plug-ins in this order:
(1) the XOCP filter logic plug-in that is provided by WebLogic Integration; and
(2) optional customer-supplied logic plug-ins.

XOCP filter logic plug-in

A logic plug-in that determines which XOCP business messages a trading partner will receive. The XOCP filter logic plug-in is one of the logic plug-ins in the XOCP filter. The XOCP filter logic plug-in uses the following sequence of XPath expressions: first, trading partner XPath filtering expressions, and then, business protocol XPath filtering expressions.

XOCP router

A logic plug-in chain that consists of the following logic plug-ins in this order:
(1) an XOCP router logic plug-in, that is provided by WebLogic Integration;
(2) optional customer-supplied logic plug-ins; and
(3) an XOCP router enqueue logic plug-in.

XOCP router enqueue logic plug-in

A logic plug-in that queues an XOCP message for potential delivery to each recipient.

XOCP router logic plug-in

A logic plug-in that determines the recipients for an XOCP business message. The XOCP router logic plug-in is one of the logic plug-ins in the XOCP router. The XOCP router logic plug-in uses the following sequence of XPath expressions: interaction specifications, trading partner XPath routing expressions, and business protocol XPath routing expressions.

XPath

XML path language. XPath models a message-context XML document as a tree of nodes and then addresses the nodes of the XML document. The XPath language includes a stand-alone subset that can be used to test whether a node matches a pattern. In B2B integration, routers and filters use this feature to identify trading partner elements of WebLogic Integration configuration information. XPath routing expressions specify business criteria for message distribution. XPath filtering expressions return a true or false result and act as gatekeepers, filtering out unwanted messages sent to a receiving trading partner. XPath expressions are associated exclusively with messages that use the default XOCP protocol. See also interaction specification, business protocol XPath filtering expression, business protocol XPath routing expression, trading partner XPath filtering expression, and trading partner XPath routing expression.

XPath filtering expression

See XPath.

XPath routing expression

See XPath.

XSL

See extensible style sheet language (XSL).

XSL style sheet language transformations (XSLT)

W3C specification for transforming XML documents from one document definition format to another.

XSLT

See XSL style sheet language transformations (XSLT).

— Y —

(No terms begin with the letter "Y")

— Z —

(No terms begin with the letter "Z")