SAP System Directories on UNIX

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

An SAP system contains the following types of directories:

        1.   Physically shared directories, which reside on the global host and are shared by Network File System (NFS)
        2.   Logically shared directories, which reside on the local host with symbolic links to the global host
        3.    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 (Unicode or Non-Unicode)

An ABAP system can be Unicode or non-Unicode.

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

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

  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

An 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:

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

  Standard SAP Directories for a Dual-Stack (ABAP+Java) System (ABAP Unicode) based on SAP NetWeaver 7.0
• 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 (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:

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

Standard SAP Directories for a 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:
  

  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
  

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

SAP System Directories in Detail

System Directories of an SAP System based on SAP NetWeaver 7.0

1) Directory:   /<sapmnt>/<SAPSID>

    Description:  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:

                           a) 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:

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

           b) 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.

           c) 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.

2) Directory: /usr/sap/<SAPSID>

   Description: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.

     a)For ABAP

        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.

     b)For ABAP+JAVA

          The instance name (instance ID) of the 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 an 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.

     c)For JAVA

            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.

          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.

3) Directory: /usr/sap/trans

     Description: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

1) Directory:   /<sapmnt>/<SAPSID>

   Description: 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:

         a) 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: 

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

         

             b) 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.

             c) profilr

                       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.

2) Directory: /usr/sap/<SAPSID>

   Description:  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.

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

                     Primary application server instance: DVEBMGS<Instance_Number>.

                     Additional application server instance: D<Instance_Number>.

                     Central services instance for ABAP (ASCS):ASCS<Instance_Number>.

                     Enqueue replication server instance (ERS): ERS<Instance_Number>.The enqueue replication server instance is only mandatory in a high-availability system.

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

                     Primary application server instance: DVEBMGS00

            Additional application server instance: D01.

                     Central services instance for ABAP (ASCS): ASCS02.

            Enqueue replication server instance (ERS): ERS03

             

              b)For ABAP+JAVA: The instance names (instance IDs) of an ABAP+Java (dual-stack) system are as follows:

                    Primary application server instance: DVEBMGS<Instance_Number>.

                    Additional application server instance: D<Instance_Number>.

                    Central services instance for ABAP (ASCS):ASCS<Instance_Number>.

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

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

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

                 Example: For an SAP ABAP+Java system 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).

                    Central services instance for ABAP (ASCS): ASCS02.

                    Enqueue replication server instance (ERS) for the ASCS: 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.

           d)For JAVA: 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.

3) Directory: /usr/sap/trans

     Description: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.