> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/setup-and-configuration/install-the-abap-agent/install-watcher-and-slabapcli.md).

# 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. The **SeaLights ABAP Server** (`SLABAPServer` Windows service) is 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.

{% hint style="info" %}
After installation, run `slabapcli setup install` (which registers the agent server as a Windows service) and `slabapcli sealights set`, then start the agent server with `slabapcli server start`. See [Start the Agent Server](broken://pages/jjXJbDJ9CnFBYzl2NDMP).
{% endhint %}

## 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>

{% hint style="warning" %}
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.
{% endhint %}

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

{% hint style="info" %}
**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](broken://pages/gzlcIedoaqgX25KaIvmi#compatibility-with-earlier-abap-agent-versions).
{% endhint %}

## Run the Installer

Download the agent ZIP file: [SeaLights\_ABAP\_Agent\_Setup.zip](https://agents.sealights.co/slabap/latest/SeaLights_ABAP_Agent_Setup.zip)

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

{% hint style="info" %}
The installer requires **administrator privileges**.
{% endhint %}

{% hint style="info" %}
**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](broken://pages/gzlcIedoaqgX25KaIvmi).
{% endhint %}

{% stepper %}
{% step %}

### Launch the installer

Run `SeaLights_ABAP_Agent_Setup.exe` from the extracted folder as an administrator.
{% endstep %}

{% step %}

### 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.
{% endstep %}

{% step %}

### 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.
{% endstep %}

{% step %}

### 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. Does **not** register or start the **SeaLights ABAP Server** Windows service (`SLABAPServer`). `slabapcli setup install` registers it (Automatic startup, **NETWORK SERVICE** account); on an upgrade, the existing registration is kept.
6. Runs `slabapcli setup migrate --yes` to migrate any existing configuration to the current version (config schema version 6).
7. Runs `slabapcli setup upgrade` automatically. On an upgrade, this restores the **SeaLights ABAP Server** service and the agent's scheduled tasks to the state they were in before the upgrade. You do not need to run this command yourself.
   {% endstep %}
   {% endstepper %}

{% hint style="info" %}
**New install?** The installer does not create `config.toml` — it's only created by `slabapcli setup install`. If you run `slabapcli setup status` now, it reports `Config file does not exist`. That's expected — continue to [Set up the agent](broken://pages/54pGpo5ULmlonbluKqHL) next, then use `setup status` later to verify the completed setup.

**Upgrading or reinstalling?** `config.toml` already exists, so you can run `slabapcli setup status` now to verify the result. See [Validate Your Setup](broken://pages/A8FSceuQXginyDTL5f4z).
{% endhint %}

{% hint style="info" %}
The installer neither registers nor starts the **SeaLights ABAP Server** Windows service (`SLABAPServer`). `slabapcli setup install` registers it with Automatic startup, so it also starts after a machine reboot. After `slabapcli setup install` and `slabapcli sealights set`, run `slabapcli server start` for the first start. See [Start the Agent Server](broken://pages/jjXJbDJ9CnFBYzl2NDMP).
{% endhint %}

## 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 6) 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 agent data (databases and caches).                                                                           |

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 <a href="#toc201668083" id="toc201668083"></a>

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`, `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-run task folders under `<Pipeline name>\{origin}\{date}\{run}\`

These paths assume the default userdata directory. If you change `[settings].userdata`, the `public\Logs` folders move with it (the watcher bootstrap log stays under ProgramData).

For the full inventory, see [Configuration settings — Log locations](broken://pages/DZM4uWEu5r51kMDWCmDB#log-locations) and [Troubleshooting — Agent Logs](broken://pages/DTAUuyOmlKawT2B8UTYM#agent-logs).

To delete aged log files and agent artifacts automatically, schedule the purger. See [Schedule the purger](broken://pages/jvmOWRjO10SvuLg7G51U#schedule-the-purger).

## Uninstall

To uninstall the ABAP Agent, use **Add or Remove Programs** in Windows Settings, or run the uninstaller from the install directory. The uninstaller stops and unregisters the **SeaLights ABAP Server** Windows service (`slabapcli server uninstall`), runs `slabapcli setup uninstall`, and removes agent binaries and SDK DLLs.

{% hint style="warning" %}
The ProgramData directories (config, logs, userdata) are **not removed** during uninstall to preserve pipeline data and configuration. Delete them manually if no longer needed.
{% endhint %}