1. Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

2. Because of increasing complexity of SAP technologies and infrastructures, all SAP enterprises must develop and maintain a technical architecture blueprint. Technical Architecture Blueprint The Technical Architecture Blueprint

3. Conclusions nSAP’s technical architecture has evolved into a comprehensive, Internet-centric offering. nSAP portal products offer leading business benefits to both R/3 and mySAP enterprises. nmySAP enterprises should plan for a more- complex technical architecture and infrastructure. nR/3 enterprises will need to plan for future changes to their technical infrastructure. nMore techniques are emerging for developing and maintaining complex SAP technical architectures.

4. Conclusions nSAP’s technical architecture has evolved into a comprehensive, Internet-centric offering. nSAP portal products offer leading business benefits to both R/3 and mySAP enterprises. nmySAP enterprises should plan for a more- complex technical architecture and infrastructure. nR/3 enterprises will need to plan for future changes to their technical infrastructure. nMore techniques are emerging for developing and maintaining complex SAP technical architectures.

5. 3) Physical SAP Application nApplication Module 1, … nApplication Module n 2) Software Web Application Server Data- base SAP Application WAS 1) Logical Features/Protocols: nGlobal operation nAuthorisations nArchiving nWebFlow, WfXML nRFC, FTP nDCOM, CORBA nHTTP, HTTPS, LDAP nSMTP, ESMTP, MIME nXML, SOAP, WSDL Develop> ABAP + Unicode > JavaScript, WebDAV Tools > Java: J2EE > ECLIPSE Environment > Web Dynpro Run> OS, DB, Hardware choice > Sizing & Performance > CCMS, TMS > 64-bit Kernel > Security Architecture of a SAP Application

6. A New Software Infrastructure Superpower? Proprietary Application Platform Suite — NetWeaver Portal WAS XI BASIS Java, Top Tier J2EE or ABAP (Proprietary) A2A and B2B Integration Suite Business Foundation — NetWeaver Business Warehouse, Knowledge Management, Content Management, Webflow and Business Process Modeling Business Foundation — NetWeaver Business Warehouse, Knowledge Management, Content Management, Webflow and Business Process Modeling Business Collaboration (Smart Enterprise Suite) xApps — Cross-Enterprise Strategic Focus 4 2 1 3 Business Applications Business One, R/3 Enterprise, mySAP Business Suite

7. SAP NetWeaver – The Platform SAP NetWeaver is the application and integration platform to unify and align people, information and business processes across technologies and organizations. DB and OS Abstraction.NET WebSphere … People Integration Composite Application Framework Process Integration Integration Broker Business Process Management Information Integration Business Intelligence Knowledge Management Life Cycle Management PortalCollaboration J2EEABAP Application Platform Multi-Channel Access SAP NetWeaver DB and OS Abstraction Master Data Management

8. SAP Technology: “Moving Terminology” mySAP Technology – Web Services Architecture Exchange Infrastructure Process-centric Collaboration PortalUser-centric Collaboration Infrastructure SAP Web Application Server Web services J2EE & ABAP mySAP CRM SAP R/3 EnterprisemySAP SCM mySAP SRM mySAP PLM Legacy...Third-party...External... Vision 2001 Technology 2002 DB and OS Abstraction.NET WebSphere … People Integration Composite Application Framework Process Integration Integration Broker Business Process Management Information Integration Business Intelligence Knowledge Management Life Cycle Management PortalCollaboration J2EEABAP Application Platform Multi-Channel Access SAP NetWeaver DB and OS Abstraction Master Data Management

9. SAP NetWeaver: Enabling xApps nWeb services architecture nLeverages existing IT investm. nOpen, masters heterogeneity nLower TCO nOne application and integration platform New, snap on cross-functional business process mySAP Business Suite and other applications xApp nSolves integration challenge at bus. level nNew, snap-on business processes nCross-functional processes nContinuous business innovation nxApps from SAP, ISVs, SIs Technology 2002SAP xApp Vision DB and OS Abstraction.NET WebSphere … People Integration Composite Application Framework Process Integration Integration Broker Business Process Management Information Integration Business Intelligence Knowledge Management Life Cycle Management PortalCollaboration J2EEABAP Application Platform Multi-Channel Access SAP NetWeaver DB and OS Abstraction Master Data Management

10. 1. User Integration: U2A nEnterprise Portal n.NET Connector nWAS mySAP Business Applications ABAP, Java CCMS, TMS Workflow 64-bit Kernel Platform Choices ABAP, Java CCMS, TMS Workflow 64-bit Kernel Platform Choices February 2003 WAS 2. Internal Integration: A2A nRFCs, BAPIs nBatch Input, Other nBDocs, IDocs nALE Messaging nR/3 Plug-Ins nInterface Advisor nWeb Projector nExchange Infrastructure (XI) nCSP Software Partners Note: Internet Business Framework => mySAP Technology => NetWeaver 3. External Integration: B2B nXML, SOAP nWSDL Web Services nBusiness Connector nXML Schema Repository nC 1’s xCBL XML nBizTalk, RosettaNet nWebFlow nCollaboration Scenarios nExchange Infrastructure (XI) nTechnology Partners mySAP Business Suite Integration Technologies

11. Integration Broker EXCHANGE LAYER ( XI ) B2B A2A A2A, B2B Collaborative Processes WAS Internet WEB APPS Custom Web WAS PORTAL LAYER U2A BW WAS Integrated mySAP Business Suite Components CRM APO Legacy, Non SAP WAS R/3 Enterprise WAS

12. Conclusions nSAP’s technical architecture has evolved into a comprehensive, Internet-centric offering. nSAP portal products offer leading business benefits to both R/3 and mySAP enterprises. nmySAP enterprises should plan for a more- complex technical architecture and infrastructure. nR/3 enterprises will need to plan for future changes to their technical infrastructure. nMore techniques are emerging for developing and maintaining complex SAP technical architectures.

13. BOSS R/3 How have most Managers used SAP ?

14. SS Enterprise Portal: Manager views What If Managers,... ?

15. Apps Internet Casual Users Legacy, Non SAP SAP Apps SAP Apps BW KM EP 6.0 - Unification Browser User Interface: nSingle Sign-On nSingle Look and Feel nPersonalized nEasy to Use EP 6.0 - Collaboration Drag & Relate: nInteractive Data Transfer nMinimize Re-entry Mini Apps, iViews: nCustomized Displays n300+ Predefined Roles nPredefined Content Yahoo Content, Services Basic Functions: nPersonal Details nSystem Messages nSearch nSAP: Top Customers nSAP: Orders nSAP: AR, Inv Data Enterprise Portal Power

16. LDAP Directory Unstructured Data Structured Data Portal Server Presentation Comp Framework iView Development: nMS ASP, nVisual Studio nJava Tools, JSP nWorkset Groups Unification Unifiers: nHyperrelational Data nMetadata: All Apps nEnable Drag & Relate SAPNon SAP Portal Framework Page Builder Fast Caching User/Role Mgt SSO BWKM ITS SAPGUI for HTML Data- Base SAP Enterprise Portal Architecture

17. Piloting a SAP Enterprise Portal Pilot 1.Determine Most Important User Needs 2.Seek Expert Assistance, Set Budget 3.Install All Infrastructure 4.Build Pilot Prototype 5.Test Pilot Prototype 6.Deploy, Plan Next Phase Pilot Approach:

18. Conclusions nSAP’s technical architecture has evolved into a comprehensive, Internet-centric offering. nSAP portal products offer leading business benefits to both R/3 and mySAP enterprises. nmySAP enterprises should plan for a more- complex technical architecture and infrastructure. nR/3 enterprises will need to plan for future changes to their technical infrastructure. nMore techniques are emerging for developing and maintaining complex SAP technical architectures.

19. ( mySAP.com = SAP’s Internet Strategy = Confusion ) 1. Technology: SAP NetWeaver 2. Business Applications: mySAP Solutions for collaborative business, in addition to 22 Industry Solutions = Supply Chain Management: APO, LES, ILOG, BW Customer Relationship Management: SAP CRM, Internet Sales, BW Supplier Relationship Management: SRM, EBP, BW Product Life Cycle Management: PLM, QM, PS, EHS, BW Financials: R/3 Enterprise, SEM, Real Estate, Leasing Human Capital Management (HCM): R/3 Enterprise, ESS 3. Marketplaces: E-Marketplace Exchanges = SAP/Commerce One: MarketSet 4. Application Hosting: IDES, SAP Hosting, ASPs Seller Buyer March 2003 mySAP Business Suite Summarized New ! mySAP ERP: R/3 Enterprise / Financials / HCM + SAP NetWeaver

20. EBP R/3 BW D/T/PD/PD/T/P Clustered DBS PC Client Intranet Traffic LAN Traffic D/P Portal Layer Portal Server + Load Balancing + Firewalls CS ITS WS ITS WS BC BrowserPortal mySAP Business Suite Infrastructure Example

21. SAP CRM 3.1 Architecture CRM Server n Sales n Service n Marketing n CRM Middle – Ware n Sales n Service n Marketing n CRM Middle – Ware CRM WAS CRM WAS Data- Base Co-browse Call Telephony Server nCTI Server Internet Services nJava Apps nIPC nCatalog (3P) WAS Mobile Client Admin Workstation nMobile Apps Comms Station nGateway nDCOM Mobile Client Admin Workstation nMobile Apps nIPC Channels: Data- Base Mobile Devt Repository Workstation nMobile Apps nDevelopment

22. Conclusions nSAP’s technical architecture has evolved into a comprehensive, Internet-centric offering. nSAP portal products offer leading business benefits to both R/3 and mySAP enterprises. nmySAP enterprises should plan for a more- complex technical architecture and infrastructure. nR/3 enterprises will need to plan for future changes to their technical infrastructure. nMore techniques are emerging for developing and maintaining complex SAP technical architectures.

23. But What About R/3 Customers ?

25. 3.1I 4.0B 4.6C 4.5B R/3 Now December 2003 (4.6C: March 2005) Technology: Availability: End of Support: From R/3 to R/3 Enterprise BASIS 4.6D 2Q02 (Ramp Up) 1Q03 (GA) R/3 Enterprise Stable 4.70 Evolving 1.10,... R/3 Enterprise Core Extensions WAS 6.20 Upgrade: Proven ? Risk ? Cost ?

26. Conclusions nSAP’s technical architecture has evolved into a comprehensive, Internet-centric offering. nSAP portal products offer leading business benefits to both R/3 and mySAP enterprises. nmySAP enterprises should plan for a more- complex technical architecture and infrastructure. nR/3 enterprises will need to plan for future changes to their technical infrastructure. nMore techniques are emerging for developing and maintaining complex SAP technical architectures.

27. We Need an Architecture … ? Architecture Maze ? Internet Apps / DBs / OSs: “Why Have We Got One of Everything?” Company B2B Strategy Due Date: Tomorrow! Recipe: Interface Spaghetti Data- base

28. Packaged application technical architecture (Not application development architecture) Potential Architectural Tasks nBusiness process standards For example, enterprise and collaborative business scenarios nMethodologies Techniques/notations to design and model systems nInterfaces and modularization Define the “fault lines”: “City planning,” “building planning” Interfaces with trading partners, c-commerce e-services nData architecture standards Shared data representation standards and formats nInfrastructure architecture Server landscapes, storage, Web layer

30. Technical Architecture Blueprint Architecture Standards Architecture Standards n Business data n Suite vs. BOB n Interfaces n Flexibility n Business data n Suite vs. BOB n Interfaces n Flexibility Company Standards v 2.0 Company Standards v 2.0 Infrastructure n Server consolidation n Enterprise storage, SANs n SAP Tools: –Landscape planning CIM –MCOD, Solution Manager n Server consolidation n Enterprise storage, SANs n SAP Tools: –Landscape planning CIM –MCOD, Solution Manager Planning Process n Business strategy n Top-down approach n No standard methodology yet n Business strategy n Top-down approach n No standard methodology yet n Functions Software CRM Architecture Maze Building a mySAP Enterprise Architecture

31. Recommendations To build an effective mySAP enterprise architecture: n Enterprises that already have a technical architecture blueprint should extend it to include mySAP applications, interfaces and infrastructure. n Other enterprises should build their own blueprints using a top-down approach and focusing on effects of globalization and their planned adoption of mySAP. n All enterprises should consider the definition of the interfaces between SAP and non-SAP applications in their technical architecture.

32. More Recommendations nEnterprises should evaluate the emerging techniques for consolidating and managing complex mySAP infrastructure landscapes. nEnterprises that need extended access to R/3 or mySAP applications for new casual users should pilot the mySAP Enterprise Portal product using Gartner’s six-step iterative pilot approach. nEnterprises implementing mySAP CRM will need to plan their technical architecture more carefully than with other mySAP applications. nEnterprises planning to upgrade to R/3 Enterprise should budget for a less-disruptive upgrade than usual.

36. Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

37. Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003