27.04.2013 Views

SAP Basis

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Unit 1: Fundamentals ADM100<br />

Caution: There are a number of different definitions for the term<br />

“central instance”. You should emphasize the definition above, as<br />

it is realized in almost all <strong>SAP</strong> systems. From the point of view of<br />

downtime security, distributing the essential processes would be<br />

equivalent to increasing the probability of system downtime.<br />

Hint: It is possible to install multiple <strong>SAP</strong> systems in one database.<br />

However, this is not usually the case. UsethekeywordMCOD<br />

(Multiple Components in One Database) to find more information<br />

about this option.<br />

Figure 1: The Elements of an <strong>SAP</strong> System<br />

It is certainly possible to install two instances of a system or even of<br />

different systems on one server. When configuring two systems (or their<br />

databases) on one server, you should ensure that the two systems are<br />

clearly differentiated, otherwise a conflict situation will eventually occur<br />

during the use of common resources (such as program libraries), especially<br />

if one system is to be upgraded while the other is to continue to be used<br />

with the same release.<br />

Within a company, no <strong>SAP</strong> System IDs (SIDs) should be assigned more than<br />

once. You can only perform a meaningful data exchange with two systems<br />

with the same SID only with a great deal of effort (renaming the systems).<br />

4 © 2003 <strong>SAP</strong> AG. All rights reserved. 2003/Q3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!