Enterprise Service Bus (ESB) Technology and Reprotice (use asynchronous messaging and intelligent route to extend Web service)
Author: Nigel Thomas and Robrert Dalies
The message delivery technology is now in development due to the requirements brought by greater tasks. In order to provide the flexibility required for today's real-time enterprises, a mixed messaging model is needed to combine the advantages of the web service 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, a new round of huge innovation; enterprises are using incidents 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 unexpected events at a rate 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 undoubted to be an obstacle for most of the key challenges that enterprises must face. These challenges include: Q Meets to meet the growing demand for the use of multi-channel communication. q Real-time management infrastructure to meet changing business needs. Q makes business diversification to promote business flexibility, and reduce economic risks associated with fixed product lines. Q ensures fast and high quality response to customer, partners, and employees.
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: Q XML as a general, self-explanatory The 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. Q Java has been accepted as a main technique for server-side, and J2EE has been accepted as a standard for application servers. Q Enterprise Services Bus is standardized around the Java Message Service (JMS) in the field of transactional messaging and real-time event notification. Q Via the Java Management Extension (JMX) standard has implemented a public management framework for server-side components.
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. Enterprise infrastructure has to operate as tangible business, allowing resources to perform dynamic management to deal with customer and partners, while handling system resources supply and availability changes. 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 grid technology (Grid Technology).
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. Table 1 Real-time enterprise model infrastructure resource and virtual operating system Layer 0 consists of infrastructure resource, 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. As a technology, JMX is initially designed to manage a single agent, such as an application server. 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 Data Fabric 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 Tuple Space that is a tether that delivers a message queue to a "one and only one" delivery semantics and pending system of the release / subscription. 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.
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. Architects have realized the superiority of more loosening and multi-layer components, rather than developing an independent or simple two-layer client / server (C / S) application. 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, competition stress and changing technology have fundamentally changed the rhythm of enterprise operations."
Managing support real-time enterprises require services to manage and coordinate applications and services on macro and micro-level levels. Layer 4 provides the management support required to implement security policies, define the resource usage guide, and integrated operation processes. Basic features include: monitoring: finishing events and statistics to understand the performance, resource usage and operational behavior of the application. It allows for simulation, error determination, and manual and automatic balance for resource utilization. Coordination: It is necessary to intelligently manage, control, self-repair, and fine-tuning applications by inspiration analysis, dynamic rules, and flexible workflows. By using a valid dynamic topology layout (where the correct number of applications is running), real-time enterprise management uses the load and selects the correct hardware and location to run the application. The ESB management structure combines distributed JMX and statistical events and comparisons with the Java specification framework based on the application level based on the same standard. This provides resource usage, performance monitoring, and warning notifications to provide location transparency, discovery, remote control, and statistical finishing. These techniques allow prophecy to intelligent resource visualization, collaborative cooperation, and supply environments across the real-time enterprise, thus giving insight for IT managers and business managers.
