SAP System Directories on UNIX

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.

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

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: D<Instance_Number>

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

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

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

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.

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.

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

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>

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

  • The instance names (instance IDs) of a dual stack (ABAP+Java) system are as follows:

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

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

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

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.

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.

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.

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

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.