1 / 58

INT404: Lessons Learned of an High Load Integration Project with SAP R/3

INT404: Lessons Learned of an High Load Integration Project with SAP R/3. Matthias Stemmler Principal Consultant stemmler@sybase.com August 15-19, 2004. INT404: Lessons Learned of an High Load Integration Project with SAP R/3. Matthias Stemmler Principal Consultant stemmler@sybase.com

castor-barron
Download Presentation

INT404: Lessons Learned of an High Load Integration Project with SAP R/3

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. INT404: Lessons Learned of an High Load Integration Project with SAP R/3 Matthias Stemmler Principal Consultant stemmler@sybase.com August 15-19, 2004

  2. INT404: Lessons Learned of an High Load Integration Project with SAP R/3 Matthias Stemmler Principal Consultant stemmler@sybase.com August 15-19, 2004

  3. The Enterprise. Unwired.

  4. The Enterprise. Unwired. Industry and Cross Platform Solutions Manage Information Unwire Information Unwire People • Adaptive Server Enterprise • Adaptive Server Anywhere • Sybase IQ • Dynamic Archive • Dynamic ODS • Replication Server • OpenSwitch • Mirror Activator • PowerDesigner • Connectivity Options • EAServer • Industry Warehouse Studio • Unwired Accelerator • Unwired Orchestrator • Unwired Toolkit • Enterprise Portal • Real Time Data Services • SQL Anywhere Studio • M-Business Anywhere • Pylon Family (Mobile Email) • Mobile Sales • XcelleNet Frontline Solutions • PocketBuilder • PowerBuilder Family • AvantGo Sybase Workspace

  5. AGENDA • Postbank • Project • Dispatcher feeder • Operating concepts • Performance Tests • Product improvements / SAP BAPI Issues • Lessons learned / conclusion

  6. AGENDA • Postbank • Project • Dispatcher feeder • Operating concepts • Performance Tests • Product improvements / SAP BAPI Issues • Lessons learned / conclusion

  7. DEUTSCHE POSTBANK • Germany’s largest retail bank with • Close to 10 million customers with 24 million accounts • Online banking with some 1,300,000 customers (100% growth compared to previous year) • Phone banking with nearly 2,000,000 customer calls/month and more than 74,000 customer transactions daily (> 60% growth compared to previous year) • Market share of 5% in core business payment transactions and deposits • Postbank is established as a universal bank in all areas of the market

  8. POSTBANK – EFFICIENT AT PROCESSING LARGE VOLUMES • Postbank is a subsidiary of Deutsche Post World Net, and an important pillar of this major corporation. Marketing is integrated with the corporation, through nearly 14,000 branch offices and some 20,000 windows. • Companies combining the logistics industry with the financial sector are an ideal combination to meet the demands of e-commerce and e-business. • Maximum demands in the areas • Mass processing • Availability of IT services • Efficiency in the processing of bank-related business processes

  9. BUSINESS CASE • Postbank used KORDOBA as their account management system • Lack of perspectives for KORDOBA • Postbank wants to be market leader with a new solution to • Provide better products to their customers • Provide account management (billing) solutions for other banks

  10. MAIN REASONS FOR THE DECISON IN FAVOROF mySAP BANKING CORE BANKING (AM) • Lack of perspectives for KORDOBA based on BS2000 • Migration of KORDOBA from BS2000 to MVS was not promising • In-house development was not a feasible alternative • High demands for flexibility and security. Decision in favor of a standard system in order to quickly and reliably meet the demands of the present and future banking sector • Clear commitment from SAP to standard applications for the banking sector • Increased efficiency

  11. SAP AND POSTBANK = IDEAL PARTNERS • SAP’s products and services cover a wide range of Postbank’s requirements • SAP has proved to be a reliable vendor of a powerful core banking system • Both partners enter a long-term partnership (collaboration) as a compromise between merely purchasing a turnkey system and complex in-house developments • Postbank is prepared to immediately implement the results of mySAP Banking Core Banking development for production use at Postbank

  12. AGENDA • Postbank • Project • Dispatcher feeder • Operating concepts • Performance test • Product improvements / SAP BAPI Issues • Lessons learned / conclusion

  13. KEY FACTORS - CORE COMPONENTS SAP expertise Postbank expertise Bank-specific functions • Comprehensive experience from earlier SAP BCA implementations • Detailed expertise regarding bank-specific processes and legal requirements • Estimation of priority of functions from a development perspective • Estimation of priority of functions from a bank perspective Prioritization of functions • Critical performance parameters from a technical and functional • perspective • Technical performance of individual system blocks and interfaces Technical performance • Experienced in integrating standard software and establishing a comprehensive system landscape • Experienced in developing a standard application architecture Functional architecture

  14. SCHEDULE Checking impl. SAP development AM checking 1 Customizing AM checking 1 Test AM checking 1 Global integration test Test AM Check-ing 2 Customizing AM checking 2 SAP development AM Checking 2 Data migration Development of programs Dry-run migration Data cleansing/maintenance Test peripheral systems Stress test of dispatcher/ feeder Porting of peripheral systems Development of dispatcher/feeder Enduser training Set up SAP test database 01/2001 01/2002 01/2003 07/2003

  15. Analyst’s opinion:: “SAP’s banking software is well positioned for success” Tower Group Postbank European banking market International banking market ... TO ACHIEVE MARKET SUCCESS

  16. IN THE PRESS ...

  17. NEXT STEPS As one first success of the new system Postbank signed a letter of intent to take over the account management for Deutsche Bank and Dresdner Bank (the biggest and the third biggest German bank). Postbank expects a yearly transaction volume of 5,4 billion transactions. Which will be 17% of all transactions in Germany.

  18. AGENDA • Postbank • Project • Dispatcher feeder • Operating concepts • Performance test • Product improvements / SAP BAPI Issues • Lessons learned / conclusion

  19. TECHNICAL ISSUEINTEGRATION OF BATCH SYSTEMS Kordoba BatchSystem Kordoba Kordoba BatchSystem Kordoba BatchSystem Kordoba BatchSystem Kordoba BatchSystem Kordoba BatchSystem Kordoba BatchSystem Kordoba BatchSystem Kordoba BatchSystem Kordoba BatchSystem Kordoba BatchSystem Kordoba BatchSystem Kordoba BatchSystem ? BatchSystem BatchSystem BatchSystem BatchSystem BatchSystem BatchSystem BatchSystem BatchSystem BatchSystem

  20. THE FOUR ELEMENTS OF COLLABORATION • Performance test / benchmarkTaking into account the strategic partnership with IBM • IBM Integration Strategy base • on Sybase Technology • Development • support • Contract involving the development of standard banking software between Postbank AG and SAP AG • ImplementationImplementation of the contractually defined application in a test environment. Acceptance by strategic partner SAP Consulting and transition to production operations at Postbank • Maintenance • and supportEstablishment of a Customer Competence Center (CCC) with SAP. Definition and implementation of an “on-site support concept” for 7x24 hour bank operations.

  21. SCHEDULE Checking impl. SAP development AM checking 1 Customizing AM checking 1 Test AM checking 1 Global integration test Test AM Check-ing 2 Customizing AM checking 2 SAP development AM Checking 2 Data migration Development of programs Dry-run migration Data cleansing/maintenance Test peripheral systems Stress test of dispatcher/ feeder Porting of peripheral systems Development of dispatcher/feeder Enduser training Set up SAP test database 01/2001 01/2002 01/2003 07/2003

  22. PROJECT: DISPATCHER / FEEDER • Book all batch transactions from the peripheral systems to SAP • Up to 6 million transactions per day • Designed, estimated and implemented by IBM Global Services with suppport of Sybase Professional Services

  23. BatchSystem BatchSystem AIX Cluster AIX Cluster zOS Host BatchSystem BatchSystem BatchSystem BatchSystem BatchSystem BatchSystem BatchSystem MQ RFC BAPI Dispatcher Feeder HIGH LEVEL ARCHITECTURE: DISPATCHER / FEEDER Reformatting SAP Handling Webshere MQ Integrator(as Sybase OEM e-Biz) Net Era of Networks SAP Adapter Batch Processing and Management

  24. Product Set Involved • Integration Platform (Feeder) • AIX 5.1 • DB2 7.2 • MQ Series 5.3 • Websphere MQ Integrator 2.1 CSD3 used ase-Biz Integrator 3.6 • Adapter for SAP 3.9 EBF1 • Visual Age for C++ V5.0 • SAP • SAP R/3 4.6D partially patched to 6.2 • Module AM (Account Management) • Host (Disptacher) • DB2 • C Programms

  25. TASKS DONE BY SPS • Review Architecture • Rectify operating concepts and product customizing • Fulfill technical lead for SAP Adapter • Optimize processing of reformatting

  26. HIGHLIGHTS • No lost transactions through BAPI Errors • No doubled transactions through BAPI Errors • 40% performance acceleration for adapters • 90% CPU usage decrease • Pass SAP audit • Other: 25% performance acceleration for formats

  27. AGENDA • Postbank • Project • Dispatcher feeder • Operating concepts • Performance test • Product improvements / SAP BAPI Issues • Lessons learned / conclusion

  28. imp_all History File imp_all History File Directory: formats Directory: formats Exp.<format>_<datestring>.fmt Exp.<format>_<datestring>.fmt Development Cycle Developer Tester/ Customer Marketplace Integration Marketplace Integration GUIs NNFie, NNRie, EDLUtil NNFie, NNRie, EDLUtil Insert Insert NNFie, NNRie, EDLUtil ftp ftp e-Biz/Process Server Repository Development Production Integration Test

  29. MONITORING CONCEPT (I) • All Error Queues are monitored • Redo of any transaction is possible • ...

  30. MONITORING CONCEPT (II) • Automatic restarts of Adapters (BAPI and ABAP direct) • Tracking weather SAP is online • Emergency stop if SAP works in improper ways • Many stopped transactions • Many transactions with bad return code • Slow transaction processing

  31. PERFORMANCE FORMATS • SAP Adapter generated formats need 2 x 4 CPUs • Optimized Formats need 2 x 3 CPU • Effort : 2 days of work

  32. AUTOMATIC EXCEPTION HANDLING • Automatic Eception Handling • A booking is try up to three times • ...

  33. AGENDA • Postbank • Project • Dispatcher feeder • Operating concepts • Performance test • Product improvements / SAP BAPI Issues • Lessons learned / conclusion

  34. HARDWARE • Testing Environment • 1 x 7017-S80 • 1 x 18 Prozessors RS64III 450 MHz • 1 x16 GB RAM • 1 x 2 Gigabit Ethernet Adapter • EMC Symmetrix 8430 • Production Environment • 2 x 7017-S80 parallel arbeitend (HACMP Mutual Takeover) • 2 x 24 Prozessors 600 MHz • 2 x 16 GB RAM • 2 x 2 Gigabit Ethernet Adapter • 2 x 72GB DASD Platten System

  35. SOFTWARE COMPONENTS Testsystem • AiX Version 4.3 • MQSeries Version 5.2 (OS/390, AiX, NT) • MQSeries Integrator Version 2.0.1 (AiX, NT) • SAP NEONAdapter Version 3.03 Productionssystem • AiX Version 5.1 • MQSeries Version 5.2 (OS/390, AiX, NT) • MQSeries Integrator Version 2.1 (AiX, NT) • SAP NEONAdapter Version 3.9

  36. AIM • Max. # Messages per day 10 Mio • Avervage # Massages per hour 200.000 bis 300.000 • Max. # Messages per hour 2 Mio • Lentgh of Message 4 kByte • Messagetyp persistent • SAP transactions rate 360.000 pro Stunde • Bundeling of transaction up to 1.000 per Message

  37. NEONDisp TESTCONFIGURATION QU.FED.TO_SAM_x01 SAP Adapter x01 QU.FED.TO_SAM_x05 MQPUT 04 MQPUT 03 SAP Adapter x05 MQPUT 02 Execution-Group: REQUEST MQPUT 01 QU.FED.TO_SAM_x10 SAP Adapter x10 Messageflow: MF.RQ Cluster-Queue QU.FED.FROM_ADD QU.FED.TO_SAM_x20 Queue-Local QU.FED.TO_SAM1 ClusterQueue QU.FED.FROM_ADD SAP Adapter x20 Dummy BAPI SAP Giro 1.2 QU.FED.TO_SAM_x40 SAP Adapter x40 AD30 Feeder-B QU.FED.TO_SAM_x50 SAP Adapter x50 Execution-Group: REPLY Messageflow: MF.RP SAP Adapter x1 - 50 ClusterQueue QU.ADD.FROM_FED Queue-Local QU.FED.FROM_SAM Cluster-Queue QU.ADD.FROM_FED zOS 1.1 AIX 4.3

  38. NEONDisp POINTS OF MEASSUREMENTS QU.FED.TO_SAM_x01 SAP Adapter x01 3. QU.FED.TO_SAM_x05 MQPUT 04 MQPUT 03 SAP Adapter x05 MQPUT 02 Execution-Group: REQUEST MQPUT 01 QU.FED.TO_SAM_x10 SAP Adapter x10 Messageflow: MF.RQ 1. 2. Cluster-Queue QU.FED.FROM_ADD QU.FED.TO_SAM_x20 Queue-Local QU.FED.TO_SAM1 ClusterQueue QU.FED.FROM_ADD SAP Adapter x20 Dummy BAPI SAP Giro 1.2 QU.FED.TO_SAM_x40 SAP Adapter x40 AD30 Feeder-B QU.FED.TO_SAM_x50 SAP Adapter x50 Execution-Group: REPLY Messageflow: MF.RP 4. 6. SAP Adapter x1 - 50 ClusterQueue QU.ADD.FROM_FED Queue-Local QU.FED.FROM_SAM 5. Cluster-Queue QU.ADD.FROM_FED zOS 1.1 AIX 4.3

  39. 1: PUT AND CLUSTER CHANNEL zOS 1.1 - UNIX

  40. 1: PUT AND CLUSTER CHANNEL zOS 1.1 - UNIX Parallele Put-Prozesse Paket Grösse GigaBit Ethernet

  41. 2: FORMATTING 1 Execution Group = 1 Prozess

  42. 2: FORMATING

  43. 3: DISPATCHINH ON ADAPTER QUEUES

  44. 4: BOOKING IN SAP (ADAPTER)

  45. 4: BOOKING IN SAP GigaBit Ethernet

  46. 5: REFORMATTING

  47. 5: REFORMATING

  48. 6: TOTAL THOUGHPUT

  49. AGENDA • Postbank • Project • Dispatcher feeder • Operating concepts • Product improvements / SAP BAPI Issues • Lessons learned / conclusion

  50. COMMIT FAILURE TO FAILQ Flag: commitFailureToFailQ IN Adapter SAP OUT ERROR Old: On Error Queue are only message which are surely not booked in SAP New(optional): On Error Queue are booked and not-booked messages New exception handling is needed.

More Related