SAP R/3 Configuration

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.

SAP Components Component NW 7.0 (2004s) 2004 J2EE ABAP Sun J2SE SDK 1.4.2_09 (not 1.4.2_10) - Server - SAP NetWeaver 7.0 ABAP Application Server SP12 - Client - Compact SAP Logon 7.10 SAP NetWeaver Development Infrastructure - - SAP NetWeaver Developer Studio (NWDI) 7.0.09 SAP NetWeaver (Enterprise) Portal with PDK Web Dynpro SAP Content Management and Collaboration TREX MaxDB + DatabaseManger and SQL Studio 7.6.00.34 7.6.02.14 SAP NetWeaver Business Intelligence (BI) Java SDK SAP Interactive Forms by Adobe (Adobe Document Services) Visual Composer Composite Application Framework (CAI) Yes No SAP NetWeaver Knowledge Management Before starting an instance, test the new instance profiles using the auxiliary program sappfpar on the operating-system level. After instance restart, verify that the instance is running without error. To ensure that the most current version of sappfpar is being used, execute OS command sappfpar ?. SAP's Internet Business Framework is the open architecture that enables arrangement of modularized components into an integrated functional package and provides the collaboration technology for building a solid Web application infrastructure at all levels (presentation, application, data).

SAP Clients and End-User Terminals In the SAP world, a "client" is a legal entity such as a corporation. The default "000" client contains client-independent settings. SAP AG reserves client "066" as part of its EarlyWatch service. 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

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. Add to the PATH environment variable ";C:\SAP\NSP\SYS\exe\run" so that  program exe's (such as sappfpar.exe) can be executed from any current folder.

Sample Environments An organization usually needs several environments. Here is an example: System name System client Server name Environment SF1 010 sap-dev1 Development - new programs are developed and tested here before they are transported to the QA environment SF2 020 sap-dev2 Prototype SF3 030 sap-int-1 Integration SF4 040 sap-qa-1 QA (QUality Assurance) SF5 050 sap-perf Performance SF6 060 sap-trng Training - used when participating in a training class. SF7 070 sap-prac Practice - has the same functions and transactions as the Production environment, but contains specially created data to support practice exercises for SAP training classes. PS0 090 Stage-1 Staging PS1 091 Production-1 Production PS2 092 Production-2 Production Fail-Over

Configure Applications Transaction SPRO is the main tree for SAP application configurations.