1 / 29

Multiple Components in One Database (MCOD)

Explore the technical realization and benefits of MCOD, a feature allowing multiple mySAP.com components to run on a single database user. Simplify system management, reduce costs, and enhance performance.

carmenmiller
Download Presentation

Multiple Components in One Database (MCOD)

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. Multiple Componentsin One Database(MCOD) Dr. Georg Leffers SAP AG

  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. 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. 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 Workplace RDBMS SAP R/3 4.6C SAP R/3 4.6C

  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 R/3 SAP CRM T100 (SAPR3) T100 (SAPCRM) DB-User: SAPR3 DB-User: SAPCRM

  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 R/3 SAP SCM RDBMS RDBMS RDBMS RDBMS RDBMS RDBMS SAP CRM SAP BW SAP WP SAP SEM 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

  8. SAP R/3 SAP SCM SAP CRM SAP BW RDBMS SAP WP SAP SEM Installed on one physical server 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

  9. business data SAP R/3 SAP CRM RDBMS X business data 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

  10. OLTP OLAP SAP R/3 SAP SCM SAP CRM SAP BW SAP WP SAP SEM Installed on one physical server RDBMS RDBMS 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

  11. multiple servers, one databases multiple servers, multiple databases one server, one database one server, multiple databases Various Deployment Options • Full range of scalability & flexibility • Decide how many different systems will reside in one physical database • Additive sizing approach

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

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

  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. PSAPC1246D PSAPSYSTEM PSAPC12USR PSAPC11 PSAPC1146D PSAPC11USR Oracle / SAPSYSTEMNAME1 : C11 SAPSYSTEMNAME 2 : C12 oracle <DB_SID> sapdata<n> sapdata1 sapdata2 sapdata3 sapdata4 sapdata5 sapc12 sapc11 PSAPROLL PSAPC12 PSAPTEMP Oracle - Database <DB_SID>

  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<sapsystemname> • Each SAP system will create its own set of tablespaces

  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. Technical Setup The following screenshots were taken from a notebook with a demo installation for MCOD Database • SAP DB 7.3Instance name: C11 mySAP.com components • SAP Basis System 4.6D SR1System name: C11Database user: SAPC11 • SAP Basis System 4.6D SR1System name: C12Database user: SAPC12

  19. SAP DB / SAPSYSTEMNAME 1 : C11 SAPSYSTEMNAME 2 : C12 SAPDB <DB_SID> sapdata sapc11 sapc12 SAPDB - Database <DB_SID>

  20. Overview of Database User

  21. Table T000 For System C11

  22. Table T000 For System C12

  23. Database Access By R/3 System C11

  24. Database Access By R/3 System C12

  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 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 Availability & More Information 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

  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. Questions

  29. More Information Visit the mySAP Technology homepage:http://service.sap.com/technology

More Related