Upgrading ABAP Agent version

When a new ABAP Agent 2.0 release is available, it is distributed at the same download location as the original installation. See Install WATCHER, SLABAPCLI and Server.

Before upgrading, review the ABAP Agent release notes for version-specific changes and authorization requirements.

Compatibility with earlier ABAP Agent versions

ABAP Agent 2.0 is not compatible with ABAP Agent 1.3.0.70 and earlier.

You cannot continue using your existing 1.3 installation, SAP add-on, local agent data, or SeaLights application history with 2.0.

Any move from 1.3.x to 2.0 (including versions above 1.3.0.70) still requires the new SAP add-on and a full rebuild path — not an in-place continuation of 1.3 data.

• The new SAP add-on for 2.0 is not backwards compatible with earlier agent versions.
• Your agent configuration must be valid for 2.0 (configuration schema version 4). Reconfigure as needed.
• Discard prior local agent build and graph data. Do not reuse local databases or coverage artifacts from 1.3.
• You must run a full initial build map for each pipeline.
• Create a new SeaLights application. Do not reuse your 1.3 application or its history.

Required actions when moving to ABAP Agent 2.0:

1. Install the new ABAP Agent 2.0 SAP add-on on your SAP landscape (it replaces the previous add-on and is not backwards compatible).
2. Install ABAP Agent 2.0 and ensure your configuration is valid for schema version 4 (migrate and/or reconfigure as needed).
3. Discard prior local agent build and graph data — do not reuse 1.3 local databases or coverage artifacts.
4. Create a new SeaLights application for each pipeline. Do not reuse the 1.3 application or its history.
5. Run a full initial build map for each pipeline before relying on coverage or test-impact results.

The ABAP Agent relies on scheduled tasks using the Windows Task Scheduler. Those tasks must be stopped before upgrading. See below.

BUILDMAP tasks only run once. If they succeeded, they can be removed from the Windows Task Scheduler.

Upgrading from a prior ABAP Agent 2.0 build

Use this section when you are already on ABAP Agent 2.0 and installing a newer 2.0 build.

1. Stop scheduled tasks

1. Open Windows Task Scheduler.
2. Under the SeaLights directory, select all FOOTPRINTS and BUILDMODS tasks.
3. Make sure none of those tasks are actively processing:

   • FOOTPRINTS: No tests are currently running.
   • BUILDMODS: No transports are currently being imported.
4. Click End, then click Disable on each selected task.

2. Stop the ABAP Agent Server

If SLABAPServer.exe is running in a console window, press Ctrl+C to stop it gracefully before running the installer.

Completing active tests and transports, ending and disabling the scheduled tasks above, and stopping a console server with Ctrl+C are required preparation before Setup. The installer can still detect leftover lock holders and ask to stop them, but that prompt is final protection — not a substitute for finishing in-flight work or preventing scheduled tasks from respawning.

3. Run the installer

Download the latest agent ZIP file and extract the installer. Run SeaLights_ABAP_Agent_Setup.exe as an administrator over the existing installation.

Setup follows a stop-then-replace sequence:

1. It checks for the SLABAPServer Windows service and for SLABAPServer.exe, SLABAPAdapterHost.exe, or watcher.exe running from the selected installation's bin directory (not every similarly named process on the machine).
2. In an interactive install, Setup asks whether to stop those processes and continue.
3. Choosing Yes stops the lock holders and continues. Choosing No, or a failure to stop them, aborts installation before any files are replaced.
4. In a silent install, Setup does not show the prompt: it automatically attempts the same stop and continues only if stopping succeeds; otherwise installation aborts.

After lock holders are stopped, Setup replaces all packaged agent files under the installation bin directory, including files whose installed version matches the packaged version. Replacement covers the packaged agent payload only — it does not remove arbitrary orphan or customer-added files under bin, and it does not wipe %ProgramData%\Tricentis\SeaLights\ABAP Agent. Configuration (config.toml), logs, and public and private userdata remain in place; Setup migrates the existing configuration after file replacement.

The installer then automatically runs setup migrate --yes (to bring config.toml to schema version 4) and setup upgrade (to re-enable scheduled tasks from the previous install) without requiring manual steps.

setup migrate is for ABAP Agent 2.0+ configuration schema only. It updates an existing 2.0 config.toml to schema version 4. It is not a supported product migration from ABAP Agent 1.3 to 2.0. For 1.3 and earlier, see Compatibility with earlier ABAP Agent versions.

4. Restart the ABAP Agent Server

After the installer completes, start SLABAPServer.exe again. See Start the ABAP Agent Server.

5. Re-enable scheduled tasks

1. In Windows Task Scheduler, select the same FOOTPRINTS and BUILDMODS tasks.
2. Click Enable, then click Run.

6. Verify the upgrade

Run the following to confirm all components are healthy:

Command Prompt

slabapcli.exe setup status

PowerShell

.\slabapcli.exe setup status

See Validate Your Setup for interpreting the output.

---

Migrating the configuration schema (2.0+ only)

If the installer does not run setup migrate (for example, in a manual or scripted 2.0 deployment), bring an existing 2.0 config.toml to schema version 4 yourself:

Command Prompt

slabapcli.exe setup migrate

PowerShell

.\slabapcli.exe setup migrate

Add --yes (-y) to suppress interactive confirmation prompts:

Command Prompt

slabapcli.exe setup migrate --yes

PowerShell

.\slabapcli.exe setup migrate --yes

For full details on what setup migrate does and how it transforms the configuration file, see Migrate a legacy configuration and Configuration settings.

---

Refreshing scheduled tasks

If scheduled tasks were not re-enabled automatically (for example, after a manual installation), run setup upgrade to re-enable them:

Command Prompt

slabapcli.exe setup upgrade

PowerShell

.\slabapcli.exe setup upgrade

setup upgrade enables agent tasks that were registered by a previous install. It takes no flags.

When you stop or replace a scheduled task through agent task management (for example with slabapcli), the agent automatically terminates any running watcher process for that task. That cleanup is separate from the installer process-stop prompt described above. You no longer need to manually kill orphaned watcher processes after stopping or replacing a task.