> 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/command-line-interface/set-up-the-agent.md).

# Set up the agent

{% hint style="warning" %}
**Upgrading from an older agent version?** The current agent requires configuration version 6. If your `config.toml` uses an older format, commands fail with an error that tells you to run `slabapcli setup migrate`. Follow the steps in [Migrate a legacy configuration](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/set-up-the-agent/migrate-a-legacy-configuration.md) to upgrade your `config.toml`.
{% endhint %}

## Prerequisite to Agent Setup

To check connectivity to SeaLights, run the following from your terminal (replace `{customerId}` with your customer ID beforehand):

{% tabs %}
{% tab title="Command Prompt" %}
{% code overflow="wrap" lineNumbers="true" %}

```batch
curl -I https://{customerId}.sealights.co
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code overflow="wrap" lineNumbers="true" %}

```powershell
Test-NetConnection {customerId}.sealights.co -Port 443
Invoke-WebRequest https://{customerId}.sealights.co
```

{% endcode %}
{% endtab %}
{% endtabs %}

## Set up the agent

To set up the ABAP agent, run the following from your terminal:

### `slabapcli setup install`

Initializes the ABAP agent by creating a default configuration file under `%ProgramData%\Tricentis\SeaLights\ABAP Agent\config\config.toml`.

Run this command from an elevated (Administrator) terminal, in the agent's `bin` folder. The current folder is recorded in the configuration as the agent's install location, and the command looks for the agent server (`SLABAPServer.exe`) there.

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Syntax" overflow="wrap" %}

```batch
slabapcli.exe setup install
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Syntax" overflow="wrap" %}

```powershell
.\slabapcli.exe setup install
```

{% endcode %}
{% endtab %}
{% endtabs %}

#### Example

{% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe setup install
[2025-06-17 08:15:56.388+01:00] [info] Detected Windows version: Windows 11
[2025-06-17 08:15:56.389+01:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
[2025-06-17 08:15:56.389+01:00] [info] Install default config
[2025-06-17 08:15:56.392+01:00] [info] Default config installed in location C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
[2025-06-17 08:15:56.398+01:00] [info] Installed symmetric key and secured configured secrets
[2025-06-17 08:15:56.401+01:00] [info] Install Windows Error Reporting
[2025-06-17 08:15:56.401+01:00] [info] Installed Windows Error Reporting
Registered Windows service 'SLABAPServer' -> C:\Program Files\Tricentis\SeaLights\ABAP Agent\bin\SLABAPServer.exe
SLABAPServer Windows service is registered.
Finish configuring config.toml (RFCs, pipelines, port, etc.), then start it with:
  slabapcli server start
```

{% endcode %}

This command does the following:

* It creates a default `config.toml` at `%ProgramData%\Tricentis\SeaLights\ABAP Agent\config\config.toml` with `version = 6`, and sets the `install` path to the current working directory and `userdata` to `%ProgramData%\Tricentis\SeaLights\ABAP Agent`.
* By default, it generates a symmetric key that is locked to this computer, and secures the secrets stored in `config.toml` (for example the SeaLights token and RFC credentials). Secrets are protected from the moment the configuration is created.
* It configures Windows Error Reporting to keep full crash dumps of the agent's watcher process.
* It registers the **SeaLights ABAP Server** Windows service (`SLABAPServer`) so that it starts automatically with Windows. It does **not** start the server now; you start it yourself (see below).

If `config.toml` already exists, the command does not overwrite it. If the configuration is already secured, the command only retries registering the service.

After you set the SeaLights token (`slabapcli sealights set`, below), start the server with `slabapcli server start`, run from the same `bin` folder. See [Start the ABAP Agent Server](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/start-the-agent-server.md).

{% hint style="warning" %}
**Note**: Be sure to back up the `config\config.toml` file. Because the key is locked to this computer, the file cannot be transferred to another computer.
{% endhint %}

### `slabapcli setup list`

Checks whether setup has already been done on this computer. If the agent has not been set up, the command prints a warning that tells you to run `slabapcli setup install`. If it has, the command prints `setup already done.`

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Syntax" overflow="wrap" %}

```batch
slabapcli.exe setup list
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Syntax" overflow="wrap" %}

```powershell
.\slabapcli.exe setup list
```

{% endcode %}
{% endtab %}
{% endtabs %}

To check the overall health of the agent, use `slabapcli setup status` (see [Validate your complete setup](#validate-your-complete-setup)).

## List the agent's settings

To list the ABAP agent's settings, run the following from your terminal:

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Command" overflow="wrap" %}

```batch
slabapcli.exe settings list
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Command" overflow="wrap" %}

```powershell
.\slabapcli.exe settings list
```

{% endcode %}
{% endtab %}
{% endtabs %}

{% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe settings list
[2025-06-20 10:22:48.782+01:00] [info] Detected Windows version: Windows 11
[2025-06-20 10:22:48.782+01:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
[2025-06-20 10:22:48.785+01:00] [info] Install dir   : C:\Program Files\Tricentis\SeaLights\ABAP Agent\bin
[2025-06-20 10:22:48.786+01:00] [info] User data dir : C:\ProgramData\Tricentis\SeaLights\ABAP Agent
[2025-06-20 10:22:48.786+01:00] [info] Key           : Encrypted
[2025-06-20 10:22:48.787+01:00] [info] IV            : 8e1f5c3a9b2d47606f0a1c7de3b45a92
```

{% endcode %}

`Key` shows `Encrypted` when secret protection is on. The key itself is never displayed in that case.

## Connect the agent to your SeaLights environment

The next step is to connect the agent to your SeaLights environment. You can do this as follows:

### Copy your SeaLights agent token <a href="#toc201668090" id="toc201668090"></a>

First you'll need to copy your SeaLights agent token to the clipboard, as follows:

1. In a web browser, navigate to the URL for your SeaLights dashboard.
2. Select the **Settings** icon, and then select **Agent Tokens** from the **Settings** menu's **Cockpit & Onboarding** section.
3. Locate the entry for your agent token, and press the **Copy token** button to copy it to the clipboard. Be sure to copy a token whose status is active.

### Connect the agent to SeaLights <a href="#toc201668091" id="toc201668091"></a>

Next, you'll need to connect the agent to SeaLights using the command-line interface. You can do this as follows:

* Run the following command from your terminal:

Connects the ABAP agent to your SeaLights environment by storing your agent token in the encrypted configuration.

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Syntax" overflow="wrap" %}

```batch
slabapcli.exe sealights set
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Syntax" overflow="wrap" %}

```powershell
.\slabapcli.exe sealights set
```

{% endcode %}
{% endtab %}
{% endtabs %}

This command takes no parameters.

## Example

{% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe sealights set
[2026-04-21 08:51:38.301+01:00] [info] Detected Windows version: Windows 11
[2026-04-21 08:51:38.306+01:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
Enter token: ********************
Confirm token: ********************
Token accepted (sha1 a3f9c1d2).
Running 'sealights test' to verify the new token...
[2026-04-21 08:51:47.710+01:00] [info] Test SeaLights: customer.sealights.co
Agent token is valid.
Sealights connectivity check succeeded.
```

{% endcode %}

{% hint style="info" %}
The token and confirmation are not shown in the terminal window; each character you type or paste is echoed as `*`. Use **Ctrl+V** to paste your token, then press **Enter**. The value in parentheses after `sha1` is a short fingerprint of the token you entered.

The command saves the token first and then automatically runs `sealights test` to verify it. If the test fails, the token stays saved: fix the problem and run `sealights test` again, or run `sealights set` with a different token.
{% endhint %}

{% hint style="warning" %}
If the agent server is already running, restart it after you change the token (`slabapcli server stop`, then `slabapcli server start`) so that it uses the new token.
{% endhint %}

{% hint style="warning" %}
You must run `sealights set` and successfully store a token **before** running `rfc set`. The CLI requires a valid SeaLights token when configuring RFC destinations.
{% endhint %}

## List the SeaLights token

To list the SeaLights connection details with the token masked, run the following from your terminal:

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Command" overflow="wrap" %}

```batch
slabapcli.exe sealights list
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Command" overflow="wrap" %}

```powershell
.\slabapcli.exe sealights list
```

{% endcode %}
{% endtab %}
{% endtabs %}

{% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe sealights list
[2025-06-17 09:03:34.867+01:00] [info] Detected Windows version: Windows 11
[2025-06-17 09:03:34.867+01:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
Hostname: customer.sealights.co
Clock sync hostname: customer.sealights.co
Token   : ****** (Encrypted)
Customer id: customer
```

{% endcode %}

`Token` shows `****** (Encrypted)` when secret protection is on. If secret protection is not enabled, the stored token is shown in clear text.

## Test the connection to SeaLights

{% hint style="info" %}
The `sealights set` command above already ran a connectivity test automatically. Use `sealights test` only if you need to re-verify connectivity later without changing the token.
{% endhint %}

Validates the agent token against the SeaLights API. Returns a confirmation if the token is valid, or an error with troubleshooting guidance if it is not.

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Syntax" overflow="wrap" %}

```batch
slabapcli.exe sealights test
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Syntax" overflow="wrap" %}

```powershell
.\slabapcli.exe sealights test
```

{% endcode %}
{% endtab %}
{% endtabs %}

This command takes no parameters.

## Example

{% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe sealights test
[2026-04-21 09:11:54.001+01:00] [info] Detected Windows version: Windows 11
[2026-04-21 09:11:54.006+01:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
[2026-04-21 09:11:54.013+01:00] [info] Test SeaLights: customer.sealights.co
Agent token is valid.
Sealights connectivity check succeeded.
```

{% endcode %}

{% hint style="info" %}
This command is also run automatically after `sealights set` to verify the token immediately.
{% endhint %}

## Add a proxy

If connection fails your organization might be using a proxy. If that's the case, use the following to set it up:

{% hint style="info" %}
This proxy covers the connection to SeaLights only. Test repositories use the `[adapters]` section of `config.toml`. For both, see [Configure a proxy](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/configure-a-proxy.md).
{% endhint %}

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Command" overflow="wrap" %}

```batch
slabapcli.exe proxy set --server "http://proxy.example.com:8080" --auth
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Command" overflow="wrap" %}

```powershell
.\slabapcli.exe proxy set --server 'http://proxy.example.com:8080' --auth
```

{% endcode %}
{% endtab %}
{% endtabs %}

{% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe proxy set --server 'http://proxy.example.com:8080' --auth
[2025-10-20 13:45:22.514+02:00] [info] Detected Windows version: Windows 11
[2025-10-20 13:45:22.516+02:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
Enter username: user1
Enter password: ********
Confirm password: ********
Password accepted (sha1 3b1f0c7a).
```

{% endcode %}

* `--server` (`-s`) is required and must be an `http` or `https` URL that includes a host name.
* `--auth` (`-a`) prompts for the proxy user name and password. The password you type is not displayed, and the `sha1` value is a short fingerprint you can use to confirm you entered the password you intended. If you omit `--auth`, the proxy is saved without credentials and any credentials stored earlier are discarded.
* Restart the agent server after you change the proxy so that it picks up the new setting (see [Start the ABAP Agent Server](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/start-the-agent-server.md)).

To display the current proxy settings, run `slabapcli.exe proxy list`:

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Command" overflow="wrap" %}

```batch
slabapcli.exe proxy list
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Command" overflow="wrap" %}

```powershell
.\slabapcli.exe proxy list
```

{% endcode %}
{% endtab %}
{% endtabs %}

{% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe proxy list
[2025-10-20 13:46:03.201+02:00] [info] Detected Windows version: Windows 11
[2025-10-20 13:46:03.203+02:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
Proxy configuration:
  Server: http://proxy.example.com:8080
  Authentication: enabled
    Username: user1
    Password: ****** (Encrypted)
```

{% endcode %}

If no proxy is configured, the output ends with `No proxy configured.` If a proxy is configured without credentials, it shows `Authentication: disabled`. When secret protection is not enabled, the stored password is shown in clear text.

## Validate your complete setup

After configuring all components (SeaLights, RFC destinations, and pipelines), run the setup status command to verify everything in one step:

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Command" overflow="wrap" %}

```batch
slabapcli.exe setup status
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Command" overflow="wrap" %}

```powershell
.\slabapcli.exe setup status
```

{% endcode %}
{% endtab %}
{% endtabs %}

For details on reading the report, see [Validate Your Setup](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/validate-your-setup.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/set-up-the-agent.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.