Community
Integration Blog Posts
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Hello fellow SAP Integrators and Community members!

This article offers a solution for writing and debugging Groovy scripts during iFlow execution. Currently, debugging Groovy scripts directly in SAP Integration Suite is quite difficult, and real-time debugging is simply not possible.

Below, I will share my approach to help you save time when writing and debugging Groovy scripts, without relying on third-party online services.

Spoiler alert: this is the result you'll get by the end of the article.

Polupanov_0-1794330761190.png

Scope and limitations of this article

This guide focuses specifically on how to build this live debugging tool. To keep things simple and avoid information overload, I will not go into detail about network configurations, access rights, or the step-by-step installation of the components. You can easily find installation guides for these tools online, so this article stays focused purely on the core method and idea.

Here is what we need to get started (versions are current as of this publication):

  • Eclipse IDE version: 2026-06 (4.40.0)
  • OpenJDK version 17.0.21 2026-10-20
  • Groovy Development Tools 6.3.0
  • Internet Information Services (IIS) for Windows
  • HttpPlatformHandler v1.2 for IIS
  • SAP library cloud.integration.script.apis-2.7.1 Download (sha1) 

1. Eclipse Configuration

1.1. Install Groovy Development Tools (If not already installed)

  1. Open Eclipse and go to Help > Eclipse Marketplace in the top menu.
  2. Type "Groovy" in the search bar and press Enter.
  3. Find Groovy Development Tools in the list and click Install.
  4. Follow the prompts and restart Eclipse when it asks you to.

Polupanov_0-1794324047234.png

1.2. Prepare Your Groovy Project

  1. Go to File > New > Project... and choose Groovy Project.
  2. Give your project a name (for example, SAP_Integration_Suite_Groovy) and click Finish.
  3. Inside your project, create a new package (folder) named Integration_Suite_Scripts.
  4. Place the server.groovy and scrTemplate.groovy files inside this folder. (The files are attached to this article; you just need to set the correct name and extension.)
    • scrTemplate.groovy -  In our local debugging architecture, is the exact equivalent of the Groovy script you would normally create inside an SAP Integration Suite iFlow.
    • Polupanov_1-1794324936626.png

       

  5. Add the necessary SAP library cloud.integration.script.apis-2.7.1 to the project's build path.
    • Polupanov_0-1794325570067.png

       

1.3. Set Up the Remote Debug Configuration

  1. Click on Run in the top menu and select Debug Configurations....
  2. Look at the list on the left side and double-click on Remote Java Application to create a new profile.
  3. Give it a simple name at the top, like groovy.
  4. In the Connect tab, make sure the Project field is empty or points to your project.
  5. Set the Host to localhost.
  6. Set the Port to 5005 (this tells Eclipse to listen to the exact port your server opened for debugging).
  7. Link the Source Code (To prevent the "Source not found" error):
    • Still inside the Debug Configurations window, switch to the Source tab at the top.
    • Click the Add... button on the right side.
    • Choose Java Project from the menu and click OK.
    • Put a checkmark next to your project (SAP_Integration_Suite_Groovy) and click OK.
    • Click Apply at the bottom to save your settings.

Polupanov_0-1794326534917.png

2. IIS Configuration

2.1. Install IIS and HttpPlatformHandler

  1. Enable Internet Information Services (IIS) in your Windows Features if it is not already active.
  2. Download and install the HttpPlatformHandler v1.2 extension from the official Microsoft download center. 
  3. Verify that both Java and Groovy are installed on your machine and that their bin directories are added to your Windows system PATH environment variable.

2.2. Configure the Workspace Directory

  1. Navigate directly to your Eclipse workspace folder (e.g., the Integration_Suite_Scripts folder).
  2. Inside this directory, create a new empty subfolder and name it logs. The HttpPlatformHandler will use this folder to write server startup logs and errors.
  3. Place the web.config file inside the main workspace folder.
  4. Open the file in any text editor and paste the required XML code. This configuration instructs IIS to pass HTTP traffic to your Groovy script and injects the JAVA_OPTS environment variable required for Eclipse debugging.

Polupanov_1-1794327245960.png

web.config

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <handlers>
            <add name="httpPlatformHandler" path="*" verb="*" modules="httpPlatformHandler" resourceType="Unspecified" />
        </handlers>
        
        <!--The -agentlib:jdwp... parameter opens port 5005 for the Eclipse connection.
 suspend=n means that the script will start immediately, without waiting for the debugger to connect.
        -->
        <httpPlatform processPath="C:\Program Files\Eclipse Adoptium\jdk-17.0.21.9-hotspot\bin\java.exe"
                      arguments="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=127.0.0.1:5005 -cp C:\groovy-6.0.0\lib\* groovy.ui.GroovyMain server.groovy"
                      stdoutLogEnabled="true"
                      stdoutLogFile=".\logs\groovy-log"
                      startupTimeLimit="20">
            <environmentVariables>
                <environmentVariable name="HTTP_PLATFORM_PORT" value="%HTTP_PLATFORM_PORT%" />
            </environmentVariables>
        </httpPlatform>
    </system.webServer>
</configuration>

processPath: Specifies the exact absolute path to the Java executable (C:\Program Files\Eclipse Adoptium\jdk-17.0.21.9-hotspot\bin\java.exe).

arguments: Passes the execution commands directly to Java. It includes the debugger configuration (-agentlib:jdwp... on port 127.0.0.1:5005), the Groovy classpath (-cp C:\groovy-6.0.0\lib\*), the main Groovy runner (groovy.ui.GroovyMain), and your script (server.groovy).

stdoutLogFile: Defines the target directory and file prefix for saving logs (.\logs\groovy-log).

3. Create an Application Pool and Configure the Application in IIS

3.1. Create a dedicated Application Pool

  1. Open the Internet Information Services (IIS) Manager application.
  2. In the left Connections pane, right-click on Application Pools and select Add Application Pool....
  3. Name it GroovyPool.
  4. Set the .NET CLR version to No Managed Code (since Groovy runs on the Java Virtual Machine, not .NET).
  5. Set the Managed pipeline mode to Integrated, and click OK.

Polupanov_0-1794327981462.png

3.2. Configure the web application

  1. In the left pane, expand your server node, expand Sites, and right-click on Default Web Site.
  2. Select Add Application... from the context menu.
  3. Type an Alias (for example, groovy-api).
  4. Click the Select... button next to the Application pool and choose the GroovyPool you just created.
  5. Set the Physical path to your workspace directory and click OK.

Polupanov_2-1794328205572.png

 

4. Grant Folder Permissions

  1. Open Windows File Explorer, right-click your Integration_Suite_Scripts folder, and select Properties.
  2. Switch to the Security tab, click Edit..., and then click Add....
  3. Type IIS_IUSRS in the object names box, click Check Names, and click OK.
  4. Ensure the IIS_IUSRS group is granted Read & Execute, List folder contents, and Read permissions.
  5. Click OK to apply and save the changes.

Polupanov_0-1794328446285.png

5. Start Debugging

5.1. Verify the Server in Your Browser

  1. Start your IIS application pool or the server process.
  2. Open your web browser and navigate to http://localhost/groovy-api (or your configured local address).
  3. The browser should display the exact confirmation message we configured: "Groovy web service is successfully running under IIS. Debugging is connected!"

Polupanov_2-1794328585304.png

5.2. Set a Breakpoint in Your Code

  • Open the scrTemplate.groovy file (or server.groovy if you are testing the server logic itself) in Eclipse and set a breakpoint on the desired line.

5.3. Attach the Remote Debugger

  1. In Eclipse, click Run > Debug Configurations....
  2. Expand the Remote Java Application section on the left, select your debugging profile (configured for localhost and port 5005), and click Debug.
  3. The Eclipse Debug perspective will activate, indicating it is successfully listening to the JVM.

Polupanov_0-1794328801525.png

6. Ready for Debugging!

  1. In SAP Integration Suite, create a simple iFlow and add a call to our API.
  2. To connect your cloud environment and your computer, use SAP Cloud Connector.
  3. You can trigger the process using a Timer event, or set up an endpoint using a tool like Bruno.
  4. Set a breakpoint in your module and run the iFlow.

As demonstrated, this local setup makes live, step-by-step Groovy debugging fully accessible directly during the execution of your iFlow.

Polupanov_0-1794331510162.png

Conclusion

In summary, this guide provides a step-by-step approach to building a local environment for real-time debugging of SAP Integration Suite Groovy scripts. By configuring Eclipse for your code and Internet Information Services (IIS) to handle the connection, you can test your scripts exactly as they run. We covered everything from installing the required tools and setting up your workspace, to configuring folder permissions and connecting to the cloud using the SAP Cloud Connector. Ultimately, this method allows you to catch errors and fix your code directly during iFlow execution, helping you save time without relying on any third-party online services.

I hope this local debugging setup saves you countless hours. Wishing you clean Groovy code, zero bugs, and clear skies in your SAP Cloud integrations!

@EvgeniiPolupanov

scrTemplate.groovy.txt
server.groovy.txt
Comment
Labels in this area