Preface

This book is meant to be a guide to the Microsoft ESB Toolkit 2.1. In this book, we will provide a high-level view along with detailed descriptions of the services and components that make up the Toolkit. Scenarios are provided to help you understand how these services and components can be used.

What this book covers

Chapter 1, ESB Toolkit, Architecture, and Features, provides us with an overview of the Enterprise Service Bus (ESB) and the architectural principles that define it.

Chapter 2, Itinerary Services, explains the conceptual definition of different services and processes that a message should go through to complete a business process.

Chapter 3, ESB Exception Handling, explores the ESB Exception framework, its components and services, and the benefits it provides.

Chapter 4, ESB Toolkit Web Services, explores the different services that the ESB provides and views a few scenarios.

Chapter 5, ESB Management Portal, shows us how to publish EndPoints into UDDI 3.0, and the use of the different parameterizations that we can do.

Chapter 6, ESB Toolkit Version 2.2 for BizTalk 2013, shows us what's new in the Toolkit, and explains how to install and configure it.

What you need for this book

You need the following to work with the examples given in the book:

• Microsoft BizTalk Server 2010 Developer or Enterprise Version

• Microsoft ESB Toolkit 2.1

• UDDI 3.0

Who this book is for

This book is primarily for experienced BizTalk Developers and Architects. IT Managers and Business Analysts would also benefit from this book.

Conventions

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, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "These are instantiated using the Microsoft.Practices.ESB.ExceptionHandling.ExceptionMgmt.CreateFaultMessage method of the API within an exception handling block in an orchestration. This generates a new BizTalk message whose schema is Microsoft.Practices.ESB.ExceptionHandling.Schemas.Faults.FaultMessage."

A block of code is set as follows:

<?mso-infoPathSolution solutionVersion="1.0.0.346" productVersion="11.0.6565"
PIVersion="1.0.0.0" 
href=file:///\\localhost\publish\Microsoft.Practices.ESB.ExceptionHandling.InfoPath.Reporting.xsn
name="urn:schemas-microsoft-com:office:infopath:
Microsoft-Practices-ESB-ExceptionHandling-InfoPath-Reporting:
http---schemas-microsoft-biztalk-practices-esb-com-exceptionhandling"
language="en-us" ?><?mso-application progid="InfoPath.Document"?>

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: "All the reports are accessible through the Reports link on the portal navigation bar, and can be filtered by application and by time range."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.

Reader feedback

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 <[e-mail]>, and mention the book title via 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.

Customer support

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.

Errata

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/submit-errata, 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 on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.

Piracy

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 <[e-mail]> with a link to the suspected pirated material.

We appreciate your help in protecting our authors, and our ability to bring you valuable content.

Questions

You can contact us at <[e-mail]> if you are having a problem with any aspect of the book, and we will do our best to address it.