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 -> IM_WINDOWS_X86_64
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 ...
14421119653247674476 |  |
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.
Comments