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

Setup and installation

Set up ABAP Agent 2.0 through initial build map and search_testrepo — for any supported test repository.

This guide is Part 1 of the ABAP Agent 2.0 onboarding path. It takes you from install through a finished initial build map and a successful search_testrepo check.

It applies to all supported test repositories (Azure DevOps, Tosca Commander, Tosca Cloud, Excel, Xray, qTest, Certify, SAP Solution Manager (SSM), OpenText ALM). Adapter-specific connection details are under Test Tool Integrations.

Next: Show the value with Test Cycles (Part 2). For Tosca Cloud runner + TIA beyond day-zero recommendations, see Tosca Cloud runner and TIA (Part 3).

After you start the ABAP Agent server later in this guide, it must remain online at all times for ongoing operation.

What you will have at the end

  • ABAP Agent 2.0 installed and configured (SeaLights token, RFC Destinations, pipeline, at least one test repository)

  • SAP authorizations and setup status healthy

  • SLABAPServer.exe running

  • Initial build map completed for the pipeline

  • At least one successful search_testrepo smoke check

What you will not see in the SeaLights UI during this part

  • The initial build map is not shown as a progress UI beyond the fact that a build exists for the application.

  • Overall / full-application coverage is not presented for this flow.

  • After build modifications (Part 2), SeaLights focuses on change coverage and test impact — not a full-system coverage percentage from the initial map.

Prerequisites

Before you begin, make sure the following are in place:

ABAP Agent is not compatible with ABAP Agent 1.3.0.70 and earlier. You cannot continue using your existing 1.3 installation, SAP add-on, local agent data, or SeaLights application history with the current release. See Upgrading ABAP Agent version for the full requirements and required actions. Documentation for the legacy product line (1.3 and earlier) is under ABAP Agent 1.x in this section.

1

Install the SAP add-on and Windows agent

Follow the install tree end-to-end:

  1. Install the ABAP Agent (prerequisites, add-on, accounts, SCMON, Windows binaries)

  2. Create SAP accounts as required — Create SAP accounts

2

Authorizations

Authorizations are part of the happy path — do not skip them until troubleshooting.

  1. Generate / assign the SeaLights authorization role — Generate Authorization Profiles (includes the authorization objects table)

  2. Assign /TRICE/SL_AUTHS (and related objects) to the RFC service user used by the agent

  3. If later checks fail, use Troubleshooting — SAP authorization role issues

3

Set up the agent

Initialize the ABAP agent on the Windows host. This generates the encryption key and default configuration file.

Initializes the ABAP agent by generating a machine-locked symmetric key and creating a default configuration file.

This command takes no parameters.

Example

This command does the following:

  • It generates a machine-locked symmetric key used to protect secrets, including RFC Destination usernames and passwords, and the SeaLights agent ID.

  • It creates a default configuration file named config.toml in the ..\config directory.

Note: You cannot use the generated key on any other computer. Be sure to back up the config\config.toml file.

Full reference: Set up the agent. Use schema migrate only if you are already on 2.0+.

4

Connect to SeaLights

Store your SeaLights agent token in the encrypted configuration. Complete both commands in this step before starting the server.

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.

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.

5

Start the ABAP Agent server

Start SLABAPServer.exe immediately after the combined Connect to SeaLights step.

Follow Start the ABAP Agent Server (recommended setup order: start after sealights set / sealights test).

6

Create RFC Destinations

Create an RFC Destination for each SAP system (QAS and PRD) that the agent needs to connect to.

Prerequisite: Run slabapcli sealights set before running rfc set. The automatic verification step requires a valid SeaLights token.

Creates or updates an RFC Destination for an SAP system. The username and password are entered interactively and stored encrypted.

Parameter
Required
Description

--name

Yes

RFC Destination name (e.g. S21).

--hostname

Yes

SAP system hostname.

--sysnr

Yes

SAP system number (instance number).

--client

Yes

SAP client number.

--lang

Yes

SAP login language (e.g. EN).

Example

The password and confirmation are not displayed in the terminal window for security. The command automatically runs rfc test after saving the RFC Destination.

Repeat this command for every SAP system the pipeline will use (for example, once for QAS and once for PRD). Full reference: Create, Test & List RFC Destinations.

7

Create a pipeline

Link your QAS and Production systems to a SeaLights application by creating a pipeline.

Creates a pipeline that links a QAS (or DEV) and Production system in your SAP landscape to a SeaLights application.

Parameter
Required
Description

--appname

Yes

The SeaLights application name to associate with this pipeline.

--qas

One of --qas or --dev

The QAS RFC Destination name.

--dev

One of --qas or --dev

The DEV RFC Destination name. Use this instead of --qas when your source system is a DEV system. The key is stored as dev in the config file and is not normalized to qas.

--prd

Yes

The PRD RFC Destination name.

--name

No

A custom name for the pipeline. If omitted, the name is auto-generated as <appname>-<qas> (for example, myapp-S21). Allowed characters: A-Za-z0-9._-

--labid

No

The lab ID for this pipeline. If omitted, it is auto-generated as <QAS SID> <QAS RFC hostname> (for example, S21 vwsvtstsap13.tricentis.com).

Multiple pipelines can share the same --appname. Each pipeline's name must be unique — the auto-generated name (appname-qas) ensures this when pipelines use different QAS systems.

Example: Create a pipeline using a QAS system

If a pipeline with the same name already exists, the command updates it and prints has been updated instead of has been created.

This writes the following entry to config.toml:

Example: Create a pipeline using a DEV system

This writes the following entry to config.toml. Note that the key is stored as dev, not qas:

Leave --labid unset when you create a pipeline. The agent derives the lab ID automatically so it matches the QAS branch name: "<SID> <ashost>" (for example, S21 vwsvtstsap13.tricentis.com).

Overriding --labid casually breaks Test Cycles in SeaLights.

The auto-derived lab ID is what SeaLights uses for Test Cycles and Footprints. Only override --labid when you deliberately need a different lab ID and understand the Test Cycle impact.

Full reference: Create & List Pipelines.

8

Configure a test repository

Configure at least one test repository for your adapter type. Each adapter page under Test Tool Integrations has a type-specific testrepo set example. Full CLI options are in Configure Test Repositories. After you save, testrepo set can run its automatic connection test.

When the test repository is saved and the connection test succeeds, stay in this Part 1 guide. Continue with the next steps in order:

  1. Validate with setup status

  2. Run the initial build map

  3. Smoke-test search_testrepo

Do not schedule ongoing repository search or Footprints capture here — Part 1 covers the day-zero smoke check after the initial build map. For adapter-specific connect guidance and the full post-connect ops flow, use the matching page under Test Tool Integrations.

9

Validate with setup status

Before build-map or search work, run the comprehensive validation gate:

This checks SeaLights connectivity, RFC connections, SAP authorizations, SCMON state, and agent-side prerequisites. Exit code 0 means you can continue.

Full reference: Validate Your Setup.

10

Run the initial build map

Create an Initial Build Map for the pipeline. This scans QAS for ABAP components in use in Production and sends them to SeaLights.

Creates an Initial Build Map for a pipeline. The build map is a snapshot of the standard and custom ABAP code components in the pipeline's QAS system (and their related objects), based on usage data from the pipeline's Production system.

Parameter
Required
Description

--pipeline

Yes

The pipeline name (as shown in pipeline list).

Example

The agent creates a scheduled INIT_BUILD_MAP task that runs once only (two minutes from now) to create the Initial Build Map.

You can also create an Initial Build Map directly by running watcher.exe INIT_BUILD_MAP --pipeline <pipeline-name> from the command line.

Duration: An initial build map can take up to about 10 hours end-to-end, depending on landscape size and system load. For IBM stages, see Create an Initial Build Map for your Pipeline.

Build modifications are usually much shorter, but duration scales with the number and size of transports imported.

When it completes, confirm in SeaLights that the application has a build. Do not expect a dedicated “initial build map progress” UI or overall coverage dashboard from this step.

Full reference: Create an Initial Build Map for your Pipeline.

11

Smoke-test search_testrepo

Schedule repository search and confirm the agent can discover matching tests for known search terms or changed contexts.

For day-zero validation, schedule search_testrepo against your configured repository, then confirm the agent can discover matching tests for known search terms or changed contexts.

search_testrepo run registers a Windows Scheduled Task (watcher.exe SEARCH_TESTREPO). The first run happens according to the cron you set (or the default). Use a near-term cron if you need the smoke check sooner than the weekly default.

Parameter
Required
Description

--pipeline

Yes

Pipeline name ([[pipeline]].name).

--testrepo

Yes

Test repository name ([[testrepo]].name) linked to that pipeline.

--cron

No

5-field cron. Default: 0 2 * * 0 (Sunday at 02:00). Example for a sooner smoke: */15 * * * * (every 15 minutes) — then tighten the schedule for production.

Pass criteria for this smoke check: the scheduled task is registered, and search returns matches for terms you expect (or FLPCA-expanded Fiori titles when FLPCA is imported). Ongoing ops detail and stop/list commands: Search Test Repositories. Adapter pages also embed the shared TTI search include for recurring schedule guidance.

If search fails, check server and adapter logs — Configuration settings — Log locations and Troubleshooting.

Troubleshooting

Problem
What to check

No application / build in SeaLights after the initial build map

Check server and watcher logs. Verify RFC connectivity with slabapcli rfc test --name <rfc>.

setup status fails

Fix SeaLights token, RFC destinations, SAP authorizations, and SCMON before starting the server. See Validate Your Setup.

search_testrepo finds nothing

Confirm every testrepo set for the pipeline is done. If you just changed config, verify it reloaded — see Configuration Settings. Check adapter logs under Log locations. For Fiori, confirm FLPCA was imported.

No coverage / Test Gaps do not move after a test

Confirm Footprints is running (footprints run). For Tosca, set SeaLightsLabId to the auto-derived pipeline lab ID — leave --labid unset on pipeline set. Wait for SeaLights to process Footprints.

Test Cycles look wrong or empty

Overriding --labid casually breaks Test Cycles. Leave it unset so the lab ID matches the QAS branch name ("<SID> <ashost>"). Use pipeline list to confirm.

TIA does not skip / optimize tests (Tosca Cloud)

Confirm a Build Modification exists for the transport, Footprints are collecting, and SeaLights optimization is enabled on the playlist. See Run a test in Tosca Cloud.

For deeper diagnosis, see Troubleshooting the ABAP Agent.

Done with Part 1

Continue to Show the value with Test Cycles to import transports, open a Test Cycle, and demonstrate recommendations, gaps, and change coverage.

Related reading

PreviousGuidesNextShow the value with Test Cycles

Last updated

Was this helpful?