Show TOC

SAP System Directories on UNIXLocate this document in the navigation structure

Here you can find information about the directory structure of an SAP system.

SAP System Directory Types

An SAP system contains the following types of directories:

  • Physically shared directories, which reside on the global host and are shared by Network File System (NFS)

  • Logically shared directories, which reside on the local host with symbolic links to the global host

  • Local directories, which reside on the local host

The figures below assume that you have set up one file system for the SAP system mount directory /<sapmnt> and one file system for the /usr/sap directory.

Standard System Directories for an SAP ABAP System

An ABAP system can be Unicode or non-Unicode.

  • SAP ABAP System (Unicode or Non-Unicode) based on SAP NetWeaver 7.0:

    For a detailed description of the directory structure, refer to section SAP System Directories in Detail underneath
    Figure 1: SAP ABAP System (Unicode or Non-Unicode) based on SAP NetWeaver 7.0
    . For more information, see section SAP System Directories in Detail

  • SAP ABAP System (Unicode or Non-Unicode) based on SAP NetWeaver 7.1 and higher:

    Note

    SAP ABAP systems based on SAP NetWeaver 7.5 and higher are only Unicode.

    For a detailed description of the directory structure, refer to section SAP System Directories in Detail underneath
    Figure 2: SAP ABAP System (Unicode or Non-Unicode) based on SAP NetWeaver 7.1 and higher
Standard System Directories for an SAP Dual-Stack (ABAP+Java) System

A dual-stack system can be Unicode or non-Unicode. That is, the ABAP system can be Unicode or non-Unicode, whereas the Java system can only be Unicode.

Standard SAP Directories for a Dual-Stack (ABAP+Java) System based on SAP NetWeaver 7.0:

  • SAP Directories for a Dual-Stack (ABAP+Java) System (ABAP Unicode) based on SAP NetWeaver 7.0:

    For a detailed description of the directory structure, refer to section SAP System Directories in Detail underneath
    Figure 3: Standard SAP Directories for a Dual-Stack (ABAP+Java) System (ABAP Unicode) based on SAP NetWeaver 7.0

  • SAP Directories for a Dual-Stack (ABAP+Java) System (ABAP non-Unicode) based on SAP NetWeaver 7.0:

    For a detailed description of the directory structure, refer to section SAP System Directories in Detail underneath
    Figure 4: Standard SAP Directories for a Dual-Stack (ABAP+Java) System (ABAP non-Unicode) based on SAP NetWeaver 7.0

Standard SAP Directories for a Dual-Stack (ABAP+Java) System based on SAP NetWeaver 7.1 to SAP NetWeaver 7.4:

Note

In SAP systems based on SAP NetWeaver 7.5 or higher, dual stack (ABAP+Java) is no longer supported.

For a detailed description of the directory structure, refer to section SAP System Directories in Detail underneath
Figure 5: Standard SAP Directories for a Dual-Stack (ABAP+Java) System based on SAP NetWeaver 7.1 to SAP NetWeaver 7.4
Standard System Directories for an SAP Java System (Unicode)

A Java system can only be a Unicode system.

  • Standard SAP Directories for a Java System (Unicode) based on SAP NetWeaver 7.0:

    For a detailed description of the directory structure, refer to section SAP System Directories in Detail underneath
    Figure 6: Standard SAP Directories for a Java System (Unicode) based on SAP NetWeaver 7.0

  • Standard SAP Directories for a Java System (Unicode) based on SAP NetWeaver 7.1 and higher

    For a detailed description of the directory structure, refer to section SAP System Directories in Detail underneath
    Figure 7: Standard SAP Directories for a Java System (Unicode) based on SAP NetWeaver 7.1 and higher
SAP System Directories in Detail

  • System Directories of an SAP System based on SAP NetWeaver 7.0:

    Directory Description
    /<sapmnt>/<SAPSID>

    Software and data for one SAP system

    This directory and its subdirectories need to be physically shared using Network File System (NFS) and mounted for all hosts belonging to the same SAP system. It contains the following subdirectories:

    1. exe

      This directory contains executable kernel programs. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system.

      Note dual-stack (ABAP (Non-Unicode) + Java) system only: exe contains a folder uc with a platform-specific subfolder: <sapmnt>/<SAPSID>/exe/uc/<platform>.
    2. global

      This directory contains log files. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system.

    3. profile

      This directory contains the start and operations profiles of all instances. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system.

    /usr/sap/<SAPSID>

    Instance-specific data, symbolic links to the data for one system

    This directory contains files for the operation of a local instance.

    Whenever a local instance is started, the sapcpe program checks the executables against those in the logically shared directories and, if necessary, replicates them to the local instance.

    • There is a subdirectory for each instance. Each instance directory has the name of the related instance.
      • The instance name (instance ID) of the ABAP central instance is DVEBMGS<Instance_Number>, and the instance name of an ABAP dialog instance is D<Instance_Number>. In a high-availability system, there is also an ABAP Central Services instance called ASCS<Instance_Number>.
        Example The file system structure might look as follows: On a central instance with SAP system ID C11 and instance name DVEBMGS00, the ABAP dialog instance has the instance name D01.
      • The instance name (instance ID) of the dual-stack (ABAP+Java) central instance is DVEBMGS<Instance_Number>, the instance name of the Java central services instance is SCS<Instance_Number>, and the instance name of a dual-stack (ABAP+Java) dialog instance is D<Instance_Number>. In a high-availability system, there is also an ABAP Central Services instance called ASCS<Instance_Number>
        Example The file system structure might look as follows:

        On a central instance with SAP system ID C11 and instance name DVEBMGS00, the J2EE Engine is installed in /usr/sap/C11/DVEBMGS00/j2ee, and the corresponding Software Delivery Manager (SDM) is installed in /usr/sap/C11/JC00/SDM

        On a dialog instance with instance name D01, the J2EE Engine is installed in /usr/sap/C11/D01/j2ee. No SDM is installed.

      • The instance name (instance ID) of the Java central instance is JC<Instance_Number>, the instance name of a Java dialog instance is J<Instance_Number>, and the instance name of the Java central services instance is SCS<Instance_Number>. The instance name (instance ID) of the central instance is JC<Instance_Number>, the instance name of a Java dialog instance is J<Instance_Number>, and the instance name of the Java central services instance is SCS<Instance_Number>.
        Example

        The file system structure might look as follows:

        On a central instance with SAP system ID C11 and instance name JC00, the J2EE Engine is installed in /usr/sap/C11/JC00/j2ee, and the corresponding SDM is installed in /usr/sap/C11/JC00/SDM.

        On a dialog instance with instance name J01, the J2EE Engine is installed in /usr/sap/C11/J01/j2ee. No SDM is installed.

    • The directory /usr/sap/<SAPSID>/SYS contains soft links to appropriate directories in /<sapmnt>/<SAPSID>/ for storing data used by several instances. SYS is logically shared and available on each host of the SAP system. Its subdirectories contain symbolic links to the corresponding subdirectories of /<sapmnt>/<SAPSID> on the SAP global host, as shown in the figures above.

    For more information about sapcpe, see The sapcpe Program documentation. Executables located in /usr/sap/<SAPSID>/SYS/exe/run are replicated by sapcpe to the exe subdirectory of the instance directories.

    /usr/sap/trans

    Global transport directory for all SAP systems

    The global transport directory is used by the Change and Transport System (CTS). The CTS helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP systems in your system landscape. For more information, see the Change and Transport System documentation.

  • System Directories of an SAP System based on SAP NetWeaver 7.1 and higher:

    Directory Description
    /<sapmnt>/<SAPSID>

    Software and data for one SAP system

    This directory and its subdirectories need to be physically shared using Network File System (NFS) and mounted for all hosts belonging to the same SAP system. It contains the following subdirectories:

    • exe

      This directory contains executable kernel programs. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system.

      Note

      Dual-stack (ABAP+Java) system only (based on SAP NetWeaver 7.1 to SAP NetWeaver 7.4): exe contains a folder uc and a folder nuc, each with a platform-specific sub folder: /<sapmnt>/<SAPSID>/exe/uc/<platform> is used in Unicode systems. Executable kernel programs are replicated from this directory to the exe directories of each Unicode system instance. /<sapmnt>/<SAPSID>/exe/nuc/<platform> is used in non-Unicode systems (see below). Executable kernel programs are replicated from this directory to the exe directories of each non-Unicode system instance (see below).

    • global

      This directory contains log files. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system.

    • profile

      This directory contains the start and operations profiles of all instances. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system.

    /usr/sap/<SAPSID>

    Instance-specific data, symbolic links to the data for one system

    This directory contains files for the operation of a local instance.

    • There is a subdirectory for each instance. Each instance directory has the name of the related instance:

      • The instance names (instance IDs) of an ABAP system are as follows:

        • Primary application server instance: DVEBMGS<Instance_Number>

          Note

          As of SAP NetWeaver 7.5 the instance name is always D<Instance_Number> for all application server instances. This means that in SAP systems based on SAP NetWeaver 7.5 and higher the instance name for the primary application server instance is D<Instance_Number> like the instance name of the additional application server instances.

        • Additional application server instance: D<Instance_Number>

        • ABAP Central Services instance (ASCS instance): ASCS<Instance_Number>

        • Enqueue replication server instance (ERS instance): ERS<Instance_Number>

        • The enqueue replication server instance is only mandatory in a high-availability system.

        Example

        For an SAP ABAP system based on SAP NetWeaver 7.1 to SAP NetWeaver 7.4 with SAP system ID C11, the instances might look as follows:

        • Primary application server instance: DVEBMGS00

        • Additional application server instance: D01

        • ABAP Central Services instance (ASCS instance): ASCS02

        • Enqueue replication server instance (ERS instance): ERS03

        Example

        For an SAP ABAP system based onSAP NetWeaver 7.5 or higher with SAP system ID C11, the instances might look as follows:

        • Primary application server instance: D00

        • Additional application server instance: D01

        • ABAP Central Services instance (ASCS instance): ASCS02

        • Enqueue replication server instance (ERS instance): ERS03

      • The instance names (instance IDs) of a dual stack (ABAP+Java) system based on SAP NetWeaver 7.1 to SAP NetWeaver 7.4 are as follows:

        Note

        In SAP systems based on to SAP NetWeaver 7.5 or higher, dual stack (ABAP+Java) is no longer supported.

        • Primary application server instance: DVEBMGS<Instance_Number>

        • Additional application server instance: D<Instance_Number>

        • ABAP Central Services instance (ASCS instance): ASCS<Instance_Number>

        • Central Services instance (SCS instance): SCS<Instance_Number>

        • Enqueue replication server instances (one for the ASCS and one for the SCS instance): ERS<Instance_Number>

          The enqueue replication server instances are only mandatory in a high-availability system.

        Example

        For an SAP ABAP+Java system based on SAP NetWeaver 7.1 to SAP NetWeaver 7.4 with SAP system ID C11, the instances might look as follows:

        • Primary application server instance: DVEBMGS00 (the Java EE Engine is installed in /usr/sap/C11/DVEBMGS00/j2ee)

        • Additional application server instance: D01 (the Java EE Engine is installed in /usr/sap/C11/D01/j2ee)

        • ABAP Central Services instance (ASCS instance): ASCS02

        • Enqueue replication server instance (ERS instance) for the ASCS instance: ERS03

        • Central services instance for Java (SCS): SCS04

        • Enqueue replication server instance (ERS) for the SCS: ERS05

        • On a primary application server instance with SAP system ID C11 and instance name DVEBMGS00, the Java EE Engine is installed in /usr/sap/C11/DVEBMGS00/j2ee.

      • The instance names (instance IDs) of a Java system are as follows:

        • Application server instance: J<Instance_Number>

        • Central services instance for Java (SCS): SCS<Instance_Number>

        • Enqueue replication server instance: ERS<Instance_Number>

        • The enqueue replication server instance is only mandatory in a high-availability system.

        Example

        For an SAP Java system with SAP system ID C11, the instances might look as follows:

        • (Primary) application server instance: J00 (the Java EE Engine is installed in /usr/sap/C11/J00/j2ee)

        • (Additional) application server instance: J01 (the Java EE Engine is installed in /usr/sap/C11/J01/j2ee)

        • Central services instance for Java (SCS): SCS02

        • Enqueue replication server instance (ERS) for the SCS: ERS03.

    • The directory /usr/sap/<SAPSID>/SYS contains soft links to appropriate directories in /<sapmnt>/<SAPSID>/ for storing data used by several instances.

      SYS is logically shared and available on each host of the SAP system. Its subdirectories contain symbolic links to the corresponding subdirectories of /<sapmnt>/<SAPSID> on the SAP global host, as shown in the figures above.

    Whenever a local instance is started, the sapcpe program checks the executables against those in the logically shared directories and, if necessary, replicates them to the local instance. For more information about sapcpe, see The sapcpe Program documentation. Executables located in /usr/sap/<SAPSID>/SYS/exe/run are replicated by sapcpe to the exe subdirectory of the instance directories.

    /usr/sap/trans

    Global transport directory for all SAP systems

    The global transport directory is used by the Change and Transport System (CTS). The CTS helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP systems in your system landscape. For more information, see the Change and Transport System documentation.