Your SlideShare is downloading. ×
0
Making SOA Operational

- Service Management enabling SOA -


Dr. Stefan Pappe
CTO Middleware Services
IBM Global Technolo...
Content


    1. Integration of Development and Operations

    2. Practitioner point of view

    3. Architecture with a ...
Every CEO and CIO cares about operational aspects
                                                   Partner with the CEO ...
Integration of the development and operations life cycles

      The lack of lifecycle integration between development and...
Content


    1. Integration of Development and Operations

    2. Practitioner point of view

    3. Architecture with a ...
SOA Deployment Best Practices & Lessons Learned from 152 projects

    Methodical, cross-IBM approach to capture, analyze,...
Functional and Non-Functional Requirements we typically find in projects
    confirm the need to focus on infrastructure a...
Content


    1. Integration of Development and Operations

    2. Practitioner point of view

    3. Architecture with a ...
Building an SOA architecture with a vision for the future

    Characteristics of Reference Architectures
                ...
SOA architectural decision accelerator

      Challenge: Hundreds of SOA implementation decisions are
       often done b...
SOA architectural decision accelerator
Faster time to value and less risk through proven recommendations
      Case Study...
SOA Projects deal with Transformation
of Functional Architecture And the Operational Architecture

                       ...
Content


     1. Integration of Development and Operations

     2. Practitioner point of view

     3. Architecture with...
SOA Represents a Marked Change in IT Prioritization
And Requires a New Way of Thinking

     Old Thinking                 ...
SOA increases the need for a mature infrastructure

     • A risk gap can arise if the
       adoption of SOA is not
     ...
IT Service Management is about people, processes,
     information and technology
     You need well-trained people armed ...
How does SOA impact infrastructure & management?
                                                                         ...
In the context of service level management, we see that service
                   levels are being matured from tradition...
Aligning IT with business priorities well, requires a deep understanding, and
continuous management, of the dependencies b...
From Service Level Agreement to Business Service Level Agreement
     Applications               Monitoring   Collection C...
Content


     1. Integration of Development and Operations

     2. Practitioner point of view

     3. Architecture with...
Best Practices suggest a project approach with
functional and operational activities running in parallel

     Business   ...
Stefan  Pappe    Making  S O A  Operational
Stefan  Pappe    Making  S O A  Operational
Stefan  Pappe    Making  S O A  Operational
Stefan  Pappe    Making  S O A  Operational
Stefan  Pappe    Making  S O A  Operational
Upcoming SlideShare
Loading in...5
×

Stefan Pappe Making S O A Operational

724

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
724
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
25
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Stefan Pappe Making S O A Operational"

  1. 1. Making SOA Operational - Service Management enabling SOA - Dr. Stefan Pappe CTO Middleware Services IBM Global Technology Services © 2008 IBM Corporation
  2. 2. Content 1. Integration of Development and Operations 2. Practitioner point of view 3. Architecture with a vision 4. SOA management 5. Exemplary project approach 6. More best practices 2 Operational SOA © 2008 IBM Corporation
  3. 3. Every CEO and CIO cares about operational aspects Partner with the CEO to drive innovation Enterprise Goals: Increase the flexibility of the business » Drive top-line revenue Drive IT growth goals: Deliver new value from existing assets (information and people) » Continue to deliver bottom-line profit growth » Run the business while Address governance, operational risk and compliance challenges changing the business Reduce the cost and complexity of IT operations Business depends on quality service delivery 3 Operational SOA © 2008 IBM Corporation
  4. 4. Integration of the development and operations life cycles The lack of lifecycle integration between development and operations continues to drive costs up and operational service quality down Development View of IT Operations View of IT Requirements Project Mgmt Act Surprised Development Help Desk Managing Changes IT Strategy Analysis & Design Change Control Installation Testing Asset Mgmt Backup / Restore Deployment Implementation Documentation System Admin System Operation Throw over Wall Availability Mgmt Human Factors Test Identity Mgmt Compliance Risk Mgmt Architecture Packaging Financial Mgmt Continuity Capacity Planning Security Mgmt Problem Mgmt Sometimes Development tends to Most IT organizations spend 70- underestimate Operations (and 80% on operations vice versa) Quality service delivery depends on integration 4 Operational SOA © 2008 IBM Corporation
  5. 5. Content 1. Integration of Development and Operations 2. Practitioner point of view 3. Architecture with a vision 4. SOA management 5. Exemplary project approach 6. More best practices 5 Operational SOA © 2008 IBM Corporation
  6. 6. SOA Deployment Best Practices & Lessons Learned from 152 projects Methodical, cross-IBM approach to capture, analyze, feedback SOA deployment experiences  SOA Deployment Lessons Learned / Best Practices Conference executed through IBM Academy of Technology  Applied standardized Case Study Template – incl. project information, architecture, project experience, assets&innovation  2007+2008 conferences resulted in 152 case studies, with 950 lessons learned / 870 best practices Reusable Results  Feedback and reuse in IBM Products and Services  White paper for clients with top 5 best practices published at: http://www-935.ibm.com/services/us/its/pdf/wp_five-best-practices-for-deploying-successful-soa.pdf 1. Develop an architecture with a vision for the future 2. Foresee linkages from IT to your business processes 3. Create an organizational culture and skills to support SOA 4. Build a scalable infrastructure 5. Enable operational visibility through governance and service management 6 Operational SOA © 2008 IBM Corporation
  7. 7. Functional and Non-Functional Requirements we typically find in projects confirm the need to focus on infrastructure and operational aspects 5% Reuse 16% Connectivity 21% Interaction and Collaboration Services 8% Sample NFRs Business Process Availability Information as a Service 3% 14% 6% 13% Flexibility Governance 10% Governance 13% Design 2% 3% 4% Interoperability 17% Security and Management Performance 5% Regulatory 9% Sample Functional Requirements Reliability 7% Reusability 6% Scalability 3% Security 3% Servicability Standards 2% 30% Technology Usability 7 Operational SOA © 2008 IBM Corporation
  8. 8. Content 1. Integration of Development and Operations 2. Practitioner point of view 3. Architecture with a vision 4. SOA management 5. Exemplary project approach 6. More best practices 8 Operational SOA © 2008 IBM Corporation
  9. 9. Building an SOA architecture with a vision for the future Characteristics of Reference Architectures The Logical Solution View emphasizes a • Architectural templates with prescriptive business or industry specific perspective. guidance Processes, Services, Applications • Common representation, concepts, terminology • End2end functional and operational view Middleware The Middleware organizes technical MW components • Static and dynamic views that provide a set of enabling Virtualized Infrastructure capabilities as services. • Multiple levels of elaboration to support multiple project phases Physical Infrastructure • Definition of specific products instantiation • Conformance with architectural practices and The Operational View identifies the IT operational capabilities that are needed for implementing and artifacts operating an SOA infrastructure. • Architectural decisions and standards 9 Operational SOA © 2008 IBM Corporation
  10. 10. SOA architectural decision accelerator  Challenge: Hundreds of SOA implementation decisions are often done by “gut feel” – identification – not systematical, decision making – driven by personal experience and preferences  Solution: Proactive, step-by-step method delivering best practices – Governance with reusable, standardized decision identification, drivers, alternatives – Navigation by role, phase, component, etc.  IBM Global Services  Architectural Decision Knowledge Wiki for Clients architecture decision – Web 2.0 tool & model for capturing decision available on accelerator for SOA alphaWorks with 20 sample decisions: http://www.alphaworks.ibm.com/tech/adkwik - ~400 decisions captured – Can address any IT domain including SOA 10 Operational SOA © 2008 IBM Corporation
  11. 11. SOA architectural decision accelerator Faster time to value and less risk through proven recommendations  Case Study: Telco client – Client Situation – IBM Solution • Challenges with workflow across • SOA-based business process integration and integrity management heterogeneous backend systems – Benefits of using SOAD – Project Domain • Faster project execution, esp. in solution outline phase • Order management • Less risk through reuse of proven recommendations  Sample Decisions  Sample Recommendations ─ Technical Executive Level • Which process layer strategy? Explicit process layer with executable • Which ESB? workflows ensuring e2e data integrity ─ Conceptual Level • Workflow pattern? Security concepts? • Synchronous or asynchronous message exchange? Pseudo-synchronous messages for guaranteed message delivery ─ Technology Level • BPEL or other BPM/workflow language? BPEL as a standardized WS-* workflow language • SOAP or RESTful service invocation? ─ Vendor Asset Level • Single WebSphere Process Server and ESB or high SOAP to meet interoperability requirements availability topology (cluster)? 11 Operational SOA © 2008 IBM Corporation
  12. 12. SOA Projects deal with Transformation of Functional Architecture And the Operational Architecture Service Oriented Architecture  Business Process orchestration Business Business  Message based communication Logic Shared Logic Shared  Loosely coupled application services Services Services Demand Secure, Robust On demand Server, environments to support Storage, Network, Security, rapid deployments & Monitoring, Connectivity & access of services Accounting Services Supply  Flexible combination of services Pooled End-to-end ESB &  Rapid provisioning Compute Pooled Monitoring Common  Virtualisation Resources Storage Service  Highly utilised shared resources Resources Platform SOA Infrastructure 12 Operational SOA © 2008 IBM Corporation
  13. 13. Content 1. Integration of Development and Operations 2. Practitioner point of view 3. Architecture with a vision 4. SOA management 5. Exemplary project approach 6. More best practices 13 Operational SOA © 2008 IBM Corporation
  14. 14. SOA Represents a Marked Change in IT Prioritization And Requires a New Way of Thinking Old Thinking New Thinking IT maintains IT resources that IT delivers services designed to support the business meet business goals From Silos … … to Services 14 Operational SOA © 2008 IBM Corporation
  15. 15. SOA increases the need for a mature infrastructure • A risk gap can arise if the adoption of SOA is not supported by underlying infrastructure capabilities. • Predicting, assessing, planning, architecting, designing, health checking the infrastructure in order to keep in synch with the business requirements. 15 Operational SOA © 2008 IBM Corporation
  16. 16. IT Service Management is about people, processes, information and technology You need well-trained people armed with the right information to execute well-defined, technology-enabled processes to deliver high-quality services to the business functions they support People Process  Roles, teams and functions  Staffing levels  Technology and information requirements  Skill requirements  Resource  Policies and governance acquisition  Job descriptions  Process design  Training curriculum  Performance indicators  Detailed workflows  Staff training  Workflow implementation  Procedures Technology Information  ITSM architecture  Development environments  Information requirements  Tool requirements  Customization and  Data model integration   Tool evaluation and Information flows selection  Testing  Interfaces and integration  Tool installation  Deployment  Measurements  Reports 16 Operational SOA © 2008 IBM Corporation
  17. 17. How does SOA impact infrastructure & management? Consumer satisfaction Service Contracts Controlled SOA operating environment Increased Business flexibility Measurement Dashboards - SOA governance - Loose coupling design of business processes - IT governance & organization - Reusable business services & components - IT services & processes Non Functional Requirements Event, Incident, Problem Increased IT flexibility management Control Change & configuration Service Level management management detailed in Introduced through SOA next charts  New managed elements Security Business Service management SOA management  Potentially many services Management  Regular changes / reconfigurations Financial Capacity & performance management management  Composite apps spanning org boundaries  Decoupled infra & app Release Availability & continuity management management  Shared / Virtualized infrastructure Test influences management 17 Operational SOA 20-Oct-08 © 2008 IBM Corporation
  18. 18. In the context of service level management, we see that service levels are being matured from traditional technical SLAs BLA: Business Level Agreement agreed quality of service, measured and reported in E2E Many clients Business the context of business results Operations are here… Management Granularity BLA (e.g. revenue generation) Business Transformation BSLA: Business Service Level Agreement Process agreed quality of service, measured and reported in Operations the context of business processes BSLA Process Mgmt / (e.g. date/time for payroll completion, business hours Reengineering lost, value of invoices in process queue) IT Operations Component SLA SLA: Service Level Agreement Systems Mgmt / agreed quality of service, measured and reported Re-engineering against criteria of technical infrastructure and applications, aligned with client requirements via IT Business Service Level Management Management Focus (e.g. UNIX availability 99.998%) based on IBM Academy Study into Business Level Agreements, 2004 18 Operational SOA © 2008 IBM Corporation
  19. 19. Aligning IT with business priorities well, requires a deep understanding, and continuous management, of the dependencies between IT business services and the underlying IT systems and resources. LOB Dependency Tree LINE OF BUSINESS ENTERPRISE SERVICE PROVIDERS define Implement platform service contracts BUSINESS PROCESS BUSINESS SERVICE Managed according to E2E Business LAs IT BUSINESS SERVICE IT service catalogue MANAGEMENT Application Request SERVICE Managed Tracked according against E2E IT to IT SLAs IT SYSTEM and KPIs SLAs and KPIs IT RESOURCE SERVICES INTEGRATOR define integrated IT /app view Business of IT Dependency Tree 19 Operational SOA © 2008 IBM Corporation
  20. 20. From Service Level Agreement to Business Service Level Agreement Applications Monitoring Collection Correlation Impact analysis Visualization Business Dashboards Service & contract Repository Monitors Notification BIM Business Servers Impact KQIs Monitors Indication KPIs SLA Violations BSLM Network Service KQIs Devices Impact Monitors Indication Notification BQM Manual (User Service Quality Initiated) Data Monitors Data aggregation and KQI calculation and KPI computation correlation 20 Operational SOA © 2008 IBM Corporation
  21. 21. Content 1. Integration of Development and Operations 2. Practitioner point of view 3. Architecture with a vision 4. SOA management 5. Exemplary project approach 6. More best practices 21 Operational SOA © 2008 IBM Corporation
  22. 22. Best Practices suggest a project approach with functional and operational activities running in parallel Business Strategy Services and Planning Design Implementation Run SOA Governance and Project Management Process Modeling Process Services SOA Strategy Service Design Service Development Business Monitoring Service Assembly Application & Resources Middleware Framework Standards and Project Non-functional requirements, SLAs + for Monitoring, Test + Launch Services Plan Definition OLAs, Capacity Planning Performance + Test Plan Definition IT Monitoring Service Management Service Management Configuration Design Infrastructure Infrastructure Infrastructure Security, Orchestration, Services Roadmap Infrastructure Virtualization Rollout Design 22 Operational SOA © 2008 IBM Corporation
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×