Here is a condensed analysis of (without the sales hype) how to configure SAP R/3 Netweaver. Included are a comparison of components and explanation of SAP SID, Profiles, PATH, and Server Services.
In the SAP world, a "client" is a legal entity such as a corporation.
The default "000" client contains client-independent settings.
However, in the IT networking world, what many other organizations call the machines used by end-users "client PCs", SAP calls "terminals".
SAP end-user terminals (usually runing Windows XP OS) are connected to client corporate servers though the public network or internal VPN servers.
Terminals make requests to a VIP (Virtual IP) configured on an inbound router into the server farm.
[_] Set protocol.ora file parameter tcp.nodelay=yes so that packets are streamed onto the network without delay.
Experts with SAP's "Remote Support" service log onto systems to resolve problems.
The multiclient concept of R/3" on SAPnet
Each R/3 installation (SAP system) of a database server and several app servers running the application logic is uniquely identified by a single SID (SAP System Identification), aka SAPSID a three-character code such as C11, PRD, E56, etc.),
The evaluation version of Netweaver ABAP uses SAP SID "NSP". This value is specified in a DEFAULT.PFL profile file as property = value pair
SAPSYSTEMNAME = NSP
SAP profile files are text files with invisible Unix newline at the end of each line. So if you are on a PC, use Wordpad rather than Notepad.
Profiles comment lines are preceded by a # (pound) character.
Several servers can be be associated with this SAPSID by referencing the DEFAULT.PFL. This is why parameters configuring Buffer synchronization by the "SAP Messaging Service for ABAP" is also specified there:
Each server under a SID is identified with a two-digit number, such as "00" which the eval. system installs.
The Windows Service "SAPNSP_00" is started by referencing a profile file, such as:
The "pf=" points to a profile for a specific host name (bubba1) and instance (DVEBMGS00), which contains:
SAPSYSTEMNAME = NSP SAPGLOBALHOST = bubba1 SAPSYSTEM = 00 INSTANCE_NAME = DVEBMGS00
This profile properties file configures an SAP Web AS instance is shared by several sister servers associated with a SID (SAP System identifier) because all servers in a SID reference logical directory /sapmnt/SID/profile even though it's physically stored in directory /usr/sap/SID/SYS/profile. Other system-wide files for SAP (including executables and global files) are also stored the same way.
An organization usually needs several environments. Here is an example:
Transaction SPRO is the main tree for SAP application configurations.
Your first name:
Your family name:
Your location (city, country):
Your Email address:
Top of Page