Talend ESB - Glossary of Terms
Abstract head element
An XML Schema element that cannot appear in an instance document. When a substitution group's head element is declared as abstract with abstract="true", a member of that element's substitution group must be used instead.
A special type of message that contains administrative information about the message broker. They are sent by the broker to special advisory topics. See advisory topics below.
A group of special topics that are created by a message broker that are used for monitoring the state of the broker. The broker sends messages about a variety of internal broker events. Clients subscribing to these topics receive advisory messages about these objects.
The root type for all XML Schema type definitions hierarchies. All primitive types are derivatives of this type, as are all user-defined complex types.
An open source project that provides the messaging technology for Talend ESB.
An open source project that provides the EIP-based routing technology used by Talend ESB.
An open source project that provides the Web services framework used by Talend ESB.
An open source project that provides the OSGi runtime container used by Talend Runtime.
A software platform that provides the services and infrastructure required to develop and deploy middle-tier applications. Middle-tier applications implement the business logic necessary to provide web clients with access to enterprise information systems. In a multi-tier architecture, an application server sits beside a web server or between a web server and enterprise information systems. Application servers provide the middleware for enterprise systems. JBoss, WebLogic and WebSphere are J2EE application servers.
A single routing rule base that defines the context for configuring routes, and specifies which policies to use during message exchanges between endpoints.
Choice complex type
An XML Schema construct defined using the choice element to constrain the possible elements in a complex data type. When using a choice complex type, only one of the elements defined in the complex type can be present at a time.
An application or process that requests services from other applications known as servers. The server processes may be running on the same or a different machine. In the context of a SOA network, a client process is called a consumer or service consumer.
An application that uses the message broker to communicate with other applications. These applications use one of the broker's client API to connect to and interact with the broker.
A collection of clustered services.
A service that is deployed multiple times and configured to work in a master/slave suppport configuration.
A block of logic that creates a routing endpoint that connects to a particular message source or message sink and do certain processing on the message. Talend Mediation perspective has mediation/routing components.
A virtual destination that serves as a proxy for multiple destinations. Producers can send messages to the composite destination an it will be automatically sent to all of the physical destinations that make up the composite destination.
A bridge between a client and a broker connector.
An object that a client uses to create a connection to a broker. A factory supports attributes that configure the quality of service for the connections it creates.
For a service consumer, it is the end user of the service, also called a client for that service. The more exact term in the context of a service-oriented network is service consumer.
For a message consumer, it is an application that consumes messages from a messaging destination.
For a routing consumer, it is the source of messages in a route.
A description of the messages and formats accepted and generated by a service. A service's contract is specified in a WSDL document that defines the interface and all connection-related information for that interface. A WSDL contract contains two sets of components: logical (or abstract) and physical (or concrete).
The logical components of the contract are those that describe the data types, message formats, operations, and interfaces for the services defined in the contract. Logical components are specified with the WSDL elements types, message, portType, and operation.