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)

General enterprise integration logging

We have several ways to log what is going on in WSO2 EI. As you may know, WSO2 EI is a Java application underneath, and as is typical in this type of application, it uses log4j for logging purposes.

You can configure this log4j logging. On the one hand, you can manually edit the configuration file you can find in <EI_HOME>/conf/log4j.properties. As you can imagine, you can modify the log4j.properties configuration file to suit your needs.

On the other hand, you can change this configuration through the management console. When you do this, the changes are persisted in the registry so that they are available after restarting the server and overwrite the configuration in the log4j.properties. You can find the logging configuration window in the Configure/Logging window, once signed into the Management Console.

The log files are placed...