Skip to Content

Server installation

(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
    For more information, see the following :
    Note: This is not an official blog. Use at own risk. However, it may be useful.
  • 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.

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

  1. To be able to use your SAP GUI on your local WINDOWS system, then the application server must either be:
    • 0.0.1,
    • or a hostname if added it to your WINDOWS hosts file
  2. 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>
  3. The SAP GUI settings should be:
    • Application server =  127.0.0.1 or <hostname>
    • Instance = 00
    • System ID = NPL

 

ABAP Plugins for Eclipse

Go to the SCN space ABAP in Eclipse | SCN 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.

 

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.

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.

Export

To export objects with a transport of copies you have to execute the following procedure:

  1. In transaction SE01 choose Create (F6).
  2. Mark Transport of Copies and choose Enter.
  3. Enter a description.
  4. As transport target enter DMY and choose Save.
  5. Add the objects you need into the request. You may enter them either directly or via the menu Request/Task à Object List à Include Objects…
  6. Release the request.

You will find your transport files in the directories:

/usr/sap/trans/data

/usr/sap/trans/cofiles

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.

Import

To import transports into the system you have to execute the following procedure:

  1. Copy your transport files to:
  • /usr/sap/trans/data
  • /usr/sap/trans/cofiles
  1. For the file transfer you can use sFTP or SCP clients like WinSCP (see above).
  2. 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.

  1. In transaction STMS open the Import Overview (F5) and double click on NPL.
  2. In the menu select Extras à Other Requests à
  3. Use the F4 help to select your transport request.
  4. Choose Enter and answer the question if you want to attach the request to the NPL import queue with yes.
  5. Mark the request in the import queue and select Ctrl+F11 (Import Request).
  6. In the popup select for Execution “Synchronous” (for smaller request) and mark all import options.
  7. Choose Enter and Yes to import your request.

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.

 

To report this post you need to login first.

1 Comment

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

  1. Chris Eubanks

     

    Hi Julie,

    Thank you for making this available! I actually have Developer 7.50 installed, but I think this question is generic enough. I’m trying to get some practice with LSMW, which I can access via the SAP* or DEVELOPER role. I wanted to look at the actual tcode for creating a Customer so I could view the field names, structure, etc of the customer object, but when I enter tCode XD01 or FD01, the transaction is not found. Are these tCodes included in the Developer edition? I apologize for my newbie-ness.

    (0) 

Leave a Reply