The Service Oriented Elephant Ajit Sagar Principal Architect, Infosys Technologies J2EE Editor, Java Developer’s Journal Technical Editor, Web Services Journal Founding Editor, XML Journal

Contents The Blind Men and the Elephant Building Blocks of SOA Organization Roadmap – How Much SOA? Implementation Scenarios

The Blind Men and the Elephant ROPE TREE SNAKE SPEAR FAN WALL

SOE: Service Oriented Elephant? SOA WEB SERVICES BPM EAI XML AGILITY

SOA Stakeholders Agile Strategy More Attractive Job Reduction of Dependency Rapid Prototyping Clearer Requirements Simplified Testing Reduced Integration Effort Future Proof Solutions Technology & Vendor Independence Shorter Time to Market Smaller, Shorter Projects Positive Role of IT Dept. Cost Reduction Manageable Project Size Greater role in Decision making Budget Reduction Code Reuse Loose Coupling Strategic Development CEO CIO/ CTO ARCHITECT DEVELOPER PROJECT MANAGER BUSINESS OWNER

Contents The Blind Men and the Elephant Building Blocks of SOA Organization Roadmap – How Much SOA? Implementation Scenarios

Is SOA the “Same Old Architecture”? Well, Yes … SOA principles have been used in earlier architectures SOA leverages existing technologies and frameworks Services can be exposed from existing functional modules And No SOA approaches architecture from the point of view of business services, not technology SOA is to distributed architectures what XML is to data formats SOA is a technology agnostic high-level concept for designing enterprise architecture blueprints

SOA principles have been used in earlier architectures

SOA leverages existing technologies and frameworks

Services can be exposed from existing functional modules

SOA approaches architecture from the point of view of business services, not technology

SOA is to distributed architectures what XML is to data formats

SOA is a technology agnostic high-level concept for designing enterprise architecture blueprints

Building Blocks of SOA SOA Application Frontend Service Service Repository Service Bus Contract Implementation Interface Business Logic Data

Building Blocks of SOA APPLICATION FRONTEND SERVICE REPOSITORY Data Business Logic Service-Oriented Architecture SERVICE BUS SERVICE Interface Contract Implementation

Estimated Lifetimes of SOA Elements Years

Types of Services Basic Service Foundational service Focus on data and business logic Intermediary Service Technology bridge Focus on functionality Process Service Business process service Focus on business flow Enterprise Service Cross-domain service Focus on enterprise integration

Basic Service

Foundational service

Focus on data and business logic

Intermediary Service

Technology bridge

Focus on functionality

Process Service

Business process service

Focus on business flow

Enterprise Service

Cross-domain service

Focus on enterprise integration

Service Types Compared No No No Yes Mandatory Element of SOA Shipment tracking service, SMS service, flight status service Booking an airline ticket, approving a loan Legacy wrapper (Technology gateway), ERP adapters (Adapters), Service Access Layer (Façade) Customer service (data), insurance product engine (logic) Examples Frequency of Change Reusability State Management Implementation Complexity Low High Moderate to high Low Low Low Low High Service Specific Stateful Stateless Stateless Service Specific High Moderate to High Low to Moderate Public Enterprise Services Process-centric Services Intermediary Services Basic Services

Relationship Between Service Types Application Frontend Process-centric Service Basic Data Service Basic Data Service Basic Business Logic Service Basic Business Logic Service Intermediary Service Intermediary Service 1 1 2 2 3 3 3 3 4 4 4 4 4 4 1 2 3 4 Frontend calls basic services directly Process-centric service coordinates basic service calls Frontend used intermediary service to get to basic services Process-centric service uses intermediary service to get to basic services

Contents The Blind Men and the Elephant Building Blocks of SOA Organization Roadmap – How Much SOA? Implementation Scenarios

What are the pieces of the puzzle? What opportunities does SOA offer my organization? What should be my SOA roadmap? Are my inter and intra business processes well coordinated? How can I leverage SOA to standardize and optimize my business processes? How will SOA help me better utilize my existing investments? Are my underlying systems SOA-enabled? Do I have a integration infrastructure in place? Will SOA help me integrate my applications? SOA Business Models and Trends Business Process Improvement & Semantic Standardization Enterprise Application Integration Existing infrastructure and investments

Motivation & Benefits AGILE ENTERPRISE SOA The ultimate goal of an SOA is the creation of the Agile Enterprise Business Infrastructure Reusability Business Infrastructure Flexibility Technology Independence Risk Mitigation Cost Savings More Efficient Development Process Multi-level Feedback Evolutionary Approach

How SOA Facilitates Business Agility Decomposition Appropriate Granularity Technology Decoupling Reuse Documentation Service Orientation Technology Business Process Business Functionality Integration Maintenance Business Agility Complexity Reduction Existing Development Effort

Stages of SOA Adoption Stage I Fundamental SOA Stage II Networked SOA Stage III Process-enabled SOA Focus on enterprise integration Complexity and business logic still in application frontend Enable multiple applications to share live data and business logic Provide an appropriate base for an enterprise landscape Focus on shared services to make data replication obsolete Focus on basic and intermediary s tateless services including facades, technology gateways, adapters, and functionality adding services Technical and conceptual abstraction focused on reducing backend complexity Service access & coordination Reduction in complexity of application frontends Focus on maintenance of process state in process-centric Stateful services Process control delegated to the SOA Service orchestration Encapsulation of complexity of processes Sharing of state between clients Handling of long-living processes FOCUS BENEFITS Creates strong platform for enterprise application landscapes Technically easy to implement Increased maintainability Data sharing Application complexity reduction Technology platform interoperability Lighter application frontends Flexible technology-agnostic integration of software assets Process complexity reduction Lightweight application frontend Integrates highly independent organizations

Focus on enterprise integration

Complexity and business logic still in application frontend

Enable multiple applications to share live data and business logic

Provide an appropriate base for an enterprise landscape

Focus on shared services to make data replication obsolete

Focus on basic and intermediary s tateless services including facades, technology gateways, adapters, and functionality adding services

Technical and conceptual abstraction focused on reducing backend complexity

Service access & coordination

Reduction in complexity of application frontends

Focus on maintenance of process state in process-centric Stateful services

Process control delegated to the SOA

Service orchestration

Encapsulation of complexity of processes

Sharing of state between clients

Handling of long-living processes

Creates strong platform for enterprise application landscapes

Technically easy to implement

Increased maintainability

Data sharing

Application complexity reduction

Technology platform interoperability

Lighter application frontends

Flexible technology-agnostic integration of software assets

Process complexity reduction

Lightweight application frontend

Integrates highly independent organizations

Business Integration and SOA Maturity Fundamental Networked Process-enabled Intra- departmental Cross- departmental Cross- Business unit Simple B2B Complex Business Processes Maintainability Flexibility Agility SOA Maturity Intra-Enterprise Integration Inter-Enterprise Integration Not Feasible Not Cost-effective

Factors Influencing SOA Adoption State of current architecture Integration level desired Budget and timeline constraints Development skill set Cultural mindset of the organization

State of current architecture

Integration level desired

Budget and timeline constraints

Development skill set

Cultural mindset of the organization

SOA Assessment Identify basic problems in the organization that could benefit from SOA Determine the readiness of the applications to adopt SOA Work into a very high level roadmap Conduct a basic Risk/Benefit analysis Identify candidates for POC project Define high level governance structure Define a reference architecture for SOA

Identify basic problems in the organization that could benefit from SOA

Determine the readiness of the applications to adopt SOA

Work into a very high level roadmap

Conduct a basic Risk/Benefit analysis

Identify candidates for POC project

Define high level governance structure

Define a reference architecture for SOA

Maturity Level Definition Level 1 Level 2 Level 3 Level 4 Level 5 SOA adopted within an application boundary. Services are used as a replacement for traditional functionalities. A good starting point for a gradual broader adoption Level 1 plus loose coupling and seamless, real-time information exchange achieved across applications within LOB. Level 2 plus loose coupling and seamless, real-time information exchange achieved across departments, but within the enterprise boundary. Level 3 plus seamless, real-time information flow achieved across enterprise boundary, with subsidiaries and group companies Level 4 plus seamless, real-time information exchange with partners, suppliers, customers. Service Interfaces Wrapping legacy P2P integration Web Services Management Governance Loosely Coupled services Service Oriented Management Reliable, discoverable services Service Oriented Process Composable, Reusable services Service Oriented Enterprise Service Federation, Dynamic Discovery Service Orientation can be adopted by an enterprise at various levels of maturity. Some of the factors contributing to the decision of SOA maturity level of an enterprise are Size, type of the enterprise Business Goals & Strategy Technology Capability SOE

Service Orientation can be adopted by an enterprise at various levels of maturity. Some of the factors contributing to the decision of SOA maturity level of an enterprise are

Size, type of the enterprise

Business Goals & Strategy

Technology Capability

SOA Practice Offerings SOA Strategy Definition Assessment, maturity level definition, Reference Model definition, roadmap, business case development SOA Competency Center setup Establish and grow SOA competency center (Center of Excellence) SOA Architecture Definition Reference architecture definition, Service analysis and definition, modeling, BIDAT architecture, Product and Vendor evaluation, PoC’s ES SOA Enablement SOA enablement for ES packages such as SAP, PeopleSoft, Oracle, Siebel SOA Development, testing and realization Service design, development, implementation and testing. Infrastructure deployment, operational support Legacy Modernization Enabling legacy applications towards SOA SOA Governance Governance model definition, Design time: Service Lifecycle development, service interface optimization Run time: MDM strategy, meta data strategy Organization Scope SOA Functions App/Project Enterprise Reference architecture definition, Service analysis and definition, modeling, BIDAT architecture, Product and Vendor evaluation, PoC’s

So, does the shoe always fit? There are situations where the organization may not be ready for an SOA transformation. Examples are: When there is no “bigger picture” When sharable services are overkill for the business problem When there is a homogeneous IT environment, and there is no need for external integration When business processes are well-defined and mature, and do not tend to change When there is no need for loosely coupled services When the organization is culturally not ready for it NO FOCUS ON BUSINESS, NOT TECHNOLOGY!

There are situations where the organization may not be ready for an SOA transformation. Examples are:

When there is no “bigger picture”

When sharable services are overkill for the business problem

When there is a homogeneous IT environment, and there is no need for external integration

When business processes are well-defined and mature, and do not tend to change

When there is no need for loosely coupled services

When the organization is culturally not ready for it

Contents The Blind Men and the Elephant Building Blocks of SOA Organization Roadmap – How Much SOA? Implementation Scenarios

Scenario 1: SOA for basic services at a bank Reduced integration expense Increased reuse of software assets Increased business agility Reduced business risk Reduced time to market ROI of SOA Service reuse Composition of services into multiple applications Promotion of standard interfaces Technology platform agnostic consumption Benefits of SOA Clear segregation of service layers from application layers Phased approach to service implementation: “ Location” (informational) services implemented first Transactional services (process orchestration) implemented next Creation of reusable basic services Data services for accessing firm systems Infrastructure services to be leveraged from an enterprise services framework Sharing of services between applications SOA Approach

Reduced integration expense

Increased reuse of software assets

Increased business agility

Reduced business risk

Reduced time to market

Service reuse

Composition of services into multiple applications

Promotion of standard interfaces

Technology platform agnostic consumption

Clear segregation of service layers from application layers

Phased approach to service implementation:

“ Location” (informational) services implemented first

Transactional services (process orchestration) implemented next

Creation of reusable basic services

Data services for accessing firm systems

Infrastructure services to be leveraged from an enterprise services framework

Sharing of services between applications

Scenario 2: Application of SOA to a derivatives desktop Higher maintainability of existing assets (Excel) Increased productivity Basic services for future consumption ROI of SOA Data aggregation and integration High capacity data processing services Benefits of SOA Sharable data integration and access services Microsoft Office 2007 “services” for management of spreadsheets Virtualization platform grid services for risk management SOA Approach

Higher maintainability of existing assets (Excel)

Increased productivity

Basic services for future consumption

Data aggregation and integration

High capacity data processing services

Sharable data integration and access services

Microsoft Office 2007 “services” for management of spreadsheets

Virtualization platform grid services for risk management

Scenario 3: Establishment of an SOA COE Flexibility in application integration Lower cost of ownership across the enterprise ROI of SOA Application integration across the enterprise Reusability of assets and business services Benefits of SOA Comprehensive SOA strategy and roadmap Definition of governance and process model for business services Training and workshops to increase the knowledge level of SOA / Web services within the client organization Setup and maintenance of infrastructure to monitor and manage web services SOA Approach

Flexibility in application integration

Lower cost of ownership across the enterprise

Application integration across the enterprise

Reusability of assets and business services

Comprehensive SOA strategy and roadmap

Definition of governance and process model for business services

Training and workshops to increase the knowledge level of SOA / Web services within the client organization

Setup and maintenance of infrastructure to monitor and manage web services

Scenario 4: Legacy Modernization Using SOA Lower the TCO- lesser code inventory, re-factored code, futuristic architecture enabling easier extensions Improved Data Quality through a unified Data Architecture Increased system availability through reduced batch window. ROI of SOA Alignment Technology strategy to Business strategy Leverage of existing assets and business services Technical foundation for the future phases of architecture transformation Benefits of SOA Re-architecting & re-factoring the monolithic CICS/COBOL based legacy application Creation of reusable Business Services for Enterprise-wide needs and implement a Service Oriented Architecture Incorporation of business process improvements in the systems with real time data updates SOA Approach

Lower the TCO- lesser code inventory, re-factored code, futuristic architecture enabling easier extensions

Improved Data Quality through a unified Data Architecture

Increased system availability through reduced batch window.

Alignment Technology strategy to Business strategy

Leverage of existing assets and business services

Technical foundation for the future phases of architecture transformation

Re-architecting & re-factoring the monolithic CICS/COBOL based legacy application

Creation of reusable Business Services for Enterprise-wide needs and implement a Service Oriented Architecture

Incorporation of business process improvements in the systems with real time data updates

Thank You “ The contents of this document are proprietary and confidential to Infosys Technologies Ltd. and may not be disclosed in whole or in part at any time, to any third party without the prior written consent of Infosys Technologies Ltd.” “ © 2008 Infosys Technologies Ltd. All rights reserved. Copyright in the whole and any part of this document belongs to Infosys Technologies Ltd. This work may not be used, sold, transferred, adapted, abridged, copied or reproduced in whole or in part, in any manner or form, or in any media, without the prior written consent of Infosys Technologies Ltd.” The Agile Elephant