> 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-1.5/command-line-reference/pipelines.md). # Pipelines A Pipeline identifies a QAS (or DEV) and Production system in your SAP landscape, and links these to a SeaLights application. ## Create a Pipeline The `pipeline set` command lets you create a Pipeline. You can specify either of the following: * A QAS and PRD RFC Destination. * A QAS and DEV RFC Destination. {% tabs %} {% tab title="Command Prompt" %} {% code title="Syntax (QAS and PRD systems)" overflow="wrap" %} ```batch slabapcli.exe pipeline set --appname --qas --prd [--name ] [--labid ] ``` {% endcode %} {% code title="Syntax (QAS and DEV systems)" overflow="wrap" %} ```batch slabapcli.exe pipeline set --appname --qas --dev [--name ] [--labid ] ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Syntax (QAS and PRD systems)" overflow="wrap" %} ```powershell .\slabapcli.exe pipeline set --appname --qas --prd [--name ] [--labid ] ``` {% endcode %} {% code title="Syntax (QAS and DEV systems)" overflow="wrap" %} ```powershell .\slabapcli.exe pipeline set --appname --qas --dev [--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` is required. | The QAS RFC Destination name. | | `--dev` | One of `--qas` or `--dev` is required. | 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" %} **TODO (from v1.5 draft):** The first Syntax heading in the source read "QAS and PRF systems" (corrected to PRD) and the `--prd` parameter description was blank (filled in as "The PRD RFC Destination name."). Please confirm. {% endhint %} 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 {% 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 %} If a Pipeline with the same name exists, the `pipeline set` command updates it and includes `has been updated` instead of `has been created` in its output. This example writes the following to your `config.toml` file: {% code title="config.toml" overflow="wrap" %} ```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 %} If a Pipeline with the same name exists, the `pipeline set` command updates it and includes `has been updated` instead of `has been created` in its output. This example writes the following to your `config.toml` file. Note that the key is stored as `dev`, not `qas`. {% code title="config.toml" overflow="wrap" %} ```toml [[pipeline]] name = "ALM_Demo-S21" appname = "ALM_Demo" dev = "S21" prd = "S23" labid = "S21 vwsvtstsap13.tricentis.com" disablesetref = false ``` {% endcode %} ## List Pipelines The `pipeline list` command lists the details for each of your Pipelines. {% 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. {% hint style="info" %} **TODO (from v1.5 draft):** The source Syntax block showed `rfc list`, and the description read "lists the details for each of your RFC Destinations." Corrected to `pipeline list` / Pipelines — please confirm. {% endhint %} ### 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: ../config/config.toml appname : ALM_Demo name : ALM_Demo-S21 qas : S21 prd : S23 labid : S21 vwsvtstsap13.tricentis.com disablesetref : false Use the pipeline name 'ALM_Demo-S21' with the buildmap, footprints, and buildmods commands. appname : ALM_Demo name : ALM_Demo-S23 qas : S23 prd : S23 labid : S23 vlsvprdsap02.tricentis.com disablesetref : false Use the pipeline name 'ALM_Demo-S23' with the buildmap, footprints, and buildmods commands. ``` {% endcode %} --- # 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-1.5/command-line-reference/pipelines.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.