> 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/test-tool-integrations/tosca-cloud/connect-tosca-cloud-to-sealights.md).

# Connect Tosca Cloud to SeaLights

Configure the ABAP Agent **`toscacloud`** adapter. For the operational order (footprints → TIA → run), 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 Tosca Commander, see [Connect Tosca Commander to SeaLights](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca/connect-tosca-to-sealights.md).

SeaLights supports Tosca Cloud **1.0**. Product-side SeaLights screens: [SeaLights integration (Tosca Cloud)](https://documentation.tricentis.com/tricentis_cloud/en/content/admin_guide/sealights_integration.htm).

{% hint style="warning" %}
When you create the ABAP pipeline with `pipeline set`, **leave `--labid` unset** unless you deliberately need to override it. The agent derives the default lab ID as `<QAS SID> <QAS RFC hostname>`. Casual overrides can break **Test Cycles** in SeaLights. See [Create and list pipelines](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-and-list-pipelines.md).
{% endhint %}

**SeaLightsLabId** in Tosca Commander or Tosca Cloud must match the **labid** of your ABAP pipeline:

1. On the agent host, run `pipeline list` (no parameters). Syntax and example output: [Create and list pipelines](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-and-list-pipelines.md).
2. In the output, find the block for your pipeline and note the **labid** line (for example, `labid : S21 vwsvtstsap13.tricentis.com`).
3. Set **SeaLightsLabId** on your Tosca execution list, playlist, or configuration parameters to that value (without the `labid` label).

## Configure the `toscacloud` adapter

Create or update a test repository with `slabapcli testrepo set --type toscacloud`.

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

```batch
slabapcli.exe testrepo set --name "toscacloud_repo" --type toscacloud --pipeline "<pipeline>" --setting url=https://my.toscacloudsite.com --setting spaceId=DemoWorkspace --setting scope=tta --test-stage "Regression Tests"
```

{% endcode %}
{% endtab %}

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

```powershell
.\slabapcli.exe testrepo set --name 'toscacloud_repo' --type toscacloud --pipeline '<pipeline>' --setting url=https://my.toscacloudsite.com --setting spaceId=DemoWorkspace --setting scope=tta --test-stage 'Regression Tests'
```

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

`--test-stage` is optional. See [Configure Test Repositories](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/configure-test-repositories.md) for the default `"{type} Tests"` value, clear-on-omit behavior, and duplicate-stage warning.

The CLI prompts for **`clientId`** and **`clientSecret`** (OAuth credentials for the IdentityServer token endpoint).

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

```log
.\slabapcli.exe testrepo set --name 'toscacloud_repo' --type toscacloud --pipeline '<pipeline>' --setting url=https://my.toscacloudsite.com --setting spaceId=DemoWorkspace --setting scope=tta --test-stage 'Regression Tests'
[2026-03-08 10:45:00.123+02:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
Enter clientId: oidc-client-id
Confirm clientId:
Enter clientSecret:
Confirm clientSecret:
Configuration for adapter 'toscacloud_repo' was saved successfully.
Running connection test for 'toscacloud_repo'...
Connection test passed for 'toscacloud_repo' (pipeline: '<pipeline>').
```

{% endcode %}

### `testrepo set` parameters for `toscacloud`

Non-secret keys use `--setting key=value`. Secrets are entered interactively (not via `--setting`). Plus common options (`--name`, `--type`, `--pipeline`, `--test-stage`) — see [Configure Test Repositories](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/configure-test-repositories.md).

| Parameter             | Kind    | Required | Description                                                                                                         |
| --------------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------------- |
| `url`                 | Setting | Yes      | Tosca Cloud REST base URL.                                                                                          |
| `spaceId`             | Setting | Yes      | Workspace / space name (resolved to a GUID at search time).                                                         |
| `scope`               | Setting | Yes      | OAuth scope for the token endpoint (for example `tta`).                                                             |
| `workstates`          | Setting | No       | Comma-separated test case workstates to include; empty = all.                                                       |
| `searchPaths`         | Setting | No       | Comma-separated list that scopes the search to specific paths. Written as top-level `searchpaths` in `config.toml`. |
| `confidenceThreshold` | Setting | No       | Integer 0–100. Minimum confidence for a match.                                                                      |
| `clientId`            | Secret  | Yes      | OIDC / OAuth client ID.                                                                                             |
| `clientSecret`        | Secret  | Yes      | OIDC / OAuth client secret.                                                                                         |

Global defaults: `[adapters.toscacloud]` in [Configuration settings](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md).

### Example `config.toml` shape

```toml
[[testrepo]]
  name = 'toscacloud_repo'
  type = 'toscacloud'
  pipeline = 'my-pipeline'
  teststage = 'Regression Tests'

[testrepo.settings]
  url = 'https://my.toscacloudsite.com'
  spaceId = 'DemoWorkspace'
  scope = 'tta'
  clientId = 'oidc-client-id'
  clientSecret = 'oidc-client-secret'
  workstates = []
```

Once the test repository is configured and the connection test succeeds:

1. Finish any remaining agent setup for the pipeline (RFC, pipeline, additional test repositories) if you have not already.
2. Schedule repository search with `search_testrepo`.
3. Capture coverage with Footprints and your test runs.

For the full setup order, 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) and [Configure Test Repositories](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/configure-test-repositories.md).

`search_testrepo` registers a Windows Scheduled Task that runs `watcher.exe SEARCH_TESTREPO` on a cron schedule.

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

```batch
slabapcli.exe search_testrepo run --pipeline <pipeline> --testrepo <name> [--cron "<cron>"]
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Schedule a search" overflow="wrap" %}

```powershell
.\slabapcli.exe search_testrepo run --pipeline <pipeline> --testrepo <name> [--cron '<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 expression. Default: `0 2 * * 0` (Sunday at 02:00).    |

Full command reference (stop, list, prerequisites): [Search Test Repositories](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/search-test-repositories.md).

## Next step

Follow [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): start footprints, enable TIA, then configure the playlist and run.


---

# 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/test-tool-integrations/tosca-cloud/connect-tosca-cloud-to-sealights.md?ask=<question>&goal=<endgoal>
```

`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.