Skip to main content

Unraveling the Secrets of SAP Directories and Parameters in Default.PFL

This list will be updated on demand and need basis , Drop a comment and it will be added.


Directories:

  1. DIR_HOME: Directory for the home folder of the SAP system.
  2. DIR_EXECUTABLE: Directory for SAP executable programs.
  3. DIR_TRANS: Directory for the transport files.
  4. DIR_GLOBAL: Directory for global data files.
  5. DIR_PROFILE: Directory for the SAP profiles.
  6. DIR_INSTANCE: Directory for instance-specific files.
  7. DIR_PAG: Directory for page files.
  8. DIR_GTP: Directory for global temporary page files.
  9. DIR_REORG: Directory for reorganization files.
  10. DIR_DUMP: Directory for system dump files.
  11. DIR_WORK: Directory for work files.
  12. DIR_DATA: Directory for data files.
  13. DIR_LOG: Directory for log files.

Parameters:

  1. INSTANCE_NAME:

    • Description: Name of the SAP instance.
    • Trade-off: Changing the instance name can impact system identification and require updates to related system configurations.

  2. SAPSYSTEMNAME:

    • Description: Name of the SAP system.
    • Trade-off: Modifying the SAP system name can affect system identification and require adjustments to related configurations.

  3. SAPGLOBALHOST:

    • Description: Hostname of the SAP system.
    • Trade-off: Changing the SAP global host can impact system connectivity and require updates to related network and system configurations.

  4. DIR_CT_RUN:

    • Description: Directory for control and work files.
    • Trade-off: Modifying this directory affects the location of control and work files and may require updates to related system configurations.

  5. DIR_EPS_ROOT:

    • Description: Directory for EPS (External Program Storage) files.
    • Trade-off: Changing this directory impacts the storage location of EPS files and may require adjustments to related system settings.

  6. DIR_HOME_PROG:

    • Description: Directory for home executables.
    • Trade-off: Modifying this directory affects the location of home executables and may require updates to related system configurations.

  7. DIR_HOME_LOG:

    • Description: Directory for home log files.
    • Trade-off: Changing this directory impacts the storage location of home log files and may require adjustments to related system settings.

  8. rdisp/mshost:

    • Description: Message server host.
    • Trade-off: Modifying the message server host affects the communication between application servers and clients, and requires updates to related network and system configurations.

  9. rdisp/msserv:

    • Description: Message server service.
    • Trade-off: Changing the message server service can impact the communication between application servers and clients and requires updates to related configurations.

  10. rdisp/wp_no_dia:

    • Description: Number of dialog work processes.
    • Trade-off: Increasing this parameter allows for more simultaneous dialog processes, improving system responsiveness. However, it consumes more system resources, so careful monitoring is necessary to ensure optimal performance.

  11. rdisp/wp_no_btc:

    • Description: Number of background work processes.
    • Trade-off: Increasing this parameter enables more simultaneous background processes, facilitating efficient execution of background jobs. However, excessive background processes can result in resource contention and affect system performance.

  12. rdisp/wp_no_enq:

    • Description: Number of enqueue work processes.
    • Trade-off: Increasing this parameter enhances lock management and improves system concurrency. However, it consumes additional resources, so it should be adjusted based on system requirements and workload.

  13. abap/heap_area_total:

    • Description: Total heap memory available for ABAP.
    • Trade-off: Increasing this parameter expands the overall heap memory available for ABAP programs, allowing for larger memory allocations. This can benefit memory-intensive processes but may require additional system resources.

  14. abap/heap_area_dia:

    • Description: Heap memory available for ABAP dialog processes.
    • Trade-off: Increasing this parameter allocates more heap memory specifically for dialog processes, facilitating better performance for interactive tasks. However, excessive allocation can lead to higher memory consumption.

  15. abap/heap_area_nondia:

    • Description: Heap memory available for ABAP non-dialog processes.
    • Trade-off: Increasing this parameter reserves more heap memory for non-dialog processes, such as background jobs, optimizing performance for non-interactive tasks. However, it may impact memory utilization.

  16. icm/host_name_full:

    • Description: Full hostname of the SAP system for ICM (Internet Communication Manager).
    • Trade-off: Modifying this parameter affects the hostname used by the ICM for communication. It is essential to ensure the correct hostname is specified to establish proper connectivity with external systems.
  17. icm/server_port_<n>: Description: Specifies the port number for a particular ICM server. The parameter <n> represents the server instance number. Each ICM server instance requires a unique port number for communication. Trade-off: Choosing the appropriate port number for the ICM server involves balancing security and accessibility. Lower port numbers (e.g., well-known ports) may be more susceptible to unauthorized access or attacks. Higher port numbers provide more security but can be challenging to manage in complex network configurations.
  18. rdisp/max_alt_modes: Description: Defines the maximum number of alternative modes for a work process. Alternative modes are used to execute non-dialog tasks during peak load times. Each alternative mode represents an additional processing mode for the work process. Trade-off: Increasing the maximum number of alternative modes allows for better load distribution and can help handle higher workloads during peak periods. However, it also consumes additional system resources, such as memory and CPU, which may impact overall system performance.
  19. abap/buffersize: Description: Specifies the buffer size for ABAP programs. A larger buffer size can improve performance by reducing disk I/O operations. It determines the amount of data read from or written to disk in a single operation. Trade-off: Increasing the buffer size can enhance performance by reducing the frequency of disk I/O, which can be a significant bottleneck. However, it also increases the memory consumption of the SAP system, potentially affecting other processes and resource utilization.
  20. icm/keep_alive_timeout: Description: Determines the duration of an idle connection before it is closed by the ICM. This parameter helps manage resource utilization and connection availability. Idle connections consume system resources and can limit the availability of resources for other connections. Trade-off: Setting a shorter keep-alive timeout reduces the duration of idle connections, freeing up resources more quickly. However, it may also lead to more frequent connection establishment and teardown, which can increase overhead.
  21. rdisp/wp_ca_blk_no: Description: Sets the number of dialog work processes used as collision avoidance blocks. These work processes handle specific tasks related to lock management and concurrency control. They prevent multiple work processes from accessing the same data simultaneously, improving system stability and consistency. Trade-off: Allocating more work processes as collision avoidance blocks enhances system concurrency and reduces the likelihood of data conflicts. However, it also reduces the number of available work processes for executing user transactions, potentially impacting system responsiveness during peak load periods.
  22. ztta/roll_area: Description: Specifies the maximum size of the roll area, which is used for storing ABAP program data during execution. The roll area holds the data that exceeds the available memory space and is temporarily stored on disk. Trade-off: Increasing the size of the roll area allows for larger data storage during program execution, reducing the frequency of disk I/O operations. However, it also consumes more memory resources, potentially impacting the overall system performance and available memory for other processes.
  23. rdisp/plugin_auto_logout: Description: Controls the automatic logout behavior for SAP GUI users who are inactive for a specified period of time. When enabled, users who remain inactive for the defined duration are automatically logged out of the SAP system. Trade-off: Enabling the automatic logout feature enhances system security by reducing the risk of unauthorized access to an active user session. However, it may inconvenience users who may need to frequently re-login if they have prolonged periods of inactivity.
  24. gw/acl_mode: Description: Determines the access control mode for the SAP Gateway. It defines how clients are authenticated and authorized to access SAP system resources. Different ACL (Access Control List) modes provide varying levels of security and control. Trade-off: Selecting the appropriate ACL mode depends on the specific security requirements of the SAP system. More restrictive ACL modes provide stronger access control but may also require more administrative effort to manage and maintain authorized client access.
  25. abap/heap_area_nolimit: Description: When set to TRUE, removes the limit on the heap memory available for ABAP programs. This allows ABAP programs to use memory without restrictions. Trade-off: Removing the heap memory limit can provide flexibility for memory-intensive processes and prevent memory-related errors. However, it also increases the risk of memory exhaustion and potential performance degradation if programs utilize excessive memory.
  26. icm/HTTP/logging_0: Description: Configures the HTTP logging level for the ICM. It determines the level of detail captured in the log files, helping with troubleshooting and monitoring. Trade-off: Increasing the logging level provides more detailed information in the log files, facilitating thorough analysis and troubleshooting. However, it also increases the volume of log data, potentially impacting disk space usage and log file management.
Labels:

Comments

Post a Comment

You might find these interesting

Notes for Build Resilient Applications on SAP BTP with Amazon Web Services [ Week 1]

Welcome back to the next chapter in our ongoing series dedicated to unraveling the dynamic interplay between SAP Business Technology Platform (BTP) and Amazon Web Services (AWS). For those just joining us, this blog serves as an invaluable resource for individuals delving into the world of SAP BTP or seeking a comprehensive reference guide. SAP BTP, or SAP Business Technology Platform, is a comprehensive platform that brings together various essential capabilities for application development, automation, data management, analytics, planning, integration, and AI. These features are all integrated into a unified environment, making it user-friendly for both professional IT developers and citizen developers. Image Credit  Key Features of SAP BTP: Application Development: SAP BTP offers a range of tools for development. For instance, SAP Build enables low-code development, while the SAP Business Application Studio caters to core developers, providing services like document management a...
1 comment
Read more

8 Must-Know Questions About Object Store on SAP Business Technology Platform

What is the problem that Object Store solves ? Modern enterprise systems increasingly deal with massive volumes of unstructured data such as documents, logs, media files, and backups. Traditional relational databases are not optimized for such workloads. What is Object Store ? Object storage—commonly referred to as blob storage—addresses this gap by providing scalable, durable, and cost-efficient storage for unstructured data. Object storage is a storage architecture designed to manage unstructured data as discrete units called objects.  Each object consists of: Binary data (file content) : Image , File etc Metadata (descriptive attributes) : File size, Content type, Last modified timestamp, Storage class (hot, cool, archive) Unique identifier (key or URL) : unique path-like string used to locate a blob inside a bucket Unlike file systems or relational databases, object storage does not rely on hierarchical file structures or schemas. The SAP BTP Object Store service is a managed, ...
Post a Comment
Read more

Understanding SAP BTP Global Accounts, Directories, Subaccounts, and Entitlements

In SAP Business Technology Platform (BTP), organizing your resources effectively is crucial for efficient management and scalability. This blog provides a comprehensive overview of global accounts, directories, subaccounts, and entitlements within SAP BTP. What is a Global Account in SAP BTP? A global account in SAP BTP represents the contractual agreement you have with SAP. It serves as the top-level container for managing various resources, including directories, subaccounts, members, entitlements, and quotas. Within a global account, you receive entitlements and quotas for platform resources, which can be allocated to subaccounts for actual consumption. How Do Directories Function in SAP BTP? Directories in SAP BTP allow you to organize and manage your subaccounts based on your technical and business requirements. A directory can contain other directories and subaccounts, enabling you to create a hierarchical structure. This hierarchy can be up to 7 levels deep, with the global ac...
Post a Comment
Read more

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with...
25 comments
Read more

KPIs for Recovery in HANA Database Administration

Introduction: In the dynamic landscape of database administration, ensuring the robustness of a system is paramount. One crucial aspect that demands meticulous attention is the recovery process following a system failure. Two key performance indicators (KPIs) stand out in this realm – Recovery Point Objective (RPO) and Recovery Time Objective (RTO) . In this technical blog, we will delve into the significance of these KPIs for HANA database administrators and explore strategies to optimize them. Recovery Point Objective (RPO): RPO is a critical metric that defines the maximum acceptable data loss in the event of a system failure . For HANA database administrators, establishing an RPO involves a careful balance between data consistency and the overhead of continuous data replication. Continuous Data Backups: To meet stringent RPO requirements, implementing continuous data backups is imperative. Utilizing HANA's native backup capabilities and integrating them with a robust backup s...
Post a Comment
Read more

Huge Multiversion Concurrency Control (MVCC) Versions in HANA

What is MVCC? MVCC is a database concurrency control method that allows multiple transactions to occur concurrently without conflicting with each other. In a nutshell, it ensures that each transaction sees a snapshot of the database at a specific point in time, even if other transactions are making changes concurrently. MVCC in SAP HANA: SAP HANA uses MVCC to manage concurrent access to data. Each transaction in HANA sees a consistent snapshot of the data at the time the transaction began. This is achieved by maintaining multiple versions of a data row, each associated with a specific transaction or point in time. The Issue of Huge MVCC Versions: Now, the term "Huge MVCC Versions" indicates a situation where there is a significant number of these versions for a particular set of data. Here's why this might become a problem: Increased Memory Usage: Each version of a data row consumes memory. As the number of versions increases, the overall memory consumption by the databas...
Post a Comment
Read more

Execute HANASitter for hang situation analysis

The SAP HANAsitter is configured to perform default checks once every hour to ascertain the online and primary status of SAP HANA. Upon confirmation, it initiates tracking procedures, which involve regular responsiveness assessments (typically every minute). If SAP HANA becomes unresponsive, the HANAsitter commences recording activities, potentially capturing call stacks of active threads, run-time dumps, index server gstacks, and/or kernel profiler traces, although, by default, no recording occurs. When SAP HANA is responsive, the script scrutinizes critical features, including a standard check for more than 30 active threads. If this threshold is exceeded, the script triggers recording. Upon completing the recording process, the script exits, with an option to be configured for restart using the command line. Setup Steps Overview: Begin by creating an SAP HANA user with the desired name (e.g., HANASITTER) and assign the CATALOG READ privilege to it. Establish a user key in the hdbuse...
Post a Comment
Read more

Deploying SAP on Google Cloud : Part 1

 Connect to Google  Connection Method To be Used for Speed Explanation Example Uses Cloud VPN Proof of Concept Variable, up to 3 Gbps Connects on-premises network to Google Cloud securely over the internet using IPsec VPN tunnels. Creating a Cloud VPN tunnel between on-premises and Google Cloud. Encrypted IPsec tunnels Dedicated Interconnect For Enterprise level connect 10 Gbps to 100 Gbps Provides a dedicated, private connection between on-premises and Google Cloud through Google's network. Provisioning a dedicated interconnect connection. Direct physical connection between on-premises and Google Cloud network infrastructure Partner Connect If you have a data center which cannot be reached to Dedicated Google facility. Variable, up to 100 Gbps Allows connecting to Google Cloud through supported service providers. Establishing a connection with a supported service provider. Utilizes service provider's network infrastructure. Configure Tunnels with Google Cloud Platform IPsec
Post a Comment
Read more

Building the Foundation of the PO System: Architecture and some terminologies

1. Loosely Coupled and Tightly Coupled Services : Loosely Coupled Services : These services interact with each other with minimal dependencies. Changes in one service don't significantly impact others. Pros include flexibility, easier updates, and better scalability. A common example in PO is when a shipping service communicates with an inventory service. Changes in the inventory service won't necessarily disrupt shipping. Tightly Coupled Services : These services are interdependent, so changes in one service can affect others. While they might provide faster communication, they can be less flexible and harder to maintain. For example, tightly coupling an order processing service with a payment service means any change in payment could ripple to order processing. 2. SOA - Service-Oriented Architecture : SOA is an architectural approach where everything is treated as a service, encapsulating specific functionality. Service Orchestration Example (Banking Transaction) : Consider ...
2 comments
Read more

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory...
7 comments
Read more