After following John Moy’s blog series on setting up the Netweaver Gateway trial on Amazon EC2, I thought it would be helpful to share how to connect your shiny new gateway trial to the ES Workplace ERP. Since using the ES Workplace systems a couple years ago for a CRM Mobile app, I have always praised the ES team for putting together a great set of resources for encouraging and enabling a service oriented architecture (SOA). The systems (ECC, CRM and PI) are great for doing testing against and developing POC’s or demo apps. In this case we will be using the ERP instance to connect our Gateway system for data consumption.
In this example we will be initially connecting our systems together and then going through setting up a very basic example of consuming data from the ES Workplace ERP system via the Netweaver Gateway system sitting in the AWS cloud.
Please note that the Prepackaged Netweaver Gateway Trials already have this configured and ready for your username/password.
|In order to connect and consume data from the ES Workplace ERP system, you will need an account. You can create one here and it only takes a couple of minutes: http://www.sdn.sap.com/irj/sdn/soareg|
|Once you have created your account, I suggest logging in and changing the initial password you received through registration. Its also just a good idea to check you are able to gain access to avoid any issues down the road.|
|Next up head over to your Netweaver Gateway Trial system and open up SPRO
-> SAP Netweaver
-> OData Channel
-> Connection Settings
->SAP Netweaver Gateway to SAP System
-> Manage RFC Destinations
|Click on ABAP Connections and select the “New” icon.|
|Name your RFC Destination and make sure that Connection Type is configured to be 3 – ABAP Connection.
Under Technical Settings enter the following values:
Target Host: iwdfvm3989
System Number: 00
Save As: IP Address
Gateway Host: /H/22.214.171.124/S/3299/W/e$workp1ace/H/iwdfvm3989.dmzwdf.sap.corp
Gateway Service: 3300
|next click the “Logon & Security” Tab and enter your ES Gateway Credentials and save the connection.|
|After saving, select “Manage SAP System Aliases” and enter the details which will create a system alias for the ES Workplace ERP system.|
|SAP System Alias: Any name e.g. ESW
RFC Connection: Should be the name of your RFC connection you specified above
Software Version: Default
|Click the connection test button and you should receive a screen looking like this.|
|Once this is done, we are ready to create our webservice.|
For our consumption example we will be pulling out a simple list of all users. If you would like to see a complete and detailed guide of CRUD (Create, Read, Update and Delete) operations – I would suggest checking out this document: https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/30aee2cc-c474-2e10-ac93-d163ee3b9576
If you have a elastic IP associated with you EC2 instance you should be able to call the REST service from any machine connected to internet. (You could also use your public DNS name, its just not all the short!).
Here are a couple of useful TCodes for working with Gateway:
|/IWFND/ERROR_LOG||Gateway Error Log|
|/IWFND/APPS_LOG||Gateway Application Log Viewer|