This section provides detailed information about the ESB components.
- Template - Templates provide an ideal way to improve reusability and readability of ESB configurations/XMLs. You can use predefined templates that reflect commonly used enterprise integration patterns for rapid development of ESB message/mediation flows.
- Task - A task allows you to run a piece of code triggered by a timer. WSO2 ESB provides a default scheduled task, which can be used to inject a message to the ESB at a scheduled interval (5000 ms). You can also write your own task, for example, you can create a task that will read a text file at a specified location and place orders for stocks that are given in the text file.
- Message Processor - You can use a message processor to implement different messaging and integration patterns along with message stores. Message processors consume and process messages in message stores. For example, you might have a back-end service that can only accept messages at a given rate, but incoming traffic to the ESB will have different message rates. To manage the traffic to the back-end services, you can use a message store to temporarily store the traffic and a message processor to consume the messages and send them to the back-end service at a given rate.
- Message Stores - A message store provides temporary storage for 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 - You can use the tree view in the Topic Browser to view and manage all the topics available on the server.