Skip to Content

For general information, download link, operating system and hardware requirements see the Developer Edition to Download: Introduction page.
Note: If you experience any problems when installing using this guide, please use the following detailed guide:
Linux for Newbies: Detailed Installation Guide, ABAP AS 751 SP02

(Also, since each virtual machine eats up HD space, ideally remove the faulty VM first, and start again.)

To get the new ASE license (valid until Q1 2019), see this blog SAP AS ABAP 751 SP02 to download.

(This Sharepoint folder includes instructions.)

Installation Instructions and First Steps

Prerequisites

Hardware requirements:

  • x86_64 Processor based hardware
  • Required: At least 8 GB RAM plus about 8 GB swap space
  • Recommended: At least 16 GB RAM plus about 8 GB swap space
  • About 100 GB free disk space for server installation
  • About 2 GB free disk space for client installation

Network configuration of the SAP host operating system: The officially supported setup requires a static IP address for the hostname used for the SAP installation. Using DHCP is possible for this developer edition, but be aware of potential consequences. If our installation cannot ping the hostname specified when installing, the installation and startup of the SAP system will fail. Make sure that the hostname specified during installation fulfills SAP requirements, most importantly that it does not exceed 13 characters length and also needs to survive subsequent reboots.

Firewall: Deactivate the firewall.

Additional software requirement

The following software packages are required:

  • csh – Ubuntu and Debian require you to install csh before you start the ABAP installation
  • libaio – SAP Sybase ASE requires the libaio library to start the installation
  • uuidd  – SAP AS ABAP requires the OS to run uuidd service to ensure the uniqueness of GUIDs. For more information – eg on why this is extremely important – please see archive thread 3379688: Is it mandatory to have uuidd for SAP installation
  • English – SAP AS ABAP requires that you configure English (LANG=en_US.UTF-8) as the operating system language

Server Installation

    1. Login as root (sudo). You need to have the password of the root user at hand, as the installation needs root privileges.
    2. Ensure that you (as superuser) have the necessary executable rights:
      chmod +x install.sh
    3. Extract downloaded archive: unzip archive.zip. Make the extracted download archive available on the server.
    4. Go into the root directory of the extracted archive.
    5. Run the installation, using the command: sudo ./install.sh

    (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
    • ./install.sh -h <own hostname>– allows you to specify your own hostname to be used by the SAP system
    • ./install.sh -s – allows you to skip the hostname check )

     

    1. Read and accept the license agreement.
    2. When prompted for a password, enter your master password of the virtual Linux OX instance twice.
      (All options prompt you for a master password. Please ensure that the password length exceeds 7 characters, contains capital letters and digits but does not contain special characters. The installation starts the database and server.)

    The installation will take a while (about 20 minutes – feel free to get a coffee).

    If the installation was successful, you should see the following message:

    • Instance on host vhcalnplci started
    • Installation of NPL successful

Client installation (optional)

SAPGUI

If you have already a SAP GUI installation you can connect to your sytem. If not go ahead now with the client installation. SAP GUI space in SDN SAP GUI | SCN leads you to more documentation around SAP GUI for Java Environment. Requirements for the SAP GUI for Java include: Sun Java SE 6 32-bit or 64-bit, a properly installed Java Plugin and C++ runtime libstdc++.so.6.

ABAP Plugins for Eclipse

Go to the SCN space ABAP in Eclipse where you will find download links and tutorials.

Post-Installation Steps

ABAP License key

  1. Start the SAP system:
    • Switch to user npladm with default password Appl1ance in the console : su npladm
    • Start the SAP system : startsap ALL
  1. Log on to the system, client 000 as user SAP* with default password Appl1ance. In  transaction SLICENSE , ascertain your hardware key.
  2. 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.
  3. 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.

 

Proxy Settings

Make the following proxy settings:

Administering the SAP NW ABAP 7.5 Developer Edition

Starting and stopping the server

Terminal commands

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.I

Directories and Users

The installation creates following directories and users:

Created Directories:

Directory Size
/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.

User name Password Description
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:

User name Password Description
SAPSR3 Appl1ance SAP Schema User

The installed system provides the following SAP users in client 000:

User name Password Description
DDIC Appl1ance Data Dictionary User
SAP* Appl1ance SAP Administrator

The installed system provides the following SAP users in client 001:

User name Password Description
DDIC Appl1ance Data Dictionary User
SAP* Appl1ance SAP Administrator
DEVELOPER Appl1ance Developer User
BWDEVELOPER Appl1ance Developer User

Uninstalling instructions

If you ever want to uninstall your server, proceed as follows:

  1. Delete the created directories
  2. Delete the OS users
  3. Delete the added lines in /etc/services (should be the last lines beginning with sap* and sql6* respectively)
  4. Delete the line containing nplhost in /etc/hosts
  5. 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
  6. Restart your network.

 

Note: Since we now have 6 blogs referring to 2 different versions of the download developer edition, blog comments are becoming unmanageable. In addition, searching through blog comments is very difficult for other users, resulting in many duplicate issues.

From now on, please DO NOT post a blog comment if you require troubleshooting.

Please post on the ABAP Development forum : https://www.sap.com/community/topic/abap.html , using the hashtag #ABAP_Trial. I promise to work through the backlog here, but cannot answer any further blog comments.

In case of Linux problems read the Linux FAQ.

Thank you for your understanding.

To report this post you need to login first.

13 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member

    Hi,

    When I am trying to debug even in simple system codes like “SE80”, “SE11” etc. The GUI is not responding. Is this because of RAM? (I am using 4GB) or what I am missing?

    Thanks.

    (0) 
    1. Julie Plummer Post author

      Hi Serkan, It may be a hardware issue. Here are the

      Ensure you have the following hardware:

      • x86_64 Processor based hardware
      • Required: at least 8 GB RAM plus about 8 GB swap space;
      • Recommended: at least 16 GB RAM plus about 8 GB swap space;
      • About 100 GB free disk space for server installation
      • About 2 GB free disk space for client installation
      • English – SAP AS ABAP requires that you configure English (LANG=en_US.UTF-8) as the operating system language

      (from Newbies’ Guide.)

      Best wishes Julie R Plummer.

      (1) 
  2. Rogerio Balassiano

    Julie,

     

    Great Blog. Thank you.

    Do you know how to connect Sap 7.51, VM, to be a destination in Sap HCP Trial ? I would like to use it as Odata source in Sap Web Ide tests.

     

    Thanks.

    (0) 
    1. Julie Plummer Post author

      Hi Rogerio,

      Thank you!

      Have you tried this:

       

      Connect to ABAP Systems?

      If that fails, then I would try the SAP CP forum.

      Also, please bear the following (see below) in mind – it also make the platform more searchable for others.

      THanks Julie.

      Note: Since we now have 6 blogs referring to 2 different versions of the download developer edition, blog comments are becoming unmanageable. In addition, searching through blog comments is very difficult for other users, resulting in many duplicate issues.

      From now on, please DO NOT post a blog comment if you require troubleshooting.

      Please post on the ABAP Development forum : https://www.sap.com/community/topic/abap.html , using the hashtag #ABAP_Trial. I promise to work through the backlog here, but cannot answer any further blog comments.

      In case of Linux problems read the Linux FAQ.

       

      (0) 
  3. Former Member

    Hi Julie,

     

    This is on developer key. Could you help me with getting it pl. ?

     

    I did step 3 and 4 to make hardware license as DEMOSYSTEM. Now i need developer Key to proceed.

     

    Thanks

     

    Om

    (0) 
    1. Julie Plummer Post author

       

      Hi Om,

      Use : 35408798513176413512 .

      Some users have had the issue that this is not recognized in ADT. If so, open a normal SAP GUI Transaction in SAP GUI – eg SE80. Create a new object (eg data element). Paste the key in there.

      If you log out and log back in, the key should now work in ADT (!).
      Best wishes Julie.

      (0) 
    1. Julie Plummer Post author

      Hi Wouter,

       

      Basically, you can transport any development objects from another system. But the server is not intended, for example, to provide a base for a full-blown ERP Suite on top.

      Can you give an example of what you would like to do?

      Best wishes Julie.

      (0) 
  4. Fred Wilhelms

    Hello,

    Installing SAP NW AS ABAP 751 SP02 – Developer Edition on openSUSE Leap 42.3:

    I unzipped the downloaded RAR-files.
    After unzipping the RAR-files there is no directory „sybase/NPL/SYSAM-2_0/licenses“. So I installed the server without replacing the file „SYBASE_ASE_TestDrive.lic“
    After installing the server I got the error-message „Unable to verify database access for login SAPSR3“. But now there is a directory named „sybase/NPL/SYSAM-2_0/licenses“. So I replaced the file „SYBASE_ASE_TestDrive.lic“ with the downloaded newer one ( user sybnpl / group sapsys / rights -rwxr-x— ) and repeated the server installation.
    After repeating the server installation I got error-messages „… id=modlib.jslib.caughtException errno=MUT-03025 …“ and „… id=controller.stepExecuted errno=FCO-00011 …“. with the note „To solve that problem start the installation without using SAPINST_START_GUI option“. But I had started the installation without SAPINST_START_GUI option!
    I had a look in log-files but I didn’t find any solution. So I don’t know what to do now. Is there anybody who is able to help me? Thank you very much in advance!

    (0) 
  5. Julie Plummer Post author

     

    Dear all,

    As of now, I will not be able to moderate comments on this blog. Therefore, comments entered after today, 26th July, 2018 will have to be ignored. (I will try to process existing comments as soon as I can, but there is a backlog.)

    From now on, please ask your question in the ABAP Development Community forum:

    https://www.sap.com/community/topic/abap/all-content.html

    If it is an issue involving ABAP developer edition, remember to add the hashtag #ABAP_Trial.

    Please do not use comments in the blogs to ask tech support questions :

    • It makes it difficult for other users to find similar issues in future, which leads to many duplicated errors.
    • Very few people follow these blogs, so you will not get help from the vast majority of the community

    I apologize for this, but there is no capacity to monitor all blogs for all released versions.

    Best wishes Julie.

     

    (0) 
  6. huang lin

    hi,i restart the sap server,i can not logon the SAP GUI.but before the restart the SAP SERVER ,i can logon it。anyone knows why?(restart the opensuse din’t effect!)

     

    (0) 
    1. huang lin

      i can not logon the SAP GUI after change the TCODE-RZ10!(because i want to CLIENT COPY),when i SAVE and ACTIVE the DEFAULT parameter and restart the SAP SERVER,it shows this error !

      (0) 

Leave a Reply