BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Collaborate Documentation

http://download.oracle.com/docs/cd/E13222_01/wls/docs60/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.

Data structure used to authorize or deny access to resources by principals. Human users of WebLogic Collaborate 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 Collaborate is authorized to access the transport servlet.

See access control list (ACL).

Basic unit of work performed by WebLogic Process Integrator. Actions define workflow and task behavior, and can be defined as part of tasks, decisions, and events. Numerous actions are shipped with WebLogic Process Integrator.

See WebLogic Collaborate Administration Console and WebLogic Server Administration Console.

Information that is sent with a business message.

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

Permission granted to WebLogic Collaborate 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.

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

See business transaction protocol (BTP).

XML part of the payload of a 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.

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, how to process the messages, and how to route them to the appropriate recipients. WebLogic Collaborate trading partners can use the XOCP, RosettaNet, and cXML business protocols to send and receive business messages.

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

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.

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.

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.

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.

Multiple logic plug-ins that share the same business protocol and are processed in a predefined sequence at run time. 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 Collaborate executes each router logic plug-in as a business message passes through the router. Similarly, WebLogic Collaborate 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.

Workflow used by WebLogic Collaborate to implement a role.

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

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

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 WebLogic Collaborate upon completion of delivery. Availability depends on the business protocol that is used.

Default Quality of Service (QoS) option that verifies receipt of a message by WebLogic Collaborate. 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.

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.

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.

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.

Collection of values that defines a conversation.

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.

Trading partner that initiates and terminates a conversation.

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

Trading partner that receives and processes business messages.

Intelligent and controlled cessation of message exchanges performed by WebLogic Collaborate or WebLogic Process Integrator. For WebLogic Process Integrator 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 WebLogic Collaborate 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.

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.

See commerce XML (cXML).

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

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.

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

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

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

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

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 Collaborate 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.

WebLogic Process Integrator 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.

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.

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.

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 equivalent of an ID card that WebLogic Collaborate 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.

Schema, such as a document type definition (DTD), that specifies the prerequisites for a valid document. WebLogic Collaborate 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.

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

WebLogic Process Integrator term for a workflow component that marks an entire workflow as complete. No further processing for any task occurs after this term is issued.

See document type definition (DTD).

See data universal numbering system (DUNS).

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 Nonpersistent (default) and Persistent. Availability depends on the business protocol that is used.

See electronic business XML (ebXML).

See Electronic Data Interchange (EDI).

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

Standard that specifies the format of business messages for electronic commerce. EDI describes the contracts that define the legal terms and conditions as well as technical specifications to which trading partners must adhere in order to conduct electronic commerce.

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

WebLogic Process Integrator term for a workflow component. 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 and/or workflow variables can be set.

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 Collaborate Administration 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.

Default business protocol used by WebLogic Collaborate. 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.

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

See chain.

XPath expression in an XOCP 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.

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

Facility through which each message in WebLogic Collaborate is time-stamped upon its arrival at WebLogic Collaborate. 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.

XPath expression that specifies the initial list of recipient trading partners for a message. An intended recipient 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. Intended recipient XPath routing expression specifications can be modified or overridden by trading partner XPath routing expressions and WebLogic Collaborate XPath routing expressions.

See Java Management Extensions (JMX).

Term for a workflow component that links WebLogic Process Integrator events, tasks, and decisions, thus controlling the transitions between them. Joins can be 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.

See log message and system log message.

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

WebLogic Collaborate 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.

See chain.

Notification of a particular occurrence that is recorded in the local log. WebLogic Collaborate 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.

Java object (JavaBean) that, as part of the Instrumentation level in JMX architecture, contains attributes for management operations. In WebLogic Collaborate, MBean classes are used to monitor run-time information. MBeans are registered with the MBean server that runs inside WebLogic Collaborate. When MBeans are created, their attributes are populated from the repository. At run time WebLogic Collaborate 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.

See managed bean (MBean).

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

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.

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 WebLogic Collaborate 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.

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.

See deferred synchronous message delivery and synchronous message delivery.

Container for a business message as it travels through WebLogic Collaborate. As the business message enters WebLogic Collaborate, WebLogic Collaborate 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.

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.

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).

Java class that implements the message manipulator interface com.bea.b2b.wlpi.MessageManipulator and that helps integrate WebLogic Collaborate and WebLogic Process Integrator. A message manipulator uses WebLogic Process Integrator variables to create and process WebLogic Collaborate business messages.

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, if 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).

Feature that provides information about the status of a message as the message progresses through various predefined message-tracking locations in the WebLogic Collaborate messaging system. WebLogic Collaborate 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 Collaborate system, the Quality of Service (QoS) for the message, and the business protocol.

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

Default Durability Quality of Service option whereby a message is not stored anywhere in the WebLogic Collaborate system. The message 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.

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

See Open Buying on the Internet (OBI).

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.

See Apache XML Parser.

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

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

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

Durability Quality of Service 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, WebLogic Collaborate 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 Nonpersistent.

See partner interface process (PIP).

See logic plug-in and WebLogic Process Integrator plug-in.

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 public processes and with back-end business systems.

Run-time component of WebLogic Process Integrator that monitors and controls workflows.

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.

See Quality of Service (QoS).

See Query for Price and Availability (QPA).

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

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

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.

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 Collaborate Administration Console. The Bulk Loader utility supports the updating and processing of repository data, and the deletion of data.

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

See RosettaNet Implementation Framework (RNIF).

In WebLogic Collaborate, 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.

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

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.

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 Collaborate;
(2) optional customer-supplied logic plug-ins; and
(3) RosettaNet router enqueue logic plug-in.

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

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.

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. WebLogic Collaborate provides an XOCP router, a cXML router, and a RosettaNet router.

See chain.

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.

XPath expression in an XOCP router logic plug-in.

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

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

Graphical representation, in the WebLogic Process Integrator drawing area, of a workflow node.

See secure sockets layer (SSL).

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.

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.

Message delivery method whereby WebLogic Collaborate 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.

WebLogic Process Integrator error handler available to every workflow template definition. Unless overridden by a workflow template definition, WebLogic Process Integrator 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.

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

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

One of a series of discrete activities that make up a workflow. Tasks are performed automatically by the WebLogic Process Integrator 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.

Occurrence in the life cycle of a task during which an action programmed by a workflow analyst is executed. WebLogic Collaborate supports four task events: Created, Activated, Executed, and Marked Done.

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.

See message token.

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

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 WebLogic Collaborate. 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.

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.

Properties for a delivery channel's transport level.

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

WebLogic Collaborate 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.

Entry point into the WebLogic Collaborate system for HTTP/HTTPS communication between the trading partners that use XOCP, and between WebLogic Collaborate and non-XOCP trading partners. Access control at this entry point is set to allow access only by relevant WebLogic Collaborate principals. (Human users do not access this entry point.)

See 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.

See World Wide Web Consortium (W3C).

Open, standards-based software platform that enables companies to implement business-to-business collaborations on the Web. WebLogic Collaborate runs on the EJB platform WebLogic Server and is implemented entirely in Java. Central to WebLogic Collaborate is XML, which provides an open data interchange format between loosely coupled participants. WebLogic Collaborate also leverages J2EE and workflow technologies (WebLogic Process Integrator) and supports leading e-commerce business protocols, such as RosettaNet, XOCP, and cXML.

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

XPath expression that can block messages passed by previous XPath filtering expressions. A WebLogic Collaborate 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 Collaborate instance. A WebLogic Collaborate XPath filtering expression applies to all messages that the WebLogic Collaborate 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 WebLogic Collaborate XPath filtering expressions are the final set of XPath expressions that evaluate messages before those messages are finally received by trading partners.

XPath expression that specifies all messages that can be sent from the WebLogic Collaborate instance. A WebLogic Collaborate 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 Collaborate instance. A WebLogic Collaborate XPath routing expression is evaluated after the intended recipient XPath routing expressions and trading partner XPath routing expressions are evaluated, and thus can modify or override the list of trading partners selected by those expressions.

Automation tool that enables you to define and monitor workflows.

WebLogic Process Integrator client application that is used to define and monitor workflows.

Name of the root element in the repository.

Definition of a calculation or an evaluation that WebLogic Process Integrator performs at run time. The syntax of workflow expressions is comparable to that of SQL.

Component of a WebLogic Process Integrator workflow, consisting of starts, tasks, events, joins, decisions, and dones.

Folder or container in the WebLogic Process Integrator 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.

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

See Web services description language (WSDL).

Widely used specification for digital certificates.

See extensible markup language (XML).

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

See extensible open collaboration protocol (XOCP).

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

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, WebLogic Collaborate XPath filtering expressions.

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

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

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: intended recipient XPath routing expressions, trading partner XPath routing expressions, and WebLogic Collaborate XPath routing expressions.

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 WebLogic Collaborate, routers and filters use this feature to identify trading partner elements of WebLogic Collaborate 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 intended recipient XPath routing expression, WebLogic Collaborate XPath filtering expression, WebLogic Collaborate XPath routing expression, trading partner XPath filtering expression, and trading partner XPath routing expression.

See XPath.

See XPath.

See extensible style sheet language (XSL).

W3C specification that explains how to transform XML documents from one document definition format to another.

See XSL style sheet language transformations (XSLT).