You have an SCP account, which is able to deploy simple Java web applications.We assume you have completed the tutorial “HelloWorld on SCP CloudFoundry”, such that the following requirements are already met:
However, the general strategy of this guide can be used for either platform deployment. Its API will be consumed by a newly created application running on SCP Cloud Foundry. It provides up-to-date runtime metrics to connected applications and processes. In the upcoming steps, we will use the Monitoring v2 service on SCP Neo. We will setup a destination to the API service to test and proof the new application. By using the latest Maven project archetype of SAP Cloud SDK, we will have a well prepared start to implement and deploy a new application to the SCP, capable of consuming an OpenAPI service. In this step-by-step guide we will choose a RESTful API from the SAP API Business Hub, take the attached OpenAPI interface file and generate Java code from it. If the REST based endpoint is well-defined, its specification can be declared as OpenAPI. But some application may target a web service, which serves resources from an REST based endpoint, instead of OData or SOAP. We have already seen the SAP Cloud SDK providing capabilities for conveniently consuming OData and SOAP based API services. For a complete overview visit the SAP Cloud SDK Overview.
Feel free to check out our updated Tutorials on the SAP Cloud SDK. We plan to continuously migrate these blog posts into our List of Tutorials. Disclaimer: This blog post is only applicable for the SAP Cloud SDK version of at most 2.19.2.