[Update: This course is being repeated with updates]
Hi everyone, please be informed that the course “Introduction to SAP HANA Cloud Platform” was updated with new functionalities of the platform. Some of the units from the first course in 2013 no longer work seamlessly. To avoid issues on your side, please look into the repetition of the course “Introduction to SAP HANA Cloud Platform”. There is also a course guide available with the links to all blog posts I wrote for the updated course.
Course Guide Week 3 – Advanced Persistency Features
in the third week of the course Introduction to SAP HANA Cloud Platform we will provide you with some features of the Persistence Service and we’ll also look into the Document Service that stores unstructured data.
Find below additional information that can be useful to you during this course week. While monitoring the forums I’ll also add some sections around common mistakes and how to fix them into the corresponding units.
Table of Contents
- [Update: This course is being repeated with updates]
- Course Guide Week 3 – Advanced Persistency Features
- Table of Contents
- Unit 1 – Local Development
- Unit 2 – Using HANA Modeler
- Unit 3 – Introduction To The Document Service
- Unit 4 – Consuming Document Service with External Tools
- Unit 5 – Document Service Metadata & Queries
Unit 1 – Local Development
Issues With This Unit
When going through this unit you’ll find a difference compared with the video. Read the blog post from Eli providing some help to get around that issue.
Unit 2 – Using HANA Modeler
To be able to establish a database tunnel through the console client you need to have your proxy settings setup correctly. Just follow this instruction: https://help.hana.ondemand.com/help/frameset.htm?7613dee4711e1014839a8273b0e91070.html
Unit 3 – Introduction To The Document Service
com.sap.ecm.api.ServiceException: Could not create repository. Document Service responded with http 400
One possibility for this error message can be that your password for your key is less than 10 characters long. Try to make the password at least 10 characters long and publish the code changes which should fix the issue.