Technical Articles

Julie Plummer

September 13, 2018 5 minute read

AS ABAP 7.52 SP01, developer edition: Concise installation guide – OBSOLETE

Note 1: We have now moved to AS ABAP 7.52 SP04, so please don’t download this version any more. Thanks

Note 2: 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.

In case of Linux problems read the Linux FAQ.

Thank you for your understanding.

Installation Instructions and First Steps

Prerequisites

Hardware requirements:

x86_64 Processor based hardware
Required: At least 4 GB RAM plus about 8 GB swap space
Recommended: At least 8 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 7.50 for Java / Windows

If you have already a SAP GUI installation you can connect to your sytem. If not go ahead now with the client installation, available as part of the download. SAP GUI space in SAP Community leads you to more documentation around SAP GUI for Java Environment. Requirements for the SAP GUI for Java include: Oracle Java SE 6 32-bit or 64-bit (update 40 or later), a properly installed Java Plugin and C++ runtime libstdc++.so.6.

ABAP Plugins for Eclipse

Go to the SAP Community space ABAP Development and scroll down to “ABAP Development Tools (ADT)”, where you will find download links and tutorials.

Post-Installation Steps

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

Proxy Settings

Make the following proxy settings (Oracle Virtual Box only):

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	master password	SAP Schema User
sa	master password	Superuser
sapsa	master password	Superuser
sapsso	master password	Superuser

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

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

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

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

Uninstalling instructions

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.

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.

25 Comments

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

Ahmed Lakssiouer

October 18, 2018 at 11:28 pm

Hi , Thanks first for this great guide

When I execute the command ./install.sh I have this message error :

the hostname you have chosen is either configured on a loopback device or not active on this server ,please check your configuration and hostname selection . if you are confident about your choice of hostname start the install script with -s flag to skip the hostname check .

and when execute the ./install.sh -s command , the installation failed with this error message :

Installation of NPL failed ,please check logifiles in tmp /tmp/sapinst_instdir

Can you help me to resolve this problem

Thanks for your help in advance

Julie Plummer

Blog Post Author

October 24, 2018 at 11:56 am

Hi Ahmed,

There are several possible reasons for this.

See our FAQs (Search for loopback).

If that fails, please create a new question in the ABAP Development Community forum:

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

There, please attach your .log files (found in /tmp/sapinst_instdir..., ending .log). Please do NOT copy and paste the whole .log file into the comments; it is very hard to read if everyone does this. Thanks

Remember to add the hashtag #ABAP_Trial.

Best wishes Julie.

Oleg Evgrafov

December 6, 2018 at 8:54 pm

At first check your /etc/hostname (must be vhcalnplci) and your /etc/hosts – if you use Oracle VM VirtualBox it must be 10.0.2.15 vhcalnplci.dummy.nodomain vhcalnplci

If you steel have this message try to edit install.sh in that way:

find string myip=`ifconfig | egrep “inet addr” | grep Bcast | awk ‘{ print $2 }’ | awk -F “:” ‘{ print $2 }’` and replase it with myip=”10.0.2.15″

the same is hostip=`ping -c1 -n ${virt_hostname} | head -n1 | sed “s/.*($[0-9]*\.[0-9]*\.[0-9]*\.[0-9]*$).*/\1/g”`

replase it with hostip=”10.0.2.15” safe and try to run sudo ./install.sh

(This message may appered in the 7.50 and 7.51 distr, in 7.52 installation i wasn’t met it )

When i install 7.52 Netweaver on opensuse, that was error:

Error: libaio: shared library not found Error: libstdc++: shared library not found Error: libnsl: shared library not found

if it so – open install.sh with editor and everywere replace string “opensuse” with “opensuse-leap” , safe install.sh

Run sudo ./install.sh , answer – yes to all qwestions, including try to install this lib’s ,and maybe you finish installation with positive result like me.

Muhammad Ilyas

October 24, 2018 at 6:38 pm

Please look into following Julie Plummer

https://answers.sap.com/questions/666583/error-during-as-abap-752-sp01-trial.html

Gregor Wolf

November 29, 2018 at 4:06 pm

Hi Julie,

last weekend I ran into the issue that the database of my NPL 7.52 got full. That is caused by the fact that the Max Size parameter for the default segment was set to 0. I’ve use the DBCOCKPIT Transaction now to adjust the size:

Before I was able to resolve this issue I was in contact with Matthias Wild and his colleague Former Member because of this error:

Login failed.
CT-LIBRARY error: ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.

that I’ve got when I tried to login with the database users and passwords you’ve provided using the isql64 command line as user sybnpl. The root cause for this was that the users sa, sapsa and sapsso are written in lowercase. The user sa is locked by default. And the password of the SAPSR3, sapsa and sapsso is set to the Master Password and not to the Down1oad password. Please correct that in your documentation.

Best regards
Gregor

RAQUEL LAJOS

December 1, 2018 at 11:52 am

Hi Julie,

I´m trying to get a new license key with the URL https://go.support.sap.com/minisap/ (SAP Sneak Preview License Key Request. ) and It doesn´t work!!!

What is hapenning? Can you help me?.

Thank you very much.

Best regards,

Rachel

Sandra Rossi

December 1, 2018 at 5:02 pm

Same for me, empty cyan page except top line with SAP logo at the left. It seems that the server is currently experiencing problems. Try later.

Julie Plummer

Blog Post Author

December 4, 2018 at 12:09 pm

Hi Raquel, Sandra, all,

es, it's an issue. As a workaround, Try it with the debug parameter:

https://go.support.sap.com/minisap/?sap-ui-debug=true#/minisap

Please let me know if that works. I'll pass on the real solution asap.

Best wishes Julie.

Sandra Rossi

December 4, 2018 at 3:13 pm

Thanks, it worked for me.

Rahul Borkar

December 7, 2018 at 6:16 pm

Finally got this working on VirtualBox+openSuse after 3rd attempt.

Thanks for posting the installation guide.

Dmitriy Romanov

January 8, 2019 at 1:01 am

Hi!

After install i have a lot messages in syslog -

Database error 241 with OPC access to table SDRAFT_PROC_EXP

[ASE Error SQL241][SAP][ASE ODBC Driver][Adaptive Server

Enterprise]Scale error during implicit conversion of DECIMAL

value '20190108004328.8812470' to a DECIMAL field.

Stop Workp. 11, PID 28766

Julie Plummer

Blog Post Author

January 28, 2019 at 1:14 pm

Hi Dimitriy, These are ASE error messages. Your best bet is to try the SAP ASE forum.

Best wishes Julie.

Sandra Rossi

March 18, 2019 at 4:02 pm

Hi Dmitriy Romanov I have exactly the same many messages for SDRAFT_PROC_EXP and SDRAFT_LOCK_EXP, did you find a solution ?

Thanks. Sandra.

Alfredo Gomez Ripoll

April 14, 2019 at 2:36 pm

Hi Sandra

I´ve just installed and the same error is in SM21, did you find any solution?

Thanks

Sandra Rossi

April 14, 2019 at 2:56 pm

No, still the same messages again and again…

SM21 (system log):

ST11 (developer trace):

Sandra Rossi

April 14, 2019 at 5:47 pm

Okay, I found the bug. Reason: the CDS function "TSTMP_ADD_SECONDS" is implemented differently in SYBASE ASE (works for timestamps WITHOUT microseconds) and in HANA (works for timestamps with microseconds). In the CDS view SDraft_Configuration, the following lines have the bug:

case
// when Customer.draft_entity is not null
// then tstmp_add_seconds( :p_current_time,
// cast( -Customer.expiry_duration as abap.dec(15,0) ),
// 'FAIL') 
 when Entity.draft_entity is not null and Entity.expiry_duration > 0 
 then tstmp_add_seconds(:p_current_time,
 -Entity.expiry_duration,
 'FAIL')
 else tstmp_add_seconds(:p_current_time,
 -Global.expiry_duration,
 'FAIL')
 end as expiration_time

It could be solved if you find a way to change these lines as follows:

case
// when Customer.draft_entity is not null
// then tstmp_add_seconds( :p_current_time,
// cast( -Customer.expiry_duration as abap.dec(15,0) ),
// 'FAIL') 
 when Entity.draft_entity is not null and Entity.expiry_duration > 0 
 then tstmp_add_seconds( floor(:p_current_time),
 -Entity.expiry_duration,
 'FAIL') + :p_current_time - floor(:p_current_time)
 else tstmp_add_seconds( floor(:p_current_time),
 -Global.expiry_duration,
 'FAIL') + :p_current_time - floor(:p_current_time) 
 end as expiration_time

Alfredo Gomez Ripoll

May 4, 2019 at 12:45 pm

Excellent Sandra, it works perfectly.

People like you make the Sap Community so useful.

Thank you ¡¡

Dmitriy Romanov

May 26, 2019 at 9:16 am

Hello!
how can i change this?
requires an object Access key.

Sandra Rossi

May 27, 2019 at 7:18 am

I was lazy, I didn't report the issue to the SAP support. I don't know if one patch exists. If you can do it, then that's the right way to solve a standard bug. There's another solution if you're using the Developer Edition, remember that most of ABAP features like input and check of modification keys are implemented by ABAP programs, and you can do almost everything you want in debug mode...

Dmitriy Romanov

July 30, 2019 at 6:08 pm

thank
i fixed using your instructions

Takieddin Mohamad

February 12, 2019 at 1:15 pm

Hi!

could you please tell me where I can find the developer key for 752 SP01 Trial version

best regads

Taki

Sandra Rossi

February 12, 2019 at 7:37 pm

it's indicated in one of other Julie's blog posts, it's easy to find.

But as she said in the blog post, "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."

Matheus Brasil

May 10, 2019 at 2:20 pm

Hi Julie Plummer, I've trying install As ABAP 7.52 as you show in this guide but get a lot of errors. Could you give me some help? This link has my last log https://git.io/fjCwO.

Julie Plummer

Blog Post Author

May 13, 2019 at 6:41 am

Hi Matheus,

As I said above ”

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.

“

Thanks and best wishes,

Julie.

Peter Strauss

August 4, 2023 at 8:01 am

Here's some notes for anyone who didn't renew their NPL license in time and also forgot the passwords in all clients for the SAP* user (yes, I allowed myself to get into this mess).
The aim here is mostly to provide guidance for using isql which most people probably have never used before.

Start by logging in and deleting entries for user SAP* from table USR02

su - sybnpl
password: <the password you set for OS users. You need to know this>

isql -SNPL -USAPSR3 -X
password: <this is the same as the user you set for OS users, so it should be the same as the password you used above. See the blog entry above for details>
NOTE: in isql CASE is important. You need to use uppercase for NPL and SAPSR3 in the command above. If you are used to Oracle then this might be new to you

delete from USR02 where bname = 'SAP*'
go
commit
go

(Again, make sure you use upper case for the able name USR02 even though it isn't quoted. I'm not sure whether commit is necessary but it didn't hurt. Maybe Sybase has an autocommit function, who knows?)

Enable login with default password for user SAP* by setting the following parameter in your instance profiles. The DEFAULT profile didn't seem to work.

Restart the system to enable the parameter you just set.

Now you can logon to the system using the default password for 'SAP*', which is 'PASS'.

See note 3303172 - Activating a Super-User SAP*

Now you can follow the instructions in the following blog to update your license.

Renewing the license for SAP NetWeaver AS ABAP 7.50 Developer Edition

Technical Articles

AS ABAP 7.52 SP01, developer edition: Concise installation guide – OBSOLETE

Installation Instructions and First Steps

Prerequisites

Additional software requirement

Server Installation

Client installation (optional)

SAPGUI 7.50 for Java / Windows

ABAP Plugins for Eclipse

Post-Installation Steps

ABAP License key

Renewing your license

Proxy Settings

Administering the SAP NW ABAP 7.5 Developer Edition

Starting and stopping the server

Terminal commands

Directories and Users

Uninstalling instructions

Assigned Tags