Continuing with the articles on how to prepare our own SAP development environment, today it was the turn of the process of configuring a “Destination” in the Subaccount of a SAP Cloud Platform Trial account.
One time configured the On-Premise server in the SAP Cloud Connector To be able to access it from the Cloud development tools, such as SAP Business Application Studio, it is necessary to configure a “Destination” in the SAP Cloud Platform.
I assume that before starting this process, you have registered an account Trial on SAP Cloud Platform If not, it is the first thing you should do.
Setting a “Destination” in SCP
Once inside the trial subaccount you must access the entry “Connectivity” -> “Destinations”
And add the connection data to the exposed On-Premise server from the SAP Cloud Connector.
The data that must be configured are the following:
Yam: The name with which you want to identify your server
Description: A free text
URL: The external address with which you have published your server in the SAP Cloud Connector
Proxy Type: OnPremise
Authentication: In this case I have selected the NoAuthentication option, because it is the one that is usually configured in the “destinations” that will be used by more than one developer. In this way, each user is forced to log in with their credentials when trying to access the server. Another widely used option is BasicAuthentication, where you must define the username and password that will be used in all connections to this destination.
In addition to the server data, at least the following additional properties must be added:
|sap-client||On-premise ABAP system client|
Additional properties for a “destination”
The end result should look something like this:
Once the “Destination” data has been saved, you can proceed to test the connection through the SAP Business Application Studio.
Note: You can try to test the connection through the “Check Connection” button, but it is common for it to fail showing the following error:
This does not mean that the server is not accessible from the SAP Business Application Studio, so I recommend that you try it by trying to create a Fiori application.
Creating a test Fiori application with data from the ABAP Developer Edition server
To create a test Fiori application, we will look at the “Service Marketplace” entry in the left menu
In the event that the account is new and you have not yet created a subscription for this service, you can create one with the “Create” button. This process takes a few seconds, and once finished you will be able to access the SAP Business Application Studio service.
It is possible that when you access the SAP Application Studio you still do not have a development space – especially the first time – which you can solve with the “Create Dev Space” button. Another common situation is that you find that the service is stopped, you can start it with the “Play” button
Once inside the SAP Business Application Studio you can try to create a Fiori Elements application, using any of the OData services pre-installed on the ABAP server. In my case I will use the OData service that I have created in this post (ZDEMO_C_PURCHASE_ORDER_CDS).
If you have not used this tool before, projects are created in a very similar way to how they are done in SAP Web IDE:
Create Fiori application:
Select SAP Fiori Elements in the application type and List Report Object Page in the floorplan:
After selecting the type of application you want to build, you must choose the data source. Since I have not added the server authentication data in the “Destination” configuration, which I have created for the ABAP Developer Edition server, it will be necessary to enter them in this part:
Once the authentication data has been filled in, a drop-down will appear with the available OData services, where you must select the one to use as the data source. At this point we will know if our ABAP server is accessible or not from the SAP Cloud Platform:
Later it will be necessary to select the main entity:
You must also add the information of the application, such as the name of the application and the title:
If the process of creating the new application has been completed successfully, you can run it by creating a new task.
In my next article I will briefly explain how to use the IDES SAP Business Application Studio to develop Fiori applications, as well as a comparison with the SAP WebIDE Fullstack, currently available only for Cloud NEO environments. The comparison between these two tools will be focused on the development of Fiori applications for SAP On-Premise systems.