ESB
(
Enterprise Service Bus
, which is
Enterprise service bus
) Is a tradition
Middleware
Technology
Xml
Product combined with Web services.
ES
B provides the most basic connection neutral in the network, which is a necessary element that constructs a corporate nervous system.
Enterprise Services Bus ESB is a new way to provide reliable, guaranteed message technology. The ESB middleware product utilizes web service standards and a recognized reliable message MOM protocol interface (such as IBM's WebSphere MQ, Tibco's RENICMQ). The common feature of the ESB product includes: connecting the heterogeneous MOM, using the web service description language interface package MOM protocol, and the ability to transfer the Simple Object Application Protocol (SOAP) transport stream on the MOM transport layer. Most ESB products support direct peer communication between distributed applications such as integrated agents.
The concept of Enterprise Service Bus (ESB) is developed from the service-oriented architecture, soa. SOA describes an IT infrastructure application integration model, with a soft component set to each other with a clear hierarchy structure, where an ESB is a pre-assembled SOA implementation, which contains the implementation SOA layering. The basic functional components necessary for the goal.
ESB is a product of traditional intermediate technology and XML, Web services and other technologies
Computer technology and software technology applied to enterprises have been 30 years of history. This is also the main driving force for software technology development. It has now entered a new stage of development. Since various companies continue to process and integrate the business operations of the entire value chain of the internal and external, business integration has a very important growth. There is an ubiquitous IT technology to turn the previously imagined things into reality. It can help achieve expansion from the background to the front desk, to our partner, and to the customer's business market. This IT application integration demand trend is an ESB platform. Rise with important paving effects.
The emergence of ESB has changed the traditional software architecture, which provides a more cheap solution than traditional middleware products, and it can eliminate technical differences between different applications, so that different application servers coordinate operation, achieving different services. Communication and integration between. From the functional view, the ESB provides an event-driven and document-oriented processing mode, as well as a distributed running management mechanism that supports content-based routes and filters, with complex data transmission capabilities, and provides a range of standard interfaces .
First, enterprise service bus (ESB) can have those use
ESB is not universal, he is not an application framework, nor is an enterprise application solution. It is just a communication module for messaging-based calling enterprise services! You can embed it into your application framework, such as embedded Inside the Spring container, or embedded in a workflow system. Its role is to provide a framework and a convenient way to call the SOA service in your business.
Second, the application characteristics of enterprise service bus (ESB)
Large-scale distributed enterprise applications require relatively simple and practical intermediate technology to simplify and unify more and more complex, cumbersome enterprise information system platforms. A service-oriented architecture (SOA) is a good interface and contract that can define a good interface between the different functional units of the application. The SOA user can reuse software unrestricted, interconnecting various resources, as long as IT staff selects the standard interface packaged application, put new application configuration, then other application systems can be very convenient Use these features.
The key to supporting SOA is its messaging architecture - Enterprise Service Bus (ESB). ESB is a product of traditional middleware technology and XML, Web services, etc., which is used to realize accurate, efficient and safe delivery of different messages and information. The emergence of ESB has changed the traditional software architecture that provides a more cheap solution than traditional middleware products, and it can also eliminate technical differences between different applications, so that different application services are coordinated, and achieve different services Communication and integration. ESB has a very wide range of uses in different fields: telecommunications
ESB can support the application integration concept of the telecommunications industry OSS in all directions. It is an ideal telecommunications application software bearer platform.
Power field
ESB can support the data integration concept of the power industry EMS in all directions, is an ideal SCADA system data exchange platform.
The financial sector
The ESB can support the process integration concept of the bank business processing platform in all directions, which is the ideal B2B transaction support platform.
E-government
ESB can support the platform, the information shared exchange platform, the decision analysis support platform and the government portal of the e-government applications.
Third, the structure and function of the Enterprise Service Bus (ESB) provide an open, standard-based message mechanism that completes interoperability between coarse particle size applications (services) and other components by simple standard adapters and interfaces. It can meet the integration needs of large heterogeneous enterprises. It allows several generation technology to achieve interoperability without changing the existing infrastructure. Interesb is specifically used for heterogeneous environments, which can help companies migrate to SOA, which allows companies to continue to use existing deployed software investments. By using ESB, you can have a new service interface with a seamless non-invasive manner with a seamless non-invasive manner, and can support any standards in the deployment environment. More importantly, act as "buffer" ESB (responsible for conversion business logic and data format between many services) is separated from service logic, so that different applications can use the same service at the same time, not in the application or When the data changes, the service code is changed. Fourth, Interesb features a combination of multiple communication technologies Interesb utilizes a variety of recognized, maturity and reliable communication technologies to support multiple modes of the upper data transmission. Based on CORBA and JMS technology, Interesb can simultaneously support synchronous communication, asynchronous communication mode. In asynchronous mode, INTERESB innovation integrates a variety of communication mode, including Message Channel, Point-to-Point, Publish-Subscribe, extension Publish / Subscribe Cluster Mode (P / S Cluster) and supports important security functions such as encryption, compression, and breakpoints during communication. INTERESB organically encapsulates the above-mentioned communication into a whole, and publishes the external interface of CORBA IDL, SOAP, JMS, so that Interesb-based enterprise applications can apply different underfolds in transparent, consistent, efficient ways. Communication mechanism. Highly flexible, distributable information buses in Interesb, implemented flexible enterprise application communication functions by deploying a variety of messaging services in different nodes and calculations. At the same time, INTERESB supports the problem-oriented distributed deployment capabilities of these communication services, including the following three modes: full-connected bus mode, deploy a full-connection message server within INTERESB; concentrated plug-in mode Bus mode, deploy a super forwarding server within INTERESB; "Snowflake Structure" distribution level, deploying multiple super forwarding servers in the interesb in-region. This model is deployed in large SOA systems with strong dynamic growth, manageability, maintainability, and extremely high efficiency. Convenient, standard enterprise application integration mode Interesb provides simple, fast, standard multi-point integration function. Interesb provides a complete development model for enterprise application development and integration to help client applications are connected to the service. These modes customize a series of mechanisms for describing services, notifications, and discovery services, communicating with services. In Interesb, standard service is an integration point between applications. That is, all modes around the service are implemented in standard-based technologies. This makes Interesb adapts to any existing system and makes systems do not have to deliberately follow any special customizations when integrating. Interesb can express two parts of data transfer and application integration when using integrated demand for enterprise application.
Among them, data transfer covers full-scale data transfer content in the user application system; application integration covers data integration, application integration, equipment integration, protocol package, etc. content. Flexible adapter technology A good design of a good adapter is a well-designed SOA service, which provides an abstraction layer that isolates the rest of the application infrastructure with a variety of tricks. The general adapter is the reusable, unified interface developed by interesb to resolve the connection between the system, and each application system needs to be connected to the service integration platform, without the need to connect with each with each other. . Interesb adapters generally include legacy system adapters, technical standards adapters, and adapter development tools. In combination with CORBA, J2EE technology, the underlying Corba distribution calculation interbus interbus, in accordance with CORBA, J2EE technology, and InterMQ message communication in accordance with JMS specification, therefore, INTERESB and CORBA, J2EE have natural combined advantages. But interesb is not equivalent to CORBA. Compared to CORBA technology, Interesb inherits the open standards of CORBA technology, distributed architecture, component technology, and high performance, suitable for complex application integration; at the same time, Interesb also provides the SOA function that CORBA technology is not available. : Interesb supports more technical standards; Interesb supports more extensive interoperability; Interesb has better scalability; Interesb supports support for proprietary systems; Interesb supports future standards. With the MDB / JDO supported by J2EE, Interesb can also be easily connected to the J2EE application system to form a valid functional integration. A wide range of platforms support the Interesb plug-in architecture is open at each level so that transparent interoperability can be implemented with existing basic components, allowing users to trade with speed, cost, and skills. . Interesb can transmit data using any format including XML and binary in any format, and can be implemented on any development platform (C and Java), rather than forcing all applications. Interesb includes a fully connected bus mode, a distribution-level associated joint-level associated with a built-in plug-in bus mode and a "snow-shaped structure". V. Enterprise Service Bus (ESB) What is the actual business application? ESB currently has many business programs, there are many open source products, such as ObjectWeb, Codehaus, SourceForge has such an open source project. Distance is still a distance from the truly maturity In addition, various manufacturers are their own, and the current JCP has no draft technology. The standard designation also has a long distance. Of course, the current state is the same as SOA. I believe that SOA is really popular, ESB will More mature. From the requirements of the Enterprise Service Bus (ESB) technology and innovation, the message delivery technology is now in development due to the requirements of larger tasks. In order to provide the flexibility to today's real-time businesses, a mixed message delivery model requires the advantages of the web service to communicate with traditional asynchronous messaging. Traditional message queuing middleware will soon be replaced by the Enterprise Service Bus (ESB) technology, thereby bringing messaging to a new height. The new ESB backbone (spawning the next generation of integration and application platform products) will significantly improve the software infrastructure of most companies. The industry is turning to message delivery and ESB, and use this as a core application platform infrastructure model, which will mark a turning point: surrounding the company's use of its information resources, it triggers new huge innovation wave; enterprises are using Event architecture. This will eliminate all the doubts about IT playing key roles in strategic business distinguishing.
Introduction In the past 10 years, the competitive pressure and the current periodic technology have changed fundamentally on the rhythm of the company. In the past, companies can make decisions based on the batch report at the end of the month. Now, the real-time process means that if the raw materials have problems in the morning, or there is a power outage accident, it will cause the goods to be delivered and consignment in the afternoon. As a result, companies have to respond to emergencies at a speed of faster - otherwise it will stand by side. The era of Zero Latency Enterprise has arrived. Today's corporate environments are developing at a point in response to this challenge. Heterogeneous storage, network and hardware support "Island Calculation" (application and data is isolated from each other or block segmentation), which leads to excessive use and management of the environment and make it a resource-intensive. This complexity is undoubtedly an obstacle for most of the key challenges that enterprises must face, including: meeting the growing demand for the use of multi-channel communication. Real-time management infrastructure to meet changing business needs. Make business diversification to promote flexibility in business, and reduce economic risks associated with fixed product lines. Ensure that the information service requests for customers, partners, and employees make a fast and high quality response. In the past few years, the rapid development of EAI, B2B and application development has promoted several key technologies and standards, and these technologies and standards have promoted significant progress in the field of infrastructure: XML as a general, self-explanatory Data exchange format has been used for most applications. For web-oriented information exchange and subsequent infrastructure, with XML to make the use of web services to inevitable things. Java has been accepted as a main technique for server-side, and J2EE has been accepted as a standard for application servers. Enterprise Service Bus is standardized around the Java Message Service (JMS) in the field of transactional messaging and real-time event notification. The public management framework for server-side components has been implemented through the Java Management Extension (JMX) standard. The infrastructure must be a large number of information services through multi-channels like business. The next generation of enterprises require loosely coupled resources to share public communication and management infrastructure across multiple fields. The enterprise infrastructure has to be operated as tangible business, allowing the resources to be dynamically managed to deal with the needs of customers and partners, while processing the supply and availability of system resources. Enterprise applications also require a standard collaborative model to maximize this infrastructure. To this end, real-time enterprises use the best practices from real-time infrastructure and GridTechnology. Real-time enterprise components form some concepts of real-time enterprises to define the concept of the server-side grid environment, which is used to describe the structure of its core components (see Table 1) similar to Gartner's 5-layer grid technology model. An ESB based on existing and widely used technologies and open standards can provide an adaptable distributed architecture for service collaboration, management, and control. ESB supports the runtime deployment of business services anywhere within the company, and provides collaboration and notification services as part of its core infrastructure. Let's take a look at how the ESB technology is mapped to the 5th floor model of Gartner. The infrastructure resource and virtual operating system Layer 0 consists of infrastructure resources, including network, server, storage, and operating system environments for each server. The first layer is located above the infrastructure layer and establishes a multi-resource distributed operating system. It supports functions such as work plan, integrating resource names into overall structures and ensuring uniform certification between different systems. Although Gartner uses J2EE as a layer 2 technology, we believe that distributed JMX and a combination of J2EE-based application servers will have the characteristics of virtual operating systems. Use containers or micro-kernels that provide deployment and full JMX to all components and services, allow remote activation and management of services. JMX is originally designed to manage individual agents as a technology.
JMX can extend to the JMS, the range can scale to manage a single agent, cluster, or loose consortium (if you like, it can be called a super cluster), allowing the joint ESB infrastructure to perform full life cycles And deploy management. Since JMX also integrates many traditional management protocols, such as SNMP, the ESB infrastructure can provide the hot deployment of on-demand for Java, Web services, and traditional platforms (self-annealing) The infrastructure. Distributed Programming Model Distributed Programming Model constitutes a first layer of real-time enterprise: a core infrastructure that can be collaborated and notified between applications and services (whether internal or external). ESB provides event notification, dynamic routing and transaction ensuring delivery; and uses a defined procedure language to make the application via a public API to act in activity coordination. Real-time enterprises require the correct data to be passed to the correct position in the appropriate time; JMS (Java Message Services) provides event distribution and transactional ways to ensure delivery. At the same time, it also requires a smart data structure (DataFabric) that can be distributed within the network range when needed, and the purpose is to improve throughput and reduce the load of the valuable background system. The backbone of this structure is formed by JCACHE (Java General Buffer Frame). A tuplespace similar to the "Tuplespace" of the message queue "one and only one" pass semantics and release / subscribers of broadcasting and pending system are combined together. The tuple space is like a connected memory shared by an unlimited number of processes. The process can add a tuple to the space (essentially the data object), or from the tetraunction to work in exclusive way - if needed, can always be waiting state until the appearance of the matching object. The process can also read the tuple without deleting it from the space. This example (a message queue "and only one" delivery semantic and release / subscribed broadcast function and peer-to-peer-to-peer-to-peer-to-pending system) are mapped to the top of JCache, which provides a high performance distribution of this concept Implementation. This can also be combined with a business process model engine (for example, JBPM: www.jbpm.org) to provide a wide range of distributed programming domains. Independent work between processes - get the appropriate input from the tuple space and put the output to the yuan group space for subsequent tasks. The process of execution on the tuple is less than the constraints received in the execution order on the traditional workflow system. This model provides distributed shared memory, universal cluster, parallel computing, and distributed workflow and BPM foundation. The application makes up the application of real-time enterprise Layer 3 depends on the resources of the enterprise infrastructure, and communicates with the collaborative programming model. Architeists have realized more loosely packed and multi-layer component models, rather than developing separate or simple two-layer client / server (C / S) applications. The standards adopted for definition, discovery, and actual execution of this model (such as WSDL, UDDI, SOAP for web services) helps to facilitate the implementation of the service architecture. The J2EE application server based on the virtual operating system provides an integration point based on transactional security services for infrastructure. Since the distributed ESB is an enable technology like a grid, the Web service interface defined by the OGSI source code is a natural selection. OGSI is currently the factual standard for external grid technology, which allows the grid service written in an environment to be easily deployed in other environments. In addition, the ESB can provide an extensible rule engine based on optimizing the TETE algorithm. Own business rules make it possible to manage rapidly changing business processes, decision mechanisms in a lower layer, and make message filtering and routing, without having to change the basic application. It liberates the business from the dependence on the slow code development cycle, allowing analysts that are proficient in business to carry out the necessary changes to support new products or regulatory demand, without interrupting the operation of the system. "In the past 10 years, competitive pressure and day-crocere-changing technology fundamentally changed the management of corporate operations" Management Support real-time enterprise requires services to manage and coordinate applications and services on macro and micro-level.
