Wso2esb sap-jkh-v2.0


Published on

Published in: Travel, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Wso2esb sap-jkh-v2.0

  1. 1. Retail sector example for Using the WSO2 ESB with SAP ERPNalaka Umagiliya – Head of Business Systems (Retail Sector), John Keells Holdings PLCHarsha Senanayake - Head of Enterprise Solutions, John Keells Holding PLCSumedha Rubasinghe – Architect, Chair-Management Committee Data Technologies, WSO2Asanka Abeysinghe - Director, Solutions Architecture, WSO2 © WSO2 2012. Not for redistribution. Commercial in Confidence.
  2. 2. WSO2 Background-  Founded in 2005 by recognized leaders in XML, Web services technologies, standards and open source-  Primary contributors to Apache Web Services projects started in 2001-  Funded by Intel Capital & Quest Software ($11M)-  Technology OEM’d by IBM, Progress, Software AG, Alcatel, EMC, and CA-  Global offices: -  Palo Alto, USA - Portsmouth, UK - Sydney, Australia - Colombo, Sri Lanka-  145+ employees and growing
  3. 3. WSO2 Platforms and PaaSWSO2 Carbon WSO2 Stratos WSO2 StratosLiveEnterprise Middleware Cloud Middleware Platform Java PaaSPlatformOn-premise on physical or Cloud-native (multi-tenant & Public Java PaaS operated byvirtualized environments metered), deployed as private WSO2 or public PaaSFull suite of products – start with Full benefits of cloud – from Instant access to middleware –one, click to add more using VMs to building higher as-a-Service level PaaS or SaaS appsIn production at 100+ F1000 Manage central ops, enable Pay just for what you use;enterprises; 1B txn per day at developers to self-provision flexible billingeBay middleware services Common Code Base •  Complete middleware stack •  OSGi-based componentized platform •  100% open source and standards
  4. 4. WSO2 support engagement model-  QuickStart-  Development Support-  Development Services-  Production Support-  Turnkey Solutions
  5. 5. John Keells Group-  Founded in 1870; A proud history spanning 140 years-  Sri Lanka’s highest market capitalized company - Exceeds USD 1.6 billion-  Group’s 9 listed companies contributes to 15 % of Colombo Stock Exchange market cap-  Group Revenue – Rs.60.5 billion in 2010-11-  10,000+ Employees-  Present in key sectors of Sri Lankan economy (Transportation, Property, Leisure, Consumer Foods & Retail, Information Technology & BPO, Financial Services & Plantation Services)-  A Full Member of the World Economic Forum-  First Sri Lankan company to be listed overseas – GDRs listed on the Luxembourg Stock Exchange with a AAA+ credit rating-  Ranked among the “200 Best under a Billion” in Asia Pacific by Forbes-  LMDs Most Respected Entity in Sri Lanka – Placed first in four out of five years, since inception-  Signatory to the UN Global Compact
  6. 6. BU - KeellsSuper-  Keells Super is one of the leading supermarket chains in the country which has been in operation for the last 20 years-  Keells Super was Instrumental in popularizing Modern trade in Sri Lanka-  Currently at 42 outlets and expanding The  First  and  only  online  supermarket  in  Sri  Lanka  -­‐   First  Retailer  to   implement  a  leading  ERP  in  Sri   Lanka  –  2004/5   Introduced  the  first  Loyalty  program  in  Retail   with  Integrated  CRM  and  BI  in  Sri  Lanka   Real-­‐Jme  stock  taking  using   handheld  scanners  (Recognized  as   a  case  study  by  Motorola)   Introduced  the  first  Retail  Radio  in  Sri  Lanka     (Keells  Super  Radio)    
  7. 7. Business Requirement-  Streamline the SAP and POS integration - Eliminate the performance issues and failures faced with the current SAP and POS integration-  Seamless integration with the online store – .com
  8. 8. Business Requirements Required Integration scenarios Direction Description Arti cl e  masters  -­‐  new  a nd  c hanges Condi ti on  masters  -­‐  pri ce  c hanges Vendor  masters  -­‐  new  a nd  c hanges Customer  master  (credi t  c ustomers) Outbound Bonus  Buy  Condi ti ons  /  Promoti ons (Head  offi ce  -­‐>   Downl oad  phys.  i nv.  docs,  upl oad  phys.  i nv.  c ount  data POS) Credi t  l i mi ts   Stock  bal ances Gi ft  vouchers  master  data Appl i cati on  a cknowl edgements Fi nanci al  transcati ons Inbound Upl oad  day-­‐end  c l osi ng  POS (POS  -­‐  >  Head   Upl oad  s al es  data  (compressed) offi ce) Inventory  c ounts Gi ft  vouchers  -­‐  i ssues
  9. 9. Technical Requirements-  Guaranteed delivery - message queuing and guaranteed delivery semantics -  Unreliable and slow networks (specially in outstations), POS Server outages-  Minimize changes to existing infrastructure – POS-  Quality of service (QOS) requirements -  Exactly Once In Order – E.g. Price changes -  Exactly Once – E.g. Sales data-  Better performance without impacting the ERP system -  Avoid using synchronous BAPIs/RFC and adopt IDOC based integration which is used by almost all SAP ERP Retail customers -  Message throttling-  Prioritization of Messages -  Price changes Vs Article description change-  Light weight, simple and easily maintainable integration middleware
  10. 10. Component Architecture :
  11. 11. Solution Architecture
  12. 12. Message flow and Enterprise Integration Patterns used (2) Transform/Map to IDOC structure - WPUUMS01 has limit on max line items per IDOC therefore will need to be split into multiple IDOCs ç (1) Query Sales line-items by Polling •  Update on message successfully accepted by the ESB - (Update TRANFFERED_TO_ESB =“TRUE”) Message translator Polling Consumer Spilter (XSLT)SAP ç (3) Post IDOC ‘WPUUMS01’ ESB POSReceiver Sender è (4) Technical ack - è (5) Update on Technical ack - UPDATE record : SQL IDOC created successfully /failed •  TRANFFERED_TO_SAP_TEC_ACK=“TRUE” messages if reprocessed in SAP. Content-Based Router Store and Forward è (6) Application ack - (ALEAUD) è (7) Update on Application ack - UPDATE record: (status, message) – Multiple ALEAUD •  ALEAUD message status and update field messages if reprocessed in SAP. TRANSFFERED_SAP _APPLICATION_ACK = “TRUE” and update field TRANSFFERED Content-Based Router Notations from the book Enterprise Integration Patterns - Gregor Hohpe
  13. 13. Deployment architecture - Sizing -  500k transactions on an Direction Message  Type    #  of  IDOCs  on  May  2 011   ALEAUD                                                                    4 ,569   average month ARTMAS                                                              7 5,189   -  1 million on seasonal COND_A                                                          3 25,517   CREMAS                                                                          2 14   months Outbound DEBMAS                                                                              1 9   (Head  offi ce  -­‐>   -  Avg Size of a message - POS) WPDBBY WVINVE                                                                          6 46                                                                      4 ,110   100kb – 5mb ZFI_CRED                                                                          3 01   ZMM_STOCK                                                              1 1,592   ZSDGV                                                                          4 91   WPUFIB                                                                    5 ,058   Inbound WPUTAB                                                                    1 ,339   (POS  -­‐  >  Head   WPUUMS                                                                    8 ,565   offi ce) WVINVE                                                              3 3,866   ZSDGVRE                                                                    4 ,140  
  14. 14. Deployment architecture Production Server Configuration DR Server 1:-CPU:- 4 Cores RAM:- 8 GB Storage :- 50 GB Server 2: CPU:- 2 Cores RAM:- 4 GB Storage :- 140 GB Development Server Configuration CPU:- 4 Cores RAM:- 8 GB Storage :- 105 GB
  15. 15. Project Challenges & Lessons learnt-  What worked in the Lab with sophisticated load test tools can break in the real environment -  When you have multiple components (SAP ERP, POS, 50+ end points over unreliable networks) it’s difficult to simulate a real production environment-  Strike a balance between offshore and onsite model-  Have frequent project / steering committee meeting to ensure EVERYONE is on the same page to avoid surprises
  16. 16. Results-  Scalability-  Lower TCO-  Peace of mind
  17. 17. Summary-  Bus architecture to connect 40+ POS endpoints-  Transform and throttle messages based on SAP specification-  Cater for higher load-  Pull model to minimize the infrastructure changes-  Map EIPs to handle message flows and QoS-  Convert SQL data into SAP iDOCsFuture Project Enhancements ?
  18. 18. More Info§  Corporate website:§  Developer portal:§  Business development team:§  John Keells SAP and WSO2 Professional services §  Website : §  Business development team :
  19. 19. lean . enterprise . middleware19