Install WATCHER, SLABAPCLI and Server

WATCHER is a program that watches for ABAP changes and reports them to SeaLights. SLABAPCLI is a command-line interface program that lets you configure the ABAP Agent and connect it to SeaLights. SLABAPServer.exe is a new component in ABAP Agent 2.0 — a local HTTP server (listening on http://127.0.0.1:17500) that hosts the test-repository adapter layer and serves requests from the CLI tools. You can install these on a Windows server or a standalone machine.

After installation, start the agent server separately by running SLABAPServer.exe. See Start the Agent Server.

Prerequisites

Before running the installer, download the SAP NW RFC SDK:

• Minimum: NetWeaver RFC SDK 7.50 Patch 13 or above for Windows X64 (64-bit).
• Recommended: Use the latest available 7.50 patch for Windows X64 (64-bit).
• See SAP NOTE 2573790 for download links: https://launchpad.support.sap.com/#/notes/2573790

If you are unable to download the SDK, your account may not have the required permissions on the SAP ONE Support Launchpad. Contact your SAP platform administrator for assistance.

Extract the SDK to a temporary directory. You will need to point the installer to the sapnwrfc.dll file during installation.

Coming from a pre-installer or earlier ABAP Agent? Those versions are not compatible with ABAP Agent 2.0. See Compatibility with earlier ABAP Agent versions.

Run the Installer

Download the agent ZIP file: SeaLights_ABAP_Agent_Setup.zip

Extract the ZIP file and locate SeaLights_ABAP_Agent_Setup.exe inside it.

The installer requires administrator privileges.

Upgrading or reinstalling? If processes from the selected installation are still running, the installer prompts you to stop them before copying files. Silent installations stop those processes automatically. For the full operator procedure — required task preparation, prompt behavior, and what is replaced — see Upgrading ABAP Agent version.

1

Launch the installer

Run SeaLights_ABAP_Agent_Setup.exe from the extracted folder as an administrator.

2

Choose the install directory

The default install location is:

C:\Program Files\Tricentis\SeaLights\ABAP Agent

The agent binaries are placed in the bin subdirectory.

3

Select the SAP NW RFC DLL

The installer prompts you to browse to your sapnwrfc.dll file. It validates that the DLL is:

• x64 (64-bit)
• At or above the minimum supported version

All DLLs from the selected folder are copied into the agent's bin directory automatically.

4

Installation completes

The installer:

1. Replaces all packaged agent files in the install bin directory (including SLABAPServer.exe and SLABAPAdapterHost.exe), including equal-version files on upgrade or reinstall. Configuration, logs, and userdata under ProgramData are retained.
2. Creates the ProgramData directory tree (config, logs, userdata).
3. Grants NETWORK SERVICE modify access to the ProgramData directories.
4. Copies all SAP NW RFC SDK DLLs to the bin directory.
5. Runs slabapcli setup migrate --yes to migrate any existing configuration to the current version (config schema version 4).
6. Runs slabapcli setup upgrade to apply any post-install setup steps.

After installation, run slabapcli setup status to verify the result. See Validate Your Setup.

The agent server (SLABAPServer.exe) is not started automatically by the installer. Start it separately as part of the setup flow. See Start the Agent Server.

Directory Layout

The installer creates the following standardized directory structure:

Directory	Path	Purpose
Install	%ProgramFiles%\Tricentis\SeaLights\ABAP Agent\bin	Agent binaries (watcher.exe, slabapcli.exe, SLABAPServer.exe, SLABAPAdapterHost.exe) and SAP NW RFC SDK DLLs.
Config	%ProgramData%\Tricentis\SeaLights\ABAP Agent\config	config.toml (schema version 4) and lock files.
Logs	%ProgramData%\Tricentis\SeaLights\ABAP Agent\public\Logs	Watcher, server, AdapterHost, and purger log files (CLI logs to the console only).
Public userdata	%ProgramData%\Tricentis\SeaLights\ABAP Agent\public	Pipeline data visible to operators.
Private userdata	%ProgramData%\Tricentis\SeaLights\ABAP Agent\private	Internal data (SQLite databases).

The NETWORK SERVICE account has modify access to the config, logs, and userdata directories so the Watcher (which runs as a scheduled task under NETWORK SERVICE) can write logs and data.

Log Files

The ABAP Agent stores log files in:

• Watcher (pipeline actions): %ProgramData%\Tricentis\SeaLights\ABAP Agent\public\Logs\<Pipeline name>\ — daily files such as InitialBuildMapping_YYYY-MM-DD.log, BuildMods_YYYY-MM-DD.log, RefreshLinks_YYYY-MM-DD.log, Footprints_YYYY-MM-DD.log
• Watcher (bootstrap): %ProgramData%\Tricentis\SeaLights\ABAP Agent\public\Logs\watcher\
• Server / AdapterHost: %ProgramData%\Tricentis\SeaLights\ABAP Agent\public\logs\ — server-YYYYMMDD.log plus per-task {taskType}\{date}\{processId}\ folders

For the full inventory, see Configuration settings — Log locations and Troubleshooting — Agent Logs.

To purge log files older than 14 days, start Windows PowerShell as an Administrator and run the following from the agent's bin directory:

Command

.\purgeLogs.exe

Uninstall

To uninstall the ABAP Agent, use Add or Remove Programs in Windows Settings, or run the uninstaller from the install directory. The uninstaller runs slabapcli setup uninstall and removes agent binaries and SDK DLLs.

The ProgramData directories (config, logs, userdata) are not removed during uninstall to preserve pipeline data and configuration. Delete them manually if no longer needed.