Your SlideShare is downloading. ×
Ws Soa V6 Theory And Practice
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Ws Soa V6 Theory And Practice

1,466

Published on

Published in: Business, Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,466
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Transcript

    • 1. Pini Cohen VP , Senior Analyst Architecture and Infrastructure Strategies [email_address] SOA and Web Services
    • 2. Agenda
      • Business Scenario
      • What is the problem?
      • Definitions
      • Current situation in Israel
      • Recommendations – process and practical
    • 3. Move From Silo-Based Development to Modular, Open Architecture (SOA) RIGIDITY Business Process Functions Presentation Layer/ UI Infrastructure (HW, Network, Data Center) Current Technology Stack Monolithic Applications 2 1 4 Data Connectivity/ Messaging 3
    • 4. The Result: Typical IT Budget Allocation Horror story: adding two digits to a part number that requires $2M and one year to implement (but added no additional business value) because it touched on almost every system in the enterprise Maintenance Integration New Applications 70-90% 15-30% 5-15%
    • 5. Agenda
      • Business Scenario
      • What is the problem?
      • Definitions
      • Current situation in Israel
      • Recommendations – process and practical
    • 6. What Is “Service-Oriented Architecture” All About? Service Provider Service Interface Why bother? Service Consumer ? ? ?
    • 7. What is a Service?
      • Service : A specific style of functionality based on a service contract
      • Characterized by:
        • Dynamic binding
        • Loose coupling
        • Modular and self contained
        • Composable
      • Managed
        • SLA
        • Lifecycle
      • Not all services are created equal.
      Service Level Agreement Service Interface Implementation Internal Data Internal Functionality Virtual Business Objects Service Interface Service Contract
    • 8. SOA vs. Web Services SOA Web Services SOA Web Services SOA Web Services Or Or
    • 9. Move From Silo-Based Development to Modular, Open Architecture (SOA) RIGIDITY Business Process Functions Presentation Layer/ UI Infrastructure (HW, Network, Data Center) Current Technology Stack Monolithic Applications 2 1 Infrastructure Services Future Loosely Coupled, Open Model Based on SOA 4 Data Interface Services Framework Connectivity/ Messaging 3 Integration Services Framework Business Services Framework FLEXIBILITY Infrastructure Services Framework Business Process Services Integration Services Interface Services 1 3 2 4
    • 10.
    • 11. Composite Applications Composite Applications Drop-and-configure Optimize Rate Plan Get Customer Process Order Get Value Get Churn
    • 12. BPM - Business Process Management
    • 13. Old vs. New concepts
      • Traditional EAI
        • Point to Point “integration projects”
        • Lack of A2P and P2P
        • No real reuse – each application with its own interfaces
        • Not necessarily open standards
        • EAI “give services to other applications” but not the “responsible”
      • Traditional Human Workflow (“old” BPM):
        • Emphasis on human to human interactions
        • Not Necessarily open standards
        • Lack of P2A and A2A
        • Tactical and not Strategic approach
    • 14. Old vs. New concepts
      • New concept - SOA
        • Service based approach
        • EAI/ ESB for open standard integration, execution and Metadata environment
        • Services to the developers – security, transformation, logs, etc.
        • BPM as composite application enabler (A2A, P2A, X2X) including BAM , B2B, simulation and more
        • Portal as the general cross application GUIs
        • Organizational Change: Enterprise Architect Group
        • Enterprise Architecture tools “SOA Governance tools”
    • 15. Loose coupling
      • Coupling refers to the amount of dependency between services
      • Loosely coupled services have few well-known dependencies
      • Tightly coupled services have many known and more importantly, unknown dependencies
      • Basic recommendation for XML, other for loosely coupling – If “receiver” gets “unknown” parameter – discard it!
    • 16. Sun Composite Application Platform Suite (CAPS) – Composite Applications are built on top of a comprehensive ESB CAPS ESB CAPS Composite Apps Messaging and Request / Reply ETL Customer Data Integration BAM Workflow B2B B2B A2A A2A BL BL B2B Portal B2B Portal Wrappers / Adapters Transformation Orchestration
    • 17. ESB Architecture Separately Available ESB Product Oracle Bus Grid UDDI AS AQ/JMS JBI Gateway Security Pub/Sub Lightweight BPEL Content Router XSLT Transform Technology Adapters Oracle Apps Adapter Java Services CEP Application Adapters Customer Data Hub BAM XQuery Task BPEL B2B Others …
    • 18. Service Infrastructure Reference Architecture Order Management Process Services Routing AquaLogic Service Bus Data Services AquaLogic Data Services Platform Portal Tier WLP Service Routing Billing Inventory Management Mainframe .Net ERP Data Warehouse Oracle Process Tier WLI Portlet Web App Security Services AquaLogic Enterprise Security Service Registry AquaLogic Service Registry End-to-end Web Services Management Service Registry
    • 19. SOA Runtime Management… Credit Service 1 Credit Service 2 <soapenv:Envelope xmlns:soapenv=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;> <soapenv:Body> <po-number> A234235 </po-number> </soapenv:Body> </soapenv:Envelope> Enterprise Service Bus
    • 20. SOA Governance - Systinet 2 Components
    • 21. Metadata Information - many sources ! Use cases Business process models Best practices Design patterns Technical architectures Applications Components Services Documentation Test cases LOGIDEX Analysis + Design Coding Testing + QA Deployment Requirements METADATA
    • 22. Governance : Example – enabling Chargeback
    • 23. IT Architect - Extending Project Value Total Value V t = V u V u = Value to User Project by itself V u = Value to user
    • 24. V e = Value to Enterprise Total Value V t = V u + V e V u = Value to User Project within the Enterprise Extending Project Value
    • 25. Project connected to Infrastructure V i = Value to Infrastructure Total Value V t = V u + V e + V i V e = Value to Enterprise V u = Value to User Extending Project Value
    • 26. Agenda
      • Business Scenario
      • What is the problem?
      • Definitions
      • Current situation in Israel
      • Recommendations – process and practical
    • 27. Web Services in local organization
      • Bezeq – WS to MQ for identity requests
      • Phoenix insurance - exposing a Cobol Legacy applications as WS.
      • Bezeq int. – Both clients and dealers (different applications) contacting the systems including roll-backs
      • Police – standard reports via Web Services used in many systems
      • Clalit Health Services – Demographic details used by many systems
      • Defence – ID of employee and the result is the picture. Used in many systems. Problems – different networks, security, where will the services be defined?
      • Poalim Bank- general Currency Rates Interface , CICS transactions (example – Charging Permission) via WS. Also extensive BPM/Event Driven
      • VISA CAL – “Snif Cal” selling credit cards directly utilizing secure Web Services for Credit Card Legacy Application via iBOLT
      • Leumi Card – Billing details
      • Defense – from CobolUnix to .NET with WS , externalizing ERP systems
      • Maccabi-Health – doctors details, lab results
    • 28. Local situation – Summary
      • Web Services- Yes!
      • Some degree of Reuse – Yes !
      • BPM – Human Workflow – Yes ! Full scale BPM (BPM is the initiator, includes UI and responsible, across vertical silos) – No!
      • EAI tools are used many times for the main mechanism for Web Services /SOA deployment
      • Some of the Challenges:
        • Monitoring
        • Operations – Versioning, Error Handling, etc.
        • Organizational Issues - why do I need it? Who is this architect ?
        • Performance (sometimes bypass is needed)
        • Guarantee Delivery
    • 29. Agenda
      • Business Scenario
      • What is the problem?
      • Definitions
      • Current situation in Israel
      • Recommendations – process and practical
    • 30. Phased Development Approach Future Business Services Architecture Business Models Infrastructure effort % done time Project 1 Infrastructure Project 1 Business Service Project 3 Infrastructure Project 3 Business Service Project 2 Infrastructure Project 2 Business Service prioritization Process and Governance
    • 31. Sample SOA Implementation Roadmap Phase 1
      • Develop:
      • First service
      • High-level architecture
      • Technical standards v1
      • Process v1
      • Deploy first service
      • Document lessons learned
      • Update the high-level arch
      • Update bus & info models
      • Update the tech stds
      • Define metrics
      • Update the process
      • Checkpoint
      • Estimate ROI
      • Produce whitepaper
      • Evaluate LHF
      • Engage stakeholders
      ~ 6 months ~ 6 months Phase 2
      • Expand to 3-5 services
      • Reuse first service
      • Provide SOA Consulting
      • Create common repository
      • Define governance process
      • Develop maintenance and ops plans
      • Collect metrics
      • Align with EA
      • Begin writing COTS wrappers
      • Deploy services
      • Document lessons learned
      • Update the high-level arch
      • Update bus & info models
      • Update the tech stds
      • Update the process
      • Deploy tools
      • Measure SLAs
      • Report on metrics
      • Align with portfolio mgmt
      • Market SOA program
      ~ 3 months ~ 3 months Q3-Q4 FY05 Q1 FY06 Q2–Q3 FY06 Q4 FY06 Implement Refactor Rollout Refactor
    • 32. SOA Roadmap project
      • 1. Determining business goals and strategy – understand what is driving towards SOA, what the overall business goals and strategy are, what is driving the industry over the next 3-5 years. Determine an ‘overall theme’. An example of this is ‘Customer Centric’
      • 2. Determine existing systems and capabilities
      • 3. Develop high-level SOA service organization – propose an organization of service groups that aligns with the goals. Elaborate on the roles and responsibilities of each service group.
      • 4. Determine technology requirements.
      • 5. Develop overall SOA Roadmap – this is where we combine the strategy, SOA and technology into an overall roadmap.
      • 6. Finalize SOA Roadmap.
    • 33. Hierarchy of Service Types Foundation Service Layer (May be used by all other services) Business Service Domain Service ... Domain Service Atomic Component Integration Service ... Utility Service ... Enterprise Business Process Business Service
    • 34. Hierarchy of Service Types Foundation Service Layer (May be used by all other services) For specific LOB – details of Check For specific LOB Operation – changing date of Check For several LOB Operation – relevant information several LOB for ZIPCODE External service (bank of Israel) or Legacy Business process – altering the status of personal Account Altering the status of person in different Accounts (savings, investments, loans, etc.) Business Service Domain Service ... Domain Service Atomic Component Integration Service ... Utility Service ... Enterprise Business Process Business Service
    • 35. Definitions
      • Composite Service: The service functionality is composed from other, smaller services (either atomic or composite).
      • Foundation Service : A utility that aids in the construction of services, such as a business rules engine or workflow system. Provides technical capabilities, not business functionality.
      • Domain Service : A lower level service that provides business functionality within a specific business domain. Domain services provide common functionality in the construction of business services.
      • Business Service : Provides a high granularity of business value. Typically constructed of finer grained processes and services.
      • Enterprise Business Process : A specific kind of business service that spans business domains within (or outside) the enterprise. Constructed from a combination of business services.
    • 36. Final Thoughts
      • Anyone can build a ‘service’. SOA is more.
      • Successful SOA is about business transformation as well as technology solution.
        • The traditional bottom up approach will not yield the desired results.
      • SOA is by nature a cross-boundary concern.
        • That’s where you get biggest value
        • The boundaries you look at are affected by the work at hand as well as the realities of your organizational environment (What boundaries “should” you look at? What boundaries “can” you look at?)
      • Build the right services, and build the services right.
    • 37. Do now for SOA :
      • All developed applications (in house, bids, contracts) should use XML. Exceptions should go through special process
      • Do the above in Loose coupling manner
      • Adopt / develop your own XML dialect
      • Focus on Monitoring-Management, Lifecycle
      • POC is a must
      • Build local www.xmethods.com
      • Prefer smaller projects. Divide large projects to several small ones? Should modules talk to each other with XML?!
    • 38. Do now:
      • Give designers developers significant credit for reuse and for writing reusable componentsfunctions
      • Apply modeling tools for enabling business-IT communication. Preferably utilize BPM tools.
      • Enterprise Architecture should be part of every important activity.
      • Tight relationship between Architecture and Integration teams.
      • Apply SOA principles in the Infrastructure domain
    • 39. Pini Cohen VP , Senior Analyst Architecture and Infrastructure Strategies [email_address]

    ×