Sap Installation - Rajesh
Sap Installation - Rajesh
SAP Installation
1. Introduction
Overview of SAP and its Components
SAP (Systems, Applications, and Products) is one of the world’s leading providers of
enterprise resource planning (ERP) software and related enterprise applications. SAP
solutions help organizations streamline processes, manage business functions, and
improve overall e iciency.
SAP’s product portfolio includes various modules for areas such as finance, logistics,
human resources, and sales. The most common SAP products are based on the SAP
NetWeaver platform, which includes the SAP Application Server (AS), SAP HANA
database, and SAP Fiori (for a modern, user-friendly interface).
SAP installations typically involve the deployment of several core components, including:
SAP Business Suite (modules like SAP S/4HANA, SAP ECC, etc.)
This document serves as a comprehensive guide for installing SAP on a server or virtual
machine, along with configuring the necessary components and software. Whether you are
setting up a test environment or a production SAP system, this guide will take you through
all the critical steps required for successful SAP installation.
Post-installation configurations
By the end of this guide, you should have a fully operational SAP system ready for use.
Before proceeding with the installation, ensure the following prerequisites are in place:
Licensing: Ensure you have the necessary SAP licenses for the components you
intend to install.
2. System Requirements
Before installing SAP, it’s essential to ensure that both the hardware and software meet the
required specifications to guarantee optimal performance and stability. Below are the
recommended system requirements for installing SAP, including details on hardware,
software, and SAP components.
Hardware Requirements
The hardware specifications required for SAP installation depend on the specific SAP
product and the number of users or clients the system will serve. Below are general
guidelines:
Processor (CPU):
o For optimal performance, a 64-bit processor (e.g., Intel Xeon or AMD EPYC) is
preferred.
Memory (RAM):
Disk Storage:
o SAP NetWeaver: Minimum 200 GB of disk space for the installation, which
may increase based on system size and log storage.
o SAP HANA: At least 500 GB of disk space for a minimal installation. SAP
HANA, being an in-memory database, requires significant disk space for
persistence and logs.
o Use SSD storage for optimal performance (especially for SAP HANA).
Network:
o Gigabit Ethernet (or higher) is recommended for both the server and client
machines.
Graphics Card:
o Not essential for SAP installations but may be required for certain visual tools
or applications (e.g., SAP Fiori).
Software Requirements
The software requirements for SAP depend on the operating system, database, and SAP
components that you plan to install. Below are the software specifications for both the
operating system and SAP components.
Operating System
SAP supports several operating systems. Below are the most commonly supported
platforms:
Linux (e.g., SUSE Linux Enterprise Server (SLES), Red Hat Enterprise Linux (RHEL))
o SAP HANA and SAP NetWeaver are often deployed on Linux servers for
enterprise-grade performance and scalability.
Windows Server
SAP INSTALLATION RAJESH
4
o Versions such as Windows Server 2016, 2019, and 2022 are supported for
SAP NetWeaver installations.
Database Requirements
SAP can integrate with several databases, but SAP HANA is the preferred and most widely
used database for modern SAP systems due to its in-memory capabilities. Below are the
key options:
Other Databases:
o Oracle: Supported versions of Oracle Database for SAP include 12c, 18c,
and 19c.
Depending on your SAP environment (SAP S/4HANA, SAP ECC, SAP BW, etc.), you will need
specific software components:
o Used for specific business functions like Finance, HR, Supply Chain, etc.
o Web-based user interface for modern SAP apps, compatible with various
browsers.
Additional Software
SAP Kernel: The core of the SAP system, containing the essential executable
programs for the SAP system's operations.
Web Dispatcher: A component used for load balancing and routing HTTP(S)
requests to the appropriate application server.
Network Configuration
A reliable network setup is crucial for communication between the SAP system
components and end-users. Some key considerations:
Ports: Ensure that the required ports are open on the firewall (e.g., ports for HTTP,
HTTPS, database connections).
3. Pre-installation Steps
Before you begin the SAP installation process, there are several important pre-installation
steps that need to be completed. These steps ensure that your environment is properly
prepared and that the installation proceeds smoothly.
Ensure that your server or virtual machine meets the hardware requirements outlined in
the earlier section. For virtual machines, distribute su icient resources (CPU, RAM, and
disk space) as per specifications, and ensure that the system can scale based on expected
workload.
Before installing SAP, ensure that your network is properly configured to allow
communication between the SAP components and external systems.
DNS Configuration: Configure DNS so that the SAP system can resolve all
hostnames correctly. A proper DNS setup is essential for resolving SAP system
components, such as the database server, application server, and SAP router.
Static IP Address: Assign a static IP address to the SAP server to prevent IP address
changes after installation, ensuring consistency in communication.
Firewall: Open the necessary ports in the firewall to allow for communication
between SAP components. Typical SAP ports include:
o SAPGUI (3200)
Prepare the operating system by installing and configuring the necessary software and
packages.
o On Linux systems, install necessary packages such as glibc, gcc, and others
required by SAP.
SAP INSTALLATION RAJESH
7
o On Windows systems, ensure that the system is configured with the correct
version of Windows Server (e.g., 2016, 2019) and the latest service packs.
Swap Space (Linux): On Linux, configure adequate swap space as required by SAP.
Typically, it should be at least 2 GB, but the exact size depends on the server's
memory and expected workload.
You need to download the necessary installation files from the SAP Software Download
Center.
o Go to the SAP Software Download Center and log in with your SAP S-user ID.
o SAP Kernel: The core system files needed for the SAP NetWeaver application
server.
o Database Client: If you are using an external database (e.g., Oracle, SQL
Server), download the respective database client.
Licensing Files: Ensure you have the necessary SAP licenses downloaded and
available for installation. The SAP license key is needed for activating the SAP
system after installation.
Before beginning the installation, you need to ensure that the system is properly licensed
and that all required software components are available.
SAP License: Ensure you have a valid SAP license file (txt or .xml) that will be used
during the post-installation configuration to activate the system.
SAP Solution Manager: If you're installing SAP Solution Manager, ensure you
download the proper version for your landscape.
6. Database Preparation
If you're using an external database (such as SAP HANA, Oracle, or SQL Server), you must
prepare the database server accordingly.
Install the Database Software: If the database is not yet installed, download and
install the database software (e.g., SAP HANA Studio, Oracle Database, etc.).
o Create the necessary database users (e.g., sapadm, saphana) with proper
privileges.
o Set up the required schemas (e.g., for SAP HANA, set up the SYSTEM schema
and other necessary database configurations).
For SAP HANA, ensure that the HANA database version is compatible with the SAP system
you intend to install.
It’s crucial to plan and configure your SAP landscape ahead of the installation. This
includes:
Planning the System Landscape: Define the SAP landscape, including the number
of application servers, database servers, and the overall architecture. You may need
to plan for a single-node or multi-node setup.
Instance Setup: Choose the proper SAP instance number (e.g., 00, 01) for your
system during installation. This instance number will be used to di erentiate
multiple SAP installations.
Client Setup: The default client number for SAP systems is usually 000. You will
create additional clients later in the process.
In this section, we will walk through the steps to install SAP NetWeaver and configure the
application server. The installation will be carried out using the SAP Software Provisioning
Manager (SWPM), a tool that simplifies the process of installing and configuring SAP
components.
SAP NetWeaver is a platform for building and running SAP applications. It provides the
infrastructure required for deploying business applications, including:
ABAP Stack: Used for traditional SAP ERP applications, such as SAP ECC and SAP
S/4HANA.
Java Stack: Required for applications that rely on Java, such as SAP Portal and SAP
PI/PO.
1. Extract the Installation Files: Extract the downloaded SAP installation files to a
local directory on your server. The SWPM installation files should be in the "SWPM"
folder.
2. Launch SWPM: On the command line, navigate to the extracted SWPM directory,
and execute the following command to start the installation:
o On Linux/Unix: ./sapinst
o On Windows: sapinst.exe
Once the SWPM is launched, select the installation type that best suits your environment.
Choose the option “Installation of SAP NetWeaver AS (ABAP+Java)”. This option installs
both the ABAP and Java components, which is typical for most SAP installations.
o The SAP system will require directories for installation and storage.
Commonly used directories are:
You will need to define these directories during the installation process.
o You will be prompted to enter a System ID (SID) for your SAP system. The SID
is a unique identifier for your SAP system (e.g., SAP or ECC).
3. Instance Number:
o The installation will prompt you to set an instance number (typically 00 for
the first instance).
4. Database Configuration:
o During installation, the SWPM will ask for the database type (e.g., SAP
HANA, Oracle, or SQL Server). The database client (which was downloaded
earlier) must be installed and configured before proceeding.
o You will also be prompted for the database host, port, and the database
administrator credentials.
5. Password Configuration:
o During installation, you will be asked to set passwords for various SAP users,
including:
SAP INSTALLATION RAJESH
11
Developer and user roles in the system (e.g., SAP* and DDIC).
6. Network Configuration:
o The installation will also require you to set up network configuration details,
such as the hostname, DNS, and ports that will be used for communication.
After the configuration steps, the installer will begin the actual installation process. This
includes:
1. Copying Files: The necessary SAP kernel and application files will be copied to the
defined directories.
2. Database Setup: The SAP system will be connected to the database, and tables will
be created.
3. Creating SAP Instances: The installation tool will create the required instances
(ABAP and Java), set up the application server, and configure communication
between the instances.
During this phase, the installer will run various checks and validations to ensure that all
components are correctly installed and configured. Depending on the resources available
on your system, the installation process may take several hours.
Once the installation is complete, the SAP system will require some post-installation steps
to configure the environment fully.
SAP Kernel Update: The SAP kernel may need to be updated after installation. Use
the Software Update Manager (SUM) to apply any patches or updates.
Check System Logs: Review the installation logs to ensure there were no errors
during the installation process. Logs are typically stored in the
/usr/sap/<SID>/DVEBMGS<Instance Number>/work directory on Linux or the
corresponding path on Windows.
Verify the SAP System: Check that all system components (application server,
database, etc.) are running correctly. You can verify this by using transaction codes
like SM51 (for application servers) and SMDA (for database connections).
SAP INSTALLATION RAJESH
12
Backup: Once the system is up and running, it's highly recommended to perform a
full system backup before proceeding with further configurations or client setups.
Supported Databases
SAP supports a variety of databases for use with its applications, including:
SAP HANA: SAP’s in-memory, columnar database designed for real-time processing
of large amounts of data. It is the preferred database for most modern SAP
environments.
Oracle Database: A traditional relational database often used for SAP ECC or other
legacy SAP applications.
Microsoft SQL Server: Supported for various SAP applications, though not as
common as SAP HANA or Oracle.
SAP HANA is the most commonly used database for new SAP installations, especially
when implementing SAP S/4HANA or other SAP applications optimized for in-memory
processing. Below are the steps for installing SAP HANA.
o Log in to the SAP Software Download Center and download the SAP HANA
installation package for your platform (Linux or Windows).
o Ensure that you download the correct version that matches your SAP version.
o Ensure your server meets the hardware requirements for SAP HANA (e.g.,
high RAM, SSD storage).
o On Linux: Unzip the SAP HANA installation files and run the installer:
bash
Copy
cd HANA
./hdblcm
o The SAP HANA installation wizard will prompt you for network configurations,
including setting up the hostname and port numbers.
o Ensure that the hostname matches the server's FQDN (Fully Qualified
Domain Name) for proper DNS resolution.
bash
Copy
o Use the HANA Studio or HDBSQL to check the health of the database and
confirm that the database instance is running correctly.
o Create necessary users for SAP to connect to the database. These include
users like SAPSR3, SAPHANA, etc., depending on your installation
requirements.
o When running the SAP NetWeaver Application Server installation, you will
be prompted to connect to the SAP HANA database.
o Enter the hostname, port number, and credentials for the HANA database
to establish the connection.
o You can check the health of the SAP HANA system using tools like HANA
Studio or via command line:
bash
Copy
HDB info
If you're using Oracle for your SAP system, follow the steps below for installation and
configuration.
o Download the Oracle Database installation files from the Oracle Technology
Network (OTN).
o Ensure you select the correct version that supports your SAP NetWeaver
version.
o Ensure that the Oracle listener is running and the Oracle database is
configured to communicate with your SAP system.
o Set the SID (System Identifier) for the Oracle database, which will be used
during the SAP installation (e.g., SAPDB).
o Create the necessary Oracle users (e.g., SAPSR3, SAPDB) with the
appropriate privileges for SAP to interact with the database.
o During the SAP installation, configure the database connection using the
Oracle client.
o During SAP installation, you will be prompted to specify the Oracle database
instance, host, port, and database credentials.
o The SAP system will connect to Oracle using the Oracle Net Listener for
database communication.
o Verify that the connection between the SAP system and the Oracle database
is successful by checking transaction codes like DB02 in SAP GUI.
Microsoft SQL Server is supported for specific SAP applications. Below are the general
steps for installing SQL Server and connecting it to your SAP system.
o Download the required SQL Server version from the Microsoft Download
Center.
o Ensure that the SQL Server instance is configured correctly to allow SAP to
connect.
o Create the necessary SAP database users in SQL Server, such as SAPSR3
and SAPDB.
o When installing SAP, provide the SQL Server instance, hostname, port, and
credentials for connecting to the SQL Server database.
2. Verify Connection:
Backup: Always take a full backup of your database once the system is up and
running to avoid data loss during future configurations.
Performance Tuning: Tune your database for performance based on your expected
workload, including adjusting cache sizes, index optimization, and query
performance.
In this section, we will focus on the essential steps needed to configure your SAP system
after installation.
After the installation is complete, the SAP system needs some initial configurations to
ensure it’s ready for use.
To start the SAP system, you can use the following commands:
o On Linux:
bash
Copy
sudo startsaph
o On Windows:
Start SAP services via the Services console or using sapcontrol -start.
After starting the SAP system, use the SAP GUI or SAP Management Console (SAP
MC) to check if the system is running correctly.
The system parameters control the behavior and performance of the SAP system. These
parameters can be configured using the transaction RZ10 (for profile parameters) and
RZ11 (for individual parameters).
For example, to adjust the maximum number of work processes, you can set:
bash
Copy
rdisp/max_wp_num = 30
1. Go to transaction RZ10.
2. Select Change and choose the profile you want to edit (typically DEFAULT.PFL).
4. After saving, restart the SAP instance for the changes to take e ect.
The SAP system requires a valid license key to run. The license file should have been
obtained from SAP Support.
1. Go to transaction SLICENSE.
2. Select Install and upload the SAP license file (typically an .xml or .txt file).
3. Once installed, verify that the license is correctly applied using the License
Management interface.
Ensure that the license is valid, as an expired or incorrect license will prevent the SAP
system from functioning.
2. Client Configuration
SAP systems are multi-client environments, which means you can create and configure
multiple clients within a single system. The default client in SAP is 000, but you may need
to create additional clients for di erent business scenarios (e.g., production, development,
testing).
Once a client is created, you may need to copy data from an existing client (usually 000) to
your newly created client.
1. Go to transaction SCCL.
3. Choose the source client (typically 000) and then specify the target client.
4. Select the data you wish to copy (e.g., master data, configuration data).
5. Execute the client copy. This can take a while depending on the amount of data
being copied.
SAP uses user roles and profiles to manage access control. The configuration of users and
roles ensures that the correct individuals have the appropriate permissions to perform their
tasks.
o Roles: Assign appropriate roles (e.g., SAP_ALL, SAP_USER for basic users).
Roles control access within SAP, and each role has a set of authorizations. Roles are
created in transaction PFCG.
After creating the role, you can assign it to a user in SU01 under the Roles tab.
Users can also be organized into user groups, and authorization profiles can be created
to standardize user permissions. Use SU10 for mass user maintenance and assigning roles
to groups.
The SAP system needs to communicate with external systems, such as other SAP systems,
non-SAP systems, or third-party services.
o Logon Credentials: Specify the username and password for the destination
system.
After configuration, you can test the RFC connection to ensure proper communication.
If your SAP system is in a complex landscape (e.g., involving external networks), you may
need to configure SAProuter for secure communication between SAP systems.
To configure SAProuter, download the SAProuter software from SAP, install it, and
configure it in saproutertab.
TMS is used to manage the transport of configuration and development changes across
SAP systems. It is essential for moving data and configurations between di erent SAP
clients or systems.
3. Select the Transport Domain Controller (TDC), which will manage all transport
requests.
4. Ensure the Transport Directory is properly configured (for file storage of transport).
Set up transport routes to control the movement of transport requests between SAP
systems. You can define:
Each transport request will flow through these systems based on the transport routes you
define.
Final Verification
After completing these configurations, verify that your SAP system is fully operational. Key
checks include:
System Logs: Use transaction SM21 (System Log) to review logs for errors or
warnings.
Job Monitoring: Use SM37 to monitor background jobs and ensure no issues.
After completing the installation and configuration, it is important to ensure that the SAP
system is running without any errors and is ready for productive use.
Use the System Log (SM21) to check for any errors or warnings that might have occurred
during startup or during initial configurations.
o Go to SM21 to check the system log for any errors that may need attention.
o Ensure there are no critical errors in the log (e.g., database connection
issues, missing system parameters).
o You can filter logs based on date and severity (e.g., Error, Warning,
Information).
SAP systems use work processes to handle various tasks, including dialog processing,
background jobs, and more. Ensuring that work processes are running smoothly is vital for
system performance.
Transaction SM50: This shows the status of all work processes for a specific
instance.
o Ensure that all dialog, update, and background work processes are up and
running.
o Check for any stuck or overloaded processes and address them as needed.
Transaction SM66: This is the global version of SM50, displaying work processes for
all instances in the system.
o It can be used to monitor the status of work processes across the entire SAP
system.
Ensure that the SAP system can connect properly to the database. Database connectivity
issues can prevent the system from functioning correctly.
o Ensure that the database instance is running without errors, and confirm
that database tables are accessible.
Check that the correct version of the SAP Kernel is installed and running. The SAP Kernel is
the essential set of executables that help SAP systems run e iciently.
Transaction RZ10: Use this to check and modify the system profiles.
o Verify that there are no errors or outdated kernel versions in the profile
settings.
It is critical to keep the SAP system up to date with the latest patches and support
packages to ensure system stability and security.
o Check if the system has any pending support packages that need to be
applied.
o Apply any critical support packages or patches to address known bugs and
security vulnerabilities.
o If you have any SAP add-ons (e.g., SAP BW, SAP CRM), you can apply them
via this transaction.
The Software Update Manager (SUM) is a tool provided by SAP to update the system’s
kernel and apply patches to various components of the SAP environment.
o Download the latest SAP Kernel version from the SAP Service Marketplace.
o Use SUM to apply the updates and perform a system consistency check.
Security is a crucial aspect of any enterprise system. Ensure that the system is protected
by applying the latest security patches.
o Review the critical SAP Security Notes and implement them as needed.
Once the system is installed and configured, you should perform basic functional testing to
ensure the system behaves as expected.
Perform a few basic tasks using the SAP GUI to verify that the system responds correctly:
1. Log in using a test user account and navigate through di erent modules (e.g., SAP
MM, SAP SD, SAP FI).
Ensure that the system allows you to create, change, and view data without errors.
If possible, perform end-to-end testing for a business process in the SAP system:
This should include transactions like creating a purchase order, posting an invoice,
receiving goods, and making a payment.
Ensure that data flows correctly across the system, and all relevant updates are
made to the database.
Test the background job execution to ensure that long-running or scheduled tasks are
processed correctly.
Execute a test background job, such as a report generation or data processing task.
Verify that the job completes without errors and that the output is generated
correctly.
Once the system is live, it's essential to monitor its performance and set up alerts to be
notified of any issues.
SAP Solution Manager is the preferred tool for monitoring SAP systems.
You can use Transaction RZ20 to configure monitoring and alerting for system
components like database performance, work process status, and memory usage.
Use transaction SM37 to monitor job executions and identify any failed or delayed
jobs.
Set up job monitoring to ensure that critical tasks are executed on time.
SAP CCMS (Computing Center Management System) allows you to monitor the
health of the system.
You can configure alerts for various parameters (e.g., system downtime, failed
background jobs, database issues).
Finally, ensure that a backup and recovery strategy is in place to protect your SAP data.
Database Backups: Perform full database backups regularly, including both the
SAP database and the application server.
Use SAP tools such as BR*Tools for Oracle or HANA Backup for SAP HANA to
schedule automated backups.
Backup essential SAP files, including the application files, instance directories,
and profiles.
Develop and document a disaster recovery plan to ensure that in case of a system
failure, you can restore the SAP system and database to the latest backup point.
Periodically test the disaster recovery process by simulating system failure and
performing a recovery from backups.
8. Conclusion
This document has provided a comprehensive guide for SAP Installation and
Configuration. From preparing the hardware and software environment to completing the
post-installation steps, you now have the key steps and best practices needed to set up a
successful SAP system.
Final Thoughts:
Testing: It's crucial to ensure that the SAP system is thoroughly tested and
configured before moving into production. This will help mitigate issues that could
impact business processes.
Patching and Upgrades: Regularly applying SAP patches and updates is necessary
for the security and optimal performance of the SAP system.
Backup and Recovery: A reliable backup and recovery plan is essential for
business continuity. Always ensure that your SAP system can be restored quickly in
the event of failure.
By following these steps and maintaining best practices, your SAP environment will be well-
positioned for reliable and e icient operation, supporting your business objectives.
Appendices (Optional)
End of Document
This concludes with the SAP installation guide. With these steps, you are now prepared to
implement, configure, and maintain an SAP system that meets your business needs.