SAP SID, Profiles, PATH, and Server Services
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:
| Parameter name | Recommended value |
| rdisp/bufrefmode | sendoff,exeoff (central system) |
| sendon,exeauto (client/server) |
| rdisp/bufreftime | 60 |
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:
...\sapstartsrv.exe pf=...\NSP_DVEBMGS00_BUBBA1
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.
|