51:53
SAP Installation Steps
SAP BASIS
Overview
This video details the practical steps for installing SAP software, focusing on the execution phase after initial preparations. It guides viewers through logging into a remote server using RDP, locating the necessary SAP software components (SWPM, kernel, exports, host agent, DB client), and initiating the installation process via the SWPM tool. The summary emphasizes understanding the SWPM port (4237), selecting the appropriate installation type (standard, distributed, high availability), and providing essential parameters like SID, instance number, and software paths. It highlights the importance of log files for troubleshooting and explains the typical vs. custom installation options, concluding with the review and execution stages of the installation process.
How was this?
Save this permanently with flashcards, quizzes, and AI chat
Chapters
- Log into the remote server using Remote Desktop Protocol (RDP) for Windows or PuTTY for Linux.
- Ensure you are using the correct IP address and user credentials for the remote server.
- Understand that in real-time scenarios, accessing remote servers is a common practice.
Secure and correct access to the server is the foundational step before any installation can begin, ensuring you are working in the right environment.
Using the 'Remote Desktop Connection' application on your local desktop, entering the server's IP address, and then providing your allocated user ID and password.
- Verify that all required SAP software (SWPM, kernel, exports, DB client, host agent) is downloaded and available.
- Confirm the server meets prerequisites like sufficient RAM (e.g., 14GB), disk space (e.g., 250GB), and CPU cores (e.g., 4 CPUs).
- The SAP Software Provisioning Manager (SWPM) is the primary tool used to start the installation.
Having all necessary software components and a properly configured server environment prevents installation failures and ensures a smooth process.
Locating the downloaded SAP software in the 'E Drive' under 'SAP Software', including folders like 'DB', 'exports', 'kernel', 'SWPM', and 'host agent'.
- Start the installation by double-clicking the 'sapinst' executable within the SWPM folder.
- This action opens a URL in the browser, typically on port 4237, which is the SWPM tool's communication port.
- Access the SWPM interface by navigating to the provided URL and proceeding with the 'unsafe' option if prompted, then entering your credentials.
SWPM is the central orchestrator for SAP installations, and understanding how to launch and access it is crucial for starting the setup.
Navigating to 'E:\SAP Software\SWPM', double-clicking 'sapinst', and then accessing the browser URL like 'http://<hostname>:4237/sapinst'.
- SWPM supports various SAP product installations, including NetWeaver, ECC, S/4HANA, and others.
- Choose the installation type: 'Standard' (SAP and DB on one OS), 'Distributed' (SAP and DB on separate OS), or 'High Availability' (for mission-critical systems with redundancy).
- For training purposes, a 'Standard' installation on a single server is typically sufficient.
The chosen installation type dictates the system architecture and resource allocation, impacting complexity and performance.
Expanding 'SAP NetWeaver 7.5 Installation' and then selecting 'ABAP' system type followed by 'Standard System'.
- The installation requires specific inputs, including the System ID (SID - 3 alphanumeric characters), instance number, and passwords for system users.
- Provide the correct paths to the downloaded software components: kernel, exports, and host agent.
- The system validates each input and software component to ensure integrity and correctness.
Accurate parameter input is vital for a successful installation; incorrect details can lead to errors or a non-functional system.
Entering 'ND1' as the SID, providing the path to the kernel files in 'E:\SAP Software\Kernel', and setting passwords for system users.
- After defining parameters, review them and proceed to the execution phase.
- The SWPM tool manages the entire installation process, which can take several hours depending on the product.
- Monitor the installation progress through log files (e.g., 'sapinst.log', 'sapdev.log') for troubleshooting.
Understanding the execution and monitoring phases allows for tracking progress, identifying issues, and knowing when the installation is complete.
Reviewing the collected parameters and clicking 'Next' to initiate the automated installation process, while periodically checking the log files for updates.
Key takeaways
- Remote server access (RDP/PuTTY) is a fundamental skill for SAP installations.
- Thorough preparation, including software download and system prerequisite checks, is essential before starting installation.
- The SAP Software Provisioning Manager (SWPM) on port 4237 is the central tool for initiating and managing SAP installations.
- Choosing the correct installation type (Standard, Distributed, High Availability) depends on the system's purpose and criticality.
- Accurate input of parameters like SID, instance number, and software paths is critical for successful installation.
- Installation log files are indispensable for monitoring progress and troubleshooting errors.
- SAP installations are time-consuming processes that require patience and careful input during the parameter definition phase.
Key terms
RDP (Remote Desktop Protocol)PuTTYSAP Software Provisioning Manager (SWPM)SWPM Port (4237)System ID (SID)Instance NumberKernelExportsHost AgentStandard InstallationDistributed InstallationHigh AvailabilityLog Files (sapinst.log, sapdev.log)
Test your understanding
- What is the primary tool used to initiate and manage SAP installations, and on which port does it typically run?
- What are the key differences between Standard, Distributed, and High Availability installation types in SAP?
- Why is it important to verify server prerequisites like RAM and disk space before starting an SAP installation?
- How can you monitor the progress and troubleshoot issues during an SAP installation?
- What information is typically required when defining parameters for an SAP installation using SWPM?