How alanldias/capgroup works
Project type and purpose
• This is an SAP Cloud Application Programming Model (CAP) multi-target application.
• It provides a simple “Bookshop” service (cat-service) with a domain model defined in CDS, sample data in CSV, a Fiori/UI5 portal front-end, a Node.js application router, and a HANA database.
• The mta.yaml ties all modules together for deployment on SAP BTP.
File structure
• Top-level files
• mta.yaml – MTA descriptor orchestrating modules and their interdependencies
• xs-security.json – JWT scopes and authentication config
• package.json / package-lock.json – root metadata and scripts
• eslint.config.mjs – lint rules
• app/portal/portal-site
• A SAP UI5 (Fiori) application, static content, i18n catalogs, CommonDataModel.json
• app/router
• Node.js “approuter” module, with xs-app.json (route definitions) and package.json
• db/
• schema.cds – CDS domain model for “Bookshop” entities
• data/*.csv – sample data to seed the database
• .hdiconfig – HANA deployment settings
• undeploy.json – cleanup instructions
• srv/
• cat-service.cds – CAP service definition exposing OData endpoints
README for additional insights
• Confirms the standard CAP layout: app/ for UI, db/ for domain & data, srv/ for services.
• Invokes cds watch to start all local modules.
Detail without over-complicating
• Sample data CSV ingestion at deployment time.
• “cds watch” in a side note as the local development runner binding all modules.