SAP BASIS System Installation

 The installation of an SAP BASIS system is a complex and multi-stage process that requires careful planning and execution. It's not a single "installation" but rather a series of installations and configurations across different layers: Operating System, Database, and SAP Application.

Here's a detailed breakdown of the process and critical parameters:

Phase 1: Planning and Preparation

This is the most crucial phase. Insufficient planning can lead to significant issues down the line.

1. Sizing (Crucial Parameter):

   • What it is: Determining the hardware resources (CPU, RAM, Disk I/O, Network Bandwidth) required for your SAP system.
   • Why it's critical: Under-sizing leads to poor performance and user experience. Over-sizing leads to unnecessary costs.
   • How it's done:
     • SAP Quick Sizer Tool: This web-based tool (requires SAP S-user ID) is the primary method. You input business requirements (number of users, types of transactions, data volume, expected growth) and it provides SAP Application Performance Standard (SAPS) values and recommended hardware.
     • User-based sizing: Categorizing users (e.g., light, medium, heavy) and their expected activity.
     • Throughput-based sizing: Estimating transaction volumes.
     • Database sizing: Estimating data growth, considering compression ratios for HANA.
     • Factors to consider: High availability (HA), disaster recovery (DR) requirements, integration with other systems.

2. System Landscape Design:

   • Development (DEV): For configuration, customization, and ABAP development.
   • Quality Assurance (QAS): For testing, integration testing, and user acceptance testing (UAT).
   • Production (PROD): The live system used by end-users.
   • Other systems: Sandbox, Training, Pre-Production, Solution Manager, etc., depending on organizational needs.

3. Software and Hardware Requirements:

   • Operating System (OS): Choose a supported OS (e.g., various Linux distributions, Windows Server). Ensure it's the correct version and bitness (64-bit is standard). Apply necessary patches and updates.
   • Database: Select a certified database (SAP HANA, Oracle, MS SQL Server, IBM Db2, SAP ASE). Ensure compatibility with your SAP NetWeaver or S/4HANA version.
   • SAP Installation Media: Download all required SAP installation files from the SAP Support Portal (SAP Software Center/Marketplace) using your S-user ID. This includes:
     • SAP Software Provisioning Manager (SWPM)
     • SAP Kernel files (SAPEXE.SAR, SAPEXEDB.SAR, IGS.SAR, etc.)
     • Database-specific files (client, export/import DVDs)
     • Application-specific files (e.g., SAP NetWeaver, S/4HANA)
     • SAP Host Agent
   • User Permissions: Ensure you have administrative privileges on the OS and database server.

4. Network Configuration:

   • Hostnames and IP Addresses: Configure static IPs and resolve hostnames (forward and reverse DNS) correctly for all SAP servers (Application Server, Database Server, Enqueue Replication Server, etc.).
   • Firewall Rules: Configure firewall exceptions for SAP ports (e.g., message server, dispatcher, gateway, database ports).
   • Shared File Systems: Plan for shared file systems (e.g., /sapmnt/<SAPSID>) for central instance installations and transport directories.

Phase 2: Core Installation Steps (Using SAP Software Provisioning Manager - SWPM)

SWPM is the primary tool for installing SAP systems. It's a wizard-driven application that guides you through the process.

1. Operating System Installation & Preparation:

   • Install the chosen OS.
   • Configure network settings, hostname, time synchronization.
   • Create necessary OS users and groups (e.g., sidadm, orasid, db2sid, sapsys, dba).
   • Adjust kernel parameters (for Linux) or OS settings (for Windows) as per SAP notes (e.g., shared memory, semaphores, file handles).
   • Install OS-level prerequisites (e.g., C++ runtime libraries, specific packages).

2. Database Installation:

   • Install the chosen database software.
   • Configure database parameters according to SAP recommendations (e.g., memory allocation, block size, character set).
   • Create the database instance and initial database users.
   • Ensure proper access rights for the SAP system to the database.

3. SAP Host Agent Installation:

   • Install the SAP Host Agent. This agent provides essential monitoring and management capabilities for the SAP system and its underlying infrastructure.

4. Starting SWPM:

   • Extract the SWPM archive.
   • Run sapinst (or sapinst.exe on Windows). It typically launches a web-based GUI.

5. Define Installation Parameters (Critical Parameters):

   • SAP System ID (SAPSID): A unique, 3-character alphanumeric identifier for your SAP system (e.g., "PRD", "DEV", "QAS"). Must start with a letter and contain only uppercase letters. Avoid reserved IDs.
   • Instance Number: A 2-digit number (00-99) that uniquely identifies an SAP instance on a host. Each instance (Central Instance, Database Instance, Dialog Instance, SCS Instance) will have one.
   • Installation Type:
     • Standard System: Installs Central Services (ASCS/SCS), Database Instance (DB), and Primary Application Server (PAS) on the same host or distributed across hosts.
     • Distributed System: Installs components on separate hosts.
     • High-Availability (HA) System: Involves clustering of Central Services for failover.
   • Database Parameters:
     • Database Hostname
     • Database SID
     • Database Administrator User and Password
     • Database Schema User and Password (e.g., SAP<SID>)
     • Database Home Directory
     • Redo Log/Archive Log locations
     • Memory configuration (SGA, PGA for Oracle, similar for other DBs)
   • Master Password: A strong password that will be used for various SAP-generated users (e.g., DDIC, SAP*, SAPADM) and internal communication.
   • SAP System Directory Structures: Confirm or adjust the proposed directory layout (/sapmnt/<SAPSID>, /usr/sap/<SAPSID>).
   • Transport Host: Specify the host where the transport directory (/usr/sap/trans) resides.
   • Kernel Files Location: Point SWPM to the extracted kernel files.
   • Language Selection: Choose the languages to install.
   • Unicode/Non-Unicode: For newer SAP systems, Unicode is mandatory. For older systems, you might have this choice.
   • Memory Configuration: Initial memory settings for SAP application servers (heap memory, buffer sizes).
   • Profile Parameters: SWPM sets default profile parameters, but you may review and adjust them.

6. Installation Execution:

   • SWPM performs pre-requisite checks.
   • It creates OS users and groups.
   • It installs the database instance (if selected).
   • It imports the SAP software components into the database.
   • It installs the Central Services Instance (ASCS/SCS) and Primary Application Server (PAS).
   • It sets up profiles and configuration files.

Phase 3: Post-Installation Steps

These steps finalize the setup and ensure the system is ready for use.

1. Initial Login:

   • Log in to client 000 (or the initial client) using the DDIC user and the master password.
   • Change the DDIC password immediately.

2. License Installation:

   • Obtain the SAP license from the SAP Support Portal.
   • Install it using transaction SLICENSE.

3. Kernel Update (Critical Parameter):

   • Why it's critical: The kernel is the core executable part of the SAP system. Keeping it updated ensures stability, performance, and security.
   • How to update:
     • Download the latest kernel files (SAPEXE.SAR, SAPEXEDB.SAR, IGS.SAR) for your OS and database from the SAP Support Portal.
     • Stop the SAP application instances.
     • Backup the existing kernel directory (/sapmnt/<SAPSID>/exe).
     • Extract the new kernel files into a temporary directory.
     • Copy the new files to the active kernel directory.
     • Run saproot.sh (UNIX/Linux) or sapcpe (Windows) to set correct permissions and copy shared libraries.
     • Start the SAP application instances.
     • Verify the kernel version using disp+work -version (OS level) or SM51 -> Go To -> Release Notes (SAP GUI).

4. SPAM/SAINT Update:

   • Update the Support Package Manager (SPAM) and Add-on Installation Tool (SAINT) to the latest version using transaction SPAM. This is essential before applying any support packages or add-ons.

5. Apply Support Packages / Support Package Stacks:

   • Download the relevant support packages or support package stacks from the SAP Support Portal.
   • Import them using SPAM. This keeps your system updated with bug fixes and new functionalities.

6. Client Administration (SCC4, SCCL, SCC7, SCC8):

   • Client 000: The original client with SAP's standard configuration. Do not make custom changes here.
   • Client 001: Often used as a copy source for new clients.
   • Create New Clients (SCC4): Define new clients for development, testing, and production.
   • Client Copy (SCCL): Copy data and configuration from an existing client (e.g., 000 or 001) to a new client. This can be a local copy or remote copy.
   • Post-Client Copy (SCC7/SCC8): Perform necessary post-copy activities.

7. Profile Parameter Configuration (RZ10, RZ11):

   • Why it's critical: Profile parameters control the behavior of the SAP system, including memory allocation, user sessions, security, and performance.
   • Key Parameters to Review and Adjust:
     • login/system_client: Sets the default client for initial login.
     • rdisp/max_wprun_time: Maximum runtime for a dialog work process.
     • rdisp/wp_no_dia, rdisp/wp_no_btc, etc.: Number of dialog, background, update, spool work processes.
     • abap/heap_area_dia, abap/heap_area_nondia: ABAP heap memory for dialog and non-dialog processes.
     • em/initial_size_MB, ztta/roll_area: Extended memory and roll area configuration.
     • buff/bufsiz_kb: Size of the ABAP program buffer.
     • rec/client: Controls client-specific recording of changes for transport.
     • Security Parameters (Critical Parameters):
       • login/min_password_lng: Minimum password length.
       • login/password_history: Number of old passwords remembered.
       • login/fails_to_user_lock: Number of failed login attempts before user lock.
       • login/failed_user_auto_unlock: Whether locked users are automatically unlocked at midnight (set to 0 for no automatic unlock).
       • rdisp/gui_auto_logout: Automatic logout of inactive GUI users.
       • auth/check_value_write: Controls the checking of authorization values.
       • rec/client: Activates table change logging.
       • gw/acl_file, gw/acl_mode: Gateway security for external programs.
       • snc/enable, snc/permit_insecure_comm: Parameters for Secure Network Communication (SNC).
   • Tools:
     • RZ10: Maintain profiles (instance and default profiles). Changes require SAP restart.
     • RZ11: Display and dynamically change some profile parameters (changes are temporary until restart).

8. Configure Transport Management System (STMS):

   • Set up transport routes to manage the movement of changes (configurations, developments) between systems (DEV -> QAS -> PROD).

9. Generate ABAP Loads (SGEN):

   • Generate and compile ABAP programs to improve performance by loading them into the program buffer.

10. System Checks and Monitoring:

    • SM21: Check system logs for errors or warnings.
    • ST22: Check for ABAP runtime errors (dumps).
    • SM50/SM66: Monitor work processes.
    • ST02: Analyze buffer statistics.
    • ST04 (or database-specific tools): Monitor database performance and health.
    • DB02: Check database tablespace utilization.
    • SM51: Check status of application servers.
    • SM04: Check logged-on users.

11. Background Job Scheduling (SM36, SM37):

    • Schedule essential background jobs (e.g., daily cleanups, database statistics updates).

12. Configure Remote Connection to SAP Support:

    • Set up SAP Router and SNC connection to allow SAP support to access your system for troubleshooting.

13. Security Post-Installation:

    • Change all default passwords (e.g., SAP*, DDIC in clients other than 000).
    • Create dedicated BASIS administrator users with appropriate authorizations (SU01, PFCG).
    • Implement robust password policies.
    • Restrict access to critical transactions and directories.
    • Review and refine authorization roles.

Important Considerations and Best Practices:

• SAP Notes: Always refer to the latest SAP Notes for your specific SAP version, OS, and database. These notes provide critical information, prerequisites, and troubleshooting tips.
• Installation Guides: Download and meticulously follow the official SAP installation guides available on the SAP Support Portal.
• Documentation: Document every step of the installation, including parameter values, user accounts, and any issues encountered.
• Backup Strategy: Implement a robust backup and recovery strategy for both the database and the SAP application files.
• Communication: Keep relevant stakeholders informed about the installation progress and any planned downtimes.
• Test Thoroughly: After installation, perform comprehensive testing to ensure all functionalities are working as expected.

SAP BASIS installation is a foundational task. A well-planned and executed installation sets the stage for a stable, high-performing, and secure SAP environment.