Objective
SAP supports you through the complete software life cycle from planning and implementation to operations and maintenance. SAP Support Portal (https://support.sap.com) provides access to the various tools and services throughout the software life cycle.
Hardware Sizing Issues
Hint
When sizing your hardware, consider the future development of load on the SAP system. For sizing information related to the SAP system, see SAP Library for System Sizing on SAP Help Portal at http://help.sap.com. For information about how to perform sizing, see SAP Library for Quick Sizer tool on SAP Help Portal at http://help.sap.comSizing – An Ongoing Process
Sizing plays a role very early in the planning of your SAP system landscape. It determines the hardware resources needed for your SAP system.
If any of these factors is subject to change, a new sizing or hardware improvement may become necessary.
A new SAP system release usually has additional hardware requirements. To check the sizing information of the system with its documentation, see SAP Library for system sizing on SAP Help Portal at https://help.sap.com.
You can distribute SAP software in several ways across the available hardware. The result of hardware sizing may influence the distribution of SAP software because the distribution of the software can affect SAP system performance.
In case of a central SAP system, the database and the PAS are installed on the same host; there is no other instance.
In case of a distributed SAP system, AASs are installed on additional hosts.
In distributed systems, the following options for installation are available:
If you decide to install the database on a separate host, interferences from the SAP application servers on database performance on host level are excluded.
If you decide to install a central system and a need arises for additional SAP system users, an AAS is a possible solution. An AAS may host as many users as the corresponding hardware allows, as long as not more than 100 dialog work processes are necessary. If you need more than 100 dialog work processes, you should install more than one AAS on the same host. SAP systems may have many AASs. Productive systems with more than 20 AASs exist.
Note
As a rule of thumb, you can estimate for an SAP S/4HANA Server system – one dispatcher can handle 100 dialog work processes and one dialog work process can handle 10 high load parallel users. This means that one dispatcher can handle 1000 high load parallel users per application server and as many named users as you want per application server.The SAP system ID must conform to specific naming conventions.
For information on reserved (forbidden) SIDs, like ADD, SAP, SET, and so on, see SAP Note 1979280 - Reserved SAP System Identifiers (SAPSID) with Software Provisioning Manager 1.0 .
A solution in this context is the combination of SAP systems, you as a customer are using in combination. A solution represents a bundle of business functions.
The SAP Solution Manager system supports you through the entire life cycle of your SAP solutions, from the business blueprint stage to configuration and production processing. It provides a central access to the tools, methods, and preconfigured contents that you can use during the evaluation, implementation, and operational processing of your SAP systems.
The SAP Solution Manager system also provides central access to all tools, methods, documents, and other data required in the implementation environment. You can use implementation contents, delivered with SAP Solution Manager and regularly updated, and adjust the SAP Solution Manager system to your requirements.
A client is a self-contained business unit in an SAP system having separate user master records, customizing and application data. After the installation of an up to date AS ABAP-based SAP systems (AS ABAP 7.50 and above), either only client 000 exists or client 000 and client 001. Client 000 contains the SAP standard customizing – and can be used to copy your own clients from it. Client 001 – if exists – is a copy of client 000 already – use it or delete it! Do not change the content of client 000! In older AS ABAP-based SAP systems a client 066 was delivered, also. It is not used at all anymore – and should be deleted.
Client 000 is used for special administrative purposes, such as initially setting up Transport Management System (TMS), importing languages, applying SAP Support Packages, and performing SAP system upgrades. Client 000 holds the default SAP customizing. You should not change client 000. Client 000 is delivered with a new installation.
Client 001 is a copy of client 000. Client 001 is meant to be your production client. Delete client 001 if you do not want to use it as your production client and copy your own client(s) from client 000. Depending on the SAP system type, client 001 is delivered with a new installation or not.
Client 066 was the client reserved to access the SAP system by SAP support. Depending on the software to be installed, client 066 might still be created during installation. Client 066 is not needed anymore and should be deleted for security reasons.
The System Landscape Directory (SLD) serves as a central information repository for your SAP system landscape. An SAP system landscape consists of a number of hardware and software components that depend on one another with regard to installation, software updates, and demands on interfaces. A SAP system landscape in this context is not a transport landscape, but – more or less – all SAP systems of one customer.
Note
Please note that this section on the System Landscape directory is only contained in the handbook, but not in the instructor's presentation. The reason is, that the significance of the SLD is far lower than in the past. For new systems, it is possible to connect SAP systems directly to the Landscape Management Database (LMDB), without involving the SLD.The SLD stores information about all the installable and installed components of an SAP system landscape. SAP provides information about installable SAP software, dependencies, and recommended scenarios. In addition, it regularly publishes updates on SAP Support Portal. SAP software components installed on SAP Systems (so called technical systems) are registered automatically and on a regular basis in the SLD; therefore, the SLD always contains up-to-date information about the installed SAP system landscape.
During Installation of a new SAP system you can select the Register in existing central SLD (default) function.
Usually there is one SLD per customer. In case of several independent SAP system landscapes, there is also the possibility to configure several SLDs and even forward the stored information to a central SLD.
The connected SAP systems actively push their information to the SLD. In AS ABAP-based SAP system this so-called SLD Bridge is defined in transaction RZ70..
The SLD can be configured and used in any AS Java-based SAP system, for example in the SAP Solution Manager Java. A better option would be, to install a dedicated, separate AS Java-based SAP system only for the SLD.
While the SLD only contains technical information about the SAP systems of the SAP system landscape, the Landscape Management Database (LMDB) contains more information.
The LMDB is part of the SAP Solution Manager ABAP system; it retrieves the technical SAP system information from the SLD as a basis for landscape data to manage SAP systems (so-called technical systems) in monitoring and maintenance processes. The LMDB acts as a single source of truth in the SAP Solution Manager system. As of SAP Solution Manager 7.1 SP04, the LMDB manages information for example about SAP systems and hosts.
Without a valid entry for an SAP system within LMDB, you cannot (for example) create a new Maintenance Transaction via Maintenance Planner for this SAP system. LMDB is required to patch and upgrade SAP systems using Maintenance Planner.
For primary information about LMDB see https://support.sap.com/en/tools/software-logistics-tools/landscape-management-process/database.html.
In addition to ensuring the lowest cost of ownership, a well-designed infrastructure improves the following system parameters:
Lower cost of ownership
Note
For more information, see SAP Library for installation guides on SAP Help Portal at https://help.sap.com.The technical infrastructure describes the technical setup of an AS ABAP-based SAP system. The technical setup includes the network layout, the server layout, the disk layout of the database, the type of computer interface used, and many more details.
The technical infrastructure influences these technical setup areas.
As shown in the figure, AS ABAP-based SAP systems use different ports for external communication. All these ports should be secured by some means, such as firewalls, routers, and the SAP router, to ensure the SAP system’s security. In addition, SAP systems use several internal connections to communicate with the database. The number of connections and the ports used depend on the type of database employed.
The figure shows only the AS ABAP-based SAP system ports. For AS Java-based SAP systems, ports 50000 and higher are used.
Note
For more information about ports used in the SAP environment and infrastructure security, see SAP Library for network security on SAP Help Portal at https://help.sap.com.
Note
For more information, see SAP Library for system sizing on SAP Help Portal at https://help.sap.com.The load between the application and database layer is considerable. As a result, SAP recommends offering a bandwidth of at least 100 megabits per second for the communication between application and database layer. It is usually not possible to separate the database by more than the LAN width from the application layer.
Note
For more information about the network layout for SAP servers, see SAP Note 21151 - Multiple Network adapters in SAP Servers and read the Network Integration of SAP Servers document.Databases of SAP systems are usually stored on disks combined with some Redundant Array of Inexpensive Disks (RAID) level (usually 1 or 5) or on Storage Area Networks (SANs). Databases used for SAP systems can hold up to several terabytes of business data because practically you are unable to restore a large database and you have to ensure that data loss is avoided under almost all circumstances. The disk layout for databases used for SAP systems affects not only the performance of SAP systems but also their reliability and availability.
| Database | Schema User | Other Users |
|---|---|---|
| SAP HANA | SAPHANADB | system |
| SAP ASE | SAPSR3/SAPSR3DB | sa, sapsso, sapsa, and so on |
| SAP MaxDB | sap<sapsid> | control, superdba, and so on |
| Oracle | SAP<SCHEMA_ID> | system and sys |
| MS SQL Server | SAP<SAPSID> | sa, <sid>adm, and SAPService<SID> |
| DB2 UDB | sap<sapsid> | db2<dbsid> |
| DB2 zOS | sap<sapsid> | See the installation guide |
| DB2 i (Series) | sap<sapsid> | <sid>OFR and see the installation guide |
Note
For more information about enhancing the security of the databases of your SAP system, read the following SAP Notes:
For SAP ASE: SAP Note 2008256 - How to reset master password for sapsso user - SAP ASE for BS
For SAP MaxDB read the "SAP MaxDB Security Guide": http://help.sap.de/saphelp_nw74/helpdata/en/44/bbe0dc91407006e10000000a155369/frameset.htm
For Oracle: SAP Notes 1622837 - Secure connection of AS ABAP to Oracle via SSFS and 926023 - Oracle database security
For MS SQL Server access http://help.sap.com/saphelp_nw74/helpdata/en/95/fb1f6ca5504992839b16370fdeb701/frameset.htm
Note
Multiple database users for SAP systems might be needed.Hint
The schema user for AS Java-based installations is sap<schema_id>db.For this training, we use different operating systems (Windows and Linux) and different databases (SAP HANA and SAP MaxDB). Most of the installation and patch procedures are not impacted by the type of operating system or database that you are using. However, some differences exist. For example, Oracle database systems are NOT installed during the installation of the SAP system using SWPM/SAPinst; instead they are installed in a separate step before starting SWPM/SAPinst. Also, the procedures for patching the different databases supported by SAP vary significantly. For example, patching SAP MaxDB, usually consists of three or four very easy activities and takes about 5-10 minutes, whereas patching an Oracle database requires a full, new installation of the database software (not of the SAP system), and might take some hours (including preparation).
Caution
Read the installation guide and related SAP Notes carefully. There are critical differences in the naming conventions. For example, for Microsoft SQL Server, user <sid>adm must be named using lowercase characters <sid>, such as tstadm, while user SAPService<SID> must be named using uppercase characters <SID>, such as SAPServiceTST.Log in to track your progress & complete quizzes