> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/setup-and-configuration/command-line-interface/create-and-list-pipelines.md). # Create & List Pipelines ## Create a Pipeline A Pipeline identifies a QAS (or DEV) and Production system in your SAP landscape, and links them to a SeaLights application. {% hint style="warning" %} **Prerequisites:** The RFC Destinations for both systems (QAS or DEV, and Production) must already exist. See [Create, Test & List RFC Destinations](broken://pages/zPfkH57Cxw3SCdFvArqI). If you omit `--labid`, the command also connects to the QAS (or DEV) system to derive the lab ID, so that system must be reachable. {% endhint %} ### `slabapcli pipeline set` 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 (QAS and PRD systems)" overflow="wrap" %} ```batch slabapcli.exe pipeline set --appname --qas --prd [--name ] [--labid ] [--use-addon true|false] ``` {% endcode %} {% code title="Syntax (DEV and PRD systems)" overflow="wrap" %} ```batch slabapcli.exe pipeline set --appname --dev --prd [--name ] [--labid ] [--use-addon true|false] ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Syntax (QAS and PRD systems)" overflow="wrap" %} ```powershell .\slabapcli.exe pipeline set --appname --qas --prd [--name ] [--labid ] [--use-addon true|false] ``` {% endcode %} {% code title="Syntax (DEV and PRD systems)" overflow="wrap" %} ```powershell .\slabapcli.exe pipeline set --appname --dev --prd [--name ] [--labid ] [--use-addon true|false] ``` {% endcode %} {% endtab %} {% endtabs %} | Parameter | Short flag | Required | Description | | ------------- | ---------- | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `--appname` | `-a` | Yes | The SeaLights application name to associate with this pipeline. | | `--qas` | `-q` | One of `--qas` or `--dev` | The QAS RFC Destination name. | | `--dev` | `-d` | 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` | `-p` | Yes | The PRD RFC Destination name. | | `--name` | `-n` | 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 | Leave unset so the agent derives the lab ID automatically as ` ` (for example, `S21 sapqas01.customer.com`). Do not set this unless you have a specific reason to override. | | `--use-addon` | — | No | `true` or `false`. Selects how the agent reads Production usage data (ST03) for this pipeline: `false` uses a standard SAP function module and needs no SeaLights add-on on the Production system; `true` uses the SeaLights add-on, which must be installed on Production. The Production RFC user needs the authorizations for the chosen setting ([without](broken://pages/JfFkO1xqq9huG22WXqhI#prd-without-add-on) or [with](broken://pages/JfFkO1xqq9huG22WXqhI#prd-with-add-on) the add-on). If omitted, a new pipeline uses `false` and an existing pipeline keeps its saved value. Pipelines that share the same `--prd` must use the same value, otherwise the command fails. See [Production usage data source](broken://pages/DZM4uWEu5r51kMDWCmDB#production-usage-data-source). | {% 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: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml Pipeline 'ALM_Demo-S21' has been created in 'C:\ProgramData\Tricentis\SeaLights\ABAP Agent\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`. When you update a pipeline without `--labid`, the lab ID is derived again, which replaces a custom lab ID. Pass `--labid` again to keep it. {% 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 sapqas01.customer.com" useaddon = false 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 sapqas01.customer.com" useaddon = false disablesetref = false ``` {% endcode %} ## List Pipelines To list the Pipelines defined in your `config.toml` file, run the following from your PowerShell window: ### `slabapcli pipeline list` Lists all pipelines defined in your `config.toml` file. The pipeline `name` is the identifier you use when running `buildmap`, `buildmods`, and `footprints` commands. {% tabs %} {% tab title="Command Prompt" %} {% code title="Syntax" overflow="wrap" %} ```batch slabapcli.exe pipeline list ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Syntax" overflow="wrap" %} ```powershell .\slabapcli.exe pipeline list ``` {% endcode %} {% endtab %} {% endtabs %} This command takes no parameters. #### Example {% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %} ```log .\slabapcli.exe pipeline list [2026-03-08 10:58:38.376+02:00] [info] Detected Windows version: Windows 11 [2026-03-08 10:58:38.377+02:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml appname : ALM_Demo name : ALM_Demo-S21 qas : S21 prd : S23 labid : S21 sapqas01.customer.com disablesetref : false useaddon : false Use the pipeline name 'ALM_Demo-S21' with the buildmap, footprints, and buildmods commands. appname : ALM_Demo name : ALM_Demo-S22 dev : S22 prd : S23 labid : S22 sapdev01.customer.com disablesetref : false useaddon : false Use the pipeline name 'ALM_Demo-S22' with the buildmap, footprints, and buildmods commands. ``` {% endcode %} The `useaddon` line shows whether the pipeline reads Production usage data through the SeaLights add-on. See [Production usage data source](broken://pages/DZM4uWEu5r51kMDWCmDB#production-usage-data-source). For a pipeline created with `--dev`, the source system is listed as `dev` instead of `qas`.