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 …
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 …
What’s new with SAP NetWeaver Gateway 2.0 SP04 (note that this release includes support for JSON)
Some other housekeeping matters …
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.