Home > Store

Next Generation Application Integration: From Simple Information to Web Services

Register your product to gain access to bonus material or receive a coupon.

Next Generation Application Integration: From Simple Information to Web Services

Book

  • Your Price: $47.99
  • List Price: $59.99
  • Usually ships in 24 hours.

Description

  • Copyright 2004
  • Dimensions: 7" x 9-1/4"
  • Pages: 512
  • Edition: 1st
  • Book
  • ISBN-10: 0-201-84456-7
  • ISBN-13: 978-0-201-84456-6

"Linthicum provides an insightful overview of the services-integration issues that will enable you to capitalize on current and future integration technologies. He also dives deep into the key Web services technologies for implementing the next generation integration architecture. Highly recommended for those thinking of moving from traditional EAI to Web services."
--Dr. Ravi Kalakota, CEO, E-Business Strategies
Author of Services Blueprint: Roadmap for Execution

For a majority of businesses, application integration is an outright failure. Most companies' computer systems are labyrinthine at best and self-destructive at worst. With the arrival of Web services, the new service-oriented middleware technology standard, and increasingly complex and challenging problem domains, it's time to take application integration to the next level.

In Next Generation Application Integration distributed computing and application-integration expert David S. Linthicum describes the effect that this new generation of middleware will have on traditional application-integration efforts. Using key industry examples and case studies, Linthicum reveals the techniques and practices that are necessary to revolutionize data-sharing for any company--from sole-proprietorship to Fortune 500.

In this book you'll find a thorough discussion of today's most advanced application-integration concepts, approaches, technologies, and solutions. Written with the technical manager and enterprise architect in mind, this book addresses essential application integration issues such as:

  • Strategies for dealing with complex problem domains
  • Forward-looking approaches to ensure long-term solutions that are right for your company
  • Techniques for implementation of new Web services middleware
  • Introductions to the appropriate technologies for next generation application integration
  • Scenarios for Web services integration
  • Support concepts outlined by case studies and real-world examples
  • Descriptions and analyses of the different types of Web service integration--standards, implementation, and enabling technology
  • Full analysis of Web services and integration, including the relationship between EAI and Web services
  • How to leverage both vertical and horizontal application-integration standards

If you're responsible for managing or implementing application-integration middleware, Next Generation Application Integration will prove to be an indispensable resource.



0201844567B07142003

Sample Content

Online Sample Chapter

Approaching Application Integration

Downloadable Sample Chapter

Download the Sample Chapter related to this title.

Table of Contents



Preface.


Acknowledgments.


1. Approaching Application Integration.

Moving from Information-Oriented to Service-Oriented Application Integration.

Application Integration Approaches.

Information-Oriented.

Business Process Integration-Oriented.

Service-Oriented.

Portal-Oriented.

Application Integration: Clearly the Future. @PARTHEAD -= I. TYPES OF APPLICATION INTEGRATION.



2. Information-Oriented Application Integration.

Coupling versus Cohesion.

It's Just Data.

IOAI: The Gory Details.

Information Producers and Consumers: Common Patterns.

Database.

Application.

User Interface.

Embedded Device.

Approaching Information Integration.

Identify the Data.

The Data Dictionary.

Catalog the Data.

Logical Model.

Building the Enterprise Metadata Model.

Normalizing the Problem Domain.

Working with Information-Oriented Application Integration.



3. Business Process Integration-Oriented Application Integration.

BPIOAI Defined.

Drilling Down on BPIOAI?

Implementing BPIOIAI.

Tools and Approaches.

Process Modeling.

Middleware Interfaces.

BPIOAI and Application Integration.



4. Service-Oriented Application Integration.

The Basics.

Enter Web Services.

Web Services Exposed.

Where's the Fit?

Scenarios.

Understanding Service Frameworks.

Moving to Application Services.



5. Portal-Oriented Application Integration.

POAI by Example.

Portal Power.

Web-Enabled World.

Single-System Portals.

Multiple-Enterprise-System Portals.

Trading Community.

Portal Architecture.

Web Clients.

Web Servers.

Database Servers.

Back-End Applications.

Application Servers.

Portals and Application Integration. @PARTHEAD -= II. APPLICATION INTEGRATION TECHNOLOGY.



6. Middleware Basics.

What Is Middleware?

Middleware Models.

Point-to-Point Middleware.

Many-to-Many Middleware.

Synchronous versus Asynchronous.

Connection-Oriented and Connectionless.

Direct Communication.

Queued Communication.

Publish/Subscribe.

Request Response.

Fire and Forget.

Types of Middleware.

RPCs.

Message-Oriented Middleware.

Distributed Objects.

Database-Oriented Middleware.

Transaction-Oriented Middleware.

TP Monitors.

Application Servers.

Integration Servers.

Tough Choices.



7. Middleware Types and Application Integration: What Works Where?

Transactional Middleware and Application Integration.

Notion of a Transaction.

The ACID Test.

Scalable Development.

Database Multiplexing.

Load Balancing.

Fault Tolerance.

Communication.

Application Servers.

Evolving Transactions.

Enterprise JavaBeans.

Transactional COM+ (Using AppCenter).

RPCs, Messaging, and Application Integration.

RPCs.

Message-Oriented Middleware.

Future of MOM.

Distributed Objects and Application Integration.

What Works?

What's So Difficult?

What's So Easy?

What's a Distributed Object?

The General Idea of ORBs.

COM+.

The Realities.

Database-Oriented Middleware and Application Integration.

What Is Database-Oriented Middleware?

Types of Database-Oriented Middleware.

Going Native.

Database Gateways.

EDA/SQL.

Ready for Prime Time.



8. Java-Based Middleware Standards and Application Integration.

Java-Based Middleware Categories.

Database Oriented.

Interprocess.

Message Oriented.

Messaging Models.

JMS and Application Development.

Application Hosting.

Connectivity.

J2EE.

Transactional J2EE.

Messaging J2EE.

Distributed Application J2EE.

Java and Middleware.



9. Integration Servers and Application Integration.

Integration Servers Defined.

Integration Server Services.

Why a New Layer?

Applications, Databases, and Middleware.

Transformation Layer.

Schema Conversion.

Data Conversion.

Intelligent Routing.

Rules Processing.

Message Warehousing.

Repository Services.

User Interface.

Directory Services.

Management.

Adapters.

Other Features.

Topologies.

The Future of Application Integration and Integration Servers.



10. Adapters and the J2EE Connector Architecture.

The Purpose of Adapters.

Thin Adapters.

Thick Adapters.

Static and Dynamic Adapters.

Information-Oriented versus Service-Oriented Adapters.

Interface Types.

JCA.

Breaking Down JCA.

Understanding JCA Resource Adapters.

Packaging Your JCA Adapter.

CCI.

Adaptable World. @PARTHEAD -= III. APPLICATION INTEGRATION STANDARDS.



11. XML, XSLT, and Application Integration.

So, What's the Big Deal?

The Value of XML.

What XML Adds.

What XML Does Not Add.

XML Meets Middleware.

Integration Solutions.

XML-Enabled Standards.

Using XSLT for B2B Application Integration.

What Is XSLT?

The Mechanisms.

XSLT Processors and Processing.

Transformation Process.

XSLT Applications.

Schema Conversions.

Converting XML to Something Else, and Vice Versa.

XSLT and Application Integration.

XML and Application Integration.



12. ebXML and Application Integration.

ebXML for Trade.

ebXML Components.

ebXML Architecture.

Business Process Modeling.

Conformance to ebXML.

ebFuture.



13. bPEL4WS and Application Integration.

The BPEL4WS Basics.

BPEL4WS and WSDL.

BPEL4WS Process Syntax.

Exception Handling.

Life Cycle.

Message Properties.

Correlation.

Data Handling.

BPEL4WS by Example.

Value of BPEL4WS.



14. UCCnet and RosettaNet: Supply Chain Integration Standards.

Categories of Standards.

UCCnet: The Basics.

UCCnet Components.

UCCnet Message Set.

UCCnet: A Contender?

RosettaNet.

RosettaNet History.

What's RosettaNet?

Business Process Analysis.

PIP Development.

Dictionaries.

It's the PIP.

The Technology.

PIP Communication.

PIP Message Structure.

RosettaNet Networked Application Protocols.

RosettaNet and B2B Application Integration.

Supply Chain Standards Moving Forward.



15. SOAP, WSDL, and UDDI, Oh My . . . Web Services Foundations and Application Integration.

SOAP.

WSDL.

UDDI.

Web Services as an Enabling Standard.



16. Other Standards.

WS-Security.

XML Encryption.

XML Signature.

XKMS.

SAML.

XrML.

Playing the Standards Game. @PARTHEAD -= IV. ADVANCED TOPICS.



17. The "Verticalization" of Application Integration Technology.

A Huge Shift in Thinking.

Approaching Finance with STP.

GSTPA.

Omgeo.

SWIFT.

Approaching Health Care with HIPPA.

Approaching Manufacturing, Retail, and Distribution with Supply Chain Integration.

Value of the Chain.

Supply Chain Entities.

Defining Your Supply Chain.

Forecasting and Supply Chains.

Extending Applications.

Binding the Home System to a Stranger's.

The Process.

Supply Chain Technology.

It's a Vertically Aligned World.



18. 12 Steps to Application Integration.

Step 1: Understand the Enterprise and Problem Domain.

Step 2: Make Sense of the Data.

Identify the Data.

The Data Dictionary.

Catalog the Data.

Build the Enterprise Metadata Model.

Logical Model.

Physical Model.

Normalizing the Enterprise.

Step 3: Make Sense of the Processes.

Process Integration.

Process Cataloging.

The Common Business Model.

Leveraging Patterns for Service-Oriented Application Integration.

Types of Patterns.

Application-to-Application Integration.

The Value of Patterns.

Step 4: Identify any Application Interfaces.

Application Interface Directory.

Step 5: Identify the Business Events.

Step 6: Identify the Data Transformation Scenarios.

Step 7: Map Information Movement.

Step 8: Apply Technology.

Step 9: Test, Test, Test.

Step 10: Consider Performance.

Step 11: Define the Value.

Step 12: Create Maintenance Procedures.

Method or Madness?



19. Leveraging Ontologies and Application Integration.

Ontologies: A Deeper Dive.

Finding the Information.

Ontology Treatment.

Web-Based Standards and Ontologies.

Types of Vertical Ontologies.

Value of Ontologies.



20. Application Integration Manifesto.

Mandatory.

Connectivity.

Support for Information-Oriented Connections.

Support for Service-Oriented Connections (a.k.a. Web Services).

Support for Coupling.

Support for Cohesion.

Support for Transaction-Oriented Connections.

Support for Abstraction.

Transformation.

Support for Differences in Application Semantics.

Support for Differences in Content.

Support for Abstract Data Types.

Information Routing.

Intelligent Routing.

Filters.

Persistence.

Logging.

Message Warehousing.

Transactionality.

Short-Term Transactions.

Long-Term Transactions.

State Management.

Process Awareness.

Support for Modeling.

Support for Monitoring (a.k.a. Business Activity Monitoring).

Support for Optimization.

Support for Abstraction.

Need for Rules.



Glossary.


Appendix A. PIP Specification.


Appendix B. Where XML Fits with Application Integration.

Understanding the Application Integration Problem.

Integration Realities and XML.

XML Meets Middleware.

Integration Solutions.

XML Standards and Application Integration.

XML and Application Integration.



Appendix C. Knowledge-Oriented Middleware.

The Next Level of Middleware.

Layers.



Bibliography.


Index.

Preface

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

Index

Download the Index file related to this title.

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020