Install a Mock Server in the SAP BTP, Kyma Runtime

If you don’t have access to an SAP back end system (SAP ECC, SAP S/4HANA Cloud or an SAP on-premise system) but still need OData services with some data, you can use this mock server application. It contains entities of SAP OData services with sample data.

You need to:

1. Install the mock server in the SAP BTP, Kyma runtime.

2. Create a destination to the mock server in the same subaccount in SAP BTP.

The installation of the mock server is only needed if you want to test an application deployed in the SAP BTP, Kyma runtime. For local development testing, you can use the local mock server.

2. Clone the mock server GitHub repository:

   Shell Copy

   git clone -b mock https://github.com/SAP-samples/cloud-extension-ecc-business-process.git

3. Navigate to the mock server project:

   Shell Copy

   cd cloud-extension-ecc-business-process

4. Open the project in VS Code:

   Shell Copy

   code .

• Make sure you’re logged in to your Kyma cluster. See Login to your Kyma cluster 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 for more info.

5. Create the productive CAP build for the mock server application:

   Shell Copy

   cds build --production

6. Build the mock server application image:

   Shell Copy

   pack build <your-container-registry>/mockserver-srv:<image version> --path gen/srv --builder paketobuildpacks/builder-jammy-base --publish

   Make sure to replace <your-container-registry> with your docker server URL and keep in mind that <image version> is a string.

   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 Copy

   cat ~/.docker/config.json

   In case you’re using Docker Hub as your container registry, replace the placeholder <your-container-registry> with your Docker Hub user ID.

7. Add Helm chart:

   Shell Copy

   cds add helm --y

   CAP provides a configurable Helm chart for Node.js applications. As a result from running the command, you see a newly created chart folder in your project. The chart folder holds the helm configuration, including the values.yaml file where you add your container image settings later on.

8. Change the chart/values.yaml file:

   1. Remove the lines messaging: and serviceInstanceName: event-mesh from the srv.bindings section:

      YAML Copy

      srv:
        bindings:
          destination:
            serviceInstanceName: 'destination'
          messaging:
            serviceInstanceName: event-mesh
        image:
          repository: mockserver-srv
      ...

   2. Remove the event-mesh section:

      yaml[7-9] Copy

      ...
      destination:
        serviceOfferingName: 'destination'
        servicePlanName: 'lite'
        parameters:
          version: '1.0.0'
      event-mesh:
        serviceOfferingName: enterprise-messaging
        servicePlanName: default

   3. Run the following command to get the domain name of your Kyma cluster:

      Shell Copy

      kubectl get gateway -n kyma-system kyma-gateway \
              -o jsonpath='{.spec.servers[0].hosts[0]}'

      The result looks like this:

      Shell Copy

      *.<xyz123>.kyma.ondemand.com

      <xyz123> is a placeholder for a string of characters that’s unique for your cluster.

   4. In the chart/values.yaml file, add the result without the leading *. in the domain property so that the URL of your CAP service can be generated:

      yaml[2] Copy

      global:
          domain: <your-cluster-domain>
      ...

9. Open the chart/Chart.yaml file and remove the dependency for event-mesh (last 3 lines) from it:

   YAML Copy

    dependencies:
      - name: web-application
        alias: srv
        version: ">0.0.0"
      - name: service-instance
        alias: destination
        version: ">0.0.0"
      - name: service-instance
        alias: event-mesh
        version: ">0.0.0"

10. Update the productive CAP build for your application:

    Shell Copy

    cds build --production

11. Deploy the mock server in the same namespace as your application (for example, incident-management):

    Shell Copy

    helm upgrade --install mock ./gen/chart -n incident-management

    The mock server must be deployed in the same namespace as your application. If you’ve followed the Deploy a Full-Stack CAP Application in SAP BTP, Kyma Runtime Following SAP BTP Developer’s Guide group of tutorial, you’ve created a namespace incident-management already. In case you haven’t created a namespace yet, run the following command to create it now:

    Shell Copy

    kubectl create namespace incident-management
    kubectl label namespace incident-management istio-injection=enabled

12. Copy the application route (URL) of the mock server from the CLI output:

    bash[6] Copy

    Thank you for installing mockserver version 1.0.0.
    
    The release mock is installed in namespace incident-management.
    
    Your services are available at:
        srv - https://mock-srv-incident-management.<xyz123>.kyma.ondemand.com

    <xyz123> is a placeholder for a string of characters that’s unique for your cluster.

3. Go back to the SAP BTP cockpit, navigate to your subaccount overview, and choose Connectivity → Destination. Then, choose Create Destination.

4. Enter the following values:

   • Name = your-destination-name
   • Type = HTTP
   • URL = The application route of the mock server
   • Proxy Type = Internet
   • Authentication = NoAuthentication

5. Select the Use default JDK truststore checkbox.

6. Save your settings.

7. Choose Check Connection. You get a 200 OK message.

   

1. Paste the application route that you’ve copied in the address bar of the browser.

2. Verify that there are a few API endpoints that display data.