1 / 35

Innovating with SAP Enterprise Service Content - a Practical Guide

Innovating with SAP Enterprise Service Content - a Practical Guide. Derek Wood –LS Computing. A CLEAR NEW AFRICA.

aleron
Download Presentation

Innovating with SAP Enterprise Service Content - a Practical Guide

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Innovating with SAP Enterprise Service Content • - a Practical Guide Derek Wood –LS Computing A CLEAR NEW AFRICA

  2. “Service-oriented architecture is a best-practice architecture pattern for the systematic design of request/reply applications. Its primary intentions are business-level software modularity and rapid, non-intrusive reuse of business software in new runtime contexts.” - Gartner, Introduction to Service Oriented Architecture, 2003 “Service-oriented architecture is a design style for maximizing service sharing, reuse, and interoperability in distributed environments.” - Burton Group, Service-Oriented Architecture: Developing the Enterprise Roadmap, 2004 “A service-oriented architecture is a framework for integrating business processes and supporting IT infrastructure as secure, standardized components –services – that can be reused and combined to address changing business priorities.” - IBM, Service-Oriented Architecture (SOA) Compass, 2006 “Service oriented architectures (SOA) is an architectural pattern which requires all exposed functionality to be published as services in a platform-independent manner. These services can be consumed by other applications.” - SAP, Enterprise SOA development handbook 1.1, 2008 What is SOA?

  3. A Service-Oriented Architecture is a collection of services that communicate with each other Services exposefunctionality using a clearly defined method and interface Services are self-contained and do not depend on the context or state of another service Work within a distributed systems architecture What is SOA?

  4. What is an Enterprise Service? • Enterprise services are "a standards-based way of encapsulating enterprise functionality and exposing it as a reusable business service that can be combined with other services to meet new requirements. Enterprise services, defined by SAP and its partners and customers, can be assembled together to compose new applications or enable new business processes." (Source: SAP) • "A business process (such as order processing) is a set of logically related activities performed within or across an organization to fulfil a defined business objective." (Source: industry term.)

  5. What is ES Content • ES Content is pre-packaged integration content, which is created based on the SAP SOA design methodology • This business content includes global data types, service interfaces, models, and mapping definitions • IT professionals can use this pre-delivered content from SAP to jump-start their SOA implementations

  6. IT of the 1990’s Inventory Accounting Human Resources Enterprise Quality Assurance Sales Warehouse

  7. Modularisation of the Enterprise Inventory Accounting Human Resources Enterprise Quality Assurance Sales Warehouse

  8. Evolution of SAP ERP Enterprise SOAProcess Component Architecture SAP R/3Reference Model SAP ERPImplementation Content Enterprise BPMBusiness Process Composition 1990’s 2003 2007 Business Engineering Implementation SOA Design & Governance Innovation Without Disruption

  9. Only 37% of current SOA projects demonstrate ROI SOA touches only 27% of current IT projects in the average organization Only 32% of published software services get reused By 2010, < 25 percent of large companies will have the sufficient technical and organisational skills necessary to deliver enterprise wide SOA. (Gartner) 60% of organizations will adopt SOA, and by 2010 it will be used in 80% of new system architectures IDC forecasts that corresponding software expenses will constitute about 11 billion dollars Before You Start - Some Figures

  10. SOA is considered to be a standard project There needs to be a change in mindset 2nd tier talent is often used Often do not have the right mindset Under resourced Need budget to invest in long-term gains Vendors often define the solutions Business needs to drive solutions Requirements are not fully gathered Need to have a holistic view to reap benefits Why do SOA Projects Fail?

  11. Underestimating the technical complexity of a large-scale SOA Insufficient validation or understanding of the SOA enabling technical infrastructure Insufficient SOA infrastructure monitoring Too-coarse / too-fine service granularity Insufficient / out-of-date documentation Technical Issues

  12. Lack of attention to impact of implementing SOA Insufficient change management for the IT service organization Not leveraging integration/SOA competency centre Thinking SOA projects should be run like any other Not anticipating service growth in a maturing SOA Outsourcing architects (or not having them at all) Overlooking governance Organisational Issues

  13. Dealing with the Issues

  14. The analysts all agree that SOA Governance is key But... ... enthusiasm for SOA and its anticipated benefits results in some companies taking risky shortcuts in establishing robust governance, service development disciplines and staffing There is no “one size fits all” approach governance, too little or too much governance will kill an SOA project, companies need just enough governance (Gartner,2007) Governance is Critical

  15. SOA Governance Ref: www.soagovsource.com

  16. SOA Governance Aligned

  17. Stability vs. Flexibility

  18. SAP’s SOA Strategy

  19. Demo • http://esoadocu.sap.com • http://esworkplace.sap.com

  20. ES Workplace

  21. SAP Documentation for ESOA

  22. Process Components

  23. Process Component View

  24. Service Interface

  25. Service Interface Detail

  26. Service Interface WSDL

  27. ERP Implementation View

  28. Enhancing Enterprise Services ABAP Proxy Implementation Enterprise Service Service Enhancement InboundBAdI Standard Implementation Outbound BAdI

  29. ES Content Distribution Partner SAP Customer Enterprise Service Repository Enterprise Service Repository Enterprise Service Repository Enterprise Service Repository Enterprise Service Repository Enterprise Service Repository SAP Software Component Version SAP Software Component Version SAP Software Component Version SAP Software Component Version SAP Software Component Version SAP Software Component Version SAP Service Interface SAP Service Interface SAP Service Interface SAP Service Interface SAP Service Interface SAP Service Interface Data TypeEnhancement Data TypeEnhancement Partner Software Component Version SAP Service Interface SAP Service Interface Partner Service Interface Partner Service Interface Partner Service Interface Partner Service Interface Data TypeEnhancement Data TypeEnhancement SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Software Component Version SAP Software Component Version SAP Software Component Version SAP Software Component Version SAP Software Component Version SAP Software Component Version BAdI BAdI SAP Service Implementation SAP Service Implementation SAP Service Implementation SAP Service Implementation BAdI BAdI SAP Service Implementation SAP Service Implementation BAdI BAdI BAdI BAdI BAdI BAdI BAdI BAdI BAdIImpl. BAdIImpl. BAdIImpl. BAdIImpl. Data TypeEnhancement Data TypeEnhancement BAdI BAdI SAP Service Implementation SAP Service Implementation BAdI BAdI Partner Software Component Version Partner Software Component Version Partner Software Component Version Partner Software Component Version BAdI BAdI BAdI BAdI BAdI BAdI Partner Service Implementation Partner Service Implementation Partner Service Implementation Partner Service Implementation BAdI BAdI BAdIImpl. BAdIImpl. BAdIImpl. BAdIImpl. Data TypeEnhancement Data TypeEnhancement

  30. Demo

  31. Huge amount of pre-built services available Service enhancements are possible SAP XI / PI not necessarily needed It is required for any enhancements to SAP Content It is a very capable ESB both SAP to SAP and SAP to non-SAP Demo Summary

  32. Start small - think holistically Align with the organization (culture, structure, maturity) Manage expectations internally as well as externally Identify and involve all stakeholders from the start Let the business process be key, not the technology Get the right skills in place – business, architecture & technical Process and services drive the project Start with a process that matters but isn’t critical Invest in Governance to save costs later Final Words

  33. SDN Resources: http://www.sdn.sap.com/irj/sdn/nw-soa http://www.sdn.sap.com/irj/sdn/soa-kit http://esworkplace.sap.com http://esoadocu.sap.com SAP PI Library Page: http://help.sap.com/saphelp_nwpi711/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm Contact me: derek.wood@ls-cs.com Further Resources

  34. Questions?

More Related