Book Image

WSO2 Developer's Guide

By : Ramón Garrido, Fidel Prieto Estrada
Book Image

WSO2 Developer's Guide

By: Ramón Garrido, Fidel Prieto Estrada

Overview of this book

WSO2 Enterprise Integrator brings together the most powerful servers provided by the WSO2 company for your SOA infrastructure. As an Enterprise Service Bus (ESB), WSO2 Enterprise Integrator provides greater flexibility and agility to meet growing enterprise demands, whereas, as a Data Services Server (DSS), it provides an easy-to-use platform for integrating data stores, creating composite views across different data sources, and hosting data services. Using real-world scenarios, this book helps you build a solid foundation in developing enterprise applications with powerful data integration capabilities using the WSO2 servers. The book gets you started by brushing up your knowledge about SOA architecture and how it can be implemented through WSO2. It will help build your expertise with the core concepts of ESB such as building proxies, sequences, endpoints, and how to work with these in WSO2. Going further, you will also get well-acquainted with DSS data service concepts such as configuring data services, tasks, events, testing, and much more. The book will also cover API management techniques. Along with ESB and DSS, you will also learn about business process servers, the rules server and other components that together provide the control and robustness your enterprise applications will need. With practical use cases, the book covers typical daily scenarios you will come across while using these servers to give you hands-on experience.
Table of Contents (14 chapters)

The Ballerina language history

In the WSO2 conference USA 2017 celebrated in San Francisco, WSO2 announced a new integration programming language, called Ballerina. The main target of this programming language is to focus on system integration with easy understanding for everyone, not only programmers. For this reason, we can develop our Ballerina programs in two different ways--writing the code or dragging and dropping the functionality to the design view, which is easy to understand for more people. In the design view, we can draw sequence diagrams that will be automatically translated into code syntax so that we can change from one view to the other and are synchronized in real time.

For example, the echo service that returns the message that we send is as follows in Ballerina code:

import ballerina.net.http; 
@BasePath("/echo") 
service echo { 
   @POST 
 ...