In the last several years application integration, at least the notion, has worked its way into most information technology departments. This has been driven by a number of emerging developments including the need to expose information found in existing systems to the Web, the need to participate in electronic marketplaces, the necessity the integrate their supply chain, and more importantly, just enabling their existing enterprise systems to finally share information and common processes. By now we know that application integration is important, thus there is not much need for me to restate that here. What is not as well understood is the amount of planning and coordination that needs to occur in order to pull off application integration today, EAI or B2B, this, despite the availability of some pretty good technology that can make short work of joining systems together. Moreover, while many are interested in application integration few have taken the time to read books such as this, or the books I''ve written in the past, to better understand both the limitations and the opportunities. More often than not application integration architects are driven more by the hype around the emerging standards and technology and less by their business needs and technology requirements. The end result is many failed projects, more due to lack of knowledge than lack of technology. In essence application integration is less about J2EE versus .

NET, and more about understanding the requirements and future growth of the problem domain, a not-so-sexy activity that is all to often left on the side of the road, choosing instead to "management by magazine." Indeed application integration is more of an all-encompassing concept, consisting of, but not limited to metadata, business logic, interfaces, performance management, business processes, workflow, information processing, database integrity, standards strategies, vertical subsystems, accountability, application design, and middleware technology. Application integration is a strategic activity and technology set that can enable an organization to run much more efficiently, and in most instances provide a significant competitive advantage. Why a New Book? If you''ve been following my writings for the last several years you''ll know that this is the third book on application integration, and perhaps the most significant. We need a new book for a few reasons: First, the arrival of a new service-oriented middleware technology standard, web services. As we move further into the world of application integration, we''re finding that application service-based approaches make sense for many problem domains. I''ve stated that in both previous books. Now with the advent of a new service-based approach, web services, we now have another opportunity to put that into perspective.

I''ll talk about web services and how they related to application integration, albeit this is not a book about web services, just the proper application of web services in application integration problem domain. Second, there is a need to take application integration to the next level. The first book on application integration, Enterprise Application Integration, the first of its kind, covered the basic concepts of allowing two or more business systems to share processes and data. That book was written for the rank beginner since EAI, at least the notion and buzzword, was new. The next book, B2B Application Integration: eBusiness-Enable Your Enterprise, really extended the concepts put forth in the first book to the inter-enterprise problem domain, which reuses many of the same approaches and technologies, but does require knowledge of old and new B2B standards and technologies including XML, EDI, RosssetaNet, BizTalk, ebXML, etc. This book is all about looking at advanced application integration concepts, approaches, and technologies, with many topics typically not covered in the previous books or any other books for that matter. We''ll be looking at how to approach very complex and challenging application integration problem domains, and leverage forward-looking concepts and technology, including how to understand your problem domain, determine your requirements, create a logical application integration architecture, and most importantly, backing the correct grouping of application integration technologies into your solution to create an infrastructure that is strategic to the success of your organization. Target Audience This books is written with the technical manager and enterprise architect in mind, those that live on the frontlines of technology everyday and have to make key technology decisions that can make or break their businesses.

This does not mean, however, that developers and IT executives won''t benefit from this information, especially when it comes to understand application integration in context of their day-to-day activities. What this Book is, What this Books is Not At its essence this is an information technology strategy book with some detailed technology discussion, just enough technology content to support the notions put forth. This book is looking to take an important topic, application integration, to the next level by suggesting certain ways to view the problem that may not have been understood in the past. This means we''ll focus on higher-level approaches and solutions, rather than spending a lot of time describing the technologies. There are plenty of other books that do that. For example, while I may talk about the Java Message System (JMS) in terms of the general ideas behind this important standard, at its use in an application integration solution set, you can obtain more details by reading the 200+ page standard found on www.javasoft.com, or other books specifically on JMS.

The same can be said about .NET, J2EE, ebXML, and other technologies I''ll discuss in this book. Indeed, I will cover the enabling technologies by focusing on their value in solving the application integration problem. For most of you, further research into these technologies or standards won''t be required; there will be enough information here. Others, however, looking for implementation level details will have to take a deeper dive using further research outside the scope of this book. Organization This book follows a clearly structure it will make your reading experience more valuable. There are 4 parts: Part I: Types of Application Integration Part II: Application Integration Technology Part III: Application Integration Standards Part IV: Advanced Topics In Part I I''m focusing on the types of application integration approaches you''ll find in your problem domain, in other words general approaches to sharing information, processes and application services between any number of applications. It''s important that you read this section since it sets up concepts for the rest of the book.

Also, if you''ve read my previous books you''ll see how my thinking is morphing after building and implementing a lot of application integration technology. In Part II we''ll talk about application integration technology including middleware, and specifically application integration middleware including integration servers and application servers. Once again, we will discuss the technology in terms of their uses within the world of application integration. If you''re a middleware god, perhaps you can skip this section, else it will be a good review. In Part III we''ll talk about application integration standards. If you''ve been in this world at all you''ll know that standards are the way people are looking to approach this problem rather than vendor solutions. In this section I''ll talk about the issues with doing that, as well as describe the standards that are relevant to application integration. In Part IV we''ll talk about how you need to approaches your own application integration problem domain, including procedures, methodologies, and techniques that you can employ to improve your chance of success.

Moreover, we''ll address advanced application integration topics, including the advent of vertically oriented application interaction technology as well as the advanced use of metadata. Other Stuff The Appendixes. There I''ll find some useful reference information supporting the core content of the book. While in many cases people skip the appendixes, I urge you to read through what''s there. So, if you''re moving on to Chapter 1, relax. It will be a painless process, perhaps fun. See you at the end. 0201844567P04252003.