> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/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. **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. {% hint style="info" %} After installation, start the agent server separately by running `SLABAPServer.exe`. See [Start the Agent Server](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/start-the-agent-server.md). {% 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: {% 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/upgrading-abap-agent-version.md#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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/upgrading-abap-agent-version.md). {% 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. 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. {% endstep %} {% endstepper %} {% hint style="info" %} After installation, run `slabapcli setup status` to verify the result. See [Validate Your Setup](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/validate-your-setup.md). {% endhint %} {% hint style="info" %} 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/start-the-agent-server.md). {% 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 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\\` — 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md#log-locations) and [Troubleshooting — Agent Logs](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/troubleshooting-the-abap-agent.md#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: {% code title="Command" overflow="wrap" %} ```powershell .\purgeLogs.exe ``` {% endcode %} ## 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. {% 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 %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/install-watcher-and-slabapcli.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.