--- title: "Debugging Groovy Scripts" slug: "debugging-groovy-scripts" description: "Learn how to debug Groovy scripts in Zilliant CPQ." tags: ["debugging", "Groovy script"] updated: 2024-05-21T18:14:32Z published: 2024-05-21T18:14:32Z canonical: "docs.zilliant.com/debugging-groovy-scripts" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.zilliant.com/llms.txt > Use this file to discover all available pages before exploring further. # Debugging Groovy Scripts Use Eclipse and Eclipse plugins to debug Groovy scripts that are deployed on a cloud system. ## Prerequisites Download and install a Java Development Kit (JDK). ## Step 1: Download tools and plugins 1. Browse to [SAP Development Tools](https://tools.hana.ondemand.com) ![](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/external-link-svgrepo-com.svg?sv=2026-02-06&spr=https&st=2026-11-11T12%3A20%3A53Z&se=2026-11-11T13%3A20%3A53Z&sr=c&sp=r&sig=6ozbo8ZWBHF1bqaLu8GmIX%2BmzIOoaNYjQSNijAADV7k%3D). Use the information referenced here to determine which version of Eclipse is compatible with SAP Cloud Platform Tools. 2. [Download and install](https://www.eclipse.org/downloads/) ![](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/external-link-svgrepo-com.svg?sv=2026-02-06&spr=https&st=2026-11-11T12%3A20%3A53Z&se=2026-11-11T13%3A20%3A53Z&sr=c&sp=r&sig=6ozbo8ZWBHF1bqaLu8GmIX%2BmzIOoaNYjQSNijAADV7k%3D) the correct Eclipse version. Note Select the package for Java developers. 3. Download and install the Eclipse plugins listed in the following table. | Tools | Download location | | --- | --- | | Eclipse Groovy Development Tools | [https://github.com/groovy/groovy-eclipse/wiki](https://github.com/groovy/groovy-eclipse/wiki) ![](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/external-link-svgrepo-com.svg?sv=2026-02-06&spr=https&st=2026-11-11T12%3A20%3A53Z&se=2026-11-11T13%3A20%3A53Z&sr=c&sp=r&sig=6ozbo8ZWBHF1bqaLu8GmIX%2BmzIOoaNYjQSNijAADV7k%3D) | | SAP Cloud Platform Tools | [https://tools.hana.ondemand.com#cloud](https://tools.hana.ondemand.com#cloud) ![](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/external-link-svgrepo-com.svg?sv=2026-02-06&spr=https&st=2026-11-11T12%3A20%3A53Z&se=2026-11-11T13%3A20%3A53Z&sr=c&sp=r&sig=6ozbo8ZWBHF1bqaLu8GmIX%2BmzIOoaNYjQSNijAADV7k%3D) | | SAP Cloud Platform Integration Tools | [https://tools.hana.ondemand.com#cloudintegration](https://tools.hana.ondemand.com#cloudintegration) ![](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/external-link-svgrepo-com.svg?sv=2026-02-06&spr=https&st=2026-11-11T12%3A20%3A53Z&se=2026-11-11T13%3A20%3A53Z&sr=c&sp=r&sig=6ozbo8ZWBHF1bqaLu8GmIX%2BmzIOoaNYjQSNijAADV7k%3D) | ## Step 2: Add the SAP server 1. Enable the Servers view. Go to **Window** > **Show View** > **Other** and select **Servers**. 2. Select the link in the Servers view to create a server. 3. Select **SAP** > **SAP Cloud Platform**. 4. In the **Define a New Server** panel, specify the region host for your cloud platform installation, then enter a name for the new server. 5. Select **Next**. 6. Enter server information and your SAP account credentials, then select **Finish**. The SAP Cloud Platform server appears in the Servers view. ## Step 3: Debug the SAP server 1. In the Servers view, right-click the server and select **Restart in Debug**. 2. Select **Groovy** > **Groovy Project**. 3. Name the project, then select **Finish**. 4. Add the Groovy file you want to debug into the project. Note The file name must be identical to the name of the file uploaded to the system. 5. Open the Groovy file and place a debug point on it. Then trigger script execution from the cloud system. Processing should be halted at the debug point in Eclipse so you can then debug the script. 1. You may see a prompt advising you to switch to Debug perspective. Select **Remember my decision**, then select **Yes**. 2. The first time, the debug point will arrive at a byte code file instead of the Groovy file in your project, as shown in the following sample: ![Groovy debug point](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/Groovy_debug_point_1.png?sv=2026-02-06&spr=https&st=2026-11-11T12%3A20%3A53Z&se=2026-11-11T13%3A20%3A53Z&sr=c&sp=r&sig=6ozbo8ZWBHF1bqaLu8GmIX%2BmzIOoaNYjQSNijAADV7k%3D) 3. To resolve this, right-click in the Debug view, then select **Edit Source Lookup**. 4. Select **Add** > **Java Project** and select the Groovy project you created earlier. The debug point should move to your Groovy file: ![Groovy debug point change](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/Groovy_debug_point_2.png?sv=2026-02-06&spr=https&st=2026-11-11T12%3A20%3A53Z&se=2026-11-11T13%3A20%3A53Z&sr=c&sp=r&sig=6ozbo8ZWBHF1bqaLu8GmIX%2BmzIOoaNYjQSNijAADV7k%3D)