TIBCO FTL Glossary. Software Release 4.3 November Two-Second Advantage

Transcription

1 TIBCO FTL Glossary Software Release 4.3 November 2015 Two-Second Advantage

2 2 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, Two-Second Advantage, TIB, Information Bus, eftl and Rendezvous are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

3 3 Contents TIBCO Documentation and Support Services...4 About this Product...6

4 4 TIBCO Documentation and Support Services Documentation for this and other TIBCO products is available on the TIBCO Documentation site: Documentation on the TIBCO Documentation site is updated more frequently than any documentation that might be included with the product. To ensure that you are accessing the latest available help topics, please visit Product-Specific Documentation Documentation for TIBCO products is not bundled with the software. Instead, it is available on the TIBCO Documentation site. To access the documentation web page for this product from a local software installation, open the following file: TIBCO_HOME/release_notes/TIB_ftl_4.2.0_docinfo.html TIBCO_HOME is the top-level directory in which TIBCO products are installed. On Windows platforms, the default TIBCO_HOME is C:\tibco. On UNIX platforms, the default TIBCO_HOME is /opt/tibco. The following documents for this product can be found on the TIBCO Documentation site. TIBCO FTL Documentation Set TIBCO FTL Concepts Everyone reads this booklet first, for an intuitive introduction to the fundamental concepts of FTL software. TIBCO FTL Development Application developers and architects read this manual to understand concepts relevant in any supported programming language. TIBCO FTL API Reference Application developers use this HTML documentation to learn the details of the FTL API in specific programming languages. TIBCO FTL Administration Administrators read this manual to learn how to use the realm server and its interfaces, and how to define a realm. Developers can also benefit from understanding FTL software from an administrator s perspective. TIBCO FTL Installation Read this manual before installing or uninstalling the product. TIBCO FTL Glossary The glossary contains brief definitions of key terms used in all other parts of the documentation set. TIBCO FTL Release Notes Read the release notes for a list of new and changed features. This document also contains lists of known issues and closed issues for this release. TIBCO eftl Documentation Set TIBCO eftl software is documented separately. Administrators use the FTL realm server GUI to configure and monitor the eftl service. For information about these GUI pages, see the documentation set for TIBCO eftl software. How to Contact TIBCO Support For comments or problems with this manual or the software it addresses, contact TIBCO Support: For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

5 5 If you already have a valid maintenance or support contract, visit this site: Entry to this site requires a user name and password. If you do not have a user name, you can request one. How to Join TIBCOmmunity TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to the following web address:

6 6 About this Product TIBCO is proud to announce the latest release of TIBCO FTL software. This release is the latest in a long history of TIBCO products that leverage the power of Information Bus technology to enable truly event-driven IT environments. To find out more about how TIBCO FTL software and other TIBCO products are powered by TIB technology, please visit us at

7 7 FTL Glossary A Ability An endpoint can carry messages using up to four abilities: One-to-many receive (subscriber) One-to-one receive (inbox subscriber) One-to-many send (send call) One-to-one send (send-to-inbox call) Administrators bind transports to specific endpoint abilities. [Development, Administration] Advisory TIBCO FTL software uses asynchronous advisory messages to convey errors, warnings or other information. [Development] Application 1. An FTL application is an executable program that communicates using TIBCO FTL software. 2. Within the realm definition, an application (or more explicitly, an application definition) configures the endpoints, formats, transports, and stores for an application program. [Administration] Application Instance An application instance definition configures transports and stores for an application process in a specific context: for example, a process that runs on a specific host computer, or supplies an application instance identifier. [Administration] Apportioning Message Streams A store can apportion a message stream among a set of cooperating subscribers. Only one subscriber receives and processes each message. Acting together, the subscribers process every message in the stream. B Backup A backup realm server is a process that can distribute the realm definition to FTL clients in a failover situation. [Administration] Bridge See Transport Bridge. C Cluster A cluster of persistence servers can cooperate for fault tolerance. [Administration]

8 8 Content Matcher A content matcher is a pattern matching template for message fields and values. A subscriber can use a content matcher to narrow its interest to a subset of a message stream. [Development] D Deploy An administrator can modify the realm definition and deploy the updated definition to the realm server s clients. [Administration] Delivery Assurance A store can retain message streams for a disconnected subscriber, assuring delivery after the subscriber returns. The subscriber receives the complete message stream. Direct Path A communications path in which messages travel directly between publishing and subscribing endpoints, without an intermediate stop at a store. In contrast, an indirect path goes through a store, which can back a direct path. [Concepts, Administration] Disable An administrator can use the realm server GUI to disable a client process. Disabled clients cannot use TIBCO FTL communications resources. [Administration] Dispatch Programs use API calls to dispatch inbound messages from event queues to callback methods. [Development] Durable A durable is a data structure (within a store) that represents subscriber interest and can track message acknowledgements. A standard durable corresponds to exactly one durable subscriber, and ensures that it acknowledges each message in the store s message stream. A shared durable corresponds to a set of durable subscribers, and ensures that exactly one of those subscribers acknowledges each message in the store s message stream. [Concepts, Development, Administration] A last-value durable corresponds to a set of durable subscribers. It ensures that every new subscriber first receives the most recent message, and then the stream of subsequent messages until the subscriber closes. It does not track message acknowledgements. Durable Subscriber A durable subscriber is a subscriber object in an application process that maintains its identity even if the process exits and restarts. The subscriber relies on its durable to ensure message delivery. [Concepts, Development, Administration] Dynamic Durable A durable that an application creates at run time. [Development, Administration]

9 9 Dynamic Durable Template An administrative configuration that supplies parameter values for dynamic durables. [Administration] Dynamic Format When a program constructs a self-describing message, its format is dynamic. That is, the format changes each time the program adds a field to the message. The message s metadata reflects the current state of the dynamic format. [Development] E eftl TIBCO eftl software is an add-on product that extends TIBCO FTL messaging to platforms that cannot support the full TIBCO FTL bus. Platforms such as web browsers and mobile phones can use TIBCO eftl software to communicate with back-end infrastructure based on TIBCO FTL software. Endpoint An endpoint is an abstraction that represents a set of publishers and subscribers in communicating application programs. Endpoints insulate programs from transport details, enabling separation of responsibilities between developers and administrators. [Development, Administration] Event Queue Event queues buffer inbound messages during message delivery. Programs dispatch messages from event queues to callback methods. [Development] F Field Each field of a message has a name, and can contain a value of a specific data type. [Development] Format A message format is a fixed set of field names and data types. Messages that use defined formats can omit explicit metadata, reducing message size. [Development, Administration] G Group Facility Programs can use the group facility to coordinate fault-tolerant operation. More generally, the group facility can coordinate several distinct operating roles with different behaviors. [Development, Administration] I Immutable A program cannot modify the fields of an immutable message. [Development]

10 10 Inbound Inbound indicates the direction proceeding into an endpoint from a transport, or into a program through an endpoint. For example, subscriber objects receive inbound messages. [Development, Administration] Inbox An inbox is a data structure that identifies a unique inbox subscriber object, enabling one-to-one communication to that subscriber. [Development] Inbox Subscriber An inbox subscriber can receive one-to-one communication. An inbox subscriber is one kind endpoint instance within a program. An inbox subscriber instantiates the one-to-one receiving capabilities of an endpoint. (Contrast Subscriber.) [Concepts, Development] Inline Mode Programs that receive time-sensitive messages can use inline mode to favor low latency over high throughput. Restrictions apply. [Development, Administration] Interest TIBCO FTL software efficiently conveys messages to endpoints where subscribers express interest in those messages. A subscriber expresses interest in the message stream arriving at an endpoint. If the subscriber has a content matcher, it expresses interest in a subset of that message stream: namely, the subset with matching content. A durable expresses interest on behalf of its durable subscriber, even when the subscriber is absent. [Development, Administration] M Managed Format A managed format is a message format defined in the realm. [Administration] Map API A set of methods for storing and retrieving key/value pairs in a last-value durable. Message A message is data, structured as a set of named fields. Programs can exchange messages. [Concepts] Message Stream A sequence of messages. [Concepts] Mutable A program may modify the fields of a mutable message. [Development] N Notification A notification is an out-of-band communication from TIBCO FTL software to an application program. TIBCO FTL software delivers notifications when conditions preclude delivering advisories using event queues. [Development]

11 11 O One-to-Many Publishing One-to-many is the basic communication paradigm in TIBCO FTL software. A subscriber can receive every message in the message stream. [Concepts] One-to-One Communication An inbox subscriber can receive only those messages that publishers send specifically to its inbox. [Concepts] Outbound Outbound indicates the direction proceeding out from an endpoint to a transport, or out from a program through an endpoint. For example, publisher objects send outbound messages. [Development, Administration] P Persistence Persistence is a potential to store a message between publishing and receiving it. Persistence servers use Stores and Durables to implement this potential. See also Apportioning Message Streams and Delivery Assurance. [Concepts, Administration, Development] Preload Format Preload formats are the managed formats available to an application program. [Administration] Primary Within a family of affiliated ream server processes, the primary is the central hub. [Administration] Publisher A publisher can send messages. A publisher is one kind endpoint instance within a program. A publisher instantiates the send capabilities of an endpoint. Each publisher is the source of a message stream. [Concepts, Development] R Realm A realm represents a distinct and unified communication fabric, consisting of applications, endpoints, transports, stores, and message formats. [Development, Administration] Realm Server A realm server is a process that maintains a realm definition, and distributes that definition to client applications. [Development, Administration] S Satellite A satellite realm server is a process that provides local service to clients that are geographically distant from the primary, or clients that are insulated from the primary. [Administration]

12 12 Send 1. Programs make send calls to send messages. 2. More narrowly, the term send also refers specifically to one-to-many publishing. (Contrast Send-to-Inbox.) Send-to-Inbox Programs make send-to-inbox calls to send one-to-one messages. (Contrast Send.) Self-Describing Message A self-describing message does not conform to a predefined format. Instead it contains metadata describing the names and data types of each field. [Concepts] Static Durable A durable that an administrator defines in the realm. Store A store is a data structure that maintains a message stream. Administrators can configure stores within a persistence server. [Concepts, Administration] Subscriber 1. A subscriber can receive messages. A subscriber is one kind endpoint instance within a program. A subscriber instantiates the receiving capabilities of an endpoint. Each subscriber expresses interest in a message stream. [Concepts, Development] 2. More narrowly, the term subscriber also refers specifically to one-to-many subscribers (contrast Inbox Subscriber). [Development] T Template See Dynamic Durable Template. Transport Messages travel from publishers to subscribers over transports. TIBCO FTL software supports a variety of transport types. [Concepts, Administration] Transport Bridge A transport bridge is a specialized process that can forward messages among sets of transports. [Administration] V Variant See Application Instance. [Concepts]