Java Reference
In-Depth Information
Layer-5: Presentation
Layer-4: Process Orchestration
Layer-3: Services
Layer-2: Reusable Components
Layer-1: Legacy Systems
Figure 11-3
SOA layered architecture.
ESB provides an abstraction layer on top of enterprise messaging
systems that are used for services integration. Layer 7 enables
management and monitoring of the deployed services. Layers 6 and 7
provide common infrastructure capabilities that can be accessed by
other layers and hence they are shown as vertical layers in
Figure 11-3. For more details about SOA refer to [Erl 2005].
Enterprise level adoption of SOA has many challenges. These
include complexities in changing monolithic legacy applications,
fundamentally changing the IT organization's approach to software
development, security of services, and performance overhead due to
loose coupling of applications. Even though SOA has fundamental
benefits, due to the complexities involved SOA projects often start
small and evolve over time. SOA adoption will increase as more soft-
ware applications and products provide out-of-the-box standards-
based Web services, and tools evolve to simplify SOA application
development and management. As data mining functionality is typi-
cally integrated with existing applications, adopting an SOA archi-
tecture with JDMWS will provide a flexible, reusable, and extensible
integration strategy. Section 11.3.2 discusses a JDMWS use case of
how JDMWS and SOA help integrate data mining functionality in an
JDM Web Service
The JDM standard defines a Web service's interface (JDMWS) that
uses the XML Schema discussed in Chapter 10 and provides func-
tionality consistent with the JDM Java API. The concepts and object
model discussed in Chapters 7 and 8 for the Java API are applicable
for the JDMWS interface. However, unlike a Java API, Web services
typically define a small number of operations with relatively large
Search WWH ::

Custom Search