Liquidhub Ibm Service Oriented Architecture Presentation 064234 (1)

our business revolves around you

Service Oriented Architecture:

Building your Web Services and SOA Roadmap

Tuesday, June 29th 2004

2Topics of Discussion

Understanding Services Oriented Architectures

The Business Case for a Service Oriented Architecture

Web Services a Foundation Technology for SOA

The Impact of SOA on Enterprise Architecture

Getting Started

About LiquidHub


Understanding Service Oriented Architectures

How SOA Works

Back to the Future: Best in Class

SOA Roadmap Planning

4Setting the Stage for SOA

Service-Oriented Architecture (SOA)

Service Orientation

XML and Web Services

A set of design and organizational principles that guide companies around the corner to Service Orientation, a roadmap to achieving the vision of business driving IT.

An approach to information technology that considers IT resources as being available and discoverable as location-independent Services on the network, providing a layer of abstraction that masks the complexity of the technical implementations.

The key enabling technologies that underlie SOAs, representing both extensible formats for data and content as well as standards-based approaches to distributed computing.

Source: ZapThink

5

Reduced interdependency between software assets

Allows individual software assets to become building blocks that can be reused in developing other applications (application assembly)

Federated and policy based security, management and deployment

Leverages open standards to represent software assets as services (XML, SOAP, WSDL, UDDI, …)

What makes up SOA?

Treating applications and processes as defined components that can be mixed and matched at willSupports a federated approach to governanceAllows smaller, incremental projects Supports business flexibility and optimized IT infrastructure

Characteristics:

Loosely coupled

Shared services

Federated control

Standards based

Source: IBM

6How Does SOA Work?

In a Service Oriented Architecture– SOAs build on previous 3-tier architectures to become more flexible, less redundant– The services then provide black-box functionality for business processes with location transparency– Location transparency provides the window of opportunity to incrementally sunset legacy applications

and/or to access 3rd party services

Source: Adapted from Microsoft

Client

Client Business Objects Data / Persistence

Client


Client


Business Services

Typical 3 tier application

Comparable Service Oriented Implementation

In House Systems

3rd Party or Business Partner Systems


The Business Case for a Service Oriented

Architecture

IT Economics and Portfolio Management

Why Consider SOA?

8IT Economics and Portfolio Management:The Potential Value of SOA

Organizations spent 80% (or more) of their IT budgets on Maintenance, Stability, Support and Operations, with only 20% remaining for New Development Initiatives.

If you could improve re-usability to leverage key IT assets more effectively and reducing impact of change impact, you would free 30% of your expenditure for new projects or savings back to the business.

50% New Projects for Business Process Improvement & Value Add

50% Maintenance, Operational Stability & Support

20% New ProjectsFor Business Process Improvement

80% Maintenance,Operational Stability &Support

20%

80%

50%

50%

Source: Adapted from James Martin

9Why Consider a Service Oriented Architecture?

Define business rationale, not technical featuresFind a pragmatic balance between technical rigor and time-to-marketValue ongoing flexibility and agility over a one-time efficiency gain

With a little planning, you can get immediate return for each service you build via the “Network Effect”And you can get increasing return as your architecture –and that of your customers, suppliers, and partners –evolves to SOA

Increase ROIIncrease ROI

Focus on the Focus on the BusinessBusiness

10Why Consider a Service Oriented Architecture?

SOA is about reuse of existing assets: Legacy, Client Server, and WebYou can “wrap” existing applications, re-using existing functionality of legacy systems to increase their reach and longevityAnd build new services on any and multiple supported platforms

Invest in a diversified portfolio of applications, not a single packaged application or a technology platform Applications are less fragile, more adaptive to Rapidly ChangingBusiness Requirements Facilitate standards based integration with trusted business partners (B2B)Ease integration needs necessitated by M&A activity

Complexity is encapsulatedCode is mobileEnhancements and changes can be added incrementally without a negative ripple effect across the application infrastructure

ReuseReuse

Achieve Achieve FlexibilityFlexibility

FutureFuture--Proof Proof Your Your

EnterpriseEnterprise


Web Services:A Technology

Foundation for SOA

What Are Web Services?

Why Web Services as Part of an SOA?

Web Services Examples

12What are Web Services?

Web Services are software components that are loosely coupled and distributed, encapsulate business functionality and are programmatically accessible using standard Internet protocols

Technically, Web Services are a stack of emerging standards that describe a service oriented, component-based application architecture, enabling SOA in an enterprise

WebServices

1 2 3

4 5 67 8 9

* 8 # TelephoneNetwork

13Why Web Services as Part of SOA?

Based on ubiquitous Industry Standard Protocols with universal supportLeverage the internet for low cost communicationsDeliver platform and technology independenceLoosely Coupled– Migration from direct calls to architectural

service reduces dependency on specific applications and packages

– Supporting multiple application connection and information sharing scenarios

Fosters re-use through publication of interfaces– Services are self describing– Reduces the time for developers to

properly understand the interface – Richer specification of the service can

be accessed programmatically– Reduces the impact of change by

providing dynamic service consumptionSource: CBDI

Additional StandardsAdditional StandardsWSXLWSXL

Business Process ExecutionBusiness Process ExecutionBPEL4WS, WFML, WSFL, BizTalk, etc.BPEL4WS, WFML, WSFL, BizTalk, etc.

Services Publishing & DiscoveryServices Publishing & DiscoveryUniversal Description, Discovery & Integration (UDDI)Universal Description, Discovery & Integration (UDDI)

Services DescriptionServices DescriptionWeb Services Description Language (WSDL)Web Services Description Language (WSDL)

Services CommunicationServices CommunicationSimple Object Access Protocol (SOAP)Simple Object Access Protocol (SOAP)

Meta LanguageMeta LanguageeXtensible Markup Language (XML)eXtensible Markup Language (XML)

Network Transport ProtocolsNetwork Transport ProtocolsTCP/IP, HTTP, SMTP, FTP, etc.TCP/IP, HTTP, SMTP, FTP, etc.

14Example of a Service Oriented Architecture

Business objects represent binary and legacy assets (pre-web services)Specific web services wrap binary objects and legacy API adapters with XML/SOAP to achieve greater re-usability and heterogeneous interoperabilityAbstract business services aggregate multiple web services in the orchestration of real business operational workflow through: – Business Process Mapping– Data Transformation (XSLT) – Transactional Routing

Discoverable Services

Client

Online Store Business Objects

SpecificWeb ServicesAbstract

Business Services Book

Order

Order Detail

Book Store Service

Discoverable Services…• Are URLs for Applications that can be redirected• Can be modified to add new attributes and

methods without ripple effect on existing applications

• Allow you to add new “Presentation Services”more rapidly


The Impact of SOA on Enterprise Architecture

Organizational Perspectives that Influence EA

Strategic and Shared Service Impacts on EA

Infrastructure/Security Impacts on EA

16What is Enterprise Architecture Planning?

Results

High ComplexityHigh Cost

Managed ComplexityManaged Cost

Increased Business Value

Process

Platform Peop

le &

Prin

cipl

es

Current State

Future StateProject Portfolio

Process

Platform

Peop

le &

Prin

cipl

es

17Enterprise Architecture and SOA

Organizations believe that Enterprise Architecture can help improve:– The Business/IT alignment gap– IT Project success rate– Business and technology communication

Organizations believe that Enterprise Architecture benefits are:– Cost reduction & technology standardization– Process improvements– Strategic differentiation

SOA approaches espoused by tool and product vendors provide the opportunity for organizations:– To re-think their approach to architecture – To enable real portfolio planning for technology-enabled enterprise business processes.

18SOA Enterprise Architecture Principles

Shift from monolithic applications to application services – Client Applications role shifts

to presentation for managing and submitting requests

Identify discrete business functions within applications and separate them to application services– Separation allows alternate business

workflows to co-exist– Separation of application from

business logic allows more responsive change to processes

– Service transparency is a key attribute given a ever-changing enterprise architecture

Application Services call other infrastructure services as necessary

ENTERPRISE ARCHITECTURE

Business Architecture

Technology ArchitectureBusiness Applications

Shared Services

Gov

ern

ance

& M

anag

emen

t

19SOA and Enterprise Architecture



Technology Architecture

Product/ Service Structure

Value Chain Structure

Business Process Structure

Relationship Structure

Business Applications

Shared Services

Governance & Management

Resource Structure

Enterprise Portfolio Structure

Architectural Principles and

Standards

Vendor and SLA Structure

SRM

Enterprise Presentation Services

DataServices

Application Infrastructure Services

Network Infrastructure Services

Enterprise Application Services

Enterprise Platforms & Integration Services

ERP Corporate Applications CRM Vertical

Applications

Shared Services: a breakdown of services to support enterprise applications– Application Presentation Services– Enterprise Application Services– Data Services– Enterprise Platforms & Integration Services– Application Infrastructure Services– Network Infrastructure Services

20SOA: Perspectives that Influence Enterprise Architecture

Each perspective needs to be considered in order to optimize current IT investments and ensure future investments are aligned with business goals and objectives

All four perspectives must be considered to create a single cohesive Enterprise Architecture view

Benefits are– Reduced complexity– Time to market– Increased flexibility– Lower cost!

Source: Adapted from Marks/Warrell




Product/ Service

Structure


Business Process

Structure



Shared Services


Resource Structure



Standards


SRM


DataServices






Applications




Product/ Service

Structure


Business Process

Structure



Shared Services


Resource Structure



Standards


SRM


DataServices






Applications

21




Product/ Service

Structure


Business Process

Structure



Shared Services


Resource Structure



Standards


SRM


DataServices




ERP Corporate Applications

Vertical Applications

Business Perspective

Business architecture define business rules to determine which service requests are handled by which Application Services.Business Applications rely on Application Services to provide the core functionality.During Business Process modeling analysts discover Application services and determine which object should be invoked for a given business need.

CRM


Business Process

Structure

22Applications Perspective

Groups of services are differentiated to define which services implement an appropriate interface. Services must implement all the methods that an object may expect to call.Business logic and infrastructure services are also isolated and infrastructure services are exposed as separate services.Application Developers design applications to request services.Component developers focus on design of services to that consume and fulfill requests.




Product/ Service

Structure


Business Process

Structure



Shared Services


Resource Structure



Standards


SRM


DataServices






Applications

23Infrastructure Perspective

Network infrastructure supporting HTML/XML already in place, but . . .Security standards are evolving, so security must be a design consideration.

Source: Reactivity




Product/ Service

Structure


Business Process

Structure



Shared Services


Resource Structure



Standards


SRM


DataServices






Applications

24Information Perspective

Information is now more highly visible.

– Federated data model allows just-in-time information joining

– Business Intelligence Data Store loads can be transactional

– Operational and reporting data can coexist in the channel

– Analytical data/Dashboards are more easily assembled directly from key services with real time data




Product/ Service

Structure


Business Process

Structure



Shared Services


Resource Structure



Standards


SRM


DataServices






Applications


Getting Started

A Study in Implementation

Tactical Bottom-up Approaches

Strategic Top-Down Approaches

26A Study in Implementation of an SOA

A well-known financial business

–Required 30 systems and 300,000 lines of Cobol and C code to make an address change for a customer

–The firm applied SOA to that one problem and reduced the lines of code to 20,000

–In addition, rather than taking 24 hours to update all 30 systems, it now takes no more than 35 seconds

27A Tactical Bottom-up Approach SOA Migration Strategy

Source: Thomas Erl

SOA

SOS

ROI of SOA and SOSincreases as youbroaden scope

Beyond the intrinsiclayer is the buildingblock for the standardized SOS model

SOA and SOS (Service Oriented Security)standards are establishedincrementally

Each layer is alogical architectureboundary

Progressing through thelayers, builds an increasingly broader SOA

The Layered Scope Model (LSM)

28

– Use a high business value application such as a Legacy Mainframe system, ERP or CRM and identify the data and processes that should be shared and common across the enterprise.

– Separate the potential shared data/methods and expose them as Web Services.

– Implementation steps:

1. Create XML/Web Service standards within one architecture boundary

2. Determine which Data/Methods to expose outside of the intrinsic application

3. Perform impact analysis to assess the cost, effort and impact to the existing technical environment

4. Publish standards and guidelines by incorporation any existing standards. This will establish re-usable application logic and utility services that can be used by other applications

5. Deploy the application and publish the Web Service methods in a Discoverable Directory (UDDI)

6. Repeat steps one thought four for each incremental release and broaden step 5 until you are ready to move on to the next architectural layer

Steps in Applying a Tactical Bottom-up Approach

Source: Thomas Erl

29Strategic Top-Down Approaches: Portfolio Management, Governance, and the EA Stack

– Starting from the Enterprise Architecture level, you can strategically identify services key to the technical and business aspects of your operation

– You can also identify application opportunities within your portfolio as you plan for your future architectures

– Implementation Steps:1. Planning Initiation2. Business Modeling3. Current Systems and

Technology Review4. Data Architecture Design5. Applications Architecture

Design6. Technology Architecture

Design7. Implementation and Migration

PlanningSource: Adapted from Steven Spewak

Planning Initiation

Current Systems & Technology

Business Modeling

DataArchitecture

ApplicationsArchitecture

TechnologyArchitecture

Implementations / Migration Plans

1

2 3

4 5

7

6




Product/ Service

Structure


Business Process

Structure



Shared Services


Resource Structure



Standards


SRM


DataServices






Applications

30Further Considerations for Implementing SOA

IT Assets What are the assets that are shared throughout the enterprise?

Service Identification What is the business functionality to be provided by a given IT Asset? What is the optimal granularity of the service? Where should a service be located within the enterprise?

Domain Definition How should services be grouped together into logical domains? (Business Units, Divisions, Departments etc.)

Packaging How is existing functionality within legacy mainframe systems re-engineered or wrapped in reusable services?

Orchestration How are composite services to be orchestrated? (Workflow/Collaboration)

Transaction Routing How are requests from service consumers to be routed to the appropriate service and/or service domain?

Governance How will the enterprise exercise governance processes to administer and maintain services?

Messaging Standards How will the enterprise adopt a given standard consistently? (Security, Interface Standards etc.)


About LiquidHub

32LiquidHub at a Glance

LiquidHub is a systems integrator and technology consultancy delivering Strategy, Applications, Data, and Infrastructure Solutions that revolve around the needs of the global enterprise.

Supporting clients in Life Sciences & Healthcare, Financial Services, Retail, Media, High Technology and other key industries, our solutions are designed to integrate new technology frameworks with enterprise and legacy systems.

With offices in Philadelphia, Boston, and Hyderabad, India, our associates serve clients globally, at their site or on ours.

Since being founded in January 2001, LiquidHub has grown into one of the region’s premier consultancies, with over 150 associates.–April 2004 - Philly Business Journal ranks LiquidHub as 6th largest Systems Integrator and 17th largest technology employer in region

–November 2003 - Named "Start-up Company of the Year" by Eastern Technology Council

33IBM and LiquidHub

LiquidHub values IBM’s applications development, SOA, middleware and multi-platform strengths for our clients in a variety of industries.

We are pleased to have them here with us today to talk about their SOA direction and the benefits of an IBM infrastructure in implementing Service Oriented Architectures.


© 2003-2004 IBM Corporation

Services Oriented ArchitectureServices Oriented Architecture: a new model for Engagement

Jim RyanJim RyanIBM SWICIBM SWIC

35 SOA: a new model for Engagement © 2003-2004 IBM Corporation

Service Oriented Architecture and Web servicesHow two critical ingredients map to the on demand operating environment

Sof

twar

e D

evel

opm

ent

Inte

grat

ion

Infra

stru

ctur

e M

anag

emen

t

Ser

vice

Orie

nted

Arc

hite

ctur

e

Indu

stry

Sta

ndar

ds

Service Oriented Architecture

Web servicesBuild Deploy

Consume

Manage Secure

IBM is committed to investing over $1 billion next year on Web services



Data

ServiceFlow

ExistingApplications

NewService Logic

B2BInteractions

SOAPService Request

(e.g. .NET)

Portal Service


WebSphereBusiness

IntegrationServer

WebSphereBusiness

IntegrationServer

and WebSphere

B2BInteractions

SOAPService Request

(e.g. .NET)

Portal Service


Data

NewService Logic


WebSphere Business Integration Server

•Create and deploy new business processes

•Synchronize business events in multiple systems

•Integrate applications on diverse platforms

•Transform information formats en-route between applications

•Link people into a new business approach


*DB2 InformationIntegrator


Service Oriented Architecture and WebSphere

NewService Logic

B2BInteractions

SOAPService Request

(e.g. .NET)

Portal Service

WebSphereBusiness

IntegrationServer


DB2 Information Integrator

Provides integrated, real-time access to diverse data as if it were a single database, regardless of where it resides.

•The federated server lets users create an abstract relational view across diverse data.

•The replication server lets users manage data movement strategies including distribution and consolidation models.


WebSphere Business Integration Adapters

+ EM Offerings


+ EM Offerings


NewService Logic

B2BInteractions

SOAPService Request

(e.g. .NET)

Portal Service


WebSphereBusiness

IntegrationServer

Enterprise Modernization Offerings

•Host Integration Software•WebSphere Host Publisher•WebSphere Host Access Transformation Services•WebSphere Host on Demand

•WebSphere Studio Software•WebSphere Studio Enterprise Developer•WebSphere Studio Asset Analyzer•WebSphere Development Studio for iSeries

•CICS Transaction Gateway


•Application adapters•e-business adapters•Mainframe adapters•Technology adapters


WebSphereApplication Server


+ EM OfferingsWebSphere

Application Server


B2BInteractions

SOAPService Request

(e.g. .NET)

Portal Service


WebSphereBusiness

IntegrationServer

WebSphere Application Server

•A next-generation application server that simplifies build-to-integrate tasks, accelerates application development, and enables dynamic application flexibility.


WebSphere Portal Server

SOAPService Request

(e.g. .NET)




B2BInteractions


WebSphereBusiness

IntegrationServer


+ EM Offerings


•Portlets can exploit WebSphere Web service functions

•Supports pluggable, interactive, user-facing Web services

•Can publish portlets as Web services using admin UI


WebSphere Web Services Gateway



B2BInteractions




WebSphereBusiness

IntegrationServer


+ EM Offerings


•A run-time component that provides configurable mapping based on WSDL documents. It maps any WSDL-defined service to another service on any available transport channel. It is usually deployed at the firewall and has access to internal services.


WebSphere Business Integration Connect







WebSphereBusiness

IntegrationServer


+ EM Offerings


•Enables operational B2B based on communities of trading partners.

•Connect to and integrate with communities of trading partners .

•Support for a wide range of industry standard protocols including RosettaNet, AS2 and XML

•Support for trading partner interactions over transports such as HTTP(S), FTP and SMTP





WebSphere Portal ServerWebSphere Messaging(MQ, WBI brokers)


WebSphereBusiness

IntegrationServer



+ EM Offerings

Liquidhub Ibm Service Oriented Architecture Presentation 064234 (1)

Documents

Transcript of Liquidhub Ibm Service Oriented Architecture Presentation 064234 (1)