Managing Serviceguard Extension for SAP Version B.05.10, September 2010

• There is no intention to install additional APO Application Servers within the cluster.
• There is no hot standby liveCache system configured.
Table 4-2 File System Layout for liveCache Package running separate from APO (Option 1)
Mount PointPackageStorage Type
/sapdb/datalc<LCSID>
shared
/sapdb/<LCSID>/datanlc<LCSID>
shared
/sapdb/<LCSID>/lognlc<LCSID>
shared
/var/spool/sqllc<LCSID>
shared
/sapdb/programslc<LCSID>
shared
In the above layout all relevant files get shared via standard procedures. The setup causes no
administrative overhead for synchronizing local files. SAP default paths are used.
NOTE: The data and log disk spaces of MAXDB are called devspaces. For security and
performance reasons SAP recommends to place the devspaces on raw devices.
Option 2: Non-MAXDB Environments
Cluster Layout Constraints:
• There is no MAXDB or additional liveCache running on cluster nodes. Especially the APO
System RDBMS is either based on , ORACLE or DB2, but not on MAXDB.
• There is no hot standby liveCache system configured.
Often APO does not rely on MAXDB as underlying database technology. But independent from
that, all Instances of the APO System still need access to the liveCache client libraries. The best
way to deal with this is to make the client libraries available throughout the cluster via AUTOFS
cross-mounts from a dedicated NFS package.
Table 4-3 File System Layout for liveCache in a non-MAXDB Environment (Option 2)
Mount PointPackageStorage Type
/sapdb/datalc<LCSID>
shared
/sapdb/<LCSID>lc<LCSID>
shared
/sapdB/<LCSID>/datanlc<LCSID>
shared
/sapdb/<LCSID>/lognlc<LCSID>
shared
/var/spool/sqllc<LCSID>
shared
/sapdb/programssapnfs1
autofs shared
1 This can be any standard, standalone NFS package. The SAP global transport directory should
already be configured in a similar package. This explains why this package is often referred to
as "the trans package" in related literature. A trans package can optionally be extended to also
serve the global liveCache fileshares.
Option 3: Full Flexibility
If multiple MAXDB based components are either planned or already installed, the setup looks
different. All directories that are shared between MAXDB instances must not be part of the
liveCache package. Otherwise a halted liveCache package would prevent that other MAXDB
instances can be started.
112 SAP Supply Chain Management