1564275 - How to Install an SAP System or SAP Components on Windows Using Virtual Host Names

SAP Knowledge Base Article

 

  1564275 - How to Install an SAP System or SAP Components on Windows Using Virtual Host Names Version   4     Validity: 17.06.2014 - active  

Language   English (Master)

Symptom How to install an SAP system or SAP components on Windows using virtual host names.

Cause

You want to use a virtual host name instead of a physical host name when installing your SAP system. Using virtual host names might be useful when you want to quickly move SAP servers or complete server landscapes to other new hardware without having to perform a reinstallation or complicated reconfiguration. Another reason might be the naming convention for DNS names specified in the security policy of your company – if, for example, an application must ru with a unique virtual host name. For more information about how to use virtual host names with SAP applications, see SAP note 1282975.

Resolution

The following procedure describes how to install a central or distributed SAP system with virtual host names in a non-high-availability environment. For more information about how to install a high-availability SAP system in a Windows Failover Cluster, see the relevant installation guide. Do not use th procedure to change an SAP system that was originally installed with physical host names to use virtual host names.

Preparing the Windows Operating System

Before you install your SAP system using a virtual host name, you must first prepare your operating system and check whether it is configured properly fo using virtual host names.  Prerequisite:

Disable the dynamic DNS update on your network card (the box must not be enabled):

If you enable the box, the Windows DNS client service registers both IP addresses for the Windows host name in DNS! This results in naming resolution  problems! 1. Define a new DNS A-record for each virtual host name. Example for a DNS A-record: 10.67.4.28  enterprise We do not recommend using DNS CNAMES. 2. Make sure that the reverse DNS lookup for this new name works properly. 3. Add the IP address to the network card configuration.

4. Check whether the IP address was successfully bound by opening a command prompt and entering the ipconfig command.

5. Check whether the reverse DNS lookup works correctly with the nslookup command (for example, nslookup ). 6. Check whether the local IPv4 address is returned with the ping command (for example, ping –a enterprise). 7. To use the virtual hostname enterprise, configure the Windows operating system as follows: Add the value DisableStrictNameChecking to the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters a. Add a value DisableStrictNameChecking of type DWORD set to 1. b. To apply the changes, either reboot your system or restart the Windows Server service without rebooting. c. Add the value BackConnectionHostnames: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 d. Add the new multi-string value BackConnectionHostNames. Enter the fully qualified domain name (FQDN) (in our example: enterprise.wdf.sap.corp) and the short name.

To use virtual host names, you also have to add the hostname to the local \etc\hosts file: %windir%\system32\drivers\etc\hosts

    8. Check whether the virtual host names work properly in Windows. If they do not work properly, you get an Access denied error. In this case, correct the registry keys and values. Use the following options to perform the checks: ¡ Enter the command: net view \\virtualhostname If you get the message Access denied, either the registry keys are not correctly set, or you have to reboot your Windows operating system.

¡

¡

Use the net view \\virtualhostname command from other servers. If you get the error A duplicate name exists on the network, the key DisableStrictNameChecking is not correctly set. Use the SAP MMC and connect to computer virtualhostname: a. Open the SAP MMC. b. Select File –> Add/remove Snap-in … c. Select Computer Management and choose Add. d. Click OK.

Installing Your SAP System Using a Virtual Host Name 1. Start SAPinst from a command prompt and execute the following case-sensitive command: SAPINST_USE_HOSTNAME=

2. Proceed as described in the installation guide. After the installation has finished successfully, your system is available in the SAP MMC. The system uses the virtual host name. In our example, the host name is PWDF1000 and the virtual host name is ENTERPRISE.

  

See Also Examples of SAP Profiles Where the Virtual Host Name Must Be Found As of SAP NetWeaver 7.1 EHP1, the start profile no longer exists. It has been merged with the instance profile. In this example we still use separate start and instance profiles.

Example of start profile: SAPSYSTEMNAME = KAT SAPGLOBALHOST = enterprise SAPSYSTEM = 00 INSTANCE_NAME = DVEBMGS00 DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64 DIR_EXECUTABLE = $(DIR_INSTANCE)\exe SAPLOCALHOST = enterprise DIR_PROFILE = $(DIR_INSTALL)\profile _PF = $(DIR_PROFILE)\KAT_DVEBMGS00_enterprise #----------------------------------------------------------------------# Copy SAP Executables #----------------------------------------------------------------------Start_Program_00 = immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) #----------------------------------------------------------------------# Start ABAP database #----------------------------------------------------------------------_DB = $(DIR_CT_RUN)\strdbs.cmd Start_Program_01 = immediate $(_DB) KAT #----------------------------------------------------------------------# Start SAP message server #----------------------------------------------------------------------_MS = $(DIR_EXECUTABLE)\msg_server$(FT_EXE) Start_Program_02 = local $(_MS) pf=$(_PF) #----------------------------------------------------------------------# Start application server #----------------------------------------------------------------------_DW = $(DIR_EXECUTABLE)\disp+work$(FT_EXE) Start_Program_03 = local $(_DW) pf=$(_PF) #----------------------------------------------------------------------# Start internet graphics server #----------------------------------------------------------------------_IG = $(DIR_EXECUTABLE)\igswd$(FT_EXE) Start_Program_04 = local $(_IG) -mode=profile pf=$(_PF) Example of instance profile: SAPSYSTEMNAME = KAT SAPGLOBALHOST = enterprise SAPSYSTEM = 00 INSTANCE_NAME = DVEBMGS00 DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64 DIR_EXECUTABLE = $(DIR_INSTANCE)\exe SAPLOCALHOST = enterprise rdisp/wp_no_dia = 10 rdisp/wp_no_btc = 3 icm/server_port_0 = PROT=HTTP,PORT=80$$ #--------------------------------------------------------------------# SAP Message Server parameters are set in the DEFAULT.PFL #--------------------------------------------------------------------ms/server_port_0 = PROT=HTTP,PORT=81$$ rdisp/wp_no_enq = 1 rdisp/wp_no_vb = 1 rdisp/wp_no_vb2 = 1 rdisp/wp_no_spo = 1 Example of default profile: SAPDBHOST = enterprise dbms/type = mss dbs/mss/server = enterprise dbs/mss/dbname = KAT dbs/mss/schema = kat SAPSYSTEMNAME = KAT SAPGLOBALHOST = enterprise SAPFQDN = wdf.sap.corp SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN) #----------------------------------------------------------------------# SAP Message Server for ABAP #----------------------------------------------------------------------rdisp/mshost = enterprise rdisp/msserv = sapmsKAT rdisp/msserv_internal = 3900 login/system_client = 001 

Keywords

virtual host name, hostname, alias name, c-name

Header Data Released On Release Status Component

17.06.2014 11:08:57 Released to Customer BC-OP-NT Windows

Other Components BC-OP-NT-CLU Please use BC-OP-NT Priority Category

Normal How To

Product This document is not restricted to a product or product version