1. Multiple Components in One Database (MCOD) Dr. Georg Leffers SAP AG

2.  SAP AG 2002, Title of Presentation, Speaker Name 2 Agenda Introducing Multiple Components in One Database (MCOD)     Simplifying the mySAP.com System Landscape using MCOD Technical Realization for Oracle Screenshots from a sample installation (SAP DB) Availability 

3.  SAP AG 2002, Title of Presentation, Speaker Name 3 Agenda Introducing Multiple Components in One Database (MCOD)     Simplifying the mySAP.com System Landscape using MCOD Technical Realization for Oracle Screenshots from a sample installation (SAP DB) Availability 

4.  SAP AG 2002, Title of Presentation, Speaker Name 4 Multiple Components in One Database Multiple Components in One Database (MCOD) is a new feature in the installation process for mySAP.com components It provides the possibility to install several components independently in one single database SAP CRM SAP R/3 4.6C SAP Workplace RDBMS

5.  SAP AG 2002, Title of Presentation, Speaker Name 5 Technical Realization Each mySAP.com component connects the database with one single database user. This user is independent of the user logged on to the SAP system itself. The default database user is SAPR3. Databases support schema. Tables with the same name can exist independent in different schema with different contents. Using a one to one relation between the database user and the database schema, each mySAP.com component uses its own schema by accessing the database with a unique dedicated database user. SAP CRM SAP R/3 DB-User: SAPCRM DB-User: SAPR3 T100 (SAPR3) T100 (SAPCRM)

6.  SAP AG 2002, Title of Presentation, Speaker Name 6 Agenda Introducing Multiple Components in One Database (MCOD)     Simplifying the mySAP.com System Landscape using MCOD Technical Realization for Oracle Screenshots from a sample installation (SAP DB) Availability 

7.  SAP AG 2002, Title of Presentation, Speaker Name 7 Highly Flexible IT Landscape Today Situation: N Systems, N Databases Benefits Flexibility through components Separate upgrades possible Different operating systems and databases Highest scalability achievable Administrative challenges Maintaining different operating systems, databases Complicated high availability solutions Synchronized backup & restore SAP R/3 SAP CRM SAP WP SAP SCM SAP BW SAP SEM RDBMS

8.  SAP AG 2002, Title of Presentation, Speaker Name 8 Simplification Of The System Landscape With MCOD Situation: N Systems, 1 Database Administrative opportunity Multiple independent and different software solutions are located in one database One logical and physical database instance Business data from different types of software solutions reside in one database Migration of existing systems is possible All systems use the same OS/DB release Installed on one physical server SAP R/3 SAP CRM SAP WP SAP SCM SAP BW SAP SEM RDBMS

9.  SAP AG 2002, Title of Presentation, Speaker Name 9 Independence Of Single Systems  (De)Installation of individual components  Upgrade of individual components  Data exchange on application level Integrity of business data No special coding for MCOD installations No locking conflicts on database tables business data X SAP R/3SAP CRM business data RDBMS

10.  SAP AG 2002, Title of Presentation, Speaker Name 10 Separate OLTP And OLAP Systems Performance considerations For performance / sizing reasons separate OLTP and OLAP systems Possible deployment option Maintain a high level of performance and good response times Installed on one physical server SAP R/3 SAP CRM SAP WP OLTP SAP SCM SAP BW SAP SEM OLAP RDBMS

11.  SAP AG 2002, Title of Presentation, Speaker Name 11 Various Deployment Options  Full range of scalability & flexibility Decide how many different systems will reside in one physical database Additive sizing approach multiple servers, multiple databases one server, one database multiple servers, one databases one server, multiple databases

12.  SAP AG 2002, Title of Presentation, Speaker Name 12 Reduced Maintenance & Operating Costs Benefits detail: Estimated savings 10% of disk space For example, tapes, tape drives, disk systems 30% of hardware backup costs Backup administration or high-availability concepts 40% of operating costs Disk Only need to administer one database Similar effort compared to maintain one component on one database

13.  SAP AG 2002, Title of Presentation, Speaker Name 13 Field Of Application Main target for MCOD installations Development systems Quality assurance systems Training systems Planned goals Small to mid-range production systems Combine systems of the same type  200 GByte  200 GByte  100 GByte Database size  2000  2000  500 SAPS  400  400  100 User Large Installation Mid size Installation Small Installation Dev... Dev Prod... Prod Dev... Dev (Prod... Prod) Dev... Dev Test... Test

14.  SAP AG 2002, Title of Presentation, Speaker Name 14 Agenda Introducing Multiple Components in One Database (MCOD)     Simplifying the mySAP.com System Landscape using MCOD Technical Realization for Oracle Screenshots from a sample installation (SAP DB) Availability 

15.  SAP AG 2002, Title of Presentation, Speaker Name 15 Oracle SAPSYSTEMNAME 1 : C11SAPSYSTEMNAME 2 : C12 / oracle sapdata1sapdata2sapdata3sapdata4sapdata5 sapdata PSAPROLL PSAPC12 sapc12 sapc11 PSAPC1146D PSAPSYSTEM PSAPC11USR PSAPC12USR PSAPC11 PSAPC1246D Oracle - Database PSAPTEMP

16.  SAP AG 2002, Title of Presentation, Speaker Name 16 Implementation on Oracle  Technical Implementation: One database will contain the data of all systems Each SAP system will create its own database schema – database user sap Each SAP system will create its own set of tablespaces

17.  SAP AG 2002, Title of Presentation, Speaker Name 17 Agenda Introducing Multiple Components in One Database (MCOD)     Simplifying the mySAP.com System Landscape using MCOD Technical Realization for Oracle Screenshots from a sample installation (SAP DB) Availability 

18.  SAP AG 2002, Title of Presentation, Speaker Name 18 Technical Setup The following screenshots were taken from a notebook with a demo installation for MCOD Database SAP DB 7.3 Instance name: C11 mySAP.com components SAP Basis System 4.6D SR1 System name: C11 Database user: SAPC11 SAP Basis System 4.6D SR1 System name: C12 Database user: SAPC12

19.  SAP AG 2002, Title of Presentation, Speaker Name 19 SAP DB SAPSYSTEMNAME 1 : C11SAPSYSTEMNAME 2 : C12 / SAPDB sapdata sapc11 sapc12 SAPDB - Database

20.  SAP AG 2002, Title of Presentation, Speaker Name 20 Overview of Database User

21.  SAP AG 2002, Title of Presentation, Speaker Name 21 Table T000 For System C11

22.  SAP AG 2002, Title of Presentation, Speaker Name 22 Table T000 For System C12

23.  SAP AG 2002, Title of Presentation, Speaker Name 23 Database Access By R/3 System C11

24.  SAP AG 2002, Title of Presentation, Speaker Name 24 Database Access By R/3 System C12

25.  SAP AG 2002, Title of Presentation, Speaker Name 25 Agenda Introducing Multiple Components in One Database (MCOD)     Simplifying the mySAP.com System Landscape using MCOD Technical Realization for Oracle Screenshots from a sample installation (SAP DB) Availability 

26.  SAP AG 2002, Title of Presentation, Speaker Name 26 What will be supported In principle, any system based on SAP Web Application Server 6.10 Technology Planned availability Currently controlled availability Available on all OS/DB platforms supported by SAP More information http://service.sap.com/onedb SAP Note 388866 Availability & More Information SAP R/3 Release 4.6C (SP15, SR2) mySAP CRM 2.0C (SP6, SR1) SAP WP 2.11 (SR1) SAP BW 3.0A SAP SEM 3.1A

27.  SAP AG 2002, Title of Presentation, Speaker Name 27 Conclusion Main advantages are Full flexibility and independence of the installed components Simplified administration, backup and recovery Additive sizing approach System spanning data consistency Reduced maintenance and operating costs With “Multiple Components in One Database” SAP offers a powerful option to install several mySAP components in one physical database

28.  SAP AG 2002, Title of Presentation, Speaker Name 28 Questions

29.  SAP AG 2002, Title of Presentation, Speaker Name 29 More Information Visit the mySAP Technology homepage: http://service.sap.com/technology http://service.sap.com/technology

30.  SAP AG 2002, Title of Presentation, Speaker Name 30 No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. ORACLE® is a registered trademark of ORACLE Corporation. INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM are registered trademarks of Informix Software Incorporated. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One. All other product and service names mentioned are the trademarks of their respective owners. Copyright 2002 SAP AG. All Rights Reserved

31.  SAP AG 2002, Title of Presentation, Speaker Name 31 Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Software-Produkte können Software- Komponenten auch anderer Software-Hersteller enthalten. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® und SQL Server® sind eingetragene Marken der Microsoft Corporation. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390® und OS/400® sind eingetragene Marken der IBM Corporation. ORACLE® ist eine eingetragene Marke der ORACLE Corporation. INFORMIX®-OnLine for SAP und Informix® Dynamic ServerTM sind eingetragene Marken der Informix Software Incorporated. UNIX®, X/Open®, OSF/1® und Motif® sind eingetragene Marken der Open Group. Citrix®, das Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc. HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® ist eine eingetragene Marke der Sun Microsystems, Inc. JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com und weitere im Text erwähnte SAP-Produkte und - Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. MarketSet und Enterprise Buyer sind gemeinsame Marken von SAP Markets und Commerce One. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Copyright 2002 SAP AG. Alle Rechte vorbehalten