Upload
sunny83sap
View
136
Download
4
Tags:
Embed Size (px)
DESCRIPTION
Windows How to Guide
Citation preview
How-To Guide
SAP Landscape Virtualization Management
Document Version: 1.0 2014-03-24
CUSTOMER
Adaptive Enabling an SAP System Windows/MSSQL/NetApp
2
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Typographic Conventions
Typographic Conventions
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions.
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they
appear in the documentation.
Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.
EXAMPLE Keys on the keyboard, for example, F2 or ENTER .
Adaptive Enabling an SAP System
Document History
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 3
Document History
Version Date Change
1.0 2014-03-24 Initial Version
4
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Table of Contents
Table of Contents
1 Abstract ........................................................................................................................................................... 6
2 Setup ................................................................................................................................................................ 7
3 Windows Users and Groups of SAP Systems ............................................................................................. 8 3.1 Distributed Installation ............................................................................................................................................ 8 3.2 Access Rights to SAP Directories and File Resources ....................................................................................... 10
4 Installing a 'hello world' Adaptive Enabled SAP System ......................................................................... 11
5 Software Provisioning Manager Installation Preparations .................................................................... 12
6 Windows Computer System Preparation .................................................................................................. 14
7 MSSQL Server Computer System Preparation ........................................................................................ 15
8 NetApp Windows Computer System Preparation .................................................................................... 16
9 Software Provisioning Manager Post Installation Steps ........................................................................ 17 9.1 Access rights handling for mounted LUNS under Windows .............................................................................. 17 9.2 Registry Entries and Important Environment Variables .................................................................................... 19
10 Manual Relocate ........................................................................................................................................... 22 10.1 Manual Activities on Host A .................................................................................................................................. 22
10.1.1 Stopping SAP Instances ....................................................................................................................... 22 10.1.2 Stopping Database ............................................................................................................................... 22 10.1.3 Unregistering SAP Instance Agents .................................................................................................... 23 10.1.4 Detaching Database.............................................................................................................................. 23 10.1.5 Unmounting LUNS ................................................................................................................................ 24 10.1.6 Unbinding Virtual IPs/Hostnames ...................................................................................................... 24
10.2 Manual Activities on Host B .................................................................................................................................. 24 10.2.1 Binding Virtual IPs/Hostnames ........................................................................................................... 25 10.2.2 Mounting LUNS ..................................................................................................................................... 25 10.2.3 Attaching Database .............................................................................................................................. 25 10.2.4 Starting Database ................................................................................................................................. 26 10.2.5 Registering SAP Instance Agents ........................................................................................................ 26 10.2.6 Starting SAP Instances ......................................................................................................................... 26
Adaptive Enabling an SAP System
Table of Contents
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 5
11 Managing Systems using LVM .................................................................................................................... 27
12 Open Issues .................................................................................................................................................. 28
13 Appendix I: saphostctrl command line interface .................................................................................... 29
14 Appendix II: sapcontrol command line interface .................................................................................... 32
15 Appendix III: sapacosprep command line interface.................................................................................35
16 Appendix V: Creating LUNS with NetApp SnapDrive .............................................................................. 37
17 Appendix VI: SAP hosts during relocation process ................................................................................ 43
18 Appendix VII: System MGL ......................................................................................................................... 44
19 Appendix VIII: Avoiding "SAPGLOBALHOST first" problem during preparation ................................. 47
20 References .................................................................................................................................................... 48 20.1 SAP Notes for Windows as an OS for Managed Systems ................................................................................. 48 20.2 SAP Notes for MSSQL .......................................................................................................................................... 48 20.3 SAP Notes with Relevant Network Topics .......................................................................................................... 49
21 Important Disclaimers on Legal Aspects ................................................................................................. 50
6
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Abstract
1 Abstract
In this paper we provide guidance in setting up an adaptive enabled landscape when the managed operating
system (OS) is Windows. We use the installation of a hello world adaptive enabled 7.11 ABAP system as
guidance through the general scenario. In the end we guide you through a scenario that allows you to manually
test the ability to relocate your system. That scenario should be executed before you start to manage an adaptive
enabled SAP system using SAP Landscape Virtualization Management. The paper is a set of governance rules for
an adaptive Windows landscape.
Adaptive Enabling an SAP System
Setup
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 7
2 Setup
Plan the landscape virtualization management (LVM) landscape with managed computer systems and SAP
systems very carefully.
In general there exist two ways to adaptive enable an SAP system:
Installing adaptively right from the start.
Creating a homogeneous system copy in a way that adaptively enables the system. This option is not
described in this document!
An adaptive installation has in general 4 dimensions. In this document we restrict the 4 dimensions to the
following:
Dimension Restriction
Operating System Windows Server 2003 x86 64 SP2
(most prominent Microsoft server version currently
in use for NetWeaver 7.11, for your SAP system
consult the PAM and the latest SP for your Windows
version.)
Database MSSQL 2005 SP3
SAP System PI EHP 1 SP0 ABAP WEB AS
Filer Software NetApp SnapDrive 6.0.2.24.16, Server 6.0.2
Caution
Ensure that you do not skim over the referenced documents and information in this guide.
We only support Windows as OS for LVM managed hosts and SAP systems under the following prerequisites:
The resources are part of a Windows domain. You must set up a Windows domain controller.
Only domain OS users for the SAP system (adm and SAPService) are supported.
Start the software provisioning manager as a domain administrator to create users in the Active Directory.
The Windows domain works as a directory service.
Usually you can rely on software provisioning manager to create the necessary users, groups and necessary
rights on the initial installation host and in the domain.
8
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Windows Users and Groups of SAP Systems
3 Windows Users and Groups of SAP Systems
It is important to have an overview of the relevant users and groups. Software provisioning manager supports
installation types for standard systems and distributed systems. Standard systems are not supported for
adaptive enabled systems.
For more information about installing SAP systems based on SAP NetWeaver 7.1 and higher using software
provisioning manager, see SAP Service Marketplace at
http://service.sap.com/~sapidb/011000358700000828172012E.
3.1 Distributed Installation
An SAP system consists of SAP instances. An SAP instance is a group of processes that are started and stopped
at the same time. In a distributed system, every instance can run on a separate host.
Software provisioning manager creates the following users and groups:
Adaptive Enabling an SAP System
Windows Users and Groups of SAP Systems
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 9
user
\sapadm
group
\SAP_SAP_LocalAdmin
group
\SAP_LocalAdmin
group
\SAP_SAP_GlobalAdmin
group
\SAP__LocalAdmin
user
\adm
user
\SAPService
SAP specific groups and users for a
distributed SAP installation
group, buildin
\Users
group, buildin
\Administrators
group
\SAP__GlobalAdmin
group, buildin
\Users
group, buildin
\Domain Admins
In a distributed installation
group to group association
play a role, therfore we have
here directed association
withe meaning isMemberOf.
The adm and the SAPService users are part of the domain and part of the domain users and
SAP__GlobalAdmin groups. These two groups become part of the local groups respectively local
SAP_LocalAdmin, local SAP_SID_LocalAdmin groups.
The users and groups are relevant for processes of the SAP instances, systems and the file resources, software
provisioning manager creates during the installation. The interesting SAP processes are:
The instance agent (sapsartsrv.exe of instance not of SAP Host Agent!) runs as
\SAPService as Windows service with name SAP_. The
\SAPService user has no rights to login to the hosts.
10
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Windows Users and Groups of SAP Systems
SAP Host Agent sapstartsrv in host mode, runs as \sapadm as Windows service
with name SAPHostControl. The \sapadm user does not need the right to login to the
hosts.
saphostexec runs as build in user NT Authority/SYSTEM as service with name SAPHostExec
saposcol is not spawned as a service but as an independent process. Existing SAPOsCol services will be
deleted by the installation of the SAP Host Agent as they are replaced by the saposcol of the SAP Host Agent.
3.2 Access Rights to SAP Directories and File Resources
You have to mount the file resources of an SAP instance and the corresponding user groups must have access
rights to the files and directories. The access control lists (ACLs) of any file resource in the SAP directories must
contain the following user groups:
SYSTEM
Group (local) Administrators
Local Group SAP__LocalAdmin
In details the ACLs must allow the control as:
Group (local) SAP__LocalAdmin has Full Control recursively on usr\sap\
Group (local) SAP_LocalAdmin has Full Control on
o usr
o usr\sap
o usr\sap\trans
o usr\sap\prfclog
Adaptive Enabling an SAP System
Installing a 'hello world' Adaptive Enabled SAP System
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 11
4 Installing a 'hello world' Adaptive Enabled SAP System
We use an ABAP Web AS with one application server, the scs instance, and the database as an example to show
the steps to install an adaptive enabled SAP system. The steps are categorized as follows:
1. Software provisioning manager installation preparation
2. Windows computer system preparation
3. MSSQL computer system preparation
4. NetApp computer system preparation
5. Post installation steps
After having done all necessary installation preparations software provisioning manager guides you through the
installation processes itself. To start the installation you have to navigate to the extracted software provisioning
manager for your platform. The sapinst.exe starts the software provisioning manager server and GUI.
Recommendation
Use software provisioning manager to copy the installation content to a local temp disc. This is not
necessary but it has shown that otherwise the installation often straggles, probably due to performance
problems of the installation media (filer). During the run, software provisioning manager provides various
options. To see them all run software provisioning manager in custom mode so you are aware of all
settings software provisioning manager offers you for a customized installation. Whenever possible, use
the default settings of software provisioning manager.
12
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Software Provisioning Manager Installation Preparations
5 Software Provisioning Manager Installation Preparations
The following description and its terminology are based on a SAP NetWeaver PI 7.1 EHP1, ABAP Web Application
Server installation.
When preparing an installation of an SAP system that is supposed to be managed by LVM you must consider the
following:
Read the technical documentation such as Master Guides, installation and upgrade guides for your SAP
system carefully. For more information, see http://service.sap.com/instguides.
Create the virtual host names for each instance that is supposed to be managed independently in your
domain name server.
Use different virtual host names for each instance. Instances that have the same virtual name can only be
relocated together. A parallel relocate of instances with the same virtual host is currently not enforced in LVM
and can lead to error situations. Using the same virtual hostnames for a subset of LVM enabled instances foils
the LVM concept and should therefore not be considered.
Activate the IP addresses for these virtual host names, by calling c:\Program
Files\SAP\hostctr\exe\sapacosprep -a ifup -i -h
Install or upgrade to the latest 720 SAP Host Agent before calling sapacosprep.
(Optional) Maintain your /etc/hosts and /etc/services file centrally and share it on all
hosts. When you are sure that your domain name service works flawlessly you can skip that step for the hosts
file.
You must use the distributed system installation option of software provisioning manager.
To use virtual hostnames for the installation of your distributed system you start the software provisioning
manager with the parameter SAPINST_USE_HOSTNAME=
Think about the mount point structure of the SAP systems you want to manage with LVM before you start the
installation! And come up with your own governance rule with respect to that issue. If you do it the wrong way
the mount point structure of your systems might prevent the efficient use of your host landscape because
you get conflicts when trying to start multiple instances on one host. In the concrete case of our hello world
SAP system things are still quite straight forward:
o C:\user\sap\ is the mount point (junction) for the installation of the global host instance.
o C:\MSSQL\ is the mount point of the database files of the SAP system. There is currently a bug in
software provisioning manager that prevents the installation below that path on drive C: because
software provisioning manager does no sense the available space below the junctions. If you have that
problem mount a LUN as e.g. drive D: and place all database files there.
o In case you want additional dialog instances take care that the mount points of the instances are not
descend or ascend nodes of each other otherwise the instances will block each other during relocate. Use
instead e the following mount points:
o c:\usr\sap\MGL\SYS
Mount point for instances on the host where SAPLOCALHOST is also the SAPGLOBALHOST
Adaptive Enabling an SAP System
Software Provisioning Manager Installation Preparations
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 13
o c:\usr\sap\MGL\ASCS00
For shared services instance of SAPGLOBALHOST
o c:\usr\sap\MGL\DVEBMGS00
For central instance
o c:\usr\sap\MGL\D01
For additional dialog instance
o Avoid the mounting of the c:\usr\sap file system, as this will prevent instances of two different
systems running on the same host.
o Size the LUNs correctly according to the requirements of software provisioning manager.
For creating the LUNS see Appendix V: Creating LUNS with NetApp SnapDrive.
Execute all tasks in all the following computer system preparation chapters before you start to use the
computer systems as an adaptive enabled resource in LVM.
These recommendations are general valid. The point that refers to management of the "etc/hosts" file hints to
another very important point in the preparation of your landscape:
Note
You must prepare each individual host, also those hosts that are not used during the installation. On the
hosts were you do your installation, software provisioning manager does a couple of things you must do
manually on all the other hosts.
14
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Windows Computer System Preparation
6 Windows Computer System Preparation
Prepare each computer system individual as follows:
Note
System management tools might be available that can help you with the following tasks but we do not
give general advice with regard to that.
Ensure that the following local user groups exist on each host and have at least the following members:
o Group SAP_LocalAdmin
Members: Group \SAP__GlobalAdmin
o Group SAP_LocalAdmin
Members: Group \SAP_GlobalAdmin
Note
Software provisioning manager creates these groups and users on all hosts were you do your distributed
installation. You have to take care that these groups and users are also available on all other hosts.
Install the most up to date SAP Host Agent 720 on each host. That installation creates the SAP_LocalAdmin
group.
For more information, see SAP Host Agent Installation on SAP Help Portal at
http://help.sap.com/saphelp_lvment20/helpdata/en/ba/5e83bd129e4932a4a7726fcea01c4f/content.htm
?frameset=/en/4d/f88a8f418c5059e10000000a42189c/frameset.htm.
Ensure that the lookup of the non-full qualified virtual host names and the corresponding reverse lookup
works in a given network for all SAP instances and DB instances that are in that network.
o Check the hostname resolution by using the ping command for all virtual hostnames on all hosts of the
network.
o Check the reverse lookup by executing ping -a . It should return the full qualified virtual
hostnames on all hosts of the network.
Ensure that the following Windows shares exist on each computer system you want to use as host for an SAP
instance:
o Saploc
o Sapmnt
Ensure that the Windows shares are mapped to the same file path. For example c:\usr\sap.
Note
The Windows shares are only created on the computer systems where you do your initial installation.
When creating the shares use the shares of the initial installation host as blue print but grant access only
to the SID independent user groups: Administrators and SAP_LocalAdmin rights (full control) on the
shares.
Adaptive Enabling an SAP System
MSSQL Server Computer System Preparation
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 15
7 MSSQL Server Computer System Preparation
When using MSSQL as database software on Windows, consider the following for a landscape that you want to
manage with LVM:
Install the MSSQL Server Software on each host that must be able to host a DB instance.
For more information, see SAP Notes for MSSQL.
Install the Microsoft SQL Server Native Client on each host that must be able to host an SAP instance.
For more information, see SAP Notes for MSSQL.
Ensure that the MSSQL server system database tempdb is not placed in the LUN of the data files of the
database that belongs to the SAP system you are about to install. The tempdb must remain local on each DB
host. Typically the location is C:\TEMPDB.
Ensure that you relocate databases only between machines that run compatible MSSQL server versions. As a
best practice, the MSSQL server versions should be all the same in the pool/network in which you can
relocate the database because we currently do not do any check for the consistency between DB and data
files.
16
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
NetApp Windows Computer System Preparation
8 NetApp Windows Computer System Preparation
To be able to mount the corresponding LUNs on the hosts of the SAP system respectively the host of the DB you
need on each host all software that is required by the sapacosprep storage library provided by your storage
partner.
This depends highly on your storage partner. We will discuss here only the case of NetApp iSCSI LUNs.
When using NetApp as your storage provider you need the following software components on each potential host
in your LVM landscape:
Microsoft iSCSI initiator
With all necessary patches for Microsoft Windows 2003 Server
SnapDrive from NetApp in the latest Version
With all necessary patches for Microsoft Windows 2003 Server
For more information, see SAP Notes for Windows as an OS for Managed Systems.
For more information about SAP Partner integrations with SAP Landscape Virtualization Management 2.0, see
SAP Community Network at http://scn.sap.com/docs/DOC-42216.
Adaptive Enabling an SAP System
Software Provisioning Manager Post Installation Steps
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 17
9 Software Provisioning Manager Post Installation Steps
After your distributed installation you must do the following steps:
Adjust the access rights on the resources in the LUNs .
Adjust the SAP profile parameters as follows if not done by the installation (SAPLOCALHOSTFULL is not
touched, created by software provisioning manager)
o SAPLOCALHOST =
o SAPLOCALHOSTFULL =
Execute the profile manipulations as detailed in Registry Entries and Important Context Variables.
9.1 Access rights handling for mounted LUNS under Windows
When you do an adaptive enabled installation, you place the database files (data and logs) into LUNS. Two very
important aspects for LVM are the following:
Security credentials under Windows are not inherited over junctions.
Software provisioning manager uses a local group SAP__LocalAdmin to grant access rights on the
SAP directory tree! You must replace that local group with the global group SAP__GlobalAdmin from
the domain!
The background behind is that software provisioning manager grants access rights based on a local group. In the
picture of the user groups in a distributed installation you can see that the relevant specific users
adm and SAPService are domain users and are assigned via the domain group
SAP__GlobalAdmin to the local group SAP__LocalAdmin that group must have recursively full
access to the resource tree below e.g. C:\usr\sap\.
Now that is done on the installation host initially by software provisioning manager. When you create a mount
point below that path or at latest when you mount the LUNs on another host consider the following:
1. The inheritance of the permissions does not work over junctions.
2. The user group SAP__LocalAdmin is a local group. Windows keeps track of its users and groups by
using GUIDS. For the generation of the GUIDS Windows uses for its local groups and users the Windows SID!
So the Group SAP__LocalAdmin is on each machine another group i.e. an unknown group. The group
GUID that cannot be resolved is the SAP__LocalAdmin from the second host used in the demo
landscape. That problem can only be overcome when you also set the permissions the global group
SAP__GlobalAdmin on all LUNs!
18
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Software Provisioning Manager Post Installation Steps
Disc 2 represents the LUN mounted below C:\usr\sap\MGL\D02, i.e. the LUN for the dialog instance D02.
Security credentials of disk 2 on acvml245, the guid that cannot be resolved is the guid of the local group
SAP__LocalAdmin on acvmw246!
Adaptive Enabling an SAP System
Software Provisioning Manager Post Installation Steps
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 19
9.2 Registry Entries and Important Environment Variables
During installation of the SAP system respectively any SAP instances software provisioning manager creates
certain registry entries that are relevant for the SAP users \adm and
\SAPService and generally for the correct functioning of the SAP instances on the given host. A
part of these entries become the environment variables for the sap users. In case of the MSSQL database the
environment of the adm looks like the following and can be found under:
HKEY_CURRENT_USER\Environment
The environment of the SAPService user can be found under:
HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MGL\Environment
And looks in case of the MGL system like:
20
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Software Provisioning Manager Post Installation Steps
These environments should be the same. The command line tool: ntreg2cmd.exe, that is part of the SAP kernel,
allows you to extract the relevant environment variables in a windows command file. That can be used to add
SETENV_XX commands in the profile of the system. Ensure that you have patched the instance agent up to 7.0
patch level 179 otherwise the SETENV_XX command does not function properly. As an example see the
DEFAULT.PFL below.
DBMS_TYPE
Here mss for Microsoft SQL Server depends on the DB type of you system must be set in the profiles
MSSQL_DBNAME
Here MGL the name of the database that belongs to the system must be set in the profiles
MSSQL_SCHEMA
Here mgl the name schema of the database that belongs to the system must be set in the profiles
MSSQL_SERVER
Here DBMGL the virtual host name of the server that hosts the Microsoft SQL Server with the system
database must be set in the profiles
PATH
The PATH environment variable the user adm respectively SAPService will see. Set it to
PATH=$(DIR_EXECUTABLE);%(PATH)
SAPEXE
You will get that value from the ntreg2cmd tool ensure it points to the SAPGLOBALHOST server.
SAPLOCALHOST
The virtual host name used last to install a SAP instance on that host. In case of adaptive computing irrelevant
since the saplocalhost name of the profiles of the instances that are bound to the host are those values that
are active.
SAPSYSTEMNAME
The SAP SID here MGL
TEMP
Here C:\usr\sap\MGL\tmp. Must be set in the profile to another value because that path does not exist on
each host.
TMP
Here C:\usr\sap\MGL\tmp. Must be set in the profile to another value because that path does not exist on
each host.
Software provisioning manager adds these environment variables to the registry for each host where you install
an instance. To ensure that these environment variables are present on a new host that has not been used during
the installation of the system you must enter these data into the profiles of the system: (the default.pfl of the
system MGL):
SAPSYSTEMNAME = MGL
SAPGLOBALHOST = scsmgl
system/type = ABAP
login/system_client = 001
SAPDBHOST = DBMGL
dbms/type = mss
dbs/mss/server = DBMGL
dbs/mss/dbname = MGL
dbs/mss/schema = mgl
rdisp/bufrefmode = sendon,exeauto
Adaptive Enabling an SAP System
Software Provisioning Manager Post Installation Steps
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 21
#-----------------------------------------------------------------------
# SAP Message Server for ABAP
#-----------------------------------------------------------------------
rdisp/mshost = scsmgl
rdisp/msserv = sapmsMGL
rdisp/msserv_internal = 3900
rdisp/TRACE = 1
#rdisp/TRACE_COMPS = XP
#Added for Registry independent environment variables
SETENV_00 = PATH=$(DIR_EXECUTABLE);%(PATH)
SETENV_01 = TEMP=%USERPROFILE%\Local Settings\Temp
SETENV_02 = TMP=%USERPROFILE%\Local Settings\Temp
SETENV_03 = SAPLOCALHOST=scsmgl
SETENV_04 = SAPSYSTEMNAME=MGL
SETENV_05 = SAPEXE= \\scsmgl\sapmnt\MGL\SYS\exe\uc\NTAMD64
SETENV_06 = DBMS_TYPE=mss
SETENV_07 = MSSQL_SERVER=DBMGL
SETENV_08 = MSSQL_DBNAME=MGL
SETENV_09 = MSSQL_SCHEMA=mgl
If you want to logon as adm on a machine where software provisioning manager did not create these
registry entries you must use the tool ntreg2env.exe/env2ntreg.exe to export/import the registry entries. If you
do not want to logon to the computer systems as adm the manipulation of the profiles is suffient to ensure
proper working of your LVM enabled systems, if you want to logon as adm you need the
ntreg2env.exe/env2ntreg.exe to export/import steps on each machine.
22
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Manual Relocate
10 Manual Relocate
After the installation is finished, test the ability to relocate the system. During this test plan you relocate the full
system at once. For the simplest possible SAP system you can write two additional test plans to relocate single
instances. Start and stop your adaptively installed SAP system at least once completely manually before you
register it in LVM.
Caution
The command line interface of sapacosprep and sapdbctrl are non- official APIs of SAP they might
change without notice. To get sapacosprep partner libraries for your specific environment, contact your
SAP technology partner representative. SAP technology partners provide libraries for platforms and data
storage solutions. sapacosprep partner libraries may require additional setup procedures. Follow the
instructions provided by your partner.
10.1 Manual Activities on Host A
To avoid wrecking your installation and data, execute the commands on host A in the following sequence.
10.1.1 Stopping SAP Instances
You stop an SAP system using the sapcontrol executable. You can find all executables under the default SAP
Host Agent directory c:\Program Files\SAP\hostctrl\exe.
For the parameters see Appendix II: sapcontrol command line interface.
Enter the command:
>sapcontrol -user adm -nr - function StopSystem ALL
Check the result with the following commands:
>sapcontrol -nr -function GetSystemInstanceList
>sapcontrol -nr -function GetProcessList
10.1.2 Stopping Database
You stop the database.
For the parameters see Appendix I: saphostctrl command line interface.
Enter the command:
Adaptive Enabling an SAP System
Manual Relocate
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 23
>saphostctrl -user sapadm -function StopDatabase -dbname -dbtype mss
-dbhost -dbinstance
You have to ensure, that the local system account has administrator permission on the MSSQL instance.
Check the result with the following commands:
>saphostctrl -function ListDatabases
>saphostctrl.exe -user sapadm -function GetDatabaseStatus -dbname
-dbtype mss -dbhost -dbinstance
10.1.3 Unregistering SAP Instance Agents
You stop and unregister the SAP instance agent for the SAP instances running on your host.
For the parameters see Appendix I: saphostctrl command line interface.
Enter the command:
> saphostctrl.exe -user sapadm -function UnregisterInstanceService -sid
-nr -saplocalhost
List all active services and check the result with the following Windows command:
Net start
The service SAP_ should be gone after unregistering.
In case of trouble, clean up the service with the following command:
sc delete SAP_
10.1.4 Detaching Database
You detach a database.
For the parameters see Appendix I: saphostctrl command line interface.
Enter the command:
>saphostctrl.exe -user sapadm -function DetachDatabase -dbconfdir -dbname -dbtype mss - dbhost -
dbinstance
Before you stop the database, fetch the necessary parameter dbconfig dir by executing the following
command:
>saphostctrl -function GetDatabaseProperties -dbname -dbtype mss -dbinstance
The result looks like follows:
Webmethod returned successfully
----- Database Properties ---
Database/IsRelocationTarget=true
Database/IsRelocatable=true
24
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Manual Relocate
Database/IsSharedInstance=true
Database/IsSharedNetService=false
Database/MaxPhysMemSize=1535
Database/CPUCount=2
Database/ConfigurationDirectory/Default=D:\MGLDATA0
Database/DBRelease=9.00.4035.00
10.1.5 Unmounting LUNS
You unmount the LUNs using the command sapacosprep.
For the parameter see Appendix III: sapacosprep command line interface.
Enter the command:
>sapacosprep.exe -a umountDFS -f - m -t ISCSI -p NTP -D
The required input is maintained in the file ntp_srid.conf that is used by the sapacosprep library from
NetApp. It looks like e.g.:
sapacosprep.exe -a umountDFS -f aip900n2:/vol/vol1/ACCWIN/MGL -m c:\usr\sap\MGL -t
ISCSI -p NTP -D
10.1.6 Unbinding Virtual IPs/Hostnames
You unbind the IP addresses of the SAP instances and database instances bound to the network adapters by
executing the sapacosprep command.
For the parameter see Appendix III: sapacosprep command line interface.
Enter the command:
>sapacosprep -a ifdown -h -n
-b
The success of the command can be checked with ipconfig under Windows and should not be reachable via the
ping-command.
10.2 Manual Activities on Host B
To avoid wrecking your installation and data, execute the commands on host B in the following sequence.
Adaptive Enabling an SAP System
Manual Relocate
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 25
10.2.1 Binding Virtual IPs/Hostnames
You bind the IP addresses and virtual host names of the SAP instances and database instances to the network
adapter.
For the parameter see Appendix III: sapacosprep command line interface.
To retrieve the interface name, enter the command:
>sapacosprep -a PrintNetwork
or
>ipconfig, after the string "Ethernet Adapter" e.g. Ethernet adapter Local Area Connection
>sapacosprep -a ifup -i -h -n -b
Check the hostname resolution and reverse look for all hostname addresses in the network.
ping
ping -a
10.2.2 Mounting LUNS
You mount all necessary LUNs by executing the sapacosprep command.
For the parameter see Appendix III: sapacosprep command line interface.
Enter the command:
>sapacosprep.exe -a mountDFS -f - m -t ISCSI -o NTFS -p
NTP -C
The required input is maintained in the file ntp_srid.conf that is used by the sapacosprep library from
NetApp. It looks like e.g.:
sapacosprep.exe -a mountDFS -f aip900n2:/vol/vol1/ACCWIN/MGL -m c:\usr\sap\MGL -t
ISCSI -p NTP -o NTFS -C
10.2.3 Attaching Database
You attach the database.
For the parameters see Appendix I: saphostctrl command line interface.
>saphostctrl.exe -user sapadm -function AttachDatabase -dbconfdir -dbname -dbtype mss - dbhost -
dbinstance -service -instance
Check the status of the database with the command:
>saphostctrl -function ListDatabases
26
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Manual Relocate
10.2.4 Starting Database
After attaching the database, start the database.
For the parameters see Appendix I: saphostctrl command line interface.
Enter the command:
> saphostctrl.exe -user sapadm -function StartDatabase -dbname -
dbtype mss -dbhost -dbinstance
10.2.5 Registering SAP Instance Agents
Before starting an SAP instance, register the instance agent as a Windows service.
For the parameters see Appendix I: saphostctrl command line interface.
Enter the command:
> saphostctrl.exe -user sapadm -function RegisterInstanceService -
profile \\\sapmnt\\SYS\profile\sapcontrol -user adm -nr - function StartSystem
To start the SAP instances one by one, enter the following commannd. Ensurte to start the instances in the
correct sequence!
>sapcontrol -user adm -nr - function Start
Check the result with the following commands:
>sapcontrol -nr -function GetSystemInstanceList
>sapcontrol -nr -function GetProcessList
Adaptive Enabling an SAP System
Managing Systems using LVM
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 27
11 Managing Systems using LVM
To configure the system in LVM, see the Application Help on SAP Help Portal at http://service.sap.com/nwlvm.
1. Create and configure your network for your computer systems and SAP systems.
For more information, see Infrastructure Configuration at
http://help.sap.com/saphelp_lvment20/helpdata/en/d6/1102558e6e4e36a5d5bd0e0e7b916c/content.ht
m?frameset=/en/4d/f88a8f418c5059e10000000a42189c/frameset.htm
2. Integrate managed landscape data into LVM.
For more information, see Initial Entities Configuration at
http://help.sap.com/saphelp_lvment20/helpdata/en/35/aa5d405c174256bc92b57cb0d09753/content.ht
m?frameset=/en/4d/f88a8f418c5059e10000000a42189c/frameset.htm
1. Enable the logical grouping of your individual instances and hosts, based on the type of user, landscape,
time zones, and so on.
For more information, see Configuring Pools.
2. Make hosts available for performing operations.
For more information, see Adding Hosts.
3. Enable starting, stopping, and relocating instances according to the hosts available.
For more information, see Configuring Hosts.
The name of the network interface ID, here the same recommendation as given in Binding Virtual
IPs/Hostnames is valid or you can choose Autoassign Networks Retrieved from Host Agent in the host
configuration.
4. Make the individual instances, such as the central instance, database instance, dialog instance, TREX
instance, or live Cache available for performing operations.
For more information, see Adding Instances.
Enable to manage your instances in the landscape.
For more information, see Configuring Instances.
For the MSSQL database you have to allow the local system account administration rights on your
MSSQL instance
The entries for the mount point of the corresponding instance can be retrieved via the Host Agent.
Remove all unnecessary mount points for the current instance.
Dont forget the windows domain when entering the service registration user i.e.
\SAPService.
Do the same for each instance you want to enable.
5. Enable to manage your systems in the landscape.
For more information, see Configuring Systems.
28
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Open Issues
12 Open Issues
Open issues you must consider when using LVM:
Initial host preparation: You must prepare a new computer system in your landscape. That means a system
that has never been touched before by software provisioning manager in a certain way to ensure that you can
relocate SAP instances or database instances to it. For example, install certain software, create sapmnt and
saplocal, and create certain users and groups locally. In case of problems, contact your SAP Basis
Technology consultant. There exist tools that can help you with parts of the problem but we cannot even
provide best practices for all problems.
Currently we do not check that the versions of the database files match with the versions of the database we
try to attach the database files. You have to ensure that the versions of the database software are same on all
potential hosts in the landscape.
Adaptive Enabling an SAP System
Appendix I: saphostctrl command line interface
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 29
13 Appendix I: saphostctrl command line interface
The SAP Host Agent has a command line interface that allows the management of the instances and databases
running on the given host. Executing the command saphostctrl in the directory
%HOST_AGENT_HOME%\exe>saphostctrl gives the following output given here as reference. All operations
executed by LVM have an equivalent command line command:
Syntax
Usage: saphostctrl [generic option]... -function [argument]...
saphostctrl -help []
Generic options:
-host
-user
Supported Webmethods:
StartInstance
-sid -nr -saplocalhost [-timeout ] [-
service] [-prehook] [-posthook]
StopInstance
-sid -nr -saplocalhost [-timeout ] [-
service] [-cleanup] [-prehook] [-posthook]
ListInstances
[-running (list running instances only) | -stopped (list stopped instances
only)]
CallServiceOperation
-op startdb|stopdb -sid [-dbname ] [-dbusage
Abap|Java|Doublestack|LiveCache] [-dbhost ] [-dbtype
ada|db6|mss...] [-
service] [-timeout ] [-prehook] [-posthook]
ACOSPrepare
-op argument... [-op argument...]... [-timeout ]
supported operations:
mount|umount|ifup|ifdown
mount/umount arguments:
-storage_type netfs|dfs|srid -fsname -mntpoint
-
30
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Appendix I: saphostctrl command line interface
storage_vendor (only for dfs and srid) -dfstype -srid
-sridtype [-fsoptions
(only for
netfs and dfs)]
ifup arguments:
-iface -vhost [-nmask ] [-bcast
]
ifdown arguments:
-vhost
GetOperationResults
-id [-timeout ]
CancelOperation
-id [-timeout ]
ExecuteOperation
-name [-timeout ] [=]
GetCIMObject
-classes [-attr ]
GetComputerSystem
-wbem [-attr ]
ListDatabases
GetDatabaseStatus
-dbname -dbtype [-dbhost ] [-dbinstance
] [-dbuser ] [-dbpass ]
StartDatabase
-dbname -dbtype [-dbhost ] [-dbinstance
] [-dbuser ] [-dbpass ] [-
timeout ] [-service] [-force]
StopDatabase
-dbname -dbtype [-dbhost ] [-dbinstance
] [-dbuser ] [-dbpass ] [-
timeout ] [-service] [-force]
AttachDatabase
-dbname -dbtype [-dbconfdir ] [-
dbhost ] [-dbinstance ] [-dbuser ]
[-
dbpass ] [-timeout ] [-service] [-force]
DetachDatabase
-dbname -dbtype [-dbconfdir ] [-
Adaptive Enabling an SAP System
Appendix I: saphostctrl command line interface
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 31
dbhost ] [-dbinstance ] [-dbuser ]
[-
dbpass ] [-timeout ] [-service] [-force]
GetDatabaseProperties
-dbname -dbtype [-dbhost ] [-dbinstance
] [-dbuser ] [-dbpass ]
LiveDatabaseUpdate
-dbname -dbtype [-updatemethod
] [-updateoption
]
[-retry ]
[-mountsrc ]
[-mounttgt
32
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Appendix II: sapcontrol command line interface
14 Appendix II: sapcontrol command line interface
For managing SAP instances manually using the command line, you use the sapcontrol command. It is fully
self-documented. By entering the command sapcontrol in the directory of the SAP Host Agent you get the
following output:
Syntax
usage: sapcontrol [
-prot GSOAP_HTTP| http using gsoap build in sockets (default)
NI_HTTP| http using SAP NI sockets (prefer Unix domain sockets)
NI_HTTPS| https using SAP NI sockets (prefer Unix domain sockets)
WINHTTP| http using Windows winhttp
WINHTTPS| https using Windows winhttp
PIPE Windows named pipes
]
[-trace ] Trace SOAP request/response
[-user ] OS user and password for Webservice authentication
[-repeat ] Repeat Webmethod call times (-1=forever) with sec
delay
[
-format list| List output format (default)
script Script output format
]
[-host ] Host to connect to (default: localhost)
-nr SAP Instance number to connect to
-function [parameter list]
Webmethods: Start
Stop [softtimeout sec]
Shutdown
RestartInstance [softtimeout sec]
StopService
StartService
RestartService
ParameterValue []
GetStartProfile
GetTraceFile
GetAlertTree
Adaptive Enabling an SAP System
Appendix II: sapcontrol command line interface
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 33
GetAlerts
GetEnvironment
GetVersionInfo
GetQueueStatistic
GetProcessList
GetInstanceProperties
ListDeveloperTraces
ReadDeveloperTrace
ListLogFiles
ReadLogFile [ [ [ []]]]
AnalyseLogFiles [] [] [
]
GetAccessPointList
GetProcessParameter [pid]
SetProcessParameter [ ...
]
OSExecute
SendSignal
GetSystemInstanceList
StartSystem [ALL|SCS|DIALOG|ABAP|J2EE|TREX|ENQREP|LEVEL []]
StopSystem [ALL|SCS|DIALOG|ABAP|J2EE|TREX|ENQREP|LEVEL [[] [softtimeout sec]]]
RestartSystem [ALL|SCS|DIALOG|ABAP|J2EE|TREX|ENQREP|LEVEL [[] [softtimeout sec]]]
AccessCheck
GetSecNetworkId [ []]
GetNetworkId []
ABAPReadSyslog
ABAPReadRawSyslog
ABAPGetWPTable
J2EEControlProcess
J2EEEnableDbgSession [ ]
J2EEDisableDbgSession
J2EEGetProcessList
J2EEGetProcessList2
J2EEGetThreadList
J2EEGetThreadList2
J2EEGetThreadCallStack []
J2EEGetThreadTaskStack []
J2EEGetSessionList
34
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Appendix II: sapcontrol command line interface
J2EEGetCacheStatistic
J2EEGetCacheStatistic2
J2EEGetApplicationAliasList
J2EEGetComponentList
J2EEGetWebSessionList
J2EEGetEJBSessionList
J2EEGetRemoteObjectList
J2EEGetVMGCHistory
J2EEGetVMGCHistory2
J2EEGetVMHeapInfo
J2EEGetClusterMsgList
J2EEGetSharedTableInfo
ICMGetThreadList
ICMGetConnectionList
ICMGetProxyConnectionList
ICMGetCacheEntries
EnqGetStatistic
EnqGetLockTable
StartWait
StopWait
WaitforStarted
WaitforStopped
RestartServiceWait
CheckHostAgent
Exitcode
0: Last Webmethod call successfull
1: Last Webmethod call failed, invalid parameter
2: StartWait, StopWait, WaitforStarted, WaitforStopped, RestartServiceWait timed out
3: GetProcessList succeeded, all processes running correctly
4: GetProcessList succeeded, all processes stopped
Security
Trusted connects without user and password check are possible through UNIX domain socket or Windows named
pipes. Protected web methods like Start or Stop require a trusted connection or OS user and password
authentication.
Adaptive Enabling an SAP System
Appendix III: sapacosprep command line interface
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 35
15 Appendix III: sapacosprep command line interface
For mounting or umounting storage devices and binding or unbinding IP addresses the SAP Host Agent uses the
sapacosprep command utility. That utility provides a generic interface to mount or unmount storage devices
independent from the storage provider and a similar generic interface to bind unbind IP addresses independent
from the operating system. As all adaptive command line tools it is self-documented so the command
sapacosprep entered on the command line in the SAP Host Agent directory gives the following output:
SAPACOSPREP USAGE
sapacosprep -a COMMAND [COMMAND ARGUMENT]... [COMMAND OPTION]... [GENERIC
OPTION]...
COMMANDS
ifup: activates a virtual IP address
-a ifup -i -h
[-n ] [-b ]
ifdown: deactivates a virtual IP address
-a ifdown -h
mount: mounts a network file system
-a mount -f -m [-o mount options]
umount: unmounts a network file system
-a umount -f -m
mountDFS: mounts a distributed file system
-a mountDFS -f -m -t
-p [-o
36
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Appendix III: sapacosprep command line interface
Create mount point directory
UMOUNT OPTIONS
-D
Delete mount point directory
GENERIC OPTIONS
-H
displays this help text
-V
displays version information
-x
Output not XML encoded (deprecated)
-R
Do not perform an effective user check (for testing purposes only)
-v
Specifies the protocol version (deprecated)
-P
Print output in a format that can easily be parsed
-L
Colon-separated list of directories to search for libraries
-T
Specifies the log and trace file. Per default it will be tried to
create a file named sapacosprep.log in one of the following directories:
\usr\sap\tmp, \path\to\sapacosprep, .\
EXAMPLES
# run diagnostics
sapacosprep -a diag
# activate virtual IP address
sapacosprep -a ifup -i eth0 -h cic11
# mount network file system
sapacosprep -a mount -f host:/sapmnt/C11 -m /sapmnt/C11
default: 1)
Adaptive Enabling an SAP System
Appendix V: Creating LUNS with NetApp SnapDrive
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 37
16 Appendix V: Creating LUNS with NetApp SnapDrive
Before you can start with the installation of an adaptive enabled SAP system you must create the necessary LUNs
on the storage system and mount them on the installation host. NetApp Provides software called SnapDrive for
Windows that comes as a MMC plugin and allows the management of LUNs on a storage system in the
background. As shown in the screen shot you can create new LUNs on the filer with that tool. During the wizard
guide creation process of the LUNS you are asked for the mount points and the path on the filer.
Wizard steps
When creating the three Luns for the three instances NetApp SnapDrive provides you a wizard to do that. Below
we show you the wizard steps that you know which information you must provide and remember.
1. Select the storage system:
38
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Appendix V: Creating LUNS with NetApp SnapDrive
2. Remember the full path of the lun:
Adaptive Enabling an SAP System
Appendix V: Creating LUNS with NetApp SnapDrive
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 39
3.
40
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Appendix V: Creating LUNS with NetApp SnapDrive
4. Remember the mount point for later:
Adaptive Enabling an SAP System
Appendix V: Creating LUNS with NetApp SnapDrive
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 41
5.
42
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Appendix V: Creating LUNS with NetApp SnapDrive
6.
Adaptive Enabling an SAP System
Appendix VI: SAP hosts during relocation process
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 43
17 Appendix VI: SAP hosts during relocation process
The SAP installation creates some files and folders on the host were it is executed. With regard to adaptive
computing the general question arises which folders are relevant for a system for an instance for a database and
must be relocated together with the system instance and data base. In that appendix we try to give an answer to
that question.
C:\usr\sap\PRFLOG: Belongs to the saposcol remains local.
All local files pointed to by the local UNC path. This saploc share must exist on any host:
\\\saploc\\
Check the DIR_TRANS, if it is a local directory, you also have to relocate it, check as adm via command:
>sapcontrol -nr -function ParameterValue DIR_TRANS
44
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Appendix VII: System MGL
18 Appendix VII: System MGL
The demo system MGL used in the paper shown in LVM:
Status One: DB and central services are running on acvmw246 dialog instance runs on acvmw245
Adaptive Enabling an SAP System
Appendix VII: System MGL
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 45
Status Two after relocating, DB and central services are running on acvmw245 dialog instance runs on acvmw246
46
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Appendix VII: System MGL
Windows Domain: ACCWIN
acvmw245
acvmw246
acvmw244
ESX ServerStoragesystem
Domain Controller &
Name Server
Ethernet
Adaptive Enabling an SAP System
Appendix VIII: Avoiding "SAPGLOBALHOST first" problem during preparation
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 47
19 Appendix VIII: Avoiding "SAPGLOBALHOST first" problem during preparation
Under windows the instance representing SAPGLOBALHOST must be prepared first since the preparation process
for the other instances depends on a prepared SAPGLOBALHOST.
Since the problem occurs only in the preparation phase during the registration of the SAP instance agent. Normal
the SAP Host Agent needs the CIFS share of the SAPGLOBALHOST to provide it to the self-registration call to the
instance agent. If the share is not up the registration fails.
Install the latest SP of your LVM and configure the start profile path of the SAP instances where SAPLOCALHOST
SAPGLOBALHOST with the unc path \\\sapmnt\.
Ensure that you update the profile parameters in the LVM instance configuration by retrieving them again from
the instance agent.
48
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
References
20 References
Installation Guides
http://service.sap.com/instguides
http://service.sap.com/instlvm
SAP Landscape Virtualization Management Online Help
http://help.sap.com/nwlvm
Creating roaming user profiles
http://support.microsoft.com/kb/324749
Configuring roaming user profiles
http://technet.microsoft.com/en-us/library/cc738596.aspx
Microsoft iSCSI Initiator
http://www.microsoft.com/windowsserver2003/technologies/storage/iscsi/default.mspx
NetApp Snapdrive for Windows
http://www.netapp.com/de/products/management-software/snapdrive-windows-de.html
Summary of SAP Partner integrations with SAP Landscape Virtualization Management 2.0
http://scn.sap.com/docs/DOC-42216
20.1 SAP Notes for Windows as an OS for Managed Systems
SAP Note Number Title
360515 TCP IP Alias host names in UNC path in Windows 2000 2003
1282975 Use of virtual TCPIP host names in Windows
DBCC CHECKDB http://technet.microsoft.com/de-de/library/ms176064.aspx
Using SQL Server 2005 with SAP R/3 http://download.microsoft.com/download/d/6/5/d65727d9-
6eda-438f-a86f-f915559592a7/SAPandSQL2005TWP.doc
908533 Prerequisites in an Windows Adaptive Computing landscape
20.2 SAP Notes for MSSQL
SAP Note Number Title
896566 SQL4SAP and SAP Installation Media for SQL Server
985137 Service Pack Installation for SQL Server 2005
Adaptive Enabling an SAP System
References
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved. 49
SAP Note Number Title
62988 Service packs for MS SQL Server
555223 FAQ: Microsoft SQL Serve
363018 File management for SQL Server
20.3 SAP Notes with Relevant Network Topics
SAP Note Number Title
1783702 SAP Landscape Virtualization Management 2.0
(Enterprise Edition)
1709155 System Provisioning with Landscape Virtualization
Management
962955 Use of virtual TCPIP host names
611361 Hostnames of SAP servers
129997 Hostname and IP address lookup
1084753 Problems with sapacosprep
50
CUSTOMER
2013 SAP AG or an SAP affiliate company. All rights reserved.
Adaptive Enabling an SAP System
Important Disclaimers on Legal Aspects
21 Important Disclaimers on Legal Aspects
This document is for informational purposes only. Its content is subject to change without notice, and SAP does
not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF
MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and
are not intended to be used in a productive system environment. The Code is only intended to better explain and
visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness
of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code,
unless damages were caused by SAP intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of
the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software
products. SAP specifically disclaims any liability with respect to this document and no contractual obligations or
commitments are formed either directly or indirectly by this document.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed
directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring
to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does
not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the
documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint
about where to find related information. SAP does not warrant the availability and correctness of this related
information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful
misconduct. Regarding link classification, see: http://help.sap.com/disclaimer.
Open Source Software and Third Party Components
Please refer to https://scn.sap.com/docs/DOC-42044 for information respecting open source software
components made available by SAP as part of SAP NetWeaver and any specific conditions that apply to your use
of such open source software components. Please refer to https://scn.sap.com/docs/DOC-42045 for
information relating to SAPs use of third party software with or within SAP NetWeaver.
www.sap.com/contactsap
2013 SAP AG or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior
notice.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software
vendors.
National product specifications may vary.
These materials are provided by SAP AG and its affiliated
companies (SAP Group) for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are
set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP AG in Germany and other countries. Please see
www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.