Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

2 Planning a File System Layout for SAP in a
Serviceguard/LX Cluster Environment
The goal of this chapter is to determine the correct storage layout for SAP file systems in a Serviceguard
cluster configuration.
Overview
The following table outlines important concepts that you should understand before using Serviceguard with
SAP. Each step is cumulative, that is each step builds upon itself.
Table 2-1 Understanding the Different SAP Environments and Components
See the following topic for more
information
ConceptStep
About SAP Configuration EnvironmentsUnderstanding the difference between the ABAP and JAVA SAP configuration
environments
1
About SAP ComponentsWhich SAP components are used with either the ABAP or JAVA configuration.
For example, ABAP Central Instance, JAVA Central Instance, and so on.
2
About Impacted File systemsDepending on which SAP configuration environment and components, which file
systems are impacted, for example for ABAP Dialog Instance, the following file
system is impacted - /usr/sap/...
3
Configurations ScenariosDepending on which SAP configuration environment and components, in an
SGeSAP/LX cluster environment, which file systems can be separated into LOCAL,
SHARED NFS or SHARED EXCLUSIVE storage.
4
Putting it all TogetherUnderstanding how can the results of the analysis of step 1-4 be implemented
in a Serviceguard package.
5
The following sections detail each step in greater detail.
About SAP Configuration Environments
The SAP Web AS (Application Server) options offer migration paths between the older ABAP engines and
the newer J2EE JAVA engines.
In general, you can choose to program your SAP applications using the following options:
• ABAP (Advanced Business and Application Programming) is the original programming language for
developing applications for an SAP R/3 system.
• .J2EE (JAVA 2 Enterprise Edition) and other JAVA components are part of the JAVA platform for
developing and running distributed multi-tier architecture JAVA applications. JAVA is used for
implementing web based applications and web based services for SAP R/3.
The following configuration environments are possible:
Table 2-2 SAP Web AS Programming Options
DescriptionSAP Web AS Programming Option
• This system option consists of the ABAP only components. There is no
J2EE JAVA Engine.
• The ABAP engine requires its own database schema. Therefore a database
instance installation is mandatory.
SAP Web AS Programming Option
• ABAP components and J2EE JAVA engine components are both installed
and can be operated in parallel. This is also called SAP Web AS - J2EE
Add-in.
• The J2EE JAVA engine requires its own database scheme. The ABAP and
J2EE though can both be installed in the same database. This is a
combination of the SAP ABAP and the SAP Web AS JAVA variant.
SAP ABAP+JAVA
Overview 29