miniSAP Installation – Part 3

Installing miniSAP on our new Linux system

You are one step closer to owning your own Personal SAP System. In Part 1, we Installed Linux Mint for our SAP system and in Part 2, we Configured the Linux system for our SAP Installation. In this part, we will install miniSAP on the Linux system which we have installed and configured.

Now is the time to pop open another beer. A big one, if you bought them in several sizes. 😛

Remember all the .rar files that we’ve downloaded, containing the SAP system? Let’s decompress them to the Shared Folder. First copy the files to the Shared Folder.

Now let’s extract them. I use 7Zip, which I’ve grown fond of, but there are several programs to extract .rar files available. Use the one you prefer:

Sit back. Watch a couple of episodes of that amazing show that is on TV that you love so much, and let’s wait for the extraction to be completed. I’ll be here when you get back.

So you’ve extracted the files into the Shared Folder. Now it’s time to start the SAP installation, per se. Just write the following commands:

cd /media/<your shared folder name>

…where <your shared folder name> is the name of the Shared Folder, in my case sf_SharedFolder.


This command lists the files on the current folder. You should see something like this.

In case you still have them, you can get rid of the .rar files, since they’re only taking up space:

rm *.rar

Then you set the permissions for the install script to be executed.

sudo chmod +x

And run the installation script (the -g flag means that we will be running the GUI version of the installer. If you want to have just the command line version, omit the -g):

sudo ./ -g

Oops! Error!

This is because we’re missing one final step. You know when you enter a new server on SAPGui. How would we do that in this case, since we don’t know the IP address of our SAP system?

First, write.


on the terminal.

See where it says inet addr? That’s our IP address. Save it on a paper somewhere. We’ll need it now and later on when we’re configuring SAPGui.

Now write.

sudo nano /etc/hosts

(I prefer vim, but nano is more user friendly for beginners, and I don’t want to enter an emacs vs vim war, so let’s go with that). 🙂

On the second line, we see our hostname, but the IP address is a local one. We’ll have to comment this line and add our own IP address. To comment, you use a # symbol. In the end, it should be something like this.

Just use your own IP address and not the own shown above, and we’re all set. To leave this program, press CTRL+X, press Y to confirm that you want to save, and press ENTER to confirm the file name:

Now we can repeat the sudo ./ -g command from before.

Press ENTER and read carefully the licence agreement… or scroll down (tip, to scroll down faster, keep pressing SPACE – it works like PAGE DOWN on these unix walls of text).

At the end of the license agreement write yes and press ENTER.

Now choose a password. I’ve used the same one as my Linux system, so I don’t forget it. It will be used for administrative purposes, and remember the rules (at least 7 characters, with at least a capital letter, small letters, digits and no other characters. Again, we’re going to go here with Abap2017).

And now you can get the rest of the six pack because it will take a while… actually, go buy another one from the grocery store. This screen will be greeting you when you come back home. 🙂

Are you back? OK, then. After a while, you’ll see some more familiar SAP colors. 🙂

If some error happened, you can contact us through the comments section, and we’ll try our best to help you out. In my case, I had a failure on the first installation and so I repeated it. If that happened to you, I suggest you to delete everything in the /sapmnt folder.

Attention – do only the following line of code if the installation failed for some reason.

sudo rm -fr /sapmnt

In my case, I tried to reinstall without deleting, so for those to which that happened, the following screen may appear. You’ll just click Next while selecting the first option.

Here we won’t change anything as well, so just click Next (and another – tiny – sip of beer…). 😀

For a changeJust 4 Versions of the same program to understand OOPs ABAP

This next screen seems scary, but we’ll continue using the old aunt approach, by clicking Next. 😀

And then we will disobey a bit by saying No (otherwise it would repeat the pre-requisites check):

Guess what button we will be pressing now? That’s right, Next. 😉

This next screen is a bit more serious. We need to setup the password for the npladm user, which is the user responsible for starting our SAP instance. It’s better if we use the same password we’ve used before, to keep consistency. After all, this is not a production machine. This is a machine used for our own training, and as long as we keep our personal computer safe, there shouldn’t be a problem in using the same password throughout our SAP system. As long as we don’t forget that one password…

After the password is set, you can press… Next (notice that it is using the csh login shell that we installed earlier. Later we will see it in action).

The same applies to the following screen.

In this screen, we leave the default settings and press… Next (hey! I just remembered a nice drinking game!).

In the next screen, we’ll leave it as it is and press Next. This screen is for the setting of the database users’ passwords. (Note: I don’t know if we can set our own passwords here. The installation always worked fine without touching this screen, so I prefer to err on the side of caution. If someone has any information regarding this, please leave a comment).

Here we change to Default Key and press Next.

Since we won’t be executing our SAP system from outside our home, we leave the default DNS settings (we would have to set up a server to access it from outside our local network. That is something we’ll not be getting into here).

Press Next.

Again here, press Next.

And here… Next.

In the next screen, we have a summary of all the settings we’ve chosen, which allows us to change anything, in case we made any mistakes. Since we are happy with our work so far, let’s click Next.

Did you actually manage to get another six pack from the grocery store? No? Then go back. 😀 This will take a while – SAP is finally installing.

During this part of the installation, you may face some errors, like this.

My best tip to take care of these errors is to delete the temporary installation folder and the SAP NPL installation folder and try to do it again. If that doesn’t work, then install Linux again and be careful to provide a password that complies with the restrictions mentioned before.

But the best tip that I’ve read concerns the error Unable to generate a new password for database login ‘sa’. This error occurred to me several times but the only way I’ve managed to address it is by following the instructions contained on the PDF of this URL, and also by deleting the temp and SAP NPL installation directories.

To delete the folders, write the following on the terminal.

sudo rm -fr /tmp/sap*

sudo rm -fr /sapmnt/NPL/*

This is the step in which your patience is required, because some things can go wrong and you have to keep trying to make it work. Be patient, delete the folders, follow the (thankfully short) instructions on the PDF mentioned above and it eventually work out. I’ve installed SAP on four computers, two of them went without a hitch, another went… OK… and the last one went totally berserk. But we got there!

Also Read: Struggle of an ABAPer in SAPUI5.

And finally, if all goes well, you’ll reach something like this, in which you just press OK and we’re done.

The next highlighted sentence should be a good reason to take a good swig at your beer. 😀

A final configuration is needed, in case we want to develop WebDynpro or SAPUI5 applications – that require the browser to recognize your hostname.

List the files in /usr/sap/NPL/SYS/profile.

ls /usr/sap/NPL/SYS/profile

Notice the NPL_D00_vhcalnplci file? Open it:

sudo nano /usr/sap/NPL/SYS/profile/NPL_D00_vhcalnplci

Go to the SAPLOCALHOST line and write under it:

icm/host_name_full = $(SAPLOCALHOST).dummy.nodomain

It should look like this.

Save it and then we can proceed to install SAPGui… I promise, that would be our last part and you would be able to write your first Program on your virgin SAP system. 🙂

…on Part 4!

The other parts of this article can be accessed on the following links:

Part 1 – Linux Mint Installation

Part 2 – Configuring Linux for the SAP installation

Part 3 – Install SAP on Linux System

Part 4 – Installing and configuring SAPGui