The Enterprise Service Bus (ESB) today serves as a key component in most of the enterprise grade deployments. In most cases the ESB removes point-to-point dependencies in your system to build a highly scalable and loosely coupled solution. But that does not necessarily mean ESB means SOA. ESB is a key ingredient to build an SOA infrastructure, but it's not a must. Even with an ESB if not followed industry best practices and patterns you will end up with a mess.
Enterprise Integration with WSO2 ESB guides you through common patterns used in the industry to address enterprise integration challenges with WSO2 ESB.
Chapter 1, Getting Started focuses on giving a brief introduction to the Enterprise Service Bus in general, when to use it and when not to. We will also see how to deploy WSO2 ESB in a production environment with optimal settings.
Chapter 2, Enterprise Integration Patterns explains how to implement a mostly used set of Enterprise Integration Patterns (EIP) with WSO2 ESB. It covers Content-Based Router, Dynamic Router, Splitter, Scatter & Gather, Publish & Subscribe, Service Chaining, Content Enricher, and Detour with examples. This is only a limited set of EIPs, which provides a base, while WSO2 ESB is capable of implementing almost all the EIPs highlighted in Gregor Hohpe's Enterprise Integration Patterns book.
Chapter 3, Integration with Third-party Message Brokers explains how to integrate WSO2 ESB with third-party message brokers. First, we will start with Apache ActiveMQ and show how WSO2 ESB can consume messages from an ActiveMQ Queue. Then, we will see how WSO2 ESB acts as a publisher. Later, we will explain how we can integrate Apache Qpid as a message broker to the WSO2 ESB message store.
Chapter 4, Business Messaging and Transformations explains, by example, a selected set of capabilities of WSO2 ESB in business messaging and transformations. FIX, HL7, and SAP are covered in the first three sections. WSO2 ESB ships with a rich set of connectors to a wide variety of business applications. Later in this chapter, we explain how to use Twitter connector and then how to transform REST/JSON messages into SOAP and vice versa.
Chapter 5, Task Scheduling explains how to setup scheduled tasks through WSO2 ESB.
Appendix A, WSO2 ESB Terminology introduces commonly used terminology related to WSO2 ESB.
This book assumes the reader is quite familiar with SOA and related concepts. To run the samples provided, you need to have the following software installed.
JDK 1.6_26 +
WSO2 ESB 4.8.0 +
cURL
Anyone quite familiar with SOA, SOAP, and REST could follow this book without having any prior understanding about WSO2 ESB. Also prior knowledge in Java is not required.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text are shown as follows: "In Windows you can simply run ESB_HOME/bin/wso2server.bat."
A block of code is set as follows:
http.socket.timeout=120000 worker_pool_size_core=400 worker_pool_size_max=500 io_buffer_size=16384
Any command-line input or output is written as follows:
$ java -Dhl7_payload=request.hl7 -cp xercesImpl-2.8.1.wso2v2.jar:hapi_1.2.0.wso2v1.jar:com.packt.wso2.esb.client.hl7.jar:commons-logging-1.1.3.jar com.packt.wso2.esb.client.hl7.HL7Client
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Select Axis2 Transport HL7 and then click on Install and follow the wizard"
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title through the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files for all Packt books you have purchased from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website, or added to any list of existing errata, under the Errata section of that title.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.