> 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/guides/setup-and-installation.md). # Setup and installation 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)](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/ssm.md), OpenText ALM). Adapter-specific connection details are under [Test Tool Integrations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations.md). **Next:** [Show the value with Test Cycles](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/show-the-value-with-test-cycles.md) (Part 2). For Tosca Cloud runner + TIA beyond day-zero recommendations, see [Tosca Cloud runner and TIA](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/tosca-cloud-runner-and-tia.md) (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 {% hint style="warning" %} **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. {% endhint %} ## Prerequisites Before you begin, make sure the following are in place: * Windows host for ABAP Agent 2.0 binaries (`slabapcli.exe`, `watcher.exe`, `SLABAPServer.exe`) — [Install WATCHER, SLABAPCLI and Server](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/install-watcher-and-slabapcli.md). * ABAP Agent **2.0** SAP add-on installed on your SAP systems — [Install the ABAP addon](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/install-the-abap-addon.md). * SCMON data collection configured on QAS — [Configure your QAS systems to collect SCMON data](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/configure-your-qas-systems-to-collect-scmon-data.md). * A SeaLights agent token. * SAP connection details for QAS and PRD (hostname, system number, client, RFC user credentials). * Access to at least one supported test repository (Azure DevOps, Tosca Commander, Tosca Cloud, Excel, Xray, qTest, Certify, [SAP Solution Manager (SSM)](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/ssm.md), or OpenText ALM). Adapter setup is under [Test Tool Integrations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations.md). {% hint style="danger" %} **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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/upgrading-abap-agent-version.md#compatibility-with-earlier-abap-agent-versions) for the full requirements and required actions. Documentation for the legacy product line (1.3 and earlier) is under [ABAP Agent 1.x](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/abap-agent.md) in this section. {% endhint %} {% stepper %} {% step %} ### Install the SAP add-on and Windows agent Follow the install tree end-to-end: 1. [Install the ABAP Agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent.md) (prerequisites, add-on, accounts, SCMON, Windows binaries) 2. Create SAP accounts as required — [Create SAP accounts](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/create-sap-accounts.md) {% endstep %} {% step %} ### Authorizations Authorizations are part of the happy path — do not skip them until troubleshooting. 1. Generate / assign the SeaLights authorization role — [Generate Authorization Profiles](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/generate-authorization-profiles.md) (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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/troubleshooting-the-abap-agent.md#diagnosing-sap-authorization-role-issues) {% endstep %} {% step %} ### 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. {% 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 %} This command takes no parameters. ## 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] Current ANSI Code Page: 65001 (UTF-8) (65001) [2025-06-17 08:15:56.389+01:00] [info] Config pathname: ../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.395+01:00] [info] Install symmetric key [2025-06-17 08:15:56.395+01:00] [info] Create symmetric key [2025-06-17 08:15:56.398+01:00] [info] Created symmetric key [2025-06-17 08:15:56.399+01:00] [info] Create IV [2025-06-17 08:15:56.399+01:00] [info] Created IV [2025-06-17 08:15:56.400+01:00] [info] Installed symmetric key [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.013 ``` {% endcode %} 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`. {% hint style="warning" %} **Note**: You cannot use the generated key on any other computer. Be sure to back up the `config\config.toml` file. {% endhint %} Full reference: [Set up the agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/set-up-the-agent.md). Use schema migrate only if you are already on 2.0+. {% endstep %} {% step %} ### 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. {% 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.306+01:00] [info] Config pathname: ..\config\config.toml Enter token: Confirm token: Token accepted (a3f***...***d2b). Running 'sealights test' to verify the new token... [2026-04-21 08:51:47.710+01:00] [info] Test SeaLights: customer.sealights.io Agent token is valid. Sealights connectivity check succeeded. ``` {% endcode %} {% hint style="info" %} 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. {% 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.006+01:00] [info] Config pathname: ..\config\config.toml [2026-04-21 09:11:54.013+01:00] [info] Test SeaLights: customer.sealights.io 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 %} {% endstep %} {% step %} ### Start the ABAP Agent server Start `SLABAPServer.exe` immediately after the combined **Connect to SeaLights** step. Follow [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) (recommended setup order: start after `sealights set` / `sealights test`). {% endstep %} {% step %} ### Create RFC Destinations Create an RFC Destination for each SAP system (QAS and PRD) that the agent needs to connect to. {% hint style="warning" %} **Prerequisite:** Run `slabapcli sealights set` before running `rfc set`. The automatic verification step requires a valid SeaLights token. {% endhint %} Creates or updates an RFC Destination for an SAP system. The username and password are entered interactively and stored encrypted. {% tabs %} {% tab title="Command Prompt" %} {% code title="Syntax" overflow="wrap" %} ```batch slabapcli.exe rfc set --name --hostname --sysnr --client --lang ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Syntax" overflow="wrap" %} ```powershell .\slabapcli.exe rfc set --name --hostname --sysnr --client --lang ``` {% endcode %} {% endtab %} {% endtabs %} | 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 {% tabs %} {% tab title="Command Prompt" %} {% code title="Command" overflow="wrap" %} ```batch slabapcli.exe rfc set --name "S21" --hostname "vwsvtstsap13.tricentis.com" --sysnr "00" --client "100" --lang "EN" ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Command" overflow="wrap" %} ```powershell .\slabapcli.exe rfc set --name 'S21' --hostname 'vwsvtstsap13.tricentis.com' --sysnr '00' --client '100' --lang 'EN' ``` {% endcode %} {% endtab %} {% endtabs %} {% code title="Expected output (PowerShell, abbreviated)" overflow="wrap" lineNumbers="true" %} ```log .\slabapcli.exe rfc set --name 'S21' --hostname 'vwsvtstsap13.tricentis.com' --sysnr '00' --client '100' --lang 'EN' [2026-05-07 11:37:08.572+01:00] [info] Config pathname: ..\config\config.toml Enter username: hunterh Enter password: Confirm password: Password accepted (a3f***...***d2b). Running 'rfc test --name S21' to verify the new RFC destination... [2026-05-07 11:37:15.910+01:00] [info] Testing rfc: S21 Connected System info: RFCDBHOST: sapqas01 RFCSYSID: S21 RFCIPADDR: 10.0.1.50 RFCKERNRL: 753 RFCSAPRL: 750 SeaLights ABAP add-on: Installed SeaLights ABAP add-on version: Installed version: RELEASE=2025_01 EXTRELEASE=0012 (minimum supported ...) Time synchronization: ... RFC function modules: All required RFC function modules callable Tables: All required tables readable SCMON Configuration: ... SCMON is running and configured to stay active until 2027-12-31 SCMON_COLLECT callability: SCMON_COLLECT call succeeded ``` {% endcode %} {% hint style="info" %} The password and confirmation are not displayed in the terminal window for security. The command automatically runs `rfc test` after saving the RFC Destination. {% endhint %} {% hint style="info" %} 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-test-and-list-rfc-destinations.md). {% endhint %} {% endstep %} {% step %} ### 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. {% tabs %} {% tab title="Command Prompt" %} {% code title="Syntax" overflow="wrap" %} ```batch slabapcli.exe pipeline set --appname --qas --prd [--name ] [--labid ] ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Syntax" overflow="wrap" %} ```powershell .\slabapcli.exe pipeline set --appname --qas --prd [--name ] [--labid ] ``` {% endcode %} {% endtab %} {% endtabs %} | 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 `-` (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 ` ` (for example, `S21 vwsvtstsap13.tricentis.com`). | {% hint style="info" %} 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. {% endhint %} ## Example: Create a pipeline using a QAS system {% tabs %} {% tab title="Command Prompt" %} {% code title="Command" overflow="wrap" %} ```batch slabapcli.exe pipeline set --appname "ALM_Demo" --qas "S21" --prd "S23" ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Command" overflow="wrap" %} ```powershell .\slabapcli.exe pipeline set --appname 'ALM_Demo' --qas 'S21' --prd 'S23' ``` {% endcode %} {% endtab %} {% endtabs %} {% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %} ```log .\slabapcli.exe pipeline set --appname 'ALM_Demo' --qas 'S21' --prd 'S23' [2026-03-08 10:33:36.956+02:00] [info] Detected Windows version: Windows 11 [2026-03-08 10:33:36.957+02:00] [info] Config pathname: ../config/config.toml [2026-03-08 10:33:37.012+02:00] [info] Pipeline 'ALM_Demo-S21' has been created in '../config/config.toml'. Use this name with the buildmap, footprints, and buildmods commands. ``` {% endcode %} {% hint style="info" %} If a pipeline with the same name already exists, the command updates it and prints `has been updated` instead of `has been created`. {% endhint %} This writes the following entry to `config.toml`: {% code title="config.toml" %} ```toml [[pipeline]] name = "ALM_Demo-S21" appname = "ALM_Demo" qas = "S21" prd = "S23" labid = "S21 vwsvtstsap13.tricentis.com" disablesetref = false ``` {% endcode %} ## Example: Create a pipeline using a DEV system {% tabs %} {% tab title="Command Prompt" %} {% code title="Command" overflow="wrap" %} ```batch slabapcli.exe pipeline set --appname "ALM_Demo" --dev "S21" --prd "S23" ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Command" overflow="wrap" %} ```powershell .\slabapcli.exe pipeline set --appname 'ALM_Demo' --dev 'S21' --prd 'S23' ``` {% endcode %} {% endtab %} {% endtabs %} This writes the following entry to `config.toml`. Note that the key is stored as `dev`, not `qas`: {% code title="config.toml" %} ```toml [[pipeline]] name = "ALM_Demo-S21" appname = "ALM_Demo" dev = "S21" prd = "S23" labid = "S21 vwsvtstsap13.tricentis.com" disablesetref = false ``` {% endcode %} {% hint style="warning" %} **Leave `--labid` unset** when you create a pipeline. The agent derives the lab ID automatically so it matches the QAS **branch name**: `" "` (for example, `S21 vwsvtstsap13.tricentis.com`). Overriding `--labid` casually breaks **Test Cycles** in SeaLights. {% endhint %} 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-and-list-pipelines.md). {% endstep %} {% step %} ### Configure a test repository Configure at least one test repository for **your** adapter type. Each adapter page under [Test Tool Integrations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations.md) has a type-specific `testrepo set` example. Full CLI options are in [Configure Test Repositories](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/configure-test-repositories.md). 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations.md). {% endstep %} {% step %} ### Validate with `setup status` Before build-map or search work, run the comprehensive validation gate: ```batch slabapcli.exe setup status ``` 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/validate-your-setup.md). {% endstep %} {% step %} ### 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. {% tabs %} {% tab title="Command Prompt" %} {% code title="Syntax" overflow="wrap" %} ```batch slabapcli.exe buildmap run --pipeline ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Syntax" overflow="wrap" %} ```powershell .\slabapcli.exe buildmap run --pipeline ``` {% endcode %} {% endtab %} {% endtabs %} | Parameter | Required | Description | | ------------ | -------- | ------------------------------------------------ | | `--pipeline` | Yes | The pipeline name (as shown in `pipeline list`). | ## Example {% tabs %} {% tab title="Command Prompt" %} {% code title="Command" overflow="wrap" %} ```batch slabapcli.exe buildmap run --pipeline "HH_SLABAPCLI_170625" ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Command" overflow="wrap" %} ```powershell .\slabapcli.exe buildmap run --pipeline 'HH_SLABAPCLI_170625' ``` {% endcode %} {% endtab %} {% endtabs %} {% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %} ```log .\slabapcli.exe buildmap run --pipeline 'HH_SLABAPCLI_170625' [2025-06-17 15:28:19.807+01:00] [info] Current ANSI Code Page: 65001 (UTF-8) (65001) [2025-06-17 15:28:19.807+01:00] [info] Config pathname: ../config/config.toml ``` {% endcode %} The agent creates a scheduled INIT\_BUILD\_MAP task that runs once only (two minutes from now) to create the Initial Build Map. {% hint style="info" %} You can also create an Initial Build Map directly by running `watcher.exe INIT_BUILD_MAP --pipeline ` from the command line. {% endhint %} {% hint style="warning" %} **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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-an-initial-build-map-for-your-pipeline.md). **Build modifications** are usually much shorter, but duration scales with the number and size of transports imported. {% endhint %} 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-an-initial-build-map-for-your-pipeline.md). {% endstep %} {% step %} ### 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. {% tabs %} {% tab title="Command Prompt" %} {% code title="Schedule a search (smoke)" overflow="wrap" %} ```batch slabapcli.exe search_testrepo run --pipeline --testrepo [--cron ""] ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Schedule a search (smoke)" overflow="wrap" %} ```powershell .\slabapcli.exe search_testrepo run --pipeline --testrepo [--cron ''] ``` {% endcode %} {% endtab %} {% endtabs %} | 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. | {% hint style="info" %} **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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/search-test-repositories.md). Adapter pages also embed the shared TTI search include for recurring schedule guidance. {% endhint %} If search fails, check server and adapter logs — [Configuration settings — Log locations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md#log-locations) and [Troubleshooting](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/troubleshooting-the-abap-agent.md). {% endstep %} {% endstepper %} ## 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 `. | | `setup status` fails | Fix SeaLights token, RFC destinations, SAP authorizations, and SCMON before starting the server. See [Validate Your Setup](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/validate-your-setup.md). | | `search_testrepo` finds nothing | Confirm every `testrepo set` for the pipeline is done. If you just changed config, verify it reloaded — see [Configuration Settings](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md). Check adapter logs under [Log locations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md#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 (`" "`). 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca-cloud/run-a-test-in-tosca-cloud.md). | For deeper diagnosis, see [Troubleshooting the ABAP Agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/troubleshooting-the-abap-agent.md). ## Done with Part 1 Continue to [Show the value with Test Cycles](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/show-the-value-with-test-cycles.md) to import transports, open a Test Cycle, and demonstrate recommendations, gaps, and change coverage. ## Related reading * [SAP objects support](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/concepts/sap-objects-support.md) * [Test Tool Integrations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations.md) * [Fiori support](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/fiori-support.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 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/guides/setup-and-installation.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.