Start the ABAP Agent Server

The ABAP Agent server (SLABAPServer.exe) is a .NET localhost HTTP process that the ABAP Agent CLI and watcher use for server-backed work such as test repository operations, build map stages, refresh links, and FLPCA import.

Start the server after Connect to SeaLights. Complete installation (setup install) and the combined Connect to SeaLights step — both sealights set and sealights test — before you start SLABAPServer.exe. Do not start the server between those two SeaLights commands.

Start the server

Run SLABAPServer.exe from the ABAP Agent bin folder. The server runs in the foreground as a console process and prints log output to the terminal. Stop it with Ctrl+C.

Command Prompt

Command

SLABAPServer.exe

PowerShell

Command

.\SLABAPServer.exe

The server binds to http://127.0.0.1:17500 by default. To change the port, set [server].port in config.toml and restart the server. See Configuration settings.

Example startup output (abbreviated)

[2026-03-08 10:55:00.000 +02:00] [INF] ========== SL.ABAP.SERVER STARTUP INITIATED ==========
[2026-03-08 10:55:00.123 +02:00] [INF] Config: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml (from ProgramData)
[2026-03-08 10:55:00.456 +02:00] [INF] Userdata: C:\ProgramData\Tricentis\SeaLights\ABAP Agent (from settings:userdata)
[2026-03-08 10:55:01.234 +02:00] [INF] SeaLights connectivity validated successfully.
[2026-03-08 10:55:01.567 +02:00] [INF] Readiness / Reason: True / ready
[2026-03-08 10:55:01.890 +02:00] [INF] ========== APPLICATION STARTED — http://127.0.0.1:17500 ==========

Check server readiness

The server exposes a readiness probe at GET http://127.0.0.1:17500/ready. Use this to confirm the server is ready to accept work before running CLI commands or scheduled tasks.

HTTP status	Response body	Meaning
200 OK	{"status":"ready"}	Config valid, SeaLights token validated, process database ready.
503 Service Unavailable	{"status":"not_ready", "reasonCode":"CONFIG_RESTART_REQUIRED", ...}	See Live reload and restart-required fields.
503 Service Unavailable	{"status":"not_ready", ...} (other reasons)	Config invalid, token missing or validation failed, or process database unavailable.

You can check readiness from the command line:

curl http://127.0.0.1:17500/ready

If the server returns not_ready:

• For CONFIG_RESTART_REQUIRED, see Live reload and restart-required fields.
• Verify that sealights set has been run and the token is valid (slabapcli sealights test).
• Verify config.toml has no syntax errors (slabapcli setup status).
• Check the server log in %ProgramData%\Tricentis\SeaLights\ABAP Agent\public\Logs\ for details.