使用Spring Integration构建企业级集成解决方案

Spring

Integration

需积分: 10 77 浏览量更新于2023-06-23 收藏 15.49MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"Pro Spring Integration (Apress)" 是一本深入介绍Spring Integration的书籍，由Dr. Mark Lui, Mario Gray, Andy H. Chan, 和 Josh Long撰写。这本书旨在帮助读者构建企业级的集成解决方案，利用Spring Integration的强大功能。 Spring Integration是Spring框架的一个扩展，专注于企业应用集成（EAI）。这个框架的设计目标是轻量级、易测试，并且具备较低的入门难度，其理念比自定义解决方案更为简洁。长期来看，Spring Integration提供了更高的灵活性和适应性。通过它可以与标准技术如EJB、RMI、JMS等协同工作，允许在单一模型中处理复杂集成问题，从而简化这些技术的使用。书中内容包括： 1. 企业应用集成基础：介绍了集成的基础概念和重要性。 2. 探索替代方案：比较了不同集成方法的优缺点。 3. 核心Spring框架介绍：深入讲解Spring框架的基本概念和组件。 4. 企业级Spring：探讨Spring在企业级应用中的角色和用法。 5. Spring Integration入门：详细阐述Spring Integration的核心概念和架构。 6. 通道（Channels）：解释如何使用通道来传输消息。 7. 转换与丰富：讨论消息的转换操作和数据的丰富过程。 8. 消息流：路由和过滤：探讨如何控制消息的流向和过滤条件。 9. 终端和适配器：介绍如何结束消息流并与其他系统接口。 10. 监控与管理：讲解如何监控和管理Spring Integration系统以确保稳定运行。 11. 与硬件交互：讨论如何处理底层系统交互。 12. 使用JMS和AMQP的企业消息传递：深入JMS和AMQP消息队列的集成。 13. 社交消息：介绍如何集成社交网络平台。 14. Web服务：涵盖基于Spring的Web服务实现和集成。此书适合对Spring框架有一定了解，希望提升到企业级集成解决方案开发的开发者阅读。通过学习，读者将能够掌握Spring Integration的关键特性和实践技巧，从而更好地应对复杂的企业级集成挑战。

资源详情

资源推荐

CHAPTER 1 ■ ENTERPRISE APPLICATION INTEGRATION FUNDAMENTALS

Figure 1–9. Enterprise Service Bus (ESB) Architecture

An ESB is still a server and still encourages isolated servers, but it provides ready-to-go routing and

integration technologies. For many people, something lighter still is required–something that can be

embedded or used standalone. To meet this call, integration frameworks like Apache Camel and Spring

Integration have proven very successful. Even old-guard ESB vendors like MuleSoft are increasingly

trying to enable use of their adapters independent of the broker through frameworks. Time will tell how

this approach works.

Domination by Proprietary Solutions

EAI solutions have traditionally been dominated by costly proprietary solutions that required domain

experts to implement. Until recently, these have been the best approach to solving integration problems.

Some of the more popular integration products are discussed in the following sections.

webMethods (Active Software)

webMethods is an integration product suite now offered by Software AG. The main components of

webMethods are the Integration Server and message broker. The Integration Server is the predecessor to

the modern application server. Essentially an HTTP server on steroids, the Integration Server was

developed to support B2B integration. With support for EDI and custom XML messages, and its own

process flow language, Integration Server provides a platform to integration between companies over

the Internet. With the acquisition of Active Software, webMethods added an enterprise integration

platform to its offerings. Active Software products included an enterprise grade message broker and a

suite of adapters supports integration with all the major ERP and legacy systems. Additional acquisitions

added monitoring and business process support, and created a complete integration platform.

Commercial products such as webMethods provide a suite of visual tools that simplify and accelerate

the implementation of an integration solution.

CHAPTER 1 ■ ENTERPRISE APPLICATION INTEGRATION FUNDAMENTALS

Tibco

Tibco is another major player in the commercial enterprise integration platforms. Tibco has similar

software offering to webMethods with messaging support from TIB/Rendezvous and an integration

server package called ActiveIntegration. Tibco has been used in financial services, telecommunications,

electronic commerce, transportation, manufacturing, and energy with an array of application adapters.

Tibco enters the analytics and next-generation business intelligence markets by acquiring Spotfire, the

grid computing and cloud computing markets by acquiring DataSynapse and enterprise data matching

software product by acquiring Netrics.

Vitria

Vitria has the following two main software product lines.

• BusinessWare: This is Vitria’s integration offering, which has a business process

management (BPM) platform that allows its users to carry out general business

process management, enterprise application integration, and B2B integration; it

supports B2B standards such as EDI, ebXML, and AS2.

• M3O: This allows users to monitor and react to processes across a company’s

internal operations. It uses a combination of BPM, business activity monitoring

(BAM), and web technologies.

IBM MQSeries

MQSeries is IBM’s message-oriented middleware (MOM) offering. Combined with IBM WebSphere and

supporting technologies, MQSeries offers a complete integration solution. This includes a suite of

application adapters and visual tools for development and configuration.

SonicMQ

SonicMQ started life as a messaging broker implementing the JMS API. Later a Sonic ESB product was

added, essentially a container supporting adapters and message routing configurations. Visual tool

support called Sonic Workbench and a BPEL process engine server completed the offering, making it a

full integration solution suite.

Axway Integrator

Axway also provides enterprise and business-to-business (B2B) integration applications. Axway’s

solutions feature a flexible integration and B2B framework, analytics, services and customized

applications.

Oracle SOA Suite

Oracle ESB is largely composed of the message broker and application server from WebLogic and the

message router from BEA AquaLogic. Together with some additional products from Oracle, this is an

integration suite that includes visual tools.

CHAPTER 1 ■ ENTERPRISE APPLICATION INTEGRATION FUNDAMENTALS

Microsoft BizTalk

BizTalk is the Microsoft offering in the enterprise integration market. However, limitation in its product

offering and its ability to run only on Windows has prevented larger market penetration.

EAI Patterns

In a broad sense, integration means connecting computer systems, companies, and people. There are

three basic patterns that you see repeatedly when implementing integrations for enterprise customers:

data synchronization, web portals, and workflow system. These three patterns cover the majority of

integration implementation requests.

Data Synchronization

Data synchronization is the most requested type of integration for an organization, and is used when

business processes in different parts of an organization require access to the same data. It’s almost an

anti-pattern, since this is usually a stop-gap approach where a façade pattern could be used instead. For

example, a customer’s address may be used in a customer relations management system, an accounting

system to bill the customer, or a delivery system to ship a product to them. It is very typical for each

system to have its own data store for customer information for a variety of reasons, including

performance and unique domain models. If a customer makes a change, for example, to his address,

each system must update its view of that customer information. This may be accomplished by

implementing a data synchronization integration pattern (see Figure 1–10).

Data replication only works if each application uses the same database vendor and schema

structure. This is usually not the case when each application has its own technology stack. Another

approach is to export the data into files and re-import them into the other system. This approach can be

slow, since it is difficult to determine what data has changed. Often all the data move between the

systems. In addition, the timeliness of the data will be dependent on how often this synchronization

process is run.

The standard integration approach to data synchronization is using a message-based system to

move the data records inside the messages. A mechanism is needed to detect when a record is created or

updated such as a database trigger or a hook or façade into the application to determine when to push

the data to the other systems.

Figure 1–10. Data Synchronization Pattern

CHAPTER 1 ■ ENTERPRISE APPLICATION INTEGRATION FUNDAMENTALS

Web Portals

Often business owners and executives require information from different systems to answer specific

questions or to get a general overview of the entire organization. It would be ideal to get this information

from a single location rather that search across several different applications. For example, a customer

agent needing to check the status of an order may need to access information from several sources,

including the web application taking the order and the fulfillment system supported by a third-party

application. Or maybe the business executive would like to monitor the activities of several different

areas using a single web page instead of running several different applications. Web portals aggregate

information from several different data sources into a single display without requiring the user to log in

into the different applications supporting the various business areas.

Portal applications have become prevalent in recent years, allowing users to configure a web page

consisting of different frames, or portlets, which allows a composite view (see Figure 1–11). In addition,

most portal frameworks allow a certain amount of interaction between the different frames. Also,

integration frameworks support combining multiple data sources into single model, including

combining the information based on shared properties such as customer or order IDs.

Figure 1–11. Web Portal Pattern

Workflow

A business process can span multiple business areas and systems within an organization, and may

require both automatic agents and human actors to complete successfully. The canonical workflow

example is that of a loan approval process, because it has multiple steps and enlists both human and

system actors. The example goes like this: a customer requests a loan from a bank. The bank rep enters

the request into the system where it will first pass basic validations–does the requester have good credit,

does the requester have the required documents in order, and so on. If that checks out, and the loan is

for an amount deemed to be low risk, the loan is approved. If the loan amount is high risk, it requires

additional audits–somebody in the risk-assessment department needs to scrutinize the request

manually and decide, on a case-by-case basis, whether the loan should be approved. Finally, a letter will

be printed and sent to the requester to notify him of the status of the request (approved or not

approved). In this example, the request moved through at least two different systems and required a

worker of specific authority to examine the request for the process to terminate.

There are a number of workflow engines available using different methods of representing a process

flow, such as BPEL and BPMN. The process flow can be designed at high level without concern for the

CHAPTER 1 ■ ENTERPRISE APPLICATION INTEGRATION FUNDAMENTALS

actual implementation. Later the process can be implemented by integrating the workflow process with

the different applications using an integration framework (see Figure 1–12).

Figure 1–12. Workflow Pattern

Spring Integration Framework

The Spring Integration Framework is a response to the need for an open-source, straightforward

integration framework that leverages the widely adopted Spring Framework. Spring Integration provides

an extension of Spring’s plain old Java object (POJO) programming model to support the standard

integration patterns while building on the Spring Framework’s existing support for enterprise

integration. The Spring Framework is the most widely adapted framework used in organizations today.

Spring Integration works in terms of the fundamental idioms of integration, including messages,

channels, and endpoints. It enables messaging within Spring-based applications and integrates with

external systems via Spring Integration’s adapter framework. The adapter framework provides a higher-

level of abstraction over Spring’s existing support for remote method invocation, messaging, scheduling,

and much more. Developers already familiar with the Spring Framework will find Spring Integration

easy to pick up, since it uses the same development model and idioms.

Summary

This chapter has covered the basics of Enterprise Application Integration (EAI) and integration in

general. It has addressed the motivations and challenges typical of an integration solution. We have

covered the basic approaches to implementing integration: file transfer, database sharing, remote

procedure calls, and messaging. The drive for real-time information has led to event-driven

architectures where information is published as events (in messages) as soon as data is available.

We have looked at the historical evolution of the technology and discipline of integration.

Application integration has been dominated by proprietary vendors for a long time. And finally, the

three most commonly requested patterns for an integration solution were covered: data

synchronization, web portal, and workflow.

剩余657页未读，继续阅读

小文

粉丝: 3
资源: 10

会员权益专享

使用Spring Integration构建企业级集成解决方案

pro spring integration.pdf （英文原版非扫描 高清）

ProSpringIntegrationPDFBooks.pdf 英文原版

Pro Spring Integration

spring boot项目英文文献

关于springboot的英文文献

springboot参考文献

springboot的参考文献

springboot框架外文参考文献列表

列举几个SpringBoot相关的技术文献,以文献引用的格式展示

springboot外文文献

springboot文献综述

推荐5本sql server的书籍，并且说明书籍的ISBN号，出版社，作者，出版日期

javascript相关外文文献

最近6年的C#参考书写在此处。要求序号、作者、书名、出版社、出版时间。

帮我找一下可以写再javaweb毕设里的英文参考文献

设计一个java的图书管理系统并给出具体的代码实现

html5的网页设计与制作研究参考文献

关于java的外语文献_java英文参考文献（涵盖3年最新120个）

oracle中.xml sql语句批量添加

pro_spring_integration.pdf （英文原版非扫描）

会员权益专享

最新资源

pro spring integration.pdf （英文原版非扫描高清）