Setup your SAP Web IDE on HANA Cloud Platform Part 2
In this and the next Blogs I will show you how you can set up your SAP Web IDE on Hana Cloud. I cut this in 5 parts:
|part 2 this part 😉||
|part 6 (old part 5)||
SAP Web IDE is ready, but we cannot connect to remote systems yet. In this part we will do the job. You need to configure the HANA Cloud Connector in order to connect the destinations, which you are going to define then, with the required systems.
Installing HANA Cloud Connector
Download the HANA Cloud connector from the link. If its possible use the plain version, not the Developer version.
For windows you have also an installer package (the one with the .msi extension). If you use it, you can skip the next step.
Once downloaded, unzip the connector and move the resulting folder in a suitable place on your local machine.
Go ins ide the extracted connector.
Run the file go.sh (or go.bat in case of Windows OS)
When the Connector is started you should see the “osgi>” prompt
Should you need to close the connector, you can simply type “close” in this console and the connector will be closed
Configuring the HANA Cloud Connector
Open browser and go to the link https://localhost:8443.
If you get the following error, click on Advanced. This error comes because you don’t have yet any valid certificate for this localhost server
Click on Proceed to localhost (unsafe)
Enter these credentials and click on Login
- User Name: Administrator
- Password: manage
Choose Master as the installation type since this is your first time you are installing the product and this is the only SAP HANA Cloud Connector in your system. Click on Apply
The first time you log in, you need to change the password. Do it and click on Save
Provide the following initial configuration and click on Apply. Proxy information is only needed if you are in a network that requires a proxy, like for example the SAP network.
|Account Name||<your account name on the landscape host>. It can be found on the top left corner of your SAP HANA Cloud Cockpit|
|User Name||<your user name on the landscape host> of SCN|
|Password||<your password> of SCN *|
|HTTPS Proxy Host||only if required (for SAP users is “proxy”)|
|HTTPS Proxy Port||only if required (for SAP users is “8080”)|
* If you don’t know your SCN password, here you can reset it!
The landscape is configured. Now we need to add some mappings with the real systems. Click on Access Control
Click on Add… in the Mapping Virtual to Internal System section.
Enter the following information and click on Save.
What you are doing in this step is to assign to a real backend system a virtual name. In this way you can decouple the SAP Web IDE from the backend infrastructure. You can also create a virtual port, which of course can be different from the real one. In this case you will be using the same port. Let’s use as virtual server name “gm6.virtual” on the port 44333;
NOTE: Please be aware that the server used in this blog (GM6) is just an example, thus you may not have granted access to it.
|Internal Host||<your server>|
|Internal Port||<your port>|
|Back-end Type||ABAP System|
Now you need to add all the resources related to the usages you want to have in your SAP Web IDE. These resources are the paths to be concatenated with the server URL in order to have the complete paths to the resources. For example, if you want to configure your SAP Web IDE to consume the OData service at the address https://<server>:<port>/sap/opu/odata and extend some SAP Fiori applications at the address https://<server>:<port>/sap/bc/adt, you just need to add the common part (the server name and the port) in the system mapping and all the different paths in the table of the accessible resources.
This is the list of the available resources that you can add as of today:
|odata_abap||/sap/opu/odata||for the OData functionality of Gateway|
|odata_gen||for generic OData functionality (service URL must be provided manually
in the New Project wizard)
|ui5_execute_abap||/sap/bc/ui5_ui5||for executing SAPUI5 applications from the SAPUI5 ABAP Repository|
|dev_abap||/sap/bc/adt||for extensibility scenarios and developing or deploying to SAPUI5 ABAP
|bsp_execute_abap||/sap/bc/bsp||For fact sheets|
|odata_xs||/sap/hba||For HANA XS Odata services|
for exposing external plugin repositories
In this case let’s add just the following resources: “/sap/opu/odata”, “/sap/bc/adt” and “/sap/bc/ui5_ui5”, because for that server we want to use OData services, extend applications and also execute some SAPUI5 applications.
So click on Add… in the Resources section
Add the first resource and click on Save
|Access Policy||Path and all sub-paths|
Do the same for /sap/bc/adt and for /sap/bc/ui5_ui5 and click on Save
At the end you should have this configuration
Your SAP HANA Cloud connector has been properly configured. The status is green and it’s connected
You have successfully installed and configured your SAP HANA Cloud Connector.
In the next part we will connect to a remote system.