In this blog I want to announce the second tutorial for my node.js OData server (n-odata-server). In this tutorial you learn how you can deploy a n-odata-server application to a Cloud Foundry platform. As SAP in the meantime has such a platform in it’s portfolio I of course used this one for this tutorial.
When SAP didn’t offer this opportunity I also already used another CF platform for deploying my application and it also worked well. That’s one of the benefits of Cloud Foundry: develop your app and deploy it to any CF platform you like without having to learn platform specifics.
YaaS is the SAP platform that is used to offer a Cloud Foundry platform for HCP. IMHO the support for Cloud Foundry was an important decision so that HCP can and will survive in the fast growing PaaS market.
Coming back to my tutorial
In this tutorial I simply used the application of my first tutorial that has a very simple data structure and exposes it via OData. I enhanced the package.json file that is an application descriptor for node.js applications, added a manifest.yml, that’s the app descriptor for a CF application, to my project and deployed it to the HCP CF services via the CF CLI.
If you follow the tutorial at the end you will have a little OData service for which you can create a HCP destination and write a UI5 application with SAP Web IDE to manage the data in that service.
The application of this tutorial saves the data that you create in a text file on your CF server. This is for several reasons not a good solution. Hence I will bind the application in one of the next tutorials to a persistence service on HCP CF services platform.
Maintenance UI for CF applications
Cause I didn’t mention it in the tutorial itself (I only explained the CLI way there) I would like to use this blog to call attention to the possibility to manage and monitor your CF apps on HCP CF services via a nice UI5 app, the HCP CF services cockpit.
Stay tuned for updates about n-odata-server.