Skip to content

prerequisites.md

Latest commit

 

History

History
126 lines (75 loc) · 5.95 KB

prerequisites.md

File metadata and controls

126 lines (75 loc) · 5.95 KB
Raw

Prerequisites

There are hardware, software, and service prerequisites for participating in this CodeJam. The exercises will be developed using SAP Integration Suite and SAP AI Core, which will be made available for the CodeJam.

Accessing the supporting material referenced in exercises

In this CodeJam, you will see that across exercises, there are references to files that will help you get started or that are needed to complete the activities. To access these files, you can download the individual files directly from the repository website, or you can make a copy of the repository on your local machine by following one of the options below:

  1. (Recommended) Clone the git repository in your local machine with the following command:

    git clone https://github.com/SAP-samples/ai-enabled-integrations-codejam.git

    [!NOTE] If you've set up SSH to communicate with GitHub from your local machine, you can clone it using the following command: git clone git@github.com:SAP-samples/ai-enabled-integrations-codejam.git

    Using git is recommended as there might be future updates on the CodeJam content; updating your local copy will just be a command away.

    git pull origin main

  2. Alternatively, download the repository as a zip, and unzip it.

Hardware

None.

Software

Web browser

A web browser supported by SAP Integration Suite1: For the UIs of the service, the following browsers are supported on Microsoft Windows PCs and, where mentioned below, on macOS. Note that, however, certain limitations might apply for specific browsers:

SAP Integration Suite has been tested using the following browsers:

  • Google Chrome (latest version)
  • Microsoft Edge (latest version)
  • Mozilla Firefox (latest version)

Bruno (REST client)

Some exercises require calling REST APIs. As part of the CodeJam we will use Bruno - a Git-friendly open source API client.

Important

Make sure you have installed Bruno version 4.0 or later.

After installing Bruno, you can import the collection that will be used in the exercises. The collection (ai-enabled-integrations-codejam.yml) is available in the https://github.com/SAP-samples/ai-enabled-integrations-codejam/tree/main/assets/bruno folder of the repository. Import it in Bruno.

Import Bruno collection

Important

During the CodeJam, the instructor will provide you with the necessary credentials to configure in the Bruno environment. We will configure it in exercise 5.

Services

SAP Integration Suite

Access to an SAP Integration Suite tenant is required. As part of this CodeJam, your instructor will provide the necessary credentials to access a shared tenant. The tenant will have the following capabilities enabled:

  • Cloud Integration - for building and running integration flows
  • API Management - for managing APIs and configuring the MCP server
If you are completing the content outside of a CodeJam event -> Expand this section ⏬️

You can use an SAP BTP Trial account and set up SAP Integration Suite there to complete part of the CodeJam content on your own. You will not be able to complete exercises 1 to 3 but it is possible to complete the exercises that explore the MCP capabilities.

[!NOTE] The Integration Cell runtime needs to be enabled in the tenant to use the new MCP capabilities. Check out the API-centric integration on SAP Integration Suite - Part 1: Build and deploy blog post in SAP Community to find out how to enable it.


SAP AI Core

SAP AI Core provides the LLM capabilities used in this CodeJam. An instance of SAP AI Core will be pre-configured in the shared environment prepared for the CodeJam. It will have the following already set up:

  • A deployed model (e.g. gpt-4o-mini or equivalent)
  • A prompt template for processing customer support requests

If running on your own, refer to the SAP AI Core documentation for setup instructions.

MCP Inspector

The MCP Inspector is a developer tool that allows exploring and testing MCP servers. It is available in the browser, on the command line, and in the terminal. As part of this CodeJam we will use the MCP Inspector to explore the MCP servers that is available and the one we will create in the next exercise.

👉 Install the MCP inspector in your local environment. Follow the instructions available here: https://modelcontextprotocol.io/docs/2026-07-28/tools/inspector

The easiest way to run MCP Inspector is via npx. npx (Node Package eXecute) is a command-line tool bundled with npm that allows you to execute Node.js packages without installing them globally or permanently in a project:

$ npx @modelcontextprotocol/inspector

# --- 
# It will automatically open in a browser
# ---

Starting MCP inspector...

MCP Inspector Web is up and running at:
   http://localhost:6274?MCP_INSPECTOR_API_TOKEN=22496....

   Sandbox (MCP Apps): http://localhost:65125/sandbox

   Auth token: 22496....

Opening browser...

Checklist

Use the checklist below to verify that you have everything ready before the CodeJam:

  • Access to a web browser (Chrome, Edge, or Firefox - latest version)
  • Installed Bruno - version 4.0
  • Import the collection in Bruno
  • MCP Inspector running locally

Footnotes

  1. Browser support for SAP Integration Suite ↩