CPA
Defined as a Collaboration Protocol Agreement and derived from a CPP. It is an agreement between business partners which defines the way partners interact in performing a chosen set of business collaborations. It is defined in XML. Further details available at http://www.oasis-open.org/committees/ebxml-cppa/documents/ebcpp-2.0.pdf
CPP
The Collaboration Protocol Profile (CPP) defines the message exchange capabilities of a business partner and the business collaborations that it supports. Further details available at http://www.oasis-open.org/committees/ebxml-cppa/documents/ebcpp-2.0.pdf
CP
Conformance Profile - the gateway profile that lists the features expected of a MSH acting as an e-Business gateway to backend systems.
DUNS
Data Universal Numbering System (DUNS) is a system developed and regulated by Dun & Bradstreet which assigns a unique numeric identifier to a single business entity. Further details available at http://www.dnb.com
FMS
Flame Message Server.
MEP
Message Exchange Pattern (MEP) is defined as a message sequence that follows a defined message exchange pattern required by a communications protocol. There are two major message exchange patterns being one-way and two-way. MEPs are manifested in the P-Mode.
MPC
A Message Partition Channel (MPC) is a flow of messages from a set of sending MSHs to a set of receiving MSHs. An MSH may have an associated priority determined by agreement between business partners.
MSH
Message Service Handler (MSH) provides the interface and services required for encapsulating messages in in an electronic envelope and securely forwarding the envelope to a remote destination possibly via an MSH chain. FMS is an instance of an MSH.
MOM
Message Oriented Middleware (MOM) is a client/server infrastructure that enables the interoperability, portability, and flexibility of an application by allowing the application to be distributed over multiple heterogeneous platforms (Wikipedia).FMS falls in this class of software.
Package Manager
A mechanism used to encapsulate messages according to the various requirements of a published messaging specification, such as ebXML or RosettaNet. Implemented as a Java class file stored in a Jar archive.
P-Mode
An MSH operates either for sending or receiving messages with knowledge of some contextual information that controls the way messages are processed. This contextual information that governs the processing of a particular message is called Processing Mode (P-Mode). Because different messages may be subject to different types of processing, an MSH generally supports several P-Modes. The set of all P-Modes that are supported by an MSH during operation, is called the P-Mode operation set of the MSH.
The association of a P-Mode with a message may be based on various criteria, usually dependent on header data (e.g. Service/Action, Conversation ID, or other message properties). Which security and/or which reliability protocol and parameters, as well as which MEP is being used when sending a message, is determined by the P-Mode associated with this message.
Partner Identifier
A unique identifier associated with a Business Partner.
Reliable Messaging
(a) WS-Reliability 1.1 and (b) WS-ReliableMessaging. (a) has been an OASIS standard for several years, has been tested and implemented by communities of users, notably in Asia. (b) is a more recent standard, still awaiting for WS-I interoperability guidance, but enjoying a broad support among US-based companies. This fulfills the Quality of Service requirements for a message.
SOAP
SOAP (from wikipedia) is a protocol for exchanging XML based messages over computer networks, normally using HTTP/HTTPS. SOAP forms the foundation layer of the web services protocol stack providing a basic messaging framework upon which abstract layers can be built.
WSS1.0/1.1
Web Services Security Encryption/decryption of any SOAP message content and generation/verification of any digital signatures forms part of this specification.
<<< Previous | Home | Next >>> |
Version History | Bibliography |