Download Multiple Components in One Database (MCOD)

Multiple
Components
in One Database
(MCOD)
Dr. Georg Leffers
SAP AG
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
 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
 SAP AG 2002, Title of Presentation, Speaker Name 3
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 AG 2002, Title of Presentation, Speaker Name 4
SAP R/3 4.6C
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)
DB-User: SAPCRM
 SAP AG 2002, Title of Presentation, Speaker Name 5
T100 (SAPCRM)
DB-User: SAPR3
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
 SAP AG 2002, Title of Presentation, Speaker Name 6
Highly Flexible IT Landscape Today
Situation: N Systems, N Databases
Benefits
 Flexibility through components
 Separate upgrades possible
 Different operating systems
and databases
SAP R/3
RDBMS
SAP CRM
SAP SCM
RDBMS
SAP BW
 Highest scalability achievable
Administrative challenges
 Maintaining different operating
systems, databases
 Complicated high availability
solutions
 Synchronized backup & restore
 SAP AG 2002, Title of Presentation, Speaker Name 7
RDBMS
SAP WP
RDBMS
RDBMS
SAP SEM
RDBMS
Simplification Of The System Landscape With MCOD
Situation: N Systems, 1 Database
Administrative opportunity
SAP R/3
SAP SCM
SAP CRM
SAP BW
 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
RDBMS
 Migration of existing systems is
possible
 All systems use the same OS/DB
release
Installed on one physical server
 SAP AG 2002, Title of Presentation, Speaker Name 8
SAP WP
SAP SEM
Independence Of Single Systems
(De)Installation of individual
components
business data
Upgrade of individual components
Data exchange on application level
SAP R/3
SAP CRM
 Integrity of business data
 No special coding for MCOD
installations
 No locking conflicts on database tables
RDBMS
X
business data
 SAP AG 2002, Title of Presentation, Speaker Name 9
Separate OLTP And OLAP Systems
Performance considerations
 For performance / sizing reasons
separate OLTP and OLAP systems
OLTP
OLAP
SAP R/3
SAP SCM
SAP CRM
SAP BW
SAP WP
SAP SEM
Possible deployment option
 Maintain a high level of
performance and good response
times
Installed on one physical server
RDBMS
 SAP AG 2002, Title of Presentation, Speaker Name 10
RDBMS
Various Deployment Options
multiple servers,
one databases
multiple servers,
multiple databases
one server,
multiple databases
one server,
one database
Full range of scalability & flexibility
 Decide how many different systems will reside in one physical database
 Additive sizing approach
 SAP AG 2002, Title of Presentation, Speaker Name 11
Reduced Maintenance & Operating Costs
Benefits detail: Estimated savings
Disk
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
Only need to administer one database
 Similar effort compared to maintain one component on one database
 SAP AG 2002, Title of Presentation, Speaker Name 12
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
Dev ... Dev
Dev ... Dev
Dev ... Dev
Test ... Test
Test ... Test
Test ... Test
Prod ... Prod
(Prod ... Prod)
Combine
systems of the
same type
 SAP AG 2002, Title of Presentation, Speaker Name 13
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
 SAP AG 2002, Title of Presentation, Speaker Name 14
Oracle
/
SAPSYSTEMNAME 1 : C11
SAPSYSTEMNAME 2 : C12
oracle
PSAPC1246D
PSAPSYSTEM
sapdata<n>
sapdata5
PSAPTEMP
PSAPC1146D
PSAPC12
PSAPC11USR
Oracle - Database
<DB_SID>
 SAP AG 2002, Title of Presentation, Speaker Name 15
sapc12
PSAPC12USR
PSAPROLL
PSAPC11
sapdata4
sapdata3
sapdata2
sapc11
sapdata1
<DB_SID>
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
 SAP AG 2002, Title of Presentation, Speaker Name 16
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
 SAP AG 2002, Title of Presentation, Speaker Name 17
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
 SAP AG 2002, Title of Presentation, Speaker Name 18
SAP DB
/
SAPSYSTEMNAME 1 : C11
SAPSYSTEMNAME 2 : C12
SAPDB
sapdata
<DB_SID>
sapc11
sapc12
SAPDB - Database
<DB_SID>
 SAP AG 2002, Title of Presentation, Speaker Name 19
Overview of Database User
 SAP AG 2002, Title of Presentation, Speaker Name 20
Table T000 For System C11
 SAP AG 2002, Title of Presentation, Speaker Name 21
Table T000 For System C12
 SAP AG 2002, Title of Presentation, Speaker Name 22
Database Access By R/3 System C11
 SAP AG 2002, Title of Presentation, Speaker Name 23
Database Access By R/3 System C12
 SAP AG 2002, Title of Presentation, Speaker Name 24
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
 SAP AG 2002, Title of Presentation, Speaker Name 25
Availability & More Information
What will be supported
 In principle, any system based on SAP Web Application Server 6.10
Technology
 Planned availability
SAP R/3 Release
mySAP CRM 2.0C
SAP WP
4.6C (SP15, SR2)
(SP6, SR1)
2.11 (SR1)
SAP BW
SAP SEM
3.0A
3.1A
 Currently controlled availability
 Available on all OS/DB platforms supported by SAP
More information
 http://service.sap.com/onedb
 SAP Note 388866
 SAP AG 2002, Title of Presentation, Speaker Name 26
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
 SAP AG 2002, Title of Presentation, Speaker Name 27
Questions
 SAP AG 2002, Title of Presentation, Speaker Name 28
More Information
Visit the mySAP Technology homepage:
http://service.sap.com/technology
 SAP AG 2002, Title of Presentation, Speaker Name 29