Ctrlk
Contact SupportProduct
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Set up the agent

Upgrading from an older agent version? The current agent requires configuration version 4. If your config.toml uses an older format, the agent will prompt you to migrate. Follow the steps in Migrate a legacy configuration to upgrade your config.toml.

Prerequisite to Agent Setup

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

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

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.

Syntax
slabapcli.exe setup install
Syntax
.\slabapcli.exe setup install

Example

Expected output (PowerShell)
.\slabapcli.exe setup install
[2025-06-17 08:15:56.388+01:00] [info] Current ANSI Code Page: 65001 (UTF-8) (65001)
[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] Installed default config
[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
[2025-06-17 08:15:56.401+01:00] [info] Total time: 00:00:00.009

This command creates a default config.toml at %ProgramData%\Tricentis\SeaLights\ABAP Agent\config\config.toml with version = 4, and sets the install path to the current working directory and userdata to %ProgramData%\Tricentis\SeaLights\ABAP Agent.

Note: Be sure to back up the config\config.toml file. It cannot be transferred to another computer if you later enable secret protection.

List the agent's settings

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

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

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

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.

This command takes no parameters.

Example

The token and confirmation are not displayed in the terminal window for security. Use Ctrl+V to paste your token, then press Enter. The command automatically runs sealights test to verify the token.

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.

List the SeaLights token

To list the SeaLights token in encrypted form, run the following from your terminal:

Test the connection to SeaLights

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.

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.

This command takes no parameters.

Example

This command is also run automatically after sealights set to verify the token immediately.

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:

Validate your complete setup

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

For details on reading the report, see Validate Your Setup.

PreviousCommand-line interfaceNextMigrate a legacy configuration

Last updated

Was this helpful?