Unit-1

The Kernal is the runtime environment to run the software component. It is

database and OS depending. It is also called Application Server or SAP Instance
or Dispatcher and work processes. The software components SAP_BASIS,
SAP_ABA and others contain basis functions (User admin, performance tools,
TMS, development tools. The basis software components together with the
kernel are also called SAP NetWeaver Application Server.
Example of AS JAVA is SAP XSS and SAP Portal.
An instance of an SAP system is an administrative unit in which components of
an SAP system that provides one or more services are combined. The services
within one instance are started or stopped together.
The instance number is a two-digit number, and is chosen at installation. It
defines a range of standard communication ports for processes of the instance.
The standard port of the dispatcher is 32$$ where $$ denotes the instance
number.
We should not use the instance numbers 98 and 99, because they are reserved
for the SAP router.
A Java instance consists of a Java dispatcher and one or more server process.
A (Java-based) SAP system can have several instances. One of them is the (Java)
central instance. It includes an additional process - the Software Deployment
Manager (SDM) - which can only be configured once across the SAP system.
There is also a Java Central Services (SCS or CS) instance. This CS instance offers
the Java Message Server and the Java Enqueue Server. In the standard
installation, the Java central instance and the CS instance are located on the
same host.
Note: In AS Java releases starting from 7.10, there will be no Java dispatcher any
longer. Instead the load balancing is been done by a Java ICM process.
AS ABAP instance of an SAP system containing the Enqueue server and the
message server (ASCS = ABAP SAP Central Services). Since SAP NetWeaver 7.0
the Message Server and the Enqueue Work Process is separated from the Central
Instance. These two are grouped within the ABAP SAP Central Services (ASCS)
as server.
Component of ASCS
o

Enqueue work process administers the lock table in the shared memory.
The lock table contains the logical database locks of the ABAP runtime
environment of the SAP system. Only one enqueue work process is
needed for each system

Message Server (MS) handles communication between the distributed

dispatchers within the AS ABAP, thereby enabling scalability of several
parallel application servers. The message server is configured only one
per SAP system

Unicode defines a character set that includes virtually all characters used
worldwide and as a result provides consistent, global character encoding.

Unit-2
Start and use 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.
During the installation, SAPinst uses port 21200 to communicate with the GUI
server. The GUI server uses port 21212 to communicate with SAPinst GUI. 4239
is the port of the HTTP server, which is part of the GUI server.
To get a list of all available SAPinst properties, start SAPinst with the parameter
-p:
Windows: sapinst.exe p and UNIX: ./sapinst -p
On your local host start SAPinst GUI by executing the following command:
o Windows: startinstgui.bat -host <remote hostname>
o UNIX: ./startInstGui.sh -host <remote hostname>
Name the log files used by SAPinst
The logs of SAPinst GUI and the GUI Server are written to the folder
%userprofile%\.stdgui (Windows) and <user_home>/.stdgui (UNIX)
If SAPinst GUI does not start, check the file sdtstart.err in the current
%userprofile% (Windows) or <user_home> (UNIX) directory.

SAPinst is controlled by XML files. The main XML files are:

o dialog.xml - contains all dialogs used in the installation
o keydb.xml - SAPinst records the installation progress and user input in the
keydb.xml file
o messages.xml - contains all messages used in the installation
o control.xml - contains the component definition used by SAPinst
o packages.xml - for software package administration

General Preparation for Installation

Download the installation DVDs.

Read the required installation guides and all required SAP Notes.
Install/update SAP front-end components like SAP GUI for Windows.
Set environment variable for SAPinst.
Install Java Development Kit for SAP NetWeaver AS Java (depending on usage
types and operation system) - depending on the need.
Set environment variable for SAP NetWeaver AS Java.
Download Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction
Policy Files for AS Java based SAP systems).
Check if the necessary hardware and software requirements are fulfilled
(Prerequisites Check).
Additional Preparation for Installation on Windows
Reduce Size of File Cache (in case of Windows Server)
Prepare the Transport Host
o On the transport host, create the directory \usr\sap\trans.
o Grant Everyone the permission Full Control for the directory.

Share the usr\sap directory on the transport host as sapmnt. This enables
SAPinst to address the transport directory in the standard way as
\\SAPTRANSHOST\SAPMNT\trans.
Additional Preparation for Installation on UNIX
o

UNIX 6

List relevant post installation steps

Explain how to complete the installation of SAP Enhancement Package 6 for
SAP ERP 6.0
Describe the steps to install an SAP license
Describe the steps to install the SAP online documentation
Describe the steps to install and configure the SAProuter
Describe the steps needed to configure the Transport Management System
(TMS)
Describe the steps needed to configure profile parameters
Describe the steps to configure operation modes
Perform final installation checks
Describe how to activate SAP ECC Extensions
Start and schedule the SAP Load Generator (SGEN)
Run the Configuration Wizard
Describe the steps to verify the AS Java configuration
Install a standalone SAP Gateway instance
using sapcontrol on the host of the SAP system using the SAP Management
Console (http://<hostname>:5$$13)
Check the following file system files in directory
\usr\sap\<SID>\<Instance>\work\
1. dev_ms
2. dev_disp
3. dev_dispatcher
4. dev_rd
5. dev_w*
6. dev_server0
Check transactions
1. SM51 (all available instances)

2. SM50 (all available work processes for the instance you are logged on
to)
3. SM21 (system log)
For AS Java based SAP systems check the Java system information.
http://<hostname>:5$$00/sap/monitoring/SystemInfo
You need to back up the following directories and files on UNIX :
1. All database specific directories
2. All SAP specific directories:
/usr/sap/<SAPSID>
/usr/sap/trans
<sapmnt>/<SAPSID>
home directory of user <sapsid>adm
root file system
You need to back up the following directories and files on Windows:
1. All database specific directories
2. Registry
3. All SAP specific directories:
\usr\sap\<SAPSID>
\usr\sap\trans
home directory of user <sapsid>adm
\%WINDIR%

Configuration of the Transport Management System (TMS)

Configuration of profile parameters
Configuration of operation modes
Perform final installation checks
Activate SAP ECC Extensions
Install additional languages
Start and schedule the SAP Load Generator (SGEN)