Build a Service-Centric Application with CAP on Kyma

Copy the repository URL.

1. In your browser, navigate to kyma-runtime-extension-samples.

2. Choose the Code button and choose one of the options to download the code locally, or simply run the following command using your CLI at your desired folder location:

   Shell/Bash

   Copy

   git clone https://github.com/SAP-samples/kyma-runtime-extension-samples
   

1. Open the cap-service directory in your desired editor.

2. Explore the content of the sample.

3. The app directory contains a ready to use Node.js CAP service application modeling Questions and Answers.

   For more information regarding the setup of the application, see CAP Getting Started

4. Within the k8s directory you can find the Kubernetes/Kyma resources you will apply to your Kyma runtime.

5. Within the docker folder you can find the Dockerfile definition that will be used to generate the Docker image. Notice the node version specified on line 2 of the file. This should be changed to match the version you use locally.

1. Within the app directory, run the following command using your command line interface (CLI) to install the application dependencies:

   Shell/Bash

   Copy

   npm install
   

2. Using the CLI, install the cds development kit globally by executing the following command:

   Shell/Bash

   Copy

   npm i -g @sap/cds-dk
   

   This process takes some minutes installing the cds command, which you will use in the next steps.

   On MacOS/Linux, you may need to follow the steps as described here.

   If there’s an older @sap/cds package already installed on the machine, you may have to remove it first; if so, you’ll be instructed to do so.

   In case of problems, see the Troubleshooting guide in the CAP documentation for more details.

3. To verify that the installation was successful, run cds without arguments:

   Shell/Bash

   Copy

   cds
   

   This lists the available cds commands. For example, use cds version to check the version that you’ve installed. To know what is the latest version, see the Release Notes for CAP.

   

1. Within the app directory, run the following command using your CLI to run the CAP service in “watch” mode to confirm all dependencies being installed

   Shell/Bash

   Copy

   cds watch
   

2. The CAP Service should run on port 4004. Confirm by opening a browser to http://localhost:4004

   Note that you don’t have the DB schemas deployed to the database, yet. We’ll have to do this now.

3. Stop the CAP service in your command line

   Pressing CTRL-c will stop the running application.

4. Deploy the DB schemas to you local sqlite database file by running the following command in your CLI

   Shell/Bash

   Copy

   cds deploy --to sqlite
   

   The CDS deploy action should give you output similar to:

   Shell/Bash

   Copy

     > filling sap.demo.faq.Authors from db/data/sap.demo.faq-Authors.csv
     > filling sap.demo.faq.Categories from db/data/sap.demo.faq-Categories.csv
     > filling sap.demo.faq.Faqs from db/data/sap.demo.faq-Faqs.csv
     > filling sap.demo.faq.Faqs_texts from db/data/sap.demo.faq.Faqs_texts.csv
     /> successfully deployed to ./sqlite.db
   

5. Start your CAP service again by executing

   Shell/Bash

   Copy

   cds watch
   

The browser page should resemble

Run the following commands from the cap-service directory within your CLI.

Make sure to replace the value of <your-docker-id> with your Docker account ID.

1. To build the Docker image, run this command:

   Shell/Bash

   Copy

   docker build -t <your-docker-id>/cap-service -f docker/Dockerfile .
   

2. To push the Docker image to your Docker repository, run this command:

   Shell/Bash

   Copy

   docker push <your-docker-id>/cap-service
   

Run the following commands from the cap-service directory within your CLI.

Make sure to replace the value of <your-docker-id> with your Docker account ID.

1. Start the image locally by running the following command:

   Shell/Bash

   Copy

   docker run -p 4004:4004 --name cap-service <dockerid>/cap-service:latest
   

   The -p command instructs Docker to map the host port 4004, shown on the left of the colon, to the port exposed by the image 4004, shown on the right. Using the –name parameter allows for an easy reference to the image to stop, start or remove it which is used in a later step.

   Running the command should result in a similar output:

   Shell/Bash

   Copy

   > faq@1.0.0 start /usr/src/app
   > npx cds run
   
   
   [cds] - model loaded from 6 file(s):
   
     db/schema.cds
     srv/admin-service.cds
     srv/admin.cds
     srv/cat-service.cds
     srv/common.cds
     node_modules/@sap/cds/common.cds
   
   [cds] - connect to db > sqlite { database: 'sqlite.db' }
   [cds] - serving AdminService { at: '/admin', impl: 'srv/admin-service.js' }
   [cds] - serving CatalogService { at: '/catalog', impl: 'srv/cat-service.js' }
   
   [cds] - launched in: 1325.610ms
   [cds] - server listening on { url: 'http://localhost:4004' }
   

2. The CAP Service should now be available on port 4004. Confirm by opening a browser to http://localhost:4004

3. Stop the Docker container by running:

   Shell/Bash

   Copy

   docker stop cap-service
   

4. Here are some additional commands that you can use:

   To restart the Docker container, run:

   Shell/Bash

   Copy

   docker start cap-service
   

   To remove the Docker container, run:

   Shell/Bash

   Copy

   docker rm cap-service
   

You can find the resource definitions in the k8s folder. If you performed any changes in the configuration, these files may also need to be updated. The folder contains the following files that are relevant to this tutorial:

• apirule.yaml: defines the API endpoint which exposes the application to the Internet. This endpoint does not define any authentication access strategy and should be disabled when not in use.
• deployment.yaml: defines the deployment definition for the CAP service, as well as a service which is used for internal communication within the Kyma runtime.

  You will need the Kubeconfig setup to perform these steps as detailed in Install the Kubernetes Command Line Tool. Please also note that the kubeconfig will need to be downloaded and configured once it expires after eight hours.

1. Start by creating the dev Namespace and enabling Istio:

   Shell/Bash

   Copy

   kubectl create namespace dev
   kubectl label namespaces dev istio-injection=enabled
   

   Namespaces separate objects inside a Kubernetes cluster. Choosing a different namespace will require adjustments to the provided samples.

   Adding the label istio-injection=enabled to the namespace enables Istio. Istio is the service mesh implementation used by the Kyma runtime.

2. Within the deployment.yaml, adjust the value of spec.template.spec.containers.image to use your Docker image. Apply the Deployment:

   Shell/Bash

   Copy

   kubectl -n dev apply -f ./k8s/deployment.yaml
   

3. Check the status of the Pod by running:

   Shell/Bash

   Copy

   kubectl -n dev get po
   

   This command results in a table similar to the one below, showing a Pod with the name cap-service- ending with a random hash. When the pod is ready it will report the STATUS of Running.

   Shell/Bash

   Copy

   NAME                           READY   STATUS    RESTARTS   AGE
   cap-service-c694bc847-tkthc   2/2     Running   0          23m
   

4. Apply the APIRule to expose the application to the internet:

   Shell/Bash

   Copy

   kubectl -n dev apply -f ./k8s/apirule.yaml
   

5. The APIRule will be create endpoint with the following format:

https://cap-service.<cluster>.kyma.ondemand.com

This can also be determined, by referencing the virtual service the APIRule creates by running:

kubectl get virtualservice -n dev

Reference the values found under HOSTS

NAME               GATEWAYS                                      HOSTS                                                       AGE
cap-service-****   [kyma-gateway.kyma-system.svc.cluster.local]  [cap-service.******.kyma.ondemand.com]  1d

Copy the value of the HOSTS field, making sure to append https:// to it, to test the application in your browser.

Congratulations! You have successfully configured the Cap Service.