Show TOC

Background documentationSAP System Directories on UNIX Locate this document in the navigation structure

 

Here you can find information about the directory structure of an SAP Composition Environment (SAP CE) system. An SAP CE system is a Java system and as such a Unicode system.

An SAP CE 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 SAP Directories for a Java System (Unicode)

This graphic is explained in the accompanying text.

SAP CE System Directories in Detail

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.

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

      End of the example.

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

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 Change and Transport System.