Docstoc

EAI and technology integration level

Document Sample
EAI and technology integration level Powered By Docstoc
					EAI and technology integration level
?Pass into EAI is a complex task, EAI integration framework and its implementation
techniques involved in many levels, such as the data layer integration /
integration-level business functions, data access technology and MOM and other
middleware technologies, let us now take a closer look .

EAI integration framework has several versions in a foreign country, some from the
operating system has been integrated into the integration layer, as many as 7 levels,
people feel EAI "inclusive", shown in Figure 1.




Figure 1 EAI integration of positioning

Data layer integration

Data layer is most likely to think of all the integration model, which is the initial
starting point for EAI. In the specific integration requirements, the data integration
include the following:

CRM call center data-sharing applications, real-time view background information on
ERP system, inventory database, or customer purchase records, is a typical
application example of data sharing between systems.

Data Migration This generally occurs when the new system installed in the enterprise,
need a lot of other applications once the initial data loading occasions. For example,
in the implementation of CRM projects are often transferred from the ERP system,
spread over a customer and product master data.

Data replication for companies with multiple branch offices, the local system in order
to improve the speed, often in the center and branch office has a data backup, and then
use the data synchronization of two databases line. In technology, from the familiar
point of FTP, to the ODBC, JDBC data gateway to news as a carrier asynchronous
message queue (MQ, including Java Message Service and IBM MQSeries and
Microsoft MSMQ messaging services provided) to XML-HTTP transfer and other
data formats, all belong to the scope of the data integration layer. Determine whether
the standard data integration, is to see whether the direct integration of data in
applications, low-rise, with or without touching the application business logic.




Figure 2 API calls the traditional environment

Integration of business functions
The integration of business functions, can be developed through the application
provider API calls, based on functional business components (Business Component)
method call and the current date based services (such as Business Service, Web
Service) function calls of three ways.

API method calls API's purpose is to "borrow" some
low-level features about the system, mainly for internal applications, tight coupling
(Tightly coupled) type integrated, component-based standard for many applications,
not directly, but must appropriate transformation of it. The call indicated in Figure 2.




Figure 3 business component method calls on

Component-based method of function calls based on business method calls on the
existing capabilities through packaged (Wrapping), installed to meet modern
component standard variety of properties and methods, so that
"repackage" become a new member of the club (that is, virtual
business components, Virtual Business Component), other line components for the
application of standards (such as COM, EJB, etc.) call, shown in Figure 3. Of course,
the application of standard components already on the need to go through the process
of packing. In technology, there Microsoft's COM, DCOM, COM +, the
Object Management Group (OMG) released the definition of distributed CORBA, and
the latest J2EE platform, launched by the Sun systems based on enterprise Java Bean
(EJB) component standard. All of these functional components technologies can be
used with the API or not brought on the application of API package deal, so that it can
be to the latest application of the standard components (such as Web applications) to
directly call.

Based on service (Service) functionality within the enterprise integration services
including business services (Business Service) and the shared network services for the
Internet (Web Service). The former is used for internal business process, which is
global enterprises, government use. An organization can be internal functional
components or business services, according to Web services standards (XML, WSDL)
components packaged into a Web service, then to service Yellow Pages (white pages,
green pages) for registration. Service requesters to find services, return to service
specific URL address, according to the use agreement, the service binding to their
business processes in order to achieve functions invoked in order to achieve B2Bi
integration purposes, it's the basic process shown in Figure 4 said.

EAI middleware technology

To provide integration between the middleware application system, various types of
EAI solutions provider is the main way, in general, middleware products are used the
following types of technology:




Figure 4 Schematic diagram of network services

Data access technology to provide direct access to the means of different data sources,
without changing the application layer procedures, such as people familiar with the
ODBC, JDBC, JDO, ADO standard interfaces such data.

Message-based middleware technology (MOM) MOM provides an asynchronous
messaging mechanism, the approach shown in Figure 5. MOM middleware
application integration in all needs within the system, must install the MOM of the
API caller to the information submitted to the middleware for processing. Obviously,
MOM's advantages are: sending and receiving do not have to wait online
(loosely coupled). Disadvantages are: overload situation occurs. With the continuous
improvement of products, of course, in the load balance will be further improved.
MOM products provide the main IBM MQseries, Microsoft's MSMQ.
With the JMS (Java Message Service) to rise, MOM product applications will become
more widespread. Relative to the application servers mentioned below, it is relatively
"pure" - for integration services.




Figure 5 MOM sending mechanism

Remote Call (RPC) Remote calls are the same as with the use of MOM client / service
model, different point, RPC is a synchronous line, that is, the receiver should wait for
a reply before continuing their work. This reduces the probability of error, of course,
to slow down to wait.

TP monitor transaction processing monitor (Transaction Processing Monitors) as a
middleware, is the prototype of the modern application servers. It is mainly used to
monitor and manage clients and multiple back-end application transactions between
the state, consider the load balancing, mapping the client's request to each
application, as shown in Figure 6.




Figure 6 TP monitor

Target requests medium (Object Request Brokers, ORB) ORB is designed for
applications    referred to    the    functional  components   of    the
"intermediary" is a business function integration level of
integration middleware, based on COM, CORBA and Java RMI and other standard
components, shown in Figure 7 said.




Figure 7 ORB intermediary schematic

Application Server Application Server is a software development platform, in addition
to the applications can be developed independently, the server also integrates a variety
of integration technologies. In addition, many manufacturers also developed a number
of specialized adapters or special connectors, so make use of application server
integration platform is now one of the options considered by many enterprises.

				
DOCUMENT INFO