After a standard installation, you can do the following:
Advantages |
Disadvantages |
You need to provide storage for executables only once, on a central system in your network. If the executables are changed, all the instances are automatically provided with the correct executables are a restart. |
Startup of instances is slow because executables have to be loaded across the network rather than from local disk storage. Central storage can result in workload problems that lower performance. If the hosts of distributed R/3 instances run out of memory, then they must page active executables over the network. This can result in heavy workloads on the network and on the central system where the executables are stored. |
See also:
Structure of the Executables after the Standard InstallationWith this procedure, you can specify for each instance, if it takes part in the automatic executable adjustment, or if it works with its local executables.
See also: Functionality of Automatic Adjustment
SAP recommends storing executables locally if the host systems in your network have adequate disk storage. To store SAP executables locally, a host system must have several hundred MB of free disk storage (depending on the SAP Release).
Not all of your R/3 instances must use local executables. You can create a "mixed" configuration in which the executables are stored locally only on certain host systems. The host systems with less memory space then access the central executables.
If the prerequisites for the automatic executable adjustment are only partially met, or not at all, the executables are not automatically kept at the same release level on the various instances. If you upgrade your system, or import Hot Packages, you risk forgetting to update your executables on the individual dialog instances.