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

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.

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

Syntax
slabapcli.exe pipeline set --appname <app> --qas <rfc> --prd <rfc> [--name <name>] [--labid <labid>]
Syntax
.\slabapcli.exe pipeline set --appname <app> --qas <rfc> --prd <rfc> [--name <name>] [--labid <labid>]
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

Command
slabapcli.exe pipeline set --appname "ALM_Demo" --qas "S21" --prd "S23"
Command
.\slabapcli.exe pipeline set --appname 'ALM_Demo' --qas 'S21' --prd 'S23'
Expected output (PowerShell)
.\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.

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:

List Pipelines

To list the Pipelines defined in your config.toml file, run the following from your PowerShell window:

Lists all pipelines defined in your config.toml file. The pipeline name is the identifier you use when running buildmap, buildmods, and footprints commands.

This command takes no parameters.

Example

PreviousUpload usage data to an RFC DestinationNextCreate an Initial Build Map for your Pipeline

Last updated

Was this helpful?