onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Reference

blog-bookshop

A CAP service with a Fiori elements UI deployed whole to Cloud Foundry: an approuter, an HTML5 deployer, a launchpad content deployer and xs-security.json beside the db and srv modules in one mta.yaml.

Six modules sit in the one mta.yaml: the CAP service and its HDI deployer, the UI generated by SAP Fiori tools as an html5 module, @sap/approuter as the entry point that routes /v2/catalog to the srv-api destination, a deployer that uploads the built app to the SAP HTML5 Application Repository service for SAP BTP, and a portal content deployer whose CommonDataModel.json is what makes the app appear in a Cloud Foundry launchpad. SAP Fiori tools reads the service over /v2, so the project puts the OData V2 adapter proxy in front of the V4 endpoint. It is a 2020 project and pinned like one: @sap/cds at ^4, the V2 proxy at ^1.4.44, the HANA client as a dependency for the deployed database and the cds kind sql for development. Developing a Fiori elements app with CAP and Fiori Tools is the walkthrough it was written for.

GitHub4 ★

Facts

Last push

Where it sits

Lives in
CAP
Demonstrates
Fiori annotationsCAPFiori annotationscapabilityDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.DeploymentCAPDeploymentcapabilityGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.
Flavors
Node.jsfrom its runtime
Runs
Cloud Foundry
Requires
@cap-js-community/odata-v2-adapter@cap-js-community/odata-v2-adapterartifactThe V2 endpoint SAP Fiori tools reads, put in front of the service's own V4 one; the project depends on it under its former name, @sap/cds-odata-v2-adapter-proxy.@sap/approuter@sap/approuterartifactThe entry point in front of the application, which routes the requests under /v2/catalog to the CAP service and forwards the auth token to it.SAP HTML5 Application Repository service for SAP BTPSAP HTML5 Application Repository service for SAP BTPartifactWhere the built UI module is uploaded to and served from; the MTA binds the app-host plan to the deployer and the app-runtime plan to the approuter.SAP Authorization and Trust Management serviceSAP Authorization and Trust Management serviceartifactThe UI module's xs-app.json sets authenticationType xsuaa for the HTML5 Application Repository route, so an xsuaa instance built from the project's xs-security.json is bound to the approuter.SAP Cloud Portal ServiceSAP Cloud Portal ServiceartifactWhat the launchpad module's content is deployed into, and what the app runs in once deployed; the MTA binds a portal instance on the standard plan to the approuter and to the launchpad deployer.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Use as
A reference
Runtime
Node.js
Runs on
Cloud Foundry

As a sample

Form
A tutorial's companion code

Connections7

Download
blog-bookshop connectionsblog-bookshopPROVIDES→ demonstrates2demonstrates authoredDeploymentdemonstrates authoredFiori annotationsNEEDS→ needs5needs declared The V2 endpoint SAP Fiori tools reads, put in front of the service's own V4 one; the project depends on it under its former name, @sap/cds-odata-v2-adapter-proxy. miyasuta/blog-bookshop — package.json: https://raw.githubusercontent.com/miyasuta/blog-bookshop/master/package.json Developing a Fiori elements app with CAP and Fiori Tools — SAP Community: https://community.sap.com/t5/technology-blog-posts-by-members/developing-a-fiori-elements-app-with-cap-and-fiori-tools/ba-p/13487547@cap-js-community/odata-v2-adapterneeds declared The entry point in front of the application, which routes the requests under /v2/catalog to the CAP service and forwards the auth token to it. Developing a Fiori elements app with CAP and Fiori Tools — SAP Community: https://community.sap.com/t5/technology-blog-posts-by-members/developing-a-fiori-elements-app-with-cap-and-fiori-tools/ba-p/13487547 miyasuta/blog-bookshop — mta.yaml: https://raw.githubusercontent.com/miyasuta/blog-bookshop/master/mta.yaml@sap/approuterneeds declared The UI module's xs-app.json sets authenticationType xsuaa for the HTML5 Application Repository route, so an xsuaa instance built from the project's xs-security.json is bound to the approuter. Developing a Fiori elements app with CAP and Fiori Tools — SAP Community: https://community.sap.com/t5/technology-blog-posts-by-members/developing-a-fiori-elements-app-with-cap-and-fiori-tools/ba-p/13487547 miyasuta/blog-bookshop — mta.yaml: https://raw.githubusercontent.com/miyasuta/blog-bookshop/master/mta.yamlSAP Authorization and Trust Managementserviceneeds declared What the launchpad module's content is deployed into, and what the app runs in once deployed; the MTA binds a portal instance on the standard plan to the approuter and to the launchpad deployer. Developing a Fiori elements app with CAP and Fiori Tools — SAP Community: https://community.sap.com/t5/technology-blog-posts-by-members/developing-a-fiori-elements-app-with-cap-and-fiori-tools/ba-p/13487547 miyasuta/blog-bookshop — mta.yaml: https://raw.githubusercontent.com/miyasuta/blog-bookshop/master/mta.yamlSAP Cloud Portal Serviceneeds declared Where the built UI module is uploaded to and served from; the MTA binds the app-host plan to the deployer and the app-runtime plan to the approuter. Developing a Fiori elements app with CAP and Fiori Tools — SAP Community: https://community.sap.com/t5/technology-blog-posts-by-members/developing-a-fiori-elements-app-with-cap-and-fiori-tools/ba-p/13487547 miyasuta/blog-bookshop — mta.yaml: https://raw.githubusercontent.com/miyasuta/blog-bookshop/master/mta.yamlSAP HTML5 Application Repositoryservice for SAP BTP

README

quoted from miyasuta/blog-bookshop, read
miyasuta/blog-bookshop/README.mdOn GitHub

Getting Started

Welcome to your new project.

It contains these folders and files, following our recommended project layout:

File / FolderPurpose
app/content for UI frontends go here
db/your domain models and data go here
srv/your service models and code go here
package.jsonproject metadata and configuration
readme.mdthis getting started guide
excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub organisations and accountsdiscovered here, miyasutachecked
github.com/miyasuta/blog-bookshoptree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
deploymentCloud Foundry
discovered viaGitHub organisations and accounts · miyasuta
first seen in the atlas
ecosystem and domaincap, ui-and-frontend-bridge
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-blog-bookshop
JSON
/artifacts/miyasuta-blog-bookshop.json
MCP
Connecting an agent