SAP ERP Central Component Installation – General Post-Installation 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 post-installation, which is the fourth 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 provides information on how to perform the post-installation steps of your SAP System. You perform the following steps:

1. Starting and Stopping the SAP System

   Check that you can start and stop the SAP System after the installation with the SAP Microsoft Management Console (SAP MMC). With a newly installed MMC you can start or stop installed SAP System administration, you can start or stop the entire system from a single host.

   Prerequisites:

   You have logged on to the SAP System host as user [sapsid]adm.

2. Logging On to the SAP System

   You need to check that you can log on to the SAP System using the following standard users. ABAP users:

   User	User Name	Client
   SAP System user	SAP*	000, 001, 066
   	DDIC	000, 001

   Prerequisites:
   

   • You have already started the SAP system.

   • You have already installed a front end.




3. Installing the SAP License

   You must install a permanent SAP license. When you install your SAP System, a temporary license is automatically installed. This temporary license allows you to use the system for only four weeks from the date of installation. Before the temporary license expires, you must apply for a permanent license key from SAP. It is recommended that you apply for a permanent license key as soon as possible after installing your system.

4. Installing the SAP Online Documentation

   SAP currently provides an HTML-based solution for the online documentation, including the Application Help, Glossary, Implementation Guide (IMG), and Release Notes. You can display the documentation with a Java-compatible web browser on all front-end platforms supported by SAP. Install the SAP online documentation in your SAP System as described in the README.TXT file contained in the root directory of the online documentation DVD, delivered as part of the installation package.

5. Configuring Remote Connection to SAP Support

   SAP offers its customers access to support and a number of remote services such as the EarlyWatch Service or the GoingLive Service. Therefore, you have to set up a remote network connection to SAP. For more information, see SAP Service Marketplace at service.sap.com/remoteconnection.

6. Performing Initial ABAP Configuration

   Here you find information about how to perform initial ABAP system configuration.

   • Go to the following place in the SAP Library:

     help.sap.com/nw2004s - SAP NetWeaver Library - SAP NetWeaver by Key Capability

   • Check the documentation on the following configuration steps:

     • Configuring the transport management system

       For more information, see Solution Life Cycle Management by Key Capability - Software Life Cycle Management - Software Logistics - Change and Transport System.

     • Performing basic operations

       For more information, see Solution Life Cycle Management by Key Capability - System Management:

       Operation	Section in SAP Documentation
       Set up operation modes – transaction RZ04	Configuration - Operation Modes
       Set up logon groups – transaction SMLG	Configuration - Logon Load Distribution - SAP Logon
       Set up administrators	Background Processing - Authorizations for Background Processing
       Schedule background jobs	Background Processing
       Install a printer	SAP Printing Guide
       Configure the system log	Tools for Monitoring the System - System Log - Configuring the System Log

     • Configuring work processes

       SAPinst install SAP Systems with a minimum number of work processes. This is only an initial configuration to get you started after the installation. It is not detailed enough for a production system because the optimal number for each type of work process depends on the system resources and on the number of users working in each SAP System application. For a detailed configuration contact SAP Technical Consulting. For more information about instance profiles, which is where work processes are defined, see Solution Life Cycle Management by Key Capability - System Management - Configuration - Profiles - Profile Files - Instance Profiles.

     • Installing languages and performing language transport

       • Installing languages using transaction I18N:

         • If you want to use English only, you must activate the default language once.
         • If you want to use languages other than English, you must install them and activate the language settings.

         For more information on configuring the language settings, see the online documentation in transaction I18N - I18N Menu - I18N Customizing.

       • Performing language transport using transaction SMLT:

         For more information on performing the language transport using transaction SMLT, see Solution Life Cycle Management by Key Capability - Software Life Cycle Management - Software Logistics - Change and Transport System - Language Transport.

     • Activating and configuring the integrated Internet Transaction Server (ITS)

       • For more information on activating and configuring the ITS, which is installed automatically with the SAP kernel, see Application Platform by Key Capability - ABAP Technology - UI Technology - ITS / SAP@Web Studio (BC-FES-ITS).

       • For more information about ITS, see SAP Note 742048, where you can find the necessary information if you do not want to use the ITS.

     • Maintaining address data

       You must maintain your company address to create ABAP system users. For more information on maintaining the company address in your SAP System using transaction SU01, see Application Platform by Key Capability - Business Services - Business Address Services (BC-SRV-ADR) - Addresses in User Administration - Maintenance of Address Data.

     • Configuring business applications

       For more information about how to prepare the SAP System for using business applications, which includes customizing the ABAP system and the business components, see Solution Life Cycle Management by Key Capability - Customizing.

7. Applying the Latest Kernel and Support Packages

   You must always replace the installed kernel with the latest kernel from SAP Service Marketplace. In particular, you must replace the installed kernel if:

   • You installed the kernel executables locally on every host.

   • Your central instance host runs on a different operating system than your dialog instance host.

   For more information about how to download a kernel, see SAP Note 19466.

   You use the Support Package Manager to apply the latest ABAP support packages. For more information about the Support Package Manager and how to use it, see help.sap.com/nw2004s - SAP NetWeaver Library - SAP NetWeaver by Key Capability - Solution Life Cycle Management by Key Capability - Software Life Cycle Management - Software Maintenance - Support Package Manager.

8. Performing a Full Installation Backup

   You must perform an offline full backup at the end of the installation.

   Prerequisites:

   • You have completed client maintenance (for example, client copy).

   • You have stopped:

     • The SAP System
     • SAP-related services (SAP[SAPSID]-[instance] and SAPOSCol)
     • The database

   • You are logged on as user [sapsid]adm.

   • You have shut down the SAP System and database.

9. Single Sign-On with Microsoft LAN Manager SSP

   Single Sign-On (SSO) is a secure method of logging on to the SAP System that simplifies the logon procedure without reducing security. When your system is configured for SSO, an authorized user who has logged on to the operating system can access the SAP System simply by selecting it in the SAP logon window or clicking the shortcut. No SAP System user name or password is necessary. SSO makes it significantly easier for you to manage SAP System user.

   This section describes the option that is the easiest to implement when using a full 32-bit Microsoft Windows landscape. It is a tailored version for SSO with Secure Network Communication (SNC), which uses Microsoft’s domain authentication, LAN Manager Security Service Provider (NTLM SSP). For more information on SNC, see the SNC User’s Guide in the SAP Service Marketplace at service.sap.com/security.

   • Typically, SNC requires an external security product that adheres to the Genuine Security Service API V2 (GSS-API V2) interface and that has been certified by the SAP Software Partner Program. However, in this scenario, SAP provides a library that adheres to the GSS-API V2 interface on one side and that communicates with Microsoft’s NTLM SSP on the other. Since NTLM SSP is already built into Microsoft Windows 32-bit platforms, you do not need to purchase an additional security product to use SSO.

     Note that the Microsoft NTLM SSP only provides authentication based on a challenge-response authentication scheme. It is does not provide data integrity or data confidentiality protection for the authenticated network connection. All third-party SNC certified security products offer data integrity and privacy protection. If you want to use these security features, you have to obtain a certified security product. If you use Windows 2000 and higher, alternatively you can use Microsoft Kerberos SSP instead of the NTLM SSP for authentication. For more information, see Single Sign-On with Microsoft Kerberos SSP on the next section.

   • A pure Microsoft Win32 environment is required (Windows 9x, Windows ME, Windows NT, Windows 2000 and higher). The Microsoft NTLM SSP is not available for UNIX or any other operating system.

   • Bi-directional trust between windows domains is required if there are separate domains for users, front-end PC’s, and SAP application servers.

   • The GSS-API V2 library wrapper (gssntlm.dll) must be installed on every application server. For more information about how to get the gssntlm.dll file, see SAP Note 595341.

   • The GSS-API V2 library wrapper must also be installed on every front-end PC.

   • It is recommended that you use 7-bit ASCII character set for all Windows user IDs.

   • When the code page of the SAP System is different from the code page on the Windows machines, it is not possible to enter Windows user IDs that contain 8-bit characters into the USRACL table (for example, by calling transaction SU01). The combination of Windows ANSI (=ISO Latin 1) and the default SAP code page 1100 provides the same encoding of 8-bit characters and permits the use of 8-bit characters with gssntlm.dll.

   • For more information on how to improve the security of your system with third party products, see help.sap.com/nw2004s - SAP NetWeaver Library - SAP NetWeaver by Key Capability - Security - Network and Transport Layer Security - Secure Network Communications.

10. Single Sign-On with Microsoft Kerberos SSP

    Kerberos Single Sign-On (SSO) is a secure method of logging on to the SAP System that simplifies the logon procedure without reducing security. It is suitable if you use Windows 2000 and higher in your system landscape. When your system is configured for SSO, an authorized user who has logged on to Windows can access the SAP System simply by selecting it in the SAP logon window or clicking the shortcut. No SAP System user name or password is necessary. SSO makes it significantly easier for you to manage SAP System user.

    The Application Programming Interface (API) and Kerberos provide the security required for authentication. The advantage of the Kerberos SSO solution is that the security information that has to be exchange between the SAP front-end and the SAP application server is encrypted. In contrast, encryption is not implemented for SSO with Microsoft NTLM SSP, which is based on the Generic Security Service API (GSS-API) interface. When using gsskrb5.dll, the Microsoft Kerberos Security Service Provider (SSP) is interoperable with Kerberos implementations from other vendors and suppliers. To use SSO with application server on UNIX and Windows front-end with gsskrb5.dll, you might have to purchase a Kerberos implementation for the UNIX machines.

    Prerequisites:

    SSO based on Kerberos can only be set up for users that are members of a Windows 2000 and higher domain.

11. Accessing Configuration Documentation in the SAP Solution Manager

    To access configuration documentation in the SAP Solution Manager, you have to connect your newly-installed SAP System to the SAP Solution Manager. For SAP NetWeaver 2004s usage types you can also find configuration documentation in the Implementation Guide at: help.sap.com/nw2004s - SAP NetWeaver Library - Technology Consultant’s Guide.

    Prerequisites:

    • You have installed an SAP Solution Manager system as described in the documentation Installation Guide – SAP Solution Manager [3.2 or 4.0] on [OS]: [Database].

    • You have connected your SAP System to the SAP Solution Manager as described in the documentation Configuration Guide – SAP Solution Manager [3.2 or 4.0].

    For more information, see SAP Service Marketplace at service.sap.com/instguides - SAP Components - SAP Solution Manager - Release [3.2 or 4.0].

12. Implementing ERP ABAP Add-On Components

    You can install several Add-On Components to your ERP ABAP system. You can find a detailed description on how to implement each available ERP Add-On Components in the related SAP Notes on SAP Service Marketplace at service.sap.com/erp-inst - MySAP ERP [2004 or 2005] - SAP Notes.

13. Ensuring User Security

    You need to ensure the security of the user that SAPinst creates during the installation. For security reasons, you also need to copy the installation directory to a separate, secure location – such as a DVD – and then delete the installation directory. In all cases, the user ID and password are only encoded when transported across the network. Therefore, using encryption at the network layer, either by using the Secure Sockets Layer (SSL) protocol for HTTP connections, or Secure Network Communications (SNC) for the SAP protocols dialog and RFC, is recommended. Make sure that you perform this procedure before the newly installed SAP System goes into production.

    Prerequisites:

    If you change user passwords, be aware that SAP System users might exist in multiple SAP System clients (for example, if a user was copied as part of the client copy). Therefore, you need to change the passwords in all the relevant SAP System clients.

    Procedure:

    For the users listed below, take the precautions described in the relevant SAP security guide, which you can find on SAP Service Marketplace at service.sap.com/securityguie:

    ABAP Users

    User	User Name	Comment
    SAP System user	SAP*	User exists at least in SAP System clients 000, 001, and 066
    	DDIC	User exists at least in SAP System clients 000 and 001
    	EARLYWATCH	User exists at least in SAP System clients 066.
    	SAPCPIC	User exists at least in SAP System clients 000 and 001.

Read more...

SAP ERP Central Component Installation – General Installation 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 installation, which is the third 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 perform a standard installation of your SAP System. You have to complete the planning and preparation activities, before you start the installation. You perform the following steps:

1. Install the MS SQL Server database software.

   The SQL Server software has to be installed on each host in the system where you intend to set up an SAP instance. Depending on the type of host involved, you either have to install the software for the database client or server.

2. Install the SAP System using SAPinst.

   • Running SAPinst on Windows.

     This step tells you how to install an SAP System with SAPinst. SAPinst includes a SAPinst GUI and a GUI server, which both use Java. Note the following information about SAPinst:

     • When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects to the GUI server with a secure SSL connection, and the GUI server connects to SAPinst.

     • SAPinst normally creates the installation directory sapinst_instdir, where it keeps its log files, and which is located directly in the Program Files directory. If SAPinst is not able to create sapinst_instdir there, it tries to create sapinst_instdir in the directory defined by the environment variable TEMP. Keep all installation directories until the system is completely and correctly installed.

     • SAPinst creates a subdirectory for each installation service called [sapinst_instdir]\[installation_service], which is located in %Program Files%\sapinst_instdir.

     • The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP, TMPDIR, or SystemRoot). These executables are deleted after SAPinst has stopped running. Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them. The temporary directory also contains the SAPinst Self-Extractor log file dev_selfex.out, which might be useful if an error occurs. If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.

       Prerequisites:

     • You are logged on as a user with the required rights and privileges to install the SAPinst tool and the SAP System.

     • You need at least 50 MB of free space in the installation directory for each ABAP installation service. In addition, you need 60-200 MB of free space for the SAPinst executables.

     • If you are installing a second or subsequent SAP System into an existing database, make sure that the database is up and running before starting the installation.

   • Using SAPinst GUI.

     The following table shows the most important functions that are available in SAPinst GUI:

     Button / Function Key / Menu Entries	Description
     F1	Displays detailed information about each input parameter.
     Exit	Cancels the installation with the following options: - Stop Stops the installation without further changing the installation files. You can restart SAPinst to continue the installation later from this point. - Continue Continues the installation.
     Log off	Stops the SAPinst GUI, but the SAPinst and the GUI server continue running.
     Retry	Performs the installation step again (if an error has occurred)
     Stop	Stop the installation without further changing the installation files. You can continue the installation later from this point.
     Continue	Continues with the option you have chosen before.

   • Interrupted Installation with SAPinst.

     The SAP System installation might be interrupted for one of the following reasons:

     • An error occurred during the dialog or processing phase

       SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appear. The dialog box contains a short description the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

     • - You interrupted the installation by choosing Exit in the SAPinst menu.

     The following table describes the options in the dialog box:

     Option	Definition
     Retry	SAPinst retries the installation from the point of failure without repeating any the previous step. This is possible because SAPinst records the installation progress in the keydb.xml file. SAP recommended that you view the entries in the log files, try to solve the problem, and then choose retry. If the same or different error occurs again, SAPinst displays the same dialog box again.
     Stop	SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server. SAPinst records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps.
     Continue	SAPinst continues the installation from the current point.

     The following table describes the steps to restart installation, which you stopped by choosing stop, or to continue an interrupted installation after an error situation:

     Alternative	Behavior
     Run a new installation	SAPinst does not continue the interrupted installation. Instead, it moves the content of the old installation directory and all specific-installation files to the backup directory. Afterwards, you can no longer continue the old installation. For the backup directory, the following naming convention is used: [log_day_month_year_ hours_minutes_seconds] (for example, log_20_Dec_2007_18_21_28)
     Continue old installation	SAPinst continues the interrupted installation from the point of failure.

Read more...

SAP ERP Central Component Installation – General Preparation 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 preparation, which is the second 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 prepare the standard installation of your SAP System. You have to complete the following preparations:

1. Check the hardware and software requirements using the Prerequisites Checker.

   You check the hardware and software requirements for your operating system (OS) and the SAP instances using the Prerequisite Checker tool. The Prerequisite Checker provides information about the requirements that you need to meet before you start the installation. The values that are checked by the Prerequisite Checker apply for the installation of development system or quality assurance system. To get precise sizing values for the production system, you have to use the SAP Quick Sizer tool that is available on SAP Service Marketplace at service.sap.com/sizing. Or you can contact your hardware vendor, who can analyze the load and calculates the requirements.

2. Check for the Windows file system.

   You need to check that you are using the Windows File System (NTFS) on host where you want to install the SAP System and database. NTFS support full Windows security and long file names. You must use NTFS for an SAP System installation. Do not install the SAP directories on a FAT partition.

3. Check the Windows domain structure.

   You do not need this step for a local installation. In Windows, you can implement either of the following domain models for the SAP System:

   • Extra domain. The SAP System is embedded in its own domain, which is specially defined for SAP. A second domain exists for the user accounts. In Windows, the SAP domain and user domain must be incorporated in a domain tree. In this tree, the user accounts must form the root domain and the SAP domain must be a child domain of this.
   • Single domain. The SAP System and the user accounts are included in a single domain.

   For a domain installation, SAP recommended that you check that all SAP System and database hosts are members of a single Windows domain. SAP recommended this for all SAP System setups.

4. Reduce the size of the file cache (if required).

   The Windows file cache directly competes with SAP programs for memory. Therefore, you should adjust the file cache.

5. Grant user rights for the installation (if required).

   You have to grant the required rights and privileges that authorize you to install the SAPinst tool and the SAP System. If you attempt the installation without the required authorization, the system aborts. If necessary, you have to ask the system administrator to grant you the necessary authorization before you start the installation.

6. Perform a domain installation without being a domain administrator (if required).

   If you are not granted domain administrator rights, you can perform the installation as a domain user who is a member of the local Administrators group. In this case, the domain administrator must prepare the system for you appropriately. The domain administrator has to:

   • Create the new global group SAP_[SAPSID]_GlobalAdmin.
   • Create the two new SAP System users [sapsid]adm and SAPService[SAPSID].
   • Add the users [sapsid]adm and SAPService[SAPSID] to the newly created group SAP_[SAPSID]_GlobalAdmin.

7. Prepare the SAP System transport host.

   You need to prepare one transport host in the SAP System. This host has the function of controlling the import or export of files between the current SAP System and other SAP System (for example, a test or development system). The transport host use the usr\sap\trans directory to temporarily store files that have been exported from one system and waiting to be imported into another system. Depending on your requirements, you can decide to use the central instance host, the dialog instance host, or any other host as the transport host.

8. Install the SAP front-end software.

   For the installation, make sure that the front-end software is installed on at least one host machine in your system environment. To simplify the administration of your SAP System, SAP recommended you install the software on the central instance host. With the SAP front-end installation software, SAPSetup, you can optimize the deployment of SAP GUI to thousands of clients. You can easily tailor installation package to match your requirements, distribute patches, and set up automatic update processes for your clients.

9. Generate the SAP Solution Manager Key.

   You need to generate the Solution Manager Key because SAPinst prompts for it during the input phase of the installation.

10. Install the Java Runtime Environment.

    You need to prepare your system for SAPinst. This includes the installation of a Java Runtime Environment (JRE), which is required both for SAPinst and the SAPinst GUI. If required, you can perform a remote installation using a standalone SAPinst GUI on a separate Windows or UNIX host. This lets you perform the installation on a remote host, controlling it with the SAPinst GUI from a local host.

11. Prepare the installation DVDs.

    You use this procedure to prepare the installation DVDs. Normally you obtain the installation DVDs as part of the installation package that you receive from SAP. However, you can also download the installation DVDs from SAP Service Marketplace. SAP recommended that you make all required DVDs available in parallel. The Export DVD and RDBMS DVD (if relevant) must be available in parallel. If you copy the installation DVDs to disk, make sure that the paths to the location of the copied DVDs do not contain any blanks. If you use network drives for mounting the export DVDs, make sure that the [sapsid]adm user has access to the UNC paths of the network drives. If the user does not yet exist, you have to create it manually before you install the database instance.

12. Download the installation DVDs from SAP Service Marketplace (if required).

    You normally obtain the installation DVDs as part of the installation package from SAP. However you can also download installation DVDs from SAP Service Marketplace at: service.sap.com/swdc à Downloads à Installations and Upgrades à Entry by Application Group à [your solution] à [release of your solution] à [your operating system] à [your database]. If you download installation DVDs, note that DVDs might be split into several files. In this case, you have to reassemble the required files after the download. To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you can find on SAP Service Marketplace at service.sap.com/swdc. You need at least SAPCAR 700 or SAPCAR 640 with patch level 4 or higher because older version of SAPCAR can no longer unpack current SAR files.

Read more...

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.

Read more...