This chapter section provides the detailed information about the ESB components. Following components are available:
- Template - Using templates is Templates provide an ideal way to improve reusability and readability of ESB configurations/XMLs. Users You can utilize use predefined templates that reflect commonly used EIP patterns for rapid development of ESB message/mediation flows.
- Task - This component A task allows you to run a piece of code triggered by a timer. WSO2 ESB is already bundled with a provides a default scheduled task, which can be used to inject a message to the ESB given by the configuration at a scheduled interval (5000 ms). A user You can also write his your own task, for example, you can create a task which that will read a text file at a specified location and place orders for stocks that are given in the text file.
- Message Processor - This component can be used You can use a message processor to implement different messaging and integration patterns along with message stores. Message processors will consume the and process messages in message stores and do the processing of them. For example, think of a scenario where we you might have a back-end service that can only accept messages at a given rate and , but incoming traffic to the ESB will have different message rates. To serve that manage the traffic utilizing to the backend back-end services, we you can have use a message store that temporary to temporarily store the traffic and a message processor that will to consume that the messages and send them to the back-end service at a given rate.
- Message Stores - A Message store serves as a message store provides temporary storage for ESB messages. For example, in a scenario where we have a back end service that can only accept messages at a given rate and incoming traffic to ESB will have different message rates. To serve that traffic utilizing the back end services, there should be a temporary storage for messages. Message Stores can be used as this temporary storage.Endpoint - It is messages so that they can be processed by a message processor.
- Endpoint - An endpoint is the external destination for an outgoing message through WSO2 ESB. An <endpoint> element defines an endpoint in the configuration.
- Carbon Application (cApp) - A cApp is a collection of artifacts, which can be deployed on a Carbon instance to easily port a Web services based solution from one environment to another.
- Topic - The user can view all the topics available in the server in a tree view with the help of the "Topic Browser" feature. The user can also perform all the operations with regarding a topic via this view.Mediation Library - This component provides a mechanism to group Templates and automatically expose them as a self-contained set of function modulesYou can use the tree view in the Topic Browser to view and manage all the topics available on the server.