Enabling Connected Applications with Service Orientation

1
Enabling Connected Applications with Service
Orientation
2
Agenda

• Connected Applications
• Business and IT drivers
• Service and Web Services Concepts
• Key elements of a Service Oriented Architecture
  (SOA)
• Business Service Bus
• Enterprise Service Bus
• Service Pipeline
• Adoption Outlook

3
Connected Applications
Service
4
Example Tesco.com
Routing
Shopping Basket
Deliveries
Returns
Products
Tesco.com Systems
5
Business Drivers
6
No Shortage of Integration Solutions!

• Distributed Computing DCOM, .NET, CORBA, J2EE
• Enterprise Application Integration Microsoft
  BizTalk, IBM WebSphere BI, Mercator, Vitria, etc
• Messaging MSMQ, IBM MQ, Tibco, etc
• Portal Servers Microsoft Sharepoint, IBM
  WebSphere Portal, Plumtree, etc
• EDI Gateways Sterling Commerce, IBM WebSphere
  BI, GE, etc
• B2B IBM WebSphere BI, SeeBeyond, iWay, etc

DistributedComputing
Enterprise AppIntegration (EAI)
Messaging
Web Site/Portal
EDI/B2B
7
That Dont Always Work Well Together

• Each scenario uses different Technology,
  Products, Communications
• Typically Proprietary, and often platform
  specific
• Creates Technology dependencies at either
  endpoint of the integration
• Often Channel Specific (i.e. technology for
  Direct channel cannot support Partner Channel
• Requires technical skills specific to each
  scenario

DistributedComputing
Enterprise AppIntegration (EAI)
Messaging
Web Site/Portal
EDI/B2B
8
Need Seamless End to End Connectivity
Disjointed Processes
B2C
EAI
B2B
Information Visibility and Accuracy
Agility
Agility
Customer
Your Organization
Supplier
RTE
RTE
STP
BPO
Seamless End to End Process
9
Service and Web Service Concepts
10
What is a Service?
BusinessService

• What it is
• A mechanism by which the consumer's need or want
  is satisfied according to a negotiated contract
• Focus on WHAT it does not HOW it does it
• What it is NOT
• A Software Service is not a synonym for the
  existing API
• A Software Service is not always a Web Service
• What is desirable?
• Defined using Web Service protocols, via a set
  policies
• Abstract definition of service

Policies
SoftwareService
SoftwareServiceDefinition


API


Executable
11
The Basic Concepts of Service
12
Example
Retailer
Requests
Stock Level
Response Time lt0.5s
Accurate at 00.00AM
Implements
Provides
Wholesaler
SAP
13
Messages, Endpoints and Intermediaries
14
Why Services?
ServiceConsumers Application

• Loose Coupling
• Requestor Agility

• Provider Encapsulation
• Managed Migration

Service
Service
Service Endpoint
Service Endpoint
ImplementationV1
ImplementationV2
Implementation
Provider B
Provider A
15
Services Enable Agility at Boundaries
Technology1
OrganizationA
Service
Technology Boundary
Technology2
Service
Organizational Boundary
OrganizationC
OrganizationB
Service
Application Boundary
ApplicationI
ApplicationII
16
Coupling is Multi-Layered
Characteristic
Locked into commercial contracts Single source
provider e.g. manufacturer of certain product
Trust - Unwilling to work with unknown partners
Semantics dependency information model Single
source provider e.g. bank account details
Workflow dependency service only works in
specific process Context dependency service
only works in specific context
Technology dependency e.g. technology must be
J2EE Application dependency e.g. application
must be SAP
Hardware dependency e.g. Service consumer must
use Nokia phone
Partners must provide closed-looped feedback
17
Layers of Architecture
.NET
Linux
MQ

• Technology Layer
• Hardware, Network
• How do you connect J2EE to .NET?

OS/390
J2EE
Unix
DB2
18
Federation Drives Need for Web Services

• Multiple Participants
• No common platform or EAI
• Demands Loose Coupling, Message Based Approach
  Web Services

Product
Customer
Sales
Employee
SAP
Finance
Outlook
Siebel
PeopleSoft
Dir
.NET
Linux
MQ
OS/390
J2EE
Unix
DB2
19
What are Web Services?
ServiceIntermediary
Service Provider
Service Consumer
ServiceRequest
Service
Standards-based protocols to describe
ProcurementSystem
SalesSystem

• Message format

• Services and Endpoints

• Addressing and Routing

J2EE
.NET

• Secure, Reliable Transactions

• Business Process Orchestration

• Publication and Discovery

20
The Web Service Protocol Stack
21
Using Web Service Protocols
Likely Adoption
Autonomic Behaviour WS-Provisioning, WS-Eventing
Orchestrated Services BPEL
Increasing Complexity
Complex Transactions WS-ReliableMessaging,
WS-Transactions
Managed Services WS-Distributed Management
Federated Services WS-Addressing, WS-Federation,
Federated Identity
Secure Services WS-Security, WS-Policy
Simple Transactions and Information Provision
Services SOAP, WSDL, UDDI, WSIL, WSRP
22
Why Web Services?

• Standardised approach for all scenarios
• Standard protocols
• Universal support
• Vendors
• Platforms
• Tools
• Leverage Ubiquitous Internet technologies and XML
• Internal and External usage
• Supports multiple messaging approaches
• Rich, Self Describing interfaces
• Loose coupled technology
• Low entry cost (essentially free!)

WebServices
DistributedComputing
EAI
Messaging
Web Site/Portal
EDI/B2B
Web Services makes Service Orientation work!
23
Service Orientation and SOA
24
Service Oriented Architecture - Definition

• The policies, practices and frameworks
• that enable application functionality
• to be provided and consumed
• as sets of services
• published at a granularity relevant to the
  service consumer,
• which are abstracted away from the implementation
  using a single, standards based form of
  interface.

25
Service Orientation
Service Oriented Analysis Understanding and
modeling the business as services Enabling
business agility
Service Oriented Provisioning Determine which
Services to use Selecting Service Providers
Service Oriented Design Designing precise
behavior of services Ensure scalability,
reliability, SLA compliance Enabling technical
agility
Service Oriented Programming Reducing effort to
code Web Services
26
Service Lifecycle
Solution Implementation
Service Consumption
Discover
Consume
Design
Analysis
Certify
Publish
Version
Execute
Deploy
Service Provision
Service Implementation
27
Multi-Layered SOA
28
Service Architecture The Functional Layer
Consuming Applications

• Solution Architecture
• Frequent change
• Device diversity

Multiple Devices
Workflow

• Component Architecture
• Less frequent change
• Server diversity
• Interface diversity

3rd PartyServices
Legacy Apps
Packaged Apps
New Components
Providing Applications
29
Elements of a Service Oriented Architecture
30
The Business Service Bus Functional View
Human Resources Bus
Logistics Bus

• Domain specific
• HR, Financial Services, Logistics, Etc.,
• Common vocabulary
• Shared specification and model
• Agreed by Service provider and consumer
• Increasingly driven by domain standards
• HL7, ACORD, Rossettanet, UN/CEFACT

• Critical Design Factors
• Schema
• Loose coupling
• Level of abstraction
• Granularity
• Reusability

31
Service Granularity and Abstraction
Coarse Grained Business Services (Business
Services Bus)
Aggregation Layer
Abstraction
Fine Grained Implementation-Based Services
ServiceWrapper
New Components
ExternalServices
ExistingApplication
InfrastructureServices
32
Enterprise Service Bus Infrastructure Layer
Consuming Applications

• Frequent change
• Device diversity

Multiple Devices
Workflow

• Less frequent change
• Server diversity
• Interface diversity

3rd PartyServices
Legacy Apps
Packaged Apps
New Components
Providing Applications
33
Service Pipeline
Policy Driven
34
Service Pipeline Implementations and
Infrastructure

• Web Service Management Tools
• Actional
• Amberpoint
• Infravio
• CapeClear
• Primordial WSBANG
• ServiceIntegrity
• Westbridge XMS
• West Global mScape
• Hosted Services
• Flamenco Networks
• GrandCentral

• Platform infrastructure
• Apache Axis
• Microsoft .NET WSE
• IBM WebSphere WSDK
• Systems Management
• HP Openview
• CA Unicenter
• IBM Tivoli
• Microsoft MOM
• Web Service Standards
• WS-Distributed Management

35
Adoption Outlook
36
Impact on End-User Organizations
Opportunities and Benefits
Simple Web Services can dramatically improve
accessibility to and integration of resources
Providing/Consuming simple Web Services will be
straightforward
Competitive Advantage can be won for the business
Now!
Challenges
Highlight weaknesses in, or unsuitability of,
current interfaces
Customers and Partners might demand greater
functionality than you can provide
Business Agility requires more effort than simply
adding Web Services
Existing applications may not be ideal for
real-term behaviour, or to support long-term
vision of adaptability
Cultural challenge of Short-termism, Service
Reuse, Business Service Bus Ownership
37
Impact on the ISV
Opportunities and Benefits
Will ease customer's integration requirements
Providing SOAP/WSDL interfaces may be
straightforward
Introduce new opportunities for collaborative
applications
Change deployment options. E.g. Bring new Hosted
Service opportunities
Challenges
Highlight weaknesses in, or unsuitability of,
current interfaces
Demand for more real-time behaviour in
applications
Need for applications to consume Web Services,
not just provide them
Converting applications to support emerging
enterprise-level Web Service standards for
transactions and process orchestration
Remove internal dependencies so that customers
can use services at a more granular level than
the whole application
38
ISV Deployment Patterns
Web Services
CustomersCustomers
1. Traditional Deployment, plus Web Services
CustomersApplications
CustomersCustomers
2. Hosted Service Provider
CustomersApplications
3. Distributed
CustomersCustomers
CustomersApplications
Customer
ISV (or ASP)
39
Outlook - Phases of Web Service Adoption
Improved Quality of Service, Security
Increasing Dynamic Behaviour
2004 2005 2006 and beyond

• 1st Phase
• Information Provision
• Simple Transactions
• Competitive Advantage

• Early Learning

40
Current Status of Web Service Protocols
Mainstream SOAP WSDL UDDI
Specification SOAP MTOM WS-Addressing WS-CAF WS-Ch
oreography WSDM WS-Eventing WS-Federation WSIL WS-
Provisioning WS-ReliableMessaging
Experimentation ASAP BPEL WS-Coordination WS-Polic
y
Early Adoption WS-Security WSRP
Approved Standards
Technology Preview
Paper Specifications
41
Web Service Imperatives

• Web Services and SOA addresses current business
  and IT needs
• Your Customers and Partners will increasingly
  desire services
• Dominant ones will DEMAND use of services
• Competitors are gaining advantage RIGHT NOW!

42
Immediate Projects

• Start using Web Services
• Identify opportunities to improve business value
  by exposing simple Web Services
• Improve access to data for customers and partners
• Use Web Services internally
• Open up existing systems for broader reuse
• Take advantage of loose technical coupling to
  integration heterogeneous systems
• Upgrade infrastructure to provide Enterprise
  Service Bus
• Start defining SOA
• Initiate Business Service Bus projects
• Investigate and participate in vertical industry
  standards

43
Summary

• Service is the important concept, not just Web
  Service
• SOA isnt just the wiring diagram for Web
  Services
• Service Orientation should be adopted across the
  whole lifecycle
• Web Services Makes SO work
• Strong drivers for Web Services adoption