(We provide you with several installation options:
- ./install.sh – installs the Developer Edition in dark mode, the installer will configure the SAP system for usage of the physical hostname
- ./install.sh -g– will present you a SAPINST GUI allowing you to modify certain system parameters. There is no official docu for this. However, this guide may be useful:
SAP AS ABAP 7.50 Dev Edition – Unofficial Install Guide by Taryck Bensiali.
- Note: Do not use ./install.sh -h <own hostname>– This allows you to specify your own hostname to be used by the SAP system. However, it is intended for advanced users only. Keep the default name for now.
Client installation (optional)
SAPGUI for Windows
If you have already a SAP GUI installation you can connect to your sytem. If not go ahead now with the client installation. See the SAP GUI space in SAP Community SAP GUI | SCN for more information.
ABAP License key
- Start the SAP system:
- Switch to user npladm with default password Appl1ance in the console : su npladm
- Start the SAP system : startsap ALL
- Log on to the system, client 000 as user SAP* with default password Appl1ance. In transaction SLICENSE , ascertain your hardware key.
- Request the license key for your trial version at SAP Sneak Preview License Key Request.
- Select NPL – SAP NetWeaver 7.x (Sybase ASE) as System ID.
- Enter your personal data and agree to the License Agreement.
- Choose Generate bottom right corner of screen.)
- The web site automatically generates a .txt file for this system/key. Download and save this file, eg on the desktop for convenience.
- Go to transaction SLICENSE and install the license file:
- In the tab Digitally signed licenses, delete the existing license, then choose Install. This opens the text file you got and installs the new license key.
Please note that all the above steps must be carried out; otherwise, the above user key will not work.
The system type changes to Demo. You can now explore the demo scenarios and develop using the ABAP tools in Eclipse and new features like the core data services or SAPUI5 UIs.
Renewing your license
Many of you have asked about this: Yes, you can apply for a new license. Just use the same procedure as above.
In theory, indefinitely, however, the ASE and HANA licenses last for about a year.
IMPORTANT: To use the developer key that we provide, you MUST delete your old license before you install the new one (as described in step 4 above). Otherwise, the system will generate a different license that no longer matches our pre-configured dev. key.
Administering the SAP NW ABAP 7.5 Developer Edition
Starting and stopping the server
With the user
npladm you can start and stop the server using the terminal commands startsap and stopsap respectively or the newer sap control commands.
To connect to SAP GUI for Windows:
The VirtualBox VM will likely be assigned the IP address 10.0.2.15 (because of the NAT network type). Your local WINDOWS cannot see that IP.
Instead it will communicate to the VirtualBox VM through port-forwarding using 127.0.0.1 (your windows local host).
- To be able to use your SAP GUI on your local WINDOWS system, then the application server must either be:
- or a hostname if added it to your WINDOWS hosts file
- Update in administrator mode the C:\Windows\System32\drivers\etc\hosts file and add an entry such as: 127.0.0.1 <your_vm_hostname>
- The SAP GUI settings should be:
- Application server = 127.0.0.1 or <hostname>
- Instance = 00
- System ID = NPL
Working with Web Dynpro ABAP (WDA)
Some users have experienced problems. If so, follow the instructions in this thread:
ABAP plugins for Eclipse
Go to the ABAP Tools page for instructions.
Guides and Tutorials
The Guides and Tutorials page includes:
- Reference scenarios
- Tutorials, eg for ABAP Basics, Core Data Services, SAP Gateway…
- Developer Guide to SAP HANA Studio
These reference scenarios, pre-configured content etc are all available out of the box. For your convenience, however, we have created a role displaying all this content, ZDEVELOPER:
For details of how to upload this role, see the blog Uploading the ZDEVELOPER Role…
Transporting ABAP development objects
NOTE: I have not tested this – use at own risk.
The system has been set up in a way that allows you to import and export ABAP objects as transport of copies. For security reasons we removed the rfc connection and user tmsadm. See TMS Documentation to complete the configuration.
This section describes an export/import scenario.
To export objects with a transport of copies you have to execute the following procedure:
- In transaction SE01 choose Create (F6).
- Mark Transport of Copies and choose Enter.
- Enter a description.
- As transport target enter DMY and choose Save.
- Add the objects you need into the request. You may enter them either directly or via the menu Request/Task à Object List à Include Objects…
- Release the request.
You will find your transport files in the directories:
For the file transfer you can use sFTP or SCP clients like WinSCP with user root and the private key file of your backend instance (see Connecting to Your Backend on OS Level) or you can directly import the existing PuTTY connection profile.
To import transports into the system you have to execute the following procedure:
- Copy your transport files to:
- For the file transfer you can use sFTP or SCP clients like WinSCP (see above).
- Ensure that user npladm has sufficient rights for accessing your transport files (e.g. use the command
chown npladm:sapsys <file>), otherwise the import will fail.
- In transaction STMS open the Import Overview (F5) and double click on NPL.
- In the menu select Extras à Other Requests à
- Use the F4 help to select your transport request.
- Choose Enter and answer the question if you want to attach the request to the NPL import queue with yes.
- Mark the request in the import queue and select Ctrl+F11 (Import Request).
- In the popup select for Execution “Synchronous” (for smaller request) and mark all import options.
- Choose Enter and Yes to import your request.
Directories and Users
The installation creates following directories and users:
|/sapmnt||~ 2 GB|
|/sybase||~ 50 GB|
|/usr/sap||~ 3 GB|
Created Users on OS level
The installation creates following users on OS level. During the installation you are prompted to enter the master password.
|sapadm||master password||Created by SAP hostagent|
|npladm||master password||SAP System Administrator|
|sybnpl||master password||SAP Database Administrator|
The installed system provides the following database users:
|SAPSR3||Appl1ance||SAP Schema User|
The installed system provides the following SAP users in client 000:
|DDIC||Appl1ance||Data Dictionary User|
The installed system provides the following SAP users in client 001:
Note: In general, you should develop using DEVELOPER or BWDEVELOPER (for BI content). SAP* is only for admin purposes, eg renewing the license.
|DDIC||Appl1ance||Data Dictionary User|
If you ever want to uninstall your server, proceed as follows:
- Delete the created directories
- Delete the OS users
- Delete the added lines in /etc/services (should be the last lines beginning with sap* and sql6* respectively)
- Delete the line containing nplhost in /etc/hosts
- Delete the symbolic link S99_nplhost.sh in the directory /etc/init.d/rc3.d in case of SUSE or /etc/rc3.d in case of Red Hat
- Restart your network.