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

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.

Syntax (QAS and PRD systems)
slabapcli.exe pipeline set --appname <app> --qas <rfc> --prd <rfc> [--name <name>] [--labid <labid>]
Syntax (QAS and DEV systems)
slabapcli.exe pipeline set --appname <app> --qas <rfc> --dev <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 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 <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).

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.

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"

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:

Example: Create a pipeline using a DEV system

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.

List Pipelines

The pipeline list command lists the details for each of your Pipelines.

This command takes no parameters.

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.

Example

Last updated

Was this helpful?