--- title: Deploy and Run the Incident Management Application in the SAP BTP, Kyma Runtime with a Mock Server description: Learn how to deploy the Incident Management application in the SAP BTP, Kyma runtime and test it with the mock server that you've installed. parser: v2 auto_validation: true time: 30 tags: [ tutorial>intermediate, software-product-function>sap-cloud-application-programming-model, programming-tool>node-js, software-product>sap-business-technology-platform] primary_tag: software-product-function>sap-cloud-application-programming-model author_name: Grzegorz Karaluch author_profile: https://github.com/grego952 slug: remote-service-deploy-with-mock-kyma canonical_url: https://developers.sap.com/tutorials/remote-service-deploy-with-mock-kyma --- ## You will learn - How to deploy and the Incident Management application in the SAP BTP, Kyma runtime. - How to test the application with the mock server that you've installed. ## Prerequisites - You've tested the extended Incident Management sample application. Follow the steps in the [Test the Extended Incident Management Application with the Business Partner API](remote-service-run-dev-test) tutorial that is part of the [Consume Remote Services from a Mock Server in Your Full-Stack CAP Application Following the SAP BTP Developer's Guide and Deploy in SAP BTP, Kyma Runtime](https://developers.sap.com/group.kyma-cap-consume-mock-services.html) tutorial group. - You've installed a mock server in your namespace in the SAP BTP, Kyma runtime. Follow the steps in the [Install a Mock Server in the SAP BTP, Kyma Runtime](remote-service-set-up-mock-kyma) tutorial that is part of the [Consume Remote Services from a Mock Server in Your Full-Stack CAP Application Following the SAP BTP Developer's Guide and Deploy in SAP BTP, Kyma Runtime](https://developers.sap.com/group.kyma-cap-consume-mock-services.html) tutorial group. - You have an [enterprise global account](https://help.sap.com/docs/btp/sap-business-technology-platform/getting-global-account#loiod61c2819034b48e68145c45c36acba6e) in SAP BTP. To use services for free, you can sign up for an SAP BTPEA (SAP BTP Enterprise Agreement) or a Pay-As-You-Go for SAP BTP global account and use the free tier services only. See [Using Free Service Plans](https://help.sap.com/docs/btp/sap-business-technology-platform/using-free-service-plans?version=Cloud). - You have a platform user. See [User and Member Management](https://help.sap.com/docs/btp/sap-business-technology-platform/user-and-member-management). - You're an administrator of the global account in SAP BTP. - You have a subaccount in SAP BTP to deploy the services and applications. > **OUT OF MAINTENANCE** > > This tutorial is no longer maintained. For an up-to-date version and support with any issues, refer to the [Develop a Side-by-Side CAP-Based Extension Application Following the SAP BTP Developer's Guide](https://discovery-center.cloud.sap/missiondetail/4426/4712/?tab=overview) mission in the [SAP Discovery Center](https://discovery-center.cloud.sap/). ### Build images >- Make sure you're logged in to your Kyma cluster. See [Login to your Kyma cluster](https://developers.sap.com/tutorials/deploy-to-kyma.html#a6e029c1-6e72-408b-bf5f-3b9dffba3499) for detailed steps how to log in. > >- Make sure you're logged in to your container registry. > >- If you're using any device with a non-x86 processor (for example, MacBook M1/M2), you need to instruct Docker to use x86 images by setting the **DOCKER_DEFAULT_PLATFORM** environment variable using the command `export DOCKER_DEFAULT_PLATFORM=linux/amd64`. Check [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) for more info. 1. In VS Code, open the **package.json** file and add the `[production]` profile `credentials` (`destination` and `path`) to the settings for **API_BUSINESS_PARTNER**: ```json "API_BUSINESS_PARTNER": { "kind": "odata", "model": "srv/external/API_BUSINESS_PARTNER", "[production]": { "credentials": { "destination": "", "path": "odata/v2/api-business-partner" } } } ``` > Replace **** with the name of the destination that you created at **Step 5: Create a destination to the mock server** of [Install a Mock Server in the SAP BTP, Kyma Runtime](remote-service-set-up-mock-kyma). 3. Create the productive CAP build for your application: ```bash cds build --production ``` The CAP build writes to the **gen/srv** folder. 4. Build a new version of the CAP Node.js image: ```bash pack build /incident-management-srv: \ --path gen/srv \ --builder paketobuildpacks/builder-jammy-base \ --publish ``` >- Make sure to replace `` with your docker server URL. > >- Keep in mind that `` is a string that’s different from the string defined in [Deploy in SAP BTP, Kyma Runtime](deploy-to-kyma) to reflect the changes in the Incident Management app. > Looking for your docker server URL? > The docker server URL is the same as the path used for docker login, so you can quickly check it by running the following command in your terminal: > ```json > cat ~/.docker/config.json > ``` > In case you're using Docker Hub as your container registry, replace the placeholder `` with your Docker Hub user ID. > The pack CLI builds the image that contains the build result in the **gen/srv** folder and the required npm packages by using the [Cloud Native Buildpack for Node.JS](https://github.com/paketo-buildpacks/nodejs) provided by Paketo. 7. In the VS Code terminal, navigate to the **ui-resources** folder and run the following command: ```bash npm install && npm run package ``` This command builds and copies the archive **nsincidents.zip** inside the **ui-resources/resources** folder. 8. In the VS Code terminal, navigate back to the root folder of your project: ```bash cd .. ``` 9. Build the UI deployer image: ```bash pack build /incident-management-html5-deployer: \ --path ui-resources \ --builder paketobuildpacks/builder-jammy-base \ --publish ``` >- Make sure to replace `` with the link to your container registry and keep in mind that `` is a string. >- Keep in mind that `` is a string that’s different from the string defined in [Deploy in SAP BTP, Kyma Runtime](deploy-to-kyma) to reflect the changes in the Incident Management app. > Looking for your docker server URL? > The docker server URL is the same as the path used for docker login, so you can quickly check it by running the following command in your terminal: > ```json > cat ~/.docker/config.json > ``` > In case you're using Docker Hub as your container registry, replace the placeholder `` with your Docker Hub user ID. Since the database image is unchanged, you don't need to build it again. ### Deploy the Incident Management application 1. Check your container image settings to your **chart/values.yaml** file: ```yaml global: domain: imagePullSecret: name: image: registry: tag: ``` > Make sure to replace `` with the link to your container registry and keep in mind that `` is a string. 2. Overwrite the global image version for the CAP Node.js image and for the UI deployer image: ```yaml srv: image: repository: incident-management-srv tag: ... html5-apps-deployer: ... image: repository: "incident-management-html5-deployer" tag: ``` 1. Update the productive CAP build for your application: ```bash cds build --production ``` 3. Make sure that your SAP HANA Cloud instance is running. Free tier HANA instances are stopped overnight. > Your SAP HANA Cloud service instance is automatically stopped overnight, according to the time zone of the region where the server is located. That means you need to restart your instance every day before you start working with it. > > You can either use the SAP BTP cockpit or the terminal in the SAP Business Application Studio to restart the stopped instance: > > ```bash > cf update-service incident-management -c '{"data":{"serviceStopped":false}}' > ``` 3. Deploy using the Helm command: ```bash helm upgrade --install incident-management --namespace incident-management ./gen/chart \ --set-file xsuaa.jsonParameters=xs-security.json ``` This command installs the Helm chart with the release name **incident-management** in the namespace **incident-management**. ### Test the Incident Management application When creating new entries in the Incident Management application, you see all values from the mock server in the value help of the **Customer** field. > Before you continue with this step, don’t forget to perform the steps from the tutorials [Assign the User Roles](https://developers.sap.com/tutorials/user-role-assignment.html) and [Integrate Your Application Deployed in SAP BTP, Kyma Runtime with SAP Build Work Zone, Standard Edition](https://developers.sap.com/tutorials/integrate-with-work-zone-kymaruntime.html). 1. Open your SAP Build Work Zone, standard edition site as described in [Integrate Your Application Deployed in SAP BTP, Kyma Runtime with SAP Build Work Zone, Standard Edition](https://developers.sap.com/tutorials/integrate-with-work-zone-kymaruntime.html). 6. Choose the **Incident Management** tile. ![Incident Management tile on the launchpage](https://raw.githubusercontent.com/sap-tutorials/btp-dev-guidance/main/tutorials/remote-service-deploy-with-mock-kyma/incident-management-tile.png) 9. Choose **Create** to start creating a new incident. ![Create a new incident](https://raw.githubusercontent.com/sap-tutorials/btp-dev-guidance/main/tutorials/remote-service-deploy-with-mock-kyma/create-new-incident.png) 11. Open the value help for the **Customer** field. ![Value help for Customer field](https://raw.githubusercontent.com/sap-tutorials/btp-dev-guidance/main/tutorials/remote-service-deploy-with-mock-kyma/value-help-customer.png) 12. Verify that customer data is fetched from the mock server. ![Data in value help](https://raw.githubusercontent.com/sap-tutorials/btp-dev-guidance/main/tutorials/remote-service-deploy-with-mock-kyma/value-help-data.png) Congratulations! You have successfully developed, configured, and deployed the Incident Management application using an external service and a mock server.