Transcript Applying SOA Principles for Business Integration

Applying SOA Principles for Business
Integration
Business Integration Platforms
Sun Microsystems
Agenda
• Clarifying a few myths about SOA and Web Services
• Presenting the benefits of SOI
• Encouraging the use of open technologies and open standards
to enable SOI
• Developing an ecosystem of technology partners to enable
Service Oriented Integration
• Q&A
2
SOA and Web Services are not synonymous.
• The essential concept of SOA – i.e., the use of modularity and
“cloaking” to create readily reusable software components –
goes back more than 30 years.
• Use of the term “SOA” goes back at least 15 years. In the early
90’s, Tuxedo applications were built on a Service Oriented
Architecture using multiple “services”.
• Web services only appeared 5-6 years ago.
• You can build an SOA today without using Web services
– Indeed, there are drawbacks to using Web services in many SOA contexts.
• You can use Web services without implementing an SOA
– Many Web services connections are point-to-point links.
3
An SOA delivers flexibility through “loose coupling”.
•
•
•
•
In operation, a Service Oriented Architecture is
similar to a fan that is plugged into the wall
blowing air into another fan which is unplugged.
The air from the powered fan “pushes” the
unplugged fan until the speeds of the two fans
are almost the same.
Because of the “loose coupling” between the fan
blades, if you stop the fan blade in the “unpowered” fan, it will have no effect on the
powered fan.
Similarly, if you change a service in an SOA, the
programs that call that service are not impacted
if:
•
the interface for the service is unchanged
•
the service provides the same results
•
the service offers the same qualities of
service
4
Within an SOA, “loosely coupled” is not the same as
“uncoupled”.
• Trade press articles suggest that SOA’s “loosely coupled”
approach to service connectivity allows free and easy
replacement of one service with another.
– This ignores the multiple issues related to data and process semantics that
must be addressed prior to implementing a link between programs written
at different times by different people for different purposes.
• For the same reason, the time when applications will
spontaneously connect to previously unknown business
services is far in the future.
– Data semantics prevent many ad hoc connections from being implemented
without out-of-band discussions.
– Process semantics – i.e., business context issues – also limit opportunities
for spontaneous integration.
5
The current Web services standards are a Work In
Progress.
• We must distinguish between “Web services technologies” and
“Web services standards”
• It’s entirely possible to implement run-the-business applications
using various Web services technologies
– However, this may require concessions to the limitations of the Web
services technologies – e.g., hardware accelerators may be needed to
enable high performance XML processing
• If you expect “plug-and-play” interoperability, then the current
Web services standards will be a disappointment
– There are too many gaps, ambiguities and options in the current Web
services standards to permit “plug-and-play” interoperability
• For example, WS-Security allows use of User IDs/Passwords, X.509
digital certificates or Kerberos tickets. So, you can't assume a
consistent security implementation among several potential Web
services providers, even though they all are “WS-Security compliant”.
6
The WS-* standards only address interoperability; they
don't address all the other requirements for integration.
1986 “Integration”
2006 Integration
What’s required?
Minimal Ambiguity
Zero Ambiguity
The Network Used
Public Phone System
Internet Backbone
Low-level Protocols
Group 3 Fax Standard, 3270
TCP/IP, HTTP, SOAP
Message Paradigm
Visual Forms
XML & XML schemas
Message Content
Private Semantics
Private/Public Semantics
Reliability & Security
Manual Verification
Web Services Intermediary
and/or SOAP Extensions
Transaction
Management
“Understood” Transactions
Trading Partner Agreements
‘Quote to Cash’
Private (Manual) Process
Private (Managed) Process
7
Service Oriented Integration takes a practical approach to
business integration challenges
• Builds on SOA principles
• Applies Web services and open standards where appropriate
• Avoids monolithic solutions by building on a “pluggable” service
oriented integration architecture
8
An ESB is critical to the implementation of an SOA.
“An ESB is a Web-services-capable middleware infrastructure
that supports intelligent program-to-program communication
and mediates the relationships among loosely-coupled and
uncoupled business components.”
– Roy Schulte, Gartner
9
The fundamental ESB functionality delivers what you need
to build your Service Oriented Architecture.
• An Orchestration or Business Process Management tool
– To combine data and business logic from multiple low-level services in order to create
high-level, “composed” business services
• Transformation/data mapping tools
– Adapt/convert data data to facilitate exchange between services and applications
– To convert multiple views of your data into a single consistent view
• Adapters/wrappers
– To create interfaces for non conforming applications
– To convert non-standard APIs to standard APIs
Orchestration
Transformation
Wrappers / Adapters
10
But, on top of your ESB you need a comprehensive suite of
tools to support development of Composite Applications.
A Complete Composite Application Product Set
Master
Data Mgt.
B2B
A2A
BL
BAM
BL
B2B
Portal
B2B
B2B
Workflow
A2A
ETL
Portal
Orchestration
Transformation
Wrappers / Adapters
11
Evaluating an integration suite? Look for standards
support to deliver maximum interoperability and portability.
Sun Java CAPS runs on multiple operating systems and multiple
application servers. Interoperates with everything.
JSP, JSR 168
Java, BPEL, SQL,
XSLT,JBI
Generate Quote Process
Validate Order
Check Credit
Consolidate Order
for Shipment Process
Check Inventory
Order Fulfillment Process
Schedule Shipment
Create Invoice
WSI BP, JMS, WS
MQ, MSMQ, AQ,
AS2, ebXML, EDI,
RosettaNet
RMI, IIOP, ECI,
BAPI, ALE, HLLAPI,
COM/DCOM/COM+
Solaris, HP-UX, AIX, Windows, Linux, HP True64, HP NonStop, z/OS
Sun Java AS, WebLogic AS, WebSphere AS, JBoss
12
An integration suite should be both comprehensive AND
fully integrated.
• With comprehensive functionality in one toolset you can have
consolidated management and monitoring.
• BPM with a single repository maximizes opportunities for reuse.
• A single repository enables comprehensive version control and
configuration management.
• A single, integrated development environment reduces the
developer learning curve and improves productivity.
13
But, avoid an inflexible, monolithic toolset. Your ESB
should offer a “pluggable” SOA architecture that
supports the flexible use of development and runtime
services.
14
Java Business Integration provides this pluggability in the
form of a broadly adopted standard for development tools.
15
The Java Business Integration standard provides benefits
at development time and at runtime.
JBI Interoperability Architecture
When you buy an integration or SOA solution based on JBI, you get an
extensible, future-proof solution that can grow with your business needs.
JBI Service Assembly
The service assembly enhances developer productivity and enable a new
generation of development tools for composite applications.
16
Though still emerging, open source ESBs can offer a
starting point for your SOI solution.
• Provides a
lightweight ESB
development and
deployment
framework
• Leverages open
standards such as
JBI, BPEL, WS*
and others
• Community guided
and developed
http://open-esb.dev.java.net/
17
Sun Offers Choice: Open ESB, Sun ESB, Composite
Application Platform Suites
Open ESB
Sun ESB
Entry Level, Standards-Based ESB
JBI Architecture
Available: 1H 2006
Product Version of Open ESB with
Java ES Integration & JBI Architecture
JBI + BPEL, XSLT, protocols,
tools, management
JBI + BPEL, XSLT, protocols,
tools, management
Java CAPS Suite
Fifth-generation, ESB-based
Integration Suite with full
functionality
Available NOW
ESB, BPM, B2B, ETL, BAM,
eVision, plus Sun App Server,
Portal, Directory, Identity, tools...
18
Resources to find out more about Service Oriented
Integration, SOA and Sun’s products and services.
- Service Oriented Integration
http://java.sun.com/integration
- Sun’s SOA Strategy
http://www.sun.com/soa
- Sun Java Composite Applications Suite
http://www.sun.com/software/javaenterprisesystem/integration_suite/index.x
ml
- Project Open ESB
http://open-esb.dev.java.net
19
Thank You
Sun Microsystems