SAP ERP Central Component Installation – General Planning Guide

This documentation contains general information about SAP System installation – SAP ERP Central Component 2004 SR1 (SAP ECC 5.0), SAP ERP Central Component 2005 SR1 (SAP ECC 6.0) – on Windows when your database is MS SQL Server. It focuses on the ABAP part of the installation and covers the planning, which is the first section of the first part of the installation. For more information and for the detailed installation procedure see the documentation on SAP Service Marketplace at service.sap.com/erp-inst.

This section tells you how to plan the standard installation of your SAP System. You have to complete the following planning activities:

1. Plan your SAP System landscape.

   You plan your system landscape according to the Master Guide. SAP recommended that you read the Technical Infrastructure Guide which is available on SAP Service Marketplace.

2. Choose your basic system variants.

   Mandatory instances of an ABAP system are the central instance and the database instance. Optionally, you can install one or more dialog instances and gateway instances on a separate host.

3. Plan how to distribute the instances to hosts.

   You use SAPinst to install SAP instances as a:

   • Central system on a single host. Run SAPinst and install all instances on a one host.
   • Distributed system on several hosts. Specify or create (if not available) a shared transport directory, run SAPinst and prepare the global host, run SAPinst and install the Database instance on the database host, run SAPinst and install the Central instance on the global host, and run SAPinst and install the Dialog instance(s), if required, on the dialog instance host(s).

4. Plan your system configuration.

   • Plan the distribution of your SAP System instances within the basic system variants.
   • Work out a high-performance configuration based on sizing information that reflects the system workload.
   • Decide whether to perform a domain or local installation.

5. Identify basic SAP System parameters.

   The table below list the basic system parameters that you need to determine before installing your SAP System.

   Parameters	Description
   SAP System ID [SAPSID]	The SAP System ID identifies the whole SAP System. Choose your SAP System ID carefully. You can not change the SAP System ID after installation. Make sure that your SAP System ID: - Is unique throughout your organization - Consists of exactly three alphanumeric characters - Contains only uppercase letters - Has a letter for the first character - Does not including any of the following, which are reserved IDs: ADD ALL AND ANY ASC COM DBA END EPS FOR GID IBN INT KEY LOG MON NIX NOT OFF OMS RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID USR VAL
   Database ID [DBSID]	The Database ID identifies the database instance. It can be different from the SAP System ID.
   Instance Number	Technical identifier for internal processes, consisting of a two-digit number from 00 to 97. The instance number must be unique on a host. That is, if more than one SAP instance is running on the same host, these instances must be assigned different number. Do not use 43, 60, and 89 for the instance number.
   Name of Instance Host	Host name of the specific instance. Make sure that your name of instance host: - Contains only alphanumerical string of alpha characters [A-Z] and [a-z] and digits [0-9] and the hyphen (or minus) character “-“ - Up to 13 characters maximum length of the hostname. - Beginning with an alpha character - Must not begin with S-[0-9] (e.g. hostname S-12345 is not allowed) - Must be considered “case sensitive”.
   Message Server Port	Port number of the SAP Message Server, if you do not specify a value, the default port number is used. The message port number must be unique for the SAP System on all hosts. The default value for the external ABAP message port is 36[nn], and 36[nn] for the internal ABAP message port, where [nn] is the instance number of the ABAP message server instance.
   Windows Domain	SAPinst creates the [sapsid]adm and SAPService[SAPSID] users in the domain specified. Make sure that you have domain administrator rights before you start the installation. If not, you have to create these users manually before starting the installation.
   ABAP RFC User, Password	The user DDIC is normally used for the RFC logon ABAP RFC user. It has the required special administrator rights. Alternatively, you can use user SAP*.
   SAP Solution Manager Key	To perform the installation of your SAP System, you need to generate a SAP Solution Manager key, which the installation requires to continue.
   SLD HTTP Host	The hostname of the System Landscape Directory (SLD)
   SLD HTTP Port	The HTTP port of the Java system where the SLD is installed. The following naming convention applies: 5[instance_number]00.
   SLD Data Supplier User and Password	- If you want to install a local SLD, SAPinst creates these user during the installation - If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier and SLD ABAP API User and password of the central SLD during the installation.
   SLD ABAP API User and Password
   RFC User and Password	The ABAP RFC user of the SLD.
   SLD Gateway Host	The host on which the gateway instance of the SLD is running.
   SLD Gateway Instance Number	The instance number of the gateway instance of the SLD.
   SAP System Client	The client in which the ABAP RFC user exists.
   Installation Drive	Base directory for the SAP System. Do not add [SAPSID] as a subdirectory because the SAP System adds this directory automatically.
   Database Instance Name	MS SQL Server instance name. You can also specify a remote database instance. For named instance enter [hostname]\[instance_name].

6. Decide whether you want to use Unicode and multi-language support.

   The default for all new installation is Unicode. Unicode is the recommended system type for all SAP System that deploys Unicode-enabled solution and components. SAP supports more than 30 languages in non-Unicode systems, but due to the technical limitations of non-Unicode code pages, only certain combinations of languages can be used without restrictions.

7. Make sure that the SAP Solution Manager is available in your SAP System landscape.

   The SAP Solution Manager is the strategic application management platform for SAP customer and the collaboration between the customer and SAP. To ensure the availability of this application management platform a SAP Solution Manager system is technically required to perform any upgrade or installation for all SAP software. During the installation/upgrade process you are prompted to enter the SAP Solution Manager Key.

   This key is needed to proceed with the installation. Without this key, the installation can not continue. You may generate all needed keys for your entire system landscape (development, quality assurance, and production system) in one SAP Solution Manager System. In case you plan to install several solution landscapes (for example in different countries), one SAP Solution Manager System is still sufficient.

   You require at least SAP Solution Manager 3.2 with Support Package 8 or SAP Solution Manager 4.0. If required, you can install SAP Solution Manager.