Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Like this? Share it with your network

Share

Custom Development of Enterprise Services

on

  • 3,258 views

These are the slides of my talk at SAP Mentor monday 8th november about development of Enterprise Services.

These are the slides of my talk at SAP Mentor monday 8th november about development of Enterprise Services.

Statistics

Views

Total Views
3,258
Views on SlideShare
3,258
Embed Views
0

Actions

Likes
2
Downloads
44
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Custom Development of Enterprise Services Presentation Transcript

  • 1. Custom Development of Enterprise Services - What does an Software Architect need to know? Tobias Trapp
  • 2. Table of Content Standardization of Web Services Component Architecture Implementation Details Summary © Tobias Trapp 2010 2
  • 3. Welcome to ABAP Web Service Jungle! Which SAP technology is the most appropriate for specific purposes? lightweight interfaces: REST are very useful for integration of output and document management systems application integration: A2A services outside-in using PI commerce transactions between businesses : B2B services generated outside-in, propably using PI integration using arbitrary clients: A2X services generated outside in exposing BOL classes on the fly: CRM Web Service framework mobile apps: Sybase CRM Mobile Sales and Mobility for SAP coming soon: project Gateway exposing function modules on thy fly: inside out generation © Tobias Trapp 2010 3
  • 4. „Inside Out“ is a Dead End Street „Inside Out“ means poor man‘s SOA no standardized data types we can‘t control mandatory and non-mandatory elements no standardized naming conventions no standardized communication patterns no patterns for asynchronous scenarios no standardized change strategies: first one wins vs. last one wins complicated & database–like because of TABLES parameters important frameworks are missing - idempotency - forward error handling - no enhancement concept for customers © Tobias Trapp 2010 4
  • 5. Enterprise Services Build your SOA on standards and best practices use global data types according UN/CEFACT standards develop enterprise „outside in“: generate ABAP proxies from a WSDL (file, URL, ESR) using transaction SPROXY / SE80 follow ESR modelling guidelines and create ESR certified content from SAP Guidelines for Best-Built Applications that Integrate with SAP Business Suite: © Tobias Trapp 2010 5
  • 6. Nearly everything you need to know is written down There are lots of resources on SCN and SAP Press many tutorials about ESR on SDN SOA 300 training everything about modelling & implementation is written down in SAP Press Book „Developing Enterprise Services for SAP“ „How To… Develop, Monitor and Debug WS Consumer and Provider“ Enterprise SOA Development Handbook 1.1 chapter about SOA & loose coupling of applications in SAP Guidelines for Best-Built Applications that Integrate with SAP Business Suite © Tobias Trapp 2010 6
  • 7. Enterprise Services have well-defined Semantics Use naming conventions and communication patterns naming convention is: <business object view> <action> <message type> Sales Order Create Request actions are Create, Read, Update (first one wins), Change (last one wins), Cancel and Check: Purchase Order Cancel Check Query Request there are well-defined semantics described below: © Tobias Trapp 2010 7
  • 8. Table of Content Standardization of Web Services Component Architecture Implementation Details Summary © Tobias Trapp 2010 8
  • 9. SOA by „Controlled Evolution“ SOA by Design vs. SOA by Evolution SAP‘s SOMAID methodology is heavy weight – you need a list of all processes whether they are IT-based or not whenever you can use Enterprise Services of SAP Business Suite - you‘ll find them on ES work place http://www.sdn.sap.com/irj/bpx/esworkplace if necessary enhance SAP standard services as described in Enterprise Service Enhancement Guide create custom Enterprise Services using SAP‘s modelling approach - construct them from business objects of your ABAP app. © Tobias Trapp 2010 9
  • 10. ABAP Apps, ESR SWCVs and XML Namespaces How to structure ESR development SWVCs in ESR correspond to ABAP SCs an ABAP application corresponds to an repository namespace define data types for reuse in separate namespaces create repository namespace for each application containing business objects this leads to a hierarchy of repository namespaces http://tempuri.org/xi/flightmanagement/CRM http://tempuri.org/xi/flightmanagement/CRM/Global http://tempuri.org/xi/flightmanagement/BP http://tempuri.org/xi/flightmanagement/BP/Global http://tempuri.org/xi/flightmanagement/Global hint: avoid special characters in XML names because package names of generated classes consumers tend to get complicated – this is a problem of many non-SAP frameworks © Tobias Trapp 2010 10
  • 11. ABAP Component Structure How to structure server proxies according to your ABAP component hierarchy? in NW 7.01 there can be only one proxy element per system (and ABAP namespace). ESR dependencies lead to dependencies in ABAP: proxy elements will be reused - so be careful if the proxies are in different ABAP components: http://tempuri.org/xi/flightmanagement/CRM http://tempuri.org/xi/flightmanagement/CRM/Global } CUSTCRM http://tempuri.org/xi/flightmanagement/BP http://tempuri.org/xi/flightmanagement/BP/Global http://tempuri.org/xi/flightmanagement/Global } CUSTBP SCs in an create packages that contain only ABAP proxies ABAP system © Tobias Trapp 2010 11
  • 12. Table of Content Standardization of Web Services Component Architecture Implementation Details Summary © Tobias Trapp 2010 12
  • 13. Best Practices for Creating Enterprise Services Common mistakes and how to avoid them specify error handling: system errors, wrong input parameters, missing authorities… consider compensation scenarios: what happens if a web service call fails? use forward error handling in asynchronous scenarios consider reviews for ESR development – developers tend to break every rule because they can do anything in XML keep code in generated classes small – delegate to classes containing business logic for each method use naming conventions for data types, parameters, message types and message data types in generated classes develop in a test driven way: check ABAP classes using unit tests, test Enterprise Services using ABAP test tool resp. eCATT study best practices in SAP guidelines esp. the SAP Press book don‘t follow guidelines for SAP Business Suite blindly: asually an ES doesn‘t need to be XI 3.0 conform and contain more than 1 operation. © Tobias Trapp 2010 13
  • 14. Absolutely necessary to know: Extended XML Handling Empty values vs. Null values NULL values have different semantics compared to initial values: - NULL values in an update service mean that they should not be changed - NULL values in a query mean that a data element is not relevant in a search Initial values can be coded as empty XML elements NULL values can be coded using xsi:nil and missing elements In the constructor of a server proxy switch extended XML handling on: set_extended_xml_handling( i_switch_on = abap_true ). Then you get the information about every data element (omitted, xsi:nil, initial) in an structure PRXCTRLTAB © Tobias Trapp 2010 14
  • 15. A hidden gem: Generic Code List Provider Framework Codes can be defined an ABAP backend system define code lists as XML schema enumeration types only if the values are well-defined & do not change In most cases code lists are defined in ABAP backend in customizing tables you can bind domain values, (text) tables to server proxy data elements and read them using the generic Enterprise Service QueryCodeList the framework is extensible – think of time depended customizing, subsets of customizing sets… © Tobias Trapp 2010 15
  • 16. Table of Content Standardization of Web Services Component Architecture Implementation Details Summary © Tobias Trapp 2010 16
  • 17. Explain to developers the concept of Enterprise Services As software architect now you are well prepared for a SOA project, but don‘t forget: keep yourself informed - ABAP frameworks are rapidly evolved by SAP learn about eventing, service groups, forward error handling… What do developers of Enterprise Services need to know? a prototype implementation will help developers to understand the concepts teach developers the transactional behaviour esp. in update/change services: SET UPDATE TASK LOCAL, cl_soap_commit_rollback and that enterprise services are stateless – no DB cursor! don‘t forget to test the enterprise services with user with different authorization profiles in the ABAP backend. © Tobias Trapp 2010 17