File systems

Read the recommendations about the location of the involved file systems to achieve a high availability.

For availability reasons, it is recommended that you place the following SAP global directories on z/OS® and share (export) them via the NFS server on z/OS with any non-z/OS hosts on which the SAP application servers run:

/sapmnt/<SAPSID>/exe
/sapmnt/<SAPSID>/profile
/sapmnt/<SAPSID>/global
/sapmnt/<SAPSID>/trans

In SAP 7.10 and subsequent SAP releases, the SAP installation copies the SAP kernel executable routines into a different directory to the one used in previous releases (SAP 7.00 and earlier). The directory name now reflects the platform for which the kernel routines were built. For example, the runtime directory of the SAP 7.10 application server for Linux® on IBM Z is:

/sapmnt/<"SAPSID">/exe/uc/linuxs390x

The mount point on the remote application server kernel routines for SAP 7.10 and higher remains:

/sapmnt/HA1/exe

File systems and directory structure

Figure 1 shows the SAP directory structure and file systems of an SAP NetWeaver PI high availability installation with the ABAP and Java™ stack. SAP high availability means that every instance can run on a separate host. Figure 1 also shows which zFS file systems must be defined to run ASCS/SCS and their ERS under z/OS UNIX and to automate them by SA z/OS. It also depicts which directories are exported by the NFS server to the application servers on AIX® or Linux.

Flow diagram of AP directory structure and file systems — Figure 1. SAP directory structure and file systems