Skip to Content

Installing Trial SAP NetWeaver Gateway 2.0 SP04 with ABAP 7.02 on AWS – Part 3

This blog post follows Part 1 where we established a basic Windows 64-bit instance on Amazon’s Elastic Compute service, and Part 2 where we prepared the environment and downloaded the SAP Trial software.

Now we will actually proceed with the installation, continuing on after step 47 in Part 2 …

Step Screenshot

48.  Commence installation of ABAP Server

From your unpacked installation files on the instance D: drive, navigate through the folders as follows …

NWABAPTRIAL70211_64_GW204 ->

SAP_NetWeaver_702e _Installation_Master ->


Double click on the file ‘sapinst’


49.  Installation of ABAP Server

Within the software delivery tool, select the Central System option. 

Press the ‘Next’ button


50.  Installation of ABAP Server

You will see the warning shown in the image to the right.  Press OK.

SAPInst immediately logs you off, causing your Remote Desktop session to disconnect.  Log back in via Remote Desktop, and the installation will automatically continue.


51.  Installation of ABAP Server

Accept the license.

Press the ‘Next’ button.


52.  Installation of ABAP Server

For the Java Runtime Environment, specify the path to the JRE which you installed from Part 2 of this blog series.

Press the ‘Next’ button.


53.  Installation of ABAP Server

Specify a Master Password for your system. 

Press the ‘Next’ button.


54.  Installation of ABAP Server

You will see a warning ‘Your system does not meet some prerequisites …’.  The reason is that the Swap Size for your service is not as large as desired.  You can ignore this warning, as the installation will still proceed successfully.

Press the ‘OK’ button.


55.  Installation of ABAP Server

On the parameter summary screen, review the settings and check to ensure the target drive for the MaxDB database is the D: drive.

Press the ‘Next’ button.


56.  Installation of ABAP Server

Your installation will commence. 


57.  Installation of ABAP Server

After approximately 45 minutes (assuming you originally provisioned a ‘High’ instance), you should see the success message shown in the image to the right.

Press the ‘OK’ button.


58.  Installation of SAP GUI

Here we can also install the SAP GUI on the Windows Server itself.  Execute the installer for this which you unpacked in Part 2.

Select all default options and proceed through the installation wizard until the installation completes.


59.  Logging into the ABAP Server

Your SAP GUI should now be installed, and the SAP ABAP server should be running by default, after the installation.

Launch the SAP GUI, and create a new system entry as per the image to the right.


60.  Logging into the ABAP Server

Log into the server with the following default credentials ..

Username:  bcuser

Password: minisap


Congratulations!  You now have a running SAP NetWeaver ABAP 7.02 + Gateway 2.0 SP04 system.  Because of the ports we have opened in the course of this blog, you should be able to connect from your local machine.

*** IMPORTANT: To proceed with using the NetWeaver Gateway components, you will need to activate and configure the SAP NetWeaver Gateway component.  Follow the steps in this blog by Andre Fischer to do that. ***

Useful links are as follows …

General Documentation for SAP NetWeaver Gateway 2.0 SP04

What’s new with SAP NetWeaver Gateway 2.0 SP04 (note that this release includes support for JSON)

SAP NetWeaver Gateway Developer Guide

SAP NetWeaver Gateway Cookbooks and Tutorials

Some other housekeeping matters …

Topic Screenshot

Registering as a Developer

To register as a developer, simply attempt to create anything in ABAP (via SE80) and use the following key for user BCUSER …



Securing your ABAP Server

You can take some basic actions to tighten the security of your ABAP server.  Since we chose to open the ports for SAP GUI access from the outside, it is prudent to change the standard password for the BCUSER account in case anyone stumbles across your running server.

Note that the SAP* and DDIC user accounts will have the password chosen by you as the master password in step 53, so they should not be accessible to strangers.

I don’t purport to be a security expert, so if anyone has any further advice here, feel free to add it in the comments.


Stopping your ABAP Server

Whenever you finish working with your ABAP server, be sure to remember to STOP your ABAP server from the sapmmc console BEFORE you stop your AWS instance.

To stop the server, right-click on the green NSP icon and select ‘Stop’.  The next time you access your instance, you will need to remember to ‘Start’ it again.


Changing the Instance Type

After the installation is complete, you no longer need to retain a ‘High’ Instance Type.  You can downgrade this to a Medium instance, as the AWS fees are lower.  The ABAP server will start and operate fine with a Medium instance.  To do this, your AWS instance must be stopped.  Right click on it, and select the option ‘Change Instance Type’, then select m1.medium


Don’t forget to stop your AWS instance from the AWS management console when you are not using your instance, to limit your fees (and as indicated above, don’t forget to stop your ABAP server first).

I hope this blog series assisted you in establishing your SAP NetWeaver Gateway server in the cloud.  Don’t forget, this is a trial ABAP server, so you can also use it in the same manner as any basic ABAP server.  This means you can also use it to refine your skills with Web Dynpro ABAP, Floorplan Manager etc.

Addendum: Fellow SAP Mentor Sascha Wenninger has also posted an accompanying Part 4 to this series, which describes in detail how to assign an Elastic IP to your AWS instance, so you can continue to reference it with a consistent IP address.

Also see this excellent blog by Paul Aschmann who describes how to connect your new trial NetWeaver Gateway instance with the ES Workplace ERP system.

You must be Logged on to comment or reply to a post.
  • Depending on your network connectivity, you may get better results by accessing the ABAP system from a desktop / local copy of SAP GUI; just remember that, in the simplest AWS setup, the IP address you connect to will change every time you start a new version of your image ....

    There are ways around this (using Amazon's 'Elastic IP' or services like that can automagically update DNS every time the server starts), and they may be useful if you're sharing the server access with other people, services or devices (like an android ...)


    • Hi Martin,

      Actually yes I am using Elastic IP for my own setup.  I didn't include it in this blog series, partly because I got tired of taking screenshots (there were 65 in total).  But yes I agree, using Elastic IP makes things much easier.  And I think Amazon recently halved their fees for that service.



  • Hi John,

    Thanks for sharing, this is a valuable guide for anyone in the community wishing to get started with this. I have a few questions.

    1. How long does the trial last for? Can it be extended?

    2. Can you share how much this cost you so far? The prices look reasonable but I just would like to see a real world bill for this. I know it depends on how long you have the instance running but would just like to get a feeling for this, would it be $10 - $20 a month?

    3. Would this be something that you could share with others? I mean can you create a template based on your system and allow others to create their own, or does this violate the SAP licensing?

    Thanks again,


    P.S. Now I know what to spend the $75 voucher that amazon gave me recently for attending their web services event in the city!

    • Hi Simon,

      My understanding is that the trial license expires after 90 days.  I do not know if it can be extended, but I documented the whole process of installation (resulting in this blog series) to make it easy to repeat the process.  I have actually performed this installation twice, once for the SP03 release, and again for the SP04 release. 

      In terms of costs, they have been negligible.  In relation to charges, because of a $25 voucher (clearly you did better) I haven't seen any charges come through yet.  To-date, I have been very happy with the service and the pricing.  My calculations have been as follows (for my own usage profile) ...

      90GB Elastic Block Storage - $9/month

      Std On-Demand Medium Instance - ~$9/month (based on 2 hrs/night for 20 nights/month @ $0.23/hour Singapore instance)

      Data Transfer - $0 (assuming I don't breach 1GB per month)

      Elastic IP Address - $3.60 per month (based on 720 hours per month * $0.005 per hour for when the IP address is not associated with a running instance)

      So in total, I am estimating ~$22.00 per month for my usage profile.  And when I am finished with it, I can terminate the instance and release the Elastic Block Storage.  Don't forget in Australia at least, these charges are most likely claimable as a tax deduction.  If you compare the thousands of dollars you might spend with SAP Education for a few days of training, I think these AWS charges are a good deal.

      In relation to cutting an 'AMI' image, I thought about that but decided not to for a few reasons ...

      • Yes it would be a breach in licensing, at least in my opinion
      • This 'image' would become out of date within a few months.  For instance, not long after I installed Gateway SP03 on AWS, SAP released SP04 (which my blog series is based on).
      • You know the old saying, 'If you teach a man to catch a fish ...'.  The concepts taught in this blog series can be mapped to other Trial installations.  For instance, SAP have also recently released a Trial NetWeaver ABAP 7.3 instance (for which you can trial ABAP in Eclipse).  If people follow the steps closely in my blog series and install Gateway, then this should give them enough confidence to install other Trial instances released by SAP in future.

      Lucky you, I think that $75 voucher will serve you well!



      • Hi Simon,

        One thing I should have mentioned .... If instead of only running your instance whenever you need to work with it, if you leave it running, the fees for the EC2 instance alone will become substantial.  Here is a calculation for one month ...

        30 days * 24 hours * 0.23/hour = $165/month

        So, remember to stop your instance when you are not using it, and then start it when you do need it!  I also configured basic CloudWatch, which is a free service by AWS which can send you email alerts based on certain criteria.  For instance, I send an email to myself whenever the CPU is detected as > 1%.



      • Thanks for sharing John - all these numbers look small when you see them per hour so it is nice to see a practical example, I totally agree with you, it seems like great value - I'd better find that voucher!

        Just one other question... when you download the installation media for SAPGUI and the Trial Version, that is 3 - 4 Gb of data right? Does Amazon count that toward your data transfer?



        • Hi Simon,

          Per this link, I see that Amazon's charge for Data Transfer IN to your instance is currently $0.0000 per GB.  At the moment they only seem to charge for Data Transfer OUT, and for that only after you have transferred more than 1 GB during the month, with a charge of $0.12 per GB thereafter.  Pretty reasonable if you ask me.

          My experience to-date with Amazon AWS is that they are genuinely reasonable in their pricing. That said, you will get a shock if you leave your instance running for a month and don't realise it.



  • John,

    Just a FYI that I got my gateway trial up and running on AWS and your guide was spot on and extremely well written. Thanks for making it easy for us!

    Cheers, Paul

    • Hi Paul,

      Thanks for the feedback.  I'm glad it all worked well for you.  I have this philosophy these days that if just one person benefits from my blog, then it was worth the effort.  That said, I always knew that I myself would be referencing these blogs in future, because they are my notes on how to repeat the process, simply shared with the community.



  • Hi John,

    I am getting following error when trying to install SAP frontend. Could you let me know how I could resolve this issue?

    Error while connecting to communication partner - see preceeding messages.

    Could not connect to host localhost on port 21212. Connection refused: connect Connection refused: connect



  • Hi John,

    Thank you for explaining the installation process of Gateway 2.0.

    My question is if we have the already installed the ABAP server NSP then how can we add the Gateway Add-on. Is there a way that we can install only the Gateway Add-on on an already installed ABAP server? If yes, can you please provide me some pointers from where I can download just the Gateway Add-on.



    • Hi Abhishek,

      I am not aware of SAP offering a trial Gateway Add-on installation for the Trial NSP server.  Of course if you had a service marketplace login and are licensed for Gateway where you work, you could try to install that. 



      • Hi John,

        Thank you for your reply.

        I have service market place login but not authorised to download the Gateway add-on 🙁 .

        Then I think we have install the the complete package with the ABAP server again in order to install the Gateway  add-on.

        Are there any suggestions to install the same?



    • Hi Angad,

      Sorry, you're on your own here.  I haven't ever installed such a system myself.  If anyone reading this has, please feel free to add your thoughts to the comment stream.



  • HI John,

    i'm new to sap .i've installed trial version 7.02 and gui as well.but in abap editor i was asked to enter access i have to install netweaver gateway .if not,how will i get access key.



    • Hi Simran,

      Usually, it is provided within the NetWeaver documentation which is downloaded (later extracted) with installer. For example, I downloaded SAP NetWeaver 7.3 ABAP AS and when I extracted the exe then there was a html file named "start.htm". The key was mentioned under section "Installing the SAP GUI for Windows (SAP frontend)" in "Start.htm".

      Please note that you can only create or edit object within customer namespace i.e. starting with Y or Z. So when you create a program then use Y or Z in front of it. For example: Z_testprogram



  • Hi John,

    Thanks for sharing this information. Can you please share how to install SAP NetWeaver Stand alone Gateway. I have installed gateway  on Netweaver  as an add-on installation. Now I need to know how to install gateway as stand alone.


    Jithin M