Glossary
Product | Term | Definition |
Active Matrix | authentication realm | Defines the method of storing and retrieving information about ActiveMatrix users and groups. ActiveMatrix Administrator supports the following authentication realms: Local XML File, Database, TIBCO Administrator, and LDAP. |
Active Matrix | binding (WSDL) | A concrete protocol and data format specification for the operations contained in a port or interface. |
Active Matrix | binding definition set | A container for binding definitions. The extension of a binding definition set file is .bdf. |
Active Matrix | cluster | A group of ActiveMatrix Administrator servers. Servers in a cluster are maintained as clones, that is, they are automatically kept in an identical state for fail-over purposes. All servers in a cluster share the same database tables and authentication realm. |
Active Matrix | component | Represents an implementation of one or more port types. The component attributes are: Name Implementation type Port types, provided and consumed by the component Links to services that export the provided port types Links to partner references or topics that export the consumed port types Links to artifacts that implement the provided port types. |
Active Matrix | component reference | Component references describe the binding information required to invoke an external service. When the component implements a process that has a reference, then the process reference is exposed as a component reference. |
Active Matrix | component service | Represents a service provided by a component. |
Active Matrix | composite | One of the outputs of the ActiveMatrix design phase. A container for composite elements. The suffix of a composite file is .composite. |
Active Matrix | composite element | A child element of a composite. Services, components, references, and topics, wires, and the properties that components are configured with. |
Active Matrix | composite reference | See reference. |
Active Matrix | composite service | See service. |
Active Matrix | endpoint | A combination of a binding and a network address. The URL at which a consumer can access a service. An internal endpoint is accessible only to consumers within an ActiveMatrix environment. An external endpoint has a binding that provides access to consumers outside the ActiveMatrix environment. See port (WSDL 1.1). |
Active Matrix | environment | A logical grouping of ActiveMatrix nodes administered as one entity. |
Active Matrix | HTTP | Hypertext Transfer Protocol. The Internet protocol used to retrieve hypertext objects from remote hosts. HTTP messages consist of requests from client to server and responses from server to client. HTTP/S is a secure version of HTTP. |
Active Matrix | interface | A collection of operations. See also port type (WSDL 1.1). |
Active Matrix | JDBC | A Java API that allows applications to invoke SQL commands to create database tables, access the data stored in a table, and create and manage distributed transactions. |
Active Matrix | JMS | A Java API that allows applications to create, send, receive, and read messages. The JMS API enables communication that is decoupled, asynchronous, and reliable. JMS can deliver messages to a client as they arrive; a client does not have to request messages in order to receive them. JMS can ensure that a message is delivered once and only once. Lower levels of reliability are available for applications that can afford to miss messages or to receive duplicate messages. |
Active Matrix | JNDI | A Java API that allows applications to store and retrieve named Java objects of any type. In addition, JNDI provides methods for performing standard directory operations, such as associating attributes with objects and searching for objects using their attributes. |
Active Matrix | keystore | A database of private keys and their associated X.509 certificate chains authenticating the corresponding public keys. |
Active Matrix | keystore entry | An entry in a keystore. An entry can be a trusted certificate entry, which contains a single public key certificate belonging to a trusted party or a key-certificate entry, which contains a private key and a corresponding public key certificate. Each entry in a keystore is identified by an alias. |
Active Matrix | location transparency | Network locations that provide services are hidden from the service consumers (and replaced with some other network location). The actual locations are transparent, that is, not visible to the service consumer. |
Active Matrix | mediation | Performing programmatic tasks on messages in between service providers and the service consumer, to enhance the services provided. |
Active Matrix | mediation flow | Software program that performs activities between consumers and providers of services, such as routing and transforming messages. |
Active Matrix | mediation service | Service provided by a mediation component. The service provided combines one or more target services, which provide business functions, with mediation functions such as routing and data transformation. |
Active Matrix | mediation task | Set of TIBCO Business Studio plug-ins that performs a mediation function. Mediation tasks are placed on mediation paths, and are processed in sequence at runtime to provide mediation logic (some coherent set of mediation tasks designed to support mediation goals, in the same way that business logic supports business goals). |
Active Matrix | message exchange pattern (MEP) | The sequence and cardinality of messages sent between the consumer and the provider. The messages include both normal and fault messages. |
Active Matrix | Messaging bus | The message exchange layer responsible for routing messages between service providers and consumers. Messaging Bus supports performing such message delivery with varying qualities of service depending on application needs and the nature of the messages being delivered. It also performs transaction propagation, policy enforcement, and so on. |
Active Matrix | node | A Java Virtual Machine running the ActiveMatrix Platform and the Messaging Bus. |
Active Matrix | normalized message | The messaging unit of interoperability between ActiveMatrix containers. It uses abstract WSDL message type definitions and consists of two parts: Content An XML document that conforms to an abstract WSDL message type, without any protocol encoding or formatting. (This is not a canonical form for the message.) Properties Data associated with a message gained during the processing of the message. Such properties can include security information (security principal for digital signers of received messages), transaction context information, and container-specific information. |
Active Matrix | point-to-point messaging | A messaging system involving a single sender and receiver. It is built on the concept of message queues. Senders send messages addressed to a specific queue; receivers extract messages from the queues established to hold their messages. |
Active Matrix | port (WSDL 1.1) | A combination of a binding (WSDL) and a network address. |
Active Matrix | port type (WSDL 1.1) | A collection of operations. |
Active Matrix | publish/subscri be messaging system | A messaging system in which clients address messages to a specific node in a content hierarchy. Publishers and subscribers are generally anonymous and may dynamically publish or subscribe to the content hierarchy. The system takes care of distributing the messages arriving from a node's multiple publishers to its multiple subscribers. |
Active Matrix | QName | A qualified name, a data type specified by XML Schema. A qualified name consists of a namespace URI and a local part. |
Active Matrix | queue | A queue. |
Active Matrix | reference | Represents an endpoint consumed by an ActiveMatrix composite element. A composite reference represents the endpoints consumed by the composite. A composite reference enables ActiveMatrix components to consume port types implemented outside ActiveMatrix. The reference attributes are: Name Port types, provided by the reference Bindings that enable composite elements to access the provided port types Resource profiles |
Active Matrix | resource template |
An object that allows services, components, and references to share access to communication, data, naming, and security resources. The shared resource types supported by ActiveMatrix are:
|
Active Matrix | resource template profile | Represents a reference to a shared resource. |
Active Matrix | SOA | Service Oriented Architecture. A software architecture in which applications and data are decomposed into discrete, operationally independent services, which can be executed in a highly distributed manner. SOA is based on three principles: Modularity — Breaking tasks and services into smaller tasks or services; Encapsulation — Clearly defined interfaces that insulate a service's internal workings from outside contact; Reuse — Re-assembling services into composite applications that support new business processes; SOA inherently encompasses a heterogeneous collection of platforms and sources. In particular, enterprise applications may be hosted on Java and .NET platforms as well as third-party packaged systems and legacy applications. SOA infrastructure spans these varied application architectures and provide mediation between them. |
Active Matrix | SOAP | Simple Object Access Protocol. A protocol for exchanging XML-based messages over a computer network, normally using HTTP. SOAP also defines a way to perform remote procedure calls (RPCs) using HTTP as the underlying communication protocol. SOAP forms the foundation layer of the web services stack. SOAP 1.1 and SOAP 1.2 are supported. |
Active Matrix | REST | Representational State Transfer. This software architectural style defines the constraints to create web services. The web services that follows the REST architectural style are called RESTful Web Services. |
Active Matrix | TIBCO ActiveMatrix Administrator | Product component for administering TIBCO ActiveMatrix infrastructure and services. |
Active Matrix | TIBCO Business Studio | Product component for developing TIBCO ActiveMatrix SOA projects. You can execute composites in run mode or in debug mode. Running or debugging in a local node is also referred to as rapid application development (RAD) because you do not have to package and deploy the composite to test it. |
Active Matrix | TIBCO Enterprise Message Service | TIBCO product that implements JMS. ActiveMatrix Messaging Bus uses Enterprise Message Service as the messaging backbone. |
Active Matrix | topic | Represents a publish-subscribe messaging channel between service consumers and providers. Topics can have multiple consumers and can consume multiple providers. Topic attributes include: Name Port type provided by the topic Links to components or references that export the provided port type See also publish/subscribe messaging system. |
Active Matrix | web service | A software system designed to support interoperable machine-to-machine interaction over a network. It has an interface that is described in a machine-processable format such as WSDL. Other systems interact with the web service in a manner prescribed by its interface using messages, which may be enclosed in a SOAP envelope. |
Active Matrix | wire | Represents a connection between composite elements. |
Active Matrix | WSDL | Web Services Definition Language. An XML-based language for describing web services. The services are described in WSDL documents or files. A client program connecting to a web service can read the WSDL document to determine what operations are available on the server. Data types referenced in the document are embedded in the WSDL file in the form of XML Schema. The client uses SOAP to invoke the operations listed in the WSDL. |
Active Matrix | XML | Extensible Markup Language. A text-based markup language in which tags (markup) identify the content, data, and text in the documents. Although tags can be defined as needed in the generation of an XML document, a document type definition (DTD) or XML Schema is usually used to define the elements allowed in a particular type of document. An XML document can be compared by using the rules in the DTD or XML Schema to determine its validity and to locate particular elements in the document. |
Active Matrix | XML schema | An XML language for describing the structure of XML documents. The suffix of an XSD document is .xsd. |
Active Matrix | JSON | JavaScript Object Notation. JSON is an open standard file format and data interchange format that uses human-readable text to store and transmit data objects consisting of attribute–value pairs and arrays. |
Active Matrix | operation | An exchange of messages, between a service consumer and provider, according to a message exchange pattern that is understood by both participants. A WSDL operation, or its name. The part of a SOAP message that specifies the WSDL operation that a consumer is requesting from a service. |
Active Matrix | Policy Directory agent | Agents are the Policy Directory components that enforce policies. Agents are embedded in ActiveMatrix nodes; external proxy agents can be deployed outside of ActiveMatrix nodes. |
Active Matrix | Policy Directory criteria | A set of target services for a policy, or a query expression that determines a set of target services. |
Active Matrix | Policy Directory endpoint | An HTTP address for interacting with a service. A combination of a binding and a network address. (WSDL 2.0) |
Active Matrix | Policy Directory external service | A service deployed outside of any ActiveMatrix node. |
Active Matrix Policy Directory | inflow | The part of a message exchange that flows from a consumer toward a provider. |
Active Matrix Policy Directory | message exchange | A pairing of a request message (inflow) and either a response message or a fault message (outflow). |
Active Matrix Policy Directory | outflow | The part of a message exchange that flows from a provider back toward the consumer. |
Active Matrix Policy Directory | policy endpoints | The subset of endpoints that become visible to Policy Directory when you deploy an ActiveMatrix service assembly. ActiveMatrix instructs Policy Directory to register and manage these endpoints. |
Active Matrix Policy Directory | proxy endpoint | A managed endpoint for an external service, managed by a proxy agent. An additional managed endpoint for a service deployed in an ActiveMatrix node. |
Active Matrix Policy Directory | SOAP | A web services protocol standard for making web services available remotely. Consumers and providers of web services exchange XML-based messages over a computer network according to the SOAP protocol. See also WSDL (Web Services Description Language). |
Active Matrix Policy Directory | SOAP binding type | When an ActiveMatrix service communicates using ActiveMatrix normalized messages, and an external service communicates using SOAP messages, the SOAP binding engine translates their messages between these two protocols, so the services can interoperate. |
Active Matrix Policy Directory | WSDL | An XML-based language for describing web services. The services are described in WSDL documents or files. A client program connecting to a web service can read the WSDL document to determine the operations that are available on the server. Data types referenced in the document are embedded in the WSDL file in the form of XML Schema. The client uses SOAP to invoke the operations listed in the WSDL file. See also SOAP, web service, WSDL file. |
Active Matrix Policy Directory | alert | A notification to an end-user, for example, scheduled alerts deliver portal headlines to a chosen device. |
Active Matrix Policy Directory | domain | In TIBCO Administrator, two kinds of domains are used: administration domain and application domain. |
Active Matrix, Active Matrix Policy Directory | policy | A rule or property that dynamically affects the behavior of a service. |
Active Matrix, Active Matrix Policy Directory | WSDL file | An XML document that describes the services offered by a service provider. A WSDL file can take two forms: abstract and concrete. An abstract WSDL file defines operations, which define specific message request and response formats, and data types, which describe the types of the objects passed in the messages. A concrete WSDL file contains the abstract WSDL plus the communication protocols and data formats by which the operations defined in the abstract WSDL can be invoked. A binding connects a port type or interface (a collection of operations) to a protocol and data format. The combination of a binding and a network address is a port (WSDL 1.1) or an endpoint (WSDL 2.0). A service is a collection of ports (WSDL 1.1) or endpoints (WSDL 2.0). |
Active Matrix | consumer | A software service that sends and receives messages defined by a WSDL document to a provider. |
Active Matrix | operation | An exchange of messages between a service consumer and provider according to a message exchange pattern that is understood by both participants. |
Active Matrix | perspective | In TIBCO Business Studio, a set and layout of views in the Workbench window. In ActiveMatrix Administrator, a set of screens and controls used to carry out a category of administration tasks. |
Active Matrix | provider | A software service that conforms to a published WSDL document. The WSDL document describes the services it offers and the messages required to access the services. The provider generates and responds to messages sent by a consumer. |