Configuration settings
This section describes the ABAP Agent 2.0 configuration settings, stored in config.toml.
Default location:
%ProgramData%\Tricentis\SeaLights\ABAP Agent\config\config.tomlBack up the config.toml file before you make any changes.
The config.toml file uses the TOML format. It is created automatically when you run slabapcli setup install. On a default Windows install, secrets (token, passwords) are encrypted at rest using AES, keyed by the key and iv values written to the [settings] section during installation.
Schema version: The current schema version is 4. If you have a legacy configuration from an older agent version, run slabapcli setup migrate to upgrade it to version 4 automatically. See Migrate a legacy configuration.
Live reload and restart-required fields
While SLABAPServer.exe is running, the server lazily reloads config.toml on the next configuration access (for example a process API call, a token lookup, an RFC/pipeline/test-repository lookup, or GET /ready). Reload is driven by file change detection on that access — it is not an idle file-system watcher and is not instantaneous while the server is idle.
Hot fields (everything not listed as cold below) apply from the newly loaded file after a successful reload. No server restart is required. Examples include
sealights.token,server.logging.defaultLevel,server.uploadBatching.*, and the entire[[rfc]],[[pipeline]], and[[testrepo]]trees.Cold fields stay at the values captured when the server process started until you restart
SLABAPServer.exe. If a reload finds a cold-field change, hot fields from that edit still apply, but/readyreturns503withreasonCode: CONFIG_RESTART_REQUIREDandchangedColdPaths. Process APIs continue to accept work — this signal means a restart is required to apply the cold values, not that the server has stopped accepting tasks.Mixed edits: change hot and cold fields in one save → hot values apply; cold values remain at the startup baseline until restart. Reverting cold fields to their startup values clears the restart-required condition.
Failed reload: if the new TOML is invalid or unreadable, the server keeps its last-known-good configuration, logs the reload failure, and retries on a later configuration access. Correct the file and check
/ready(or another config-using operation). Restart is not the default remedy for a failed reload.In-flight work: after a hot change to RFC, pipeline, credential, logging, or similar context that an already-running footprint or other scheduled task may already be using, stop and start that task as needed (
footprints stop/footprints run, and similar). That is a task restart — not a restart ofSLABAPServer.exe.
Cold fields (server restart required)
version
Schema generation; use slabapcli setup migrate to change it.
settings.userdata, settings.install
Agent path layout.
settings.key, settings.iv
Encryption material. Public /ready may show these as settings.<redacted>.
server.port
Listen port (process already bound).
server.retry.maxAttempts, initialDelayMs, maxDelayMs, backoffMultiplier, retryOnTimeout
Internal retry host settings.
server.seaLightsClient.timeoutSeconds
SeaLights HTTP client timeout.
server.uploadClient.timeoutSeconds
Upload HTTP client timeout.
server.uploadRetry.enabled, scanIntervalSeconds, maxConcurrentUploads
Upload-retry host enablement / scan / concurrency.
http.disableSslCheck
TLS verification flag.
Each cold field is also marked with Reload behavior: Restart required in the reference tables below. That per-field annotation is authoritative; this summary is for scanning.
Legitimate server restarts still apply for cold-field changes, upgrades, and other process-lifecycle events. Do not restart the server after routine hot changes such as RFC, pipeline, test-repository, token, or secret updates.
Configuration file sections
version
The root key that identifies the configuration schema version. The current supported version is 4.
Do not modify this value manually. Use slabapcli setup migrate to upgrade older configurations. The CLI refuses to start with a config version below 4 and prints a migration hint.
Reload behavior: Restart required. Migration remains the supported way to change version.
[settings]
Stores the agent's installation paths and encryption keys. This section is written by slabapcli setup install.
install
Path to the directory that contains the bin, config, and userdata subdirectories. Set by setup install to the current working directory.
Restart required
userdata
Path to the ABAP Agent's user-data directory. Default: C:\ProgramData\Tricentis\SeaLights\ABAP Agent.
Restart required
key
Encryption key used to protect secrets. Written during setup install.
Restart required
iv
Encryption initialisation vector. Written during setup install.
Restart required
You may modify userdata and install if you need to relocate the agent directories. Do not modify key or iv — these values are managed by the encryption subsystem.
[logging]
Defines the agent's C++ component logging settings.
level
The minimum logging level. Default: info.
flushinterval
(Optional) Interval in seconds after which log messages are flushed to disk.
flushlevel
(Optional) Log level that triggers an immediate flush. Default: info.
consolelevel
(Optional) Minimum level for console output. Default: info.
retentionperiod
(Optional) Number of days to retain log files before deletion.
Valid level values:
trace
Detailed trace information.
debug
Detailed debug information.
info
Informational messages (default).
warning
Warnings only.
error
Errors only.
critical
Critical messages only.
off
No logging.
Reload behavior: Hot for the server configuration snapshot. Already-running watcher / scheduled-task processes that read C++ [logging].level at their own start still need a task restart to pick up a new level.
[sealights]
Defines how the agent communicates with the SeaLights platform.
token
The SeaLights bearer token. Encrypted on disk. Set via slabapcli sealights set.
delaybetweenmods
(Optional) Seconds between Build Modification uploads. Default: 300.
clientattempts
(Optional) Number of retry attempts for SeaLights REST API calls. Default: 5.
Do not modify the token field directly — it is encrypted. Use slabapcli sealights set to update the token. You may modify delaybetweenmods and clientattempts as needed.
Reload behavior: Hot — token, delaybetweenmods, and clientattempts apply on the next successful reload without restarting SLABAPServer.exe.
The delaybetweenmods (300) and clientattempts (5) values are runtime defaults applied when the key is omitted — they are not written into the config.toml template that setup install generates. Add the keys explicitly only if you need non-default values.
Environment variable override: Set SL_AGENT_TOKEN to override the token value at runtime without modifying config.toml. The environment variable takes precedence over the token field. See Environment variable overrides.
[proxy]
Optional. Defines the HTTP proxy the agent uses to connect to SeaLights. If this section is present, the server field is required.
The agent evaluates proxy settings in the following order of priority:
Environment variables (highest priority):
SL_PROXY_SERVERorSL_PROXY— proxy server URISL_PROXY_USERNAME— proxy username (optional)SL_PROXY_PASSWORD— proxy password (optional)
Configuration file — the
[proxy]section inconfig.toml
If neither is configured, the agent connects directly without a proxy.
[http]
disableSslCheck
Disables TLS certificate verification on HTTPS calls. Default: false. Set to true only in trusted internal environments.
Restart required
[server]
Controls the ABAP Agent server (SLABAPServer.exe). Only the cold fields marked below require a server restart; other [server] settings are hot and apply on the next successful reload.
port
The TCP port the server listens on. Default: 17500. Must match the port used by slabapcli when communicating with the server.
Restart required
The server always binds to the loopback address 127.0.0.1 (localhost only); the bind host is not configurable. Only the port can be changed.
[server.retry]
Retry policy for internal server-to-agent calls. All fields in this subsection are cold.
maxAttempts
Maximum number of attempts. Default: 3.
Restart required
initialDelayMs
Initial retry delay in milliseconds. Default: 1000.
Restart required
maxDelayMs
Maximum retry delay in milliseconds. Default: 30000.
Restart required
backoffMultiplier
Exponential back-off multiplier. Default: 2.0.
Restart required
retryOnTimeout
Whether to retry when a call times out. Default: true.
Restart required
[server.tokenValidation]
timeoutSeconds
Timeout in seconds for token validation requests. Default: 10.
Hot (no server restart)
[server.logging]
defaultLevel
Minimum log level for the server (.NET component). Default: info.
Hot (no server restart)
[server.seaLightsClient]
timeoutSeconds
HTTP timeout in seconds for the SeaLights API client. Default: 100.
Restart required
[server.uploadClient]
timeoutSeconds
HTTP timeout in seconds for upload (presigned URL) requests. Default: 600.
Restart required
[server.uploadRetry]
Background retry of failed test-repository uploads. Cold fields control host enablement, scan interval, and concurrency; the backoff / attempt policy fields are hot.
enabled
Whether the background upload-retry service runs. Default: true.
Restart required
scanIntervalSeconds
How often the service scans for failed uploads, in seconds. Default: 60.
Restart required
maxConcurrentUploads
Maximum concurrent retry uploads. Default: 4.
Restart required
minBackoffSeconds
Minimum backoff between retries for a row, in seconds. Default: 30.
Hot (no server restart)
maxBackoffSeconds
Maximum backoff between retries for a row, in seconds. Default: 1800.
Hot (no server restart)
backoffMultiplier
Exponential back-off multiplier for per-row retries. Default: 2.0.
Hot (no server restart)
maxAttempts
Maximum retry attempts per failed upload. 0 means unlimited. Default: 0.
Hot (no server restart)
[server.uploadBatching]
maxGzipBytesPerBatch
Hard cap on compressed SeaLights upload batch body size in bytes. Default: 94371840 (90 MiB).
Hot (no server restart)
[adapters]
Global settings for the adapter host (SLABAPAdapterHost.exe). These apply to all AdapterHost-backed [[testrepo]] types: ado, tosca, toscacloud, excel, xray, qtest, certify, ssm, and alm (OpenText ALM). Per-type connection keys live under [[testrepo]] — see Configure test repositories.
proxyAddress
Proxy server URI used by adapters. Empty = no proxy.
proxyUsername
Proxy username for adapter connections. Optional, encrypted on disk on a secure install.
proxyPassword
Proxy password for adapter connections. Optional, encrypted on disk on a secure install.
proxyDomain
Proxy domain for adapter connections. Optional, encrypted on disk on a secure install.
restClientTimeoutSeconds
HTTP client timeout for adapter REST calls in seconds. Default: 600.
restClientRecycleThreshold
Number of requests after which the HTTP client is recycled. Default: 500.
logLevel
Minimum log level for adapter processes. Default: info.
[adapters.tosca]
scanTestCases
Whether to scan individual test cases during the search. Default: false.
findSAPModules
Whether to search SAP module test cases. Default: true.
findUI5Modules
Whether to search UI5 module test cases. Default: true.
ui5ModuleNames
Array of UI5 module names to include. Default: empty (all).
reusableTestStepBlocksDepth
Depth for traversing reusable test step blocks. Default: 1.
[adapters.toscacloud]
testCasesPageSize
Page size for paginated test case queries. Default: 1000.
minimumSearchTermLength
Minimum length of a search term before it is sent to the adapter. Default: 0.
[adapters.excel]
minimumSearchTermLength
Minimum length of a search term. Default: 0.
[adapters.xray]
minimumSearchTermLength
Minimum length of a search term. Default: 0.
[adapters.qtest]
testCasesPageSize
Page size for paginated test case queries. Default: 1000.
userAgent
User-Agent string sent in HTTP headers. Default: Sealights.
minimumSearchTermLength
Minimum length of a search term. Default: 0.
[rfcdata.prd]
Defines how the agent retrieves usage data from each PRD (Production) system.
retentionperiod
Number of months of usage data the agent retains per PRD system. Default: 13.
typequeries
Array of { type, query } filter entries that exclude matching SCMON context objects from PRD data collection. See the default config for the pre-populated exclusion list.
You may modify retentionperiod as required. Do not modify typequeries unless Tricentis Support asks you to.
[rfcdata.qas]
Defines how the agent retrieves SCMON data from each QAS (Quality Assurance) system.
retentionperiod
Number of months of SCMON data the agent retains per QAS system. Default: 1.
tables
Array of SAP table names from which SCMON data is read. Default: ['SCMON_VDATA'].
You may modify retentionperiod as required. Do not modify tables unless Tricentis Support asks you to.
[rfcdata.phd]
Defines how the agent parses Performance History Data (PHD) exported from SAP transaction ST03.
separators
Field separator characters expected in PHD export files. Default: [",", "|", "\t"].
mnemonicfieldtokens
Column header tokens that identify the "mnemonic" (program/transaction name) column across different SAP locales.
stepsfieldtokens
Column header tokens that identify the "steps/calls" column across different SAP locales.
descriptionfieldtokens
Column header tokens that identify the "description" column across different SAP locales.
Do not modify these fields unless Tricentis Support asks you to.
[componentstoignore]
Optional. Specifies SAP software components (delivery units, DLVUNIT values) to exclude when building the initial build map. Objects belonging to listed components are filtered out during buildmap run.
components
Array of SAP delivery-unit names (DLVUNIT values) to exclude from the build map.
Default exclusion list: If this section is omitted or components is empty, the agent uses the defaults set during setup install: SAP_BASIS, SAP_UI, SAP_GWFND, and PERSONAS. To exclude all components from filtering (include all objects), set components to an explicit empty array [].
See also: Create an initial build map.
[footprints]
Defines how the agent processes Footprints data collected from Tosca test executions.
testexecutionqueryingfreq
Frequency in seconds at which the agent queries the test repository for new test executions. Default: 5.
scmonrecollectionfreqmins
(Optional) How often in minutes the agent re-collects SCMON baseline data. Uses the agent default when not set.
labid
(Optional) The lab ID for which to process Footprints data. Usually set automatically.
typequeries
Array of { type, query } entries that exclude SCMON context objects from footprints collection. See Footprints type queries below.
readstartdate
Deprecated — retained for backward compatibility. Ignored by the agent.
readstarttime
Deprecated — retained for backward compatibility. Ignored by the agent.
readtime
Deprecated — retained for backward compatibility. Ignored by the agent.
You may modify testexecutionqueryingfreq, scmonrecollectionfreqmins, and typequeries as required.
Footprints type queries
The typequeries field lets you exclude specific SCMON context objects from footprints collection based on object type and name pattern. Each entry has a type and a query (glob pattern):
ALL
Any object type
PROG
Programs
TCOD
Transaction codes
FUNC
RFC function modules
ODAT
OData services
Pattern syntax: * matches any sequence of characters, ? matches a single character. Matching is case-insensitive.
If typequeries is empty or not set, no objects are excluded. The agent auto-migrates older configs to include an empty typequeries array.
See also: Collect Footprints data for your Pipeline.
[[rfc]]
Array table. Each [[rfc]] section stores the connection details for one RFC Destination. RFC Destinations are created and managed with slabapcli rfc set.
name
The name of the RFC Destination. Used as the identifier in [[pipeline]] entries.
hostname
The SAP server hostname or IP address.
sysnr
The SAP system number (two-digit string, e.g. "00").
client
The SAP client number (three-digit string, e.g. "100").
language
The SAP logon language (e.g. "EN").
username
The SLUSER account name. Encrypted on disk.
password
The SLUSER account password. Encrypted on disk.
router
(Optional) SAP router string for the connection.
cachedusage
Whether usage data is cached for this RFC Destination. Managed by rfc set.
cachedprdrfc
Effective PRD RFC name used when cachedusage is true. Added automatically in schema version 4. Do not edit manually.
maxretries
(Optional) Maximum number of RFC connection retries.
retrieswait
(Optional) Seconds to wait between RFC connection retries.
You may rename an RFC Destination by modifying its name field. If you do, also update the matching references in all [[pipeline]] sections.
Do not modify the username, password, or cachedprdrfc fields directly. These values are managed by the CLI.
Reload behavior: [[rfc]] is hot — no server restart is required after a successful reload. You do not need to rerun buildmap or buildmods. If an active footprints (or other scheduled) task may already be using the old connection context, stop and start that task as needed (footprints stop followed by footprints run).
[[pipeline]]
Array table. Each [[pipeline]] section stores the configuration for one Pipeline. Pipelines are created and managed with slabapcli pipeline set.
appname
The SeaLights application name associated with this pipeline. Set by pipeline set --appname.
name
The pipeline identifier used by buildmap, buildmods, footprints, and testrepo commands. Auto-generated as <appname>-<qas> if not set explicitly via --name.
qas
The QAS RFC Destination name for this pipeline. Mutually exclusive with dev.
dev
(Alternative to qas) The DEV RFC Destination name when the source system is a DEV system. Mutually exclusive with qas.
prd
The PRD RFC Destination name for this pipeline.
labid
The SeaLights lab ID for this pipeline. Leave unset so the agent derives it as <QAS SID> <QAS hostname> (matches the QAS branch name). Do not override casually.
disablesetref
(Optional) Boolean. When true, disables the set-ref step for this pipeline. Managed by CLI only — do not edit directly.
Leave --labid unset when you create a pipeline. The agent derives the lab ID automatically so it matches the QAS branch name: "<SID> <ashost>" (for example, S21 vwsvtstsap13.tricentis.com).
Overriding --labid casually breaks Test Cycles in SeaLights.
The auto-derived lab ID is what SeaLights uses for Test Cycles and Footprints. Only override --labid when you deliberately need a different lab ID and understand the Test Cycle impact.
Reload behavior: [[pipeline]] is hot — no server restart is required after a successful reload. You do not need to rerun buildmap or buildmods. If an active footprints (or other scheduled) task may already be using the old pipeline/RFC context, stop and start that task as needed.
[[testrepo]]
Array table. Each [[testrepo]] section stores the configuration for one test repository adapter. Test repositories are created and managed with slabapcli testrepo set.
name
Unique name for this test repository entry.
type
Adapter type: ado, tosca, toscacloud, excel, xray, qtest, certify, ssm, or alm (OpenText ALM).
pipeline
The pipeline name this test repository is linked to.
searchpaths
(Optional) Array of repository or filesystem paths to scope the adapter search. Stored as a sibling key directly under [[testrepo]], not in [testrepo.settings].
teststage
(Optional) SeaLights test stage used when the agent uploads results for this test repository (unless a REST upload override supplies a stage). Top-level sibling of searchpaths — not a [testrepo.settings] key and not a CLI --setting. Direct TOML edits use teststage; the CLI flag is --test-stage. When omitted, the effective default is "{type} Tests" (for example qtest Tests or ado Tests).
Adapter-specific connection settings are stored in the [testrepo.settings] subtable. The keys depend on the adapter type — see Configure test repositories for the full per-adapter key reference, and the matching Test Tool Integrations page for type-specific examples.
Config-only editing paths for [[testrepo]]
testrepo set replaces settings on every call. Running slabapcli testrepo set replaces the entire [testrepo.settings] block, searchpaths, and teststage on every invocation. Any key you omit is cleared — omitting --test-stage clears a previously stored teststage.
To make a partial change without re-entering all settings, edit config.toml directly. [[testrepo]] is hot — the next server configuration access uses the valid saved configuration without restarting SLABAPServer.exe. Optionally confirm readiness with GET /ready or re-run testrepo test.
Two categories of testrepo parameters can only be set by editing config.toml directly:
Secrets — credential fields are never accepted via
--setting. They are entered interactively duringtestrepo set(input is hidden). To change a secret without re-running the full command, use the interactivesetcommands, or edit the field directly inconfig.tomlwhen it is stored as plaintext (keyandivin[settings]are empty). No server restart is required after a successful reload; if a scheduled task may already hold the prior credentials, stop and start that task as needed.AdapterSecret fieldsqtestusername,passwordtoscausername+passwordorapikey+apisecrettoscacloudclientId,clientSecretexcel(none)
xray(none)
adopassword(Azure DevOps Personal Access Token)certifyusername,password(optional — leave blank for Windows Integrated Authentication)ssmusername,passwordalmusername+passwordorapikey+apisecret(OpenText ALM)Partial updates to optional fields — because
testrepo setreplaces the whole settings block, editing an optional key (e.g.workstates,bufferPatterns,confidenceThreshold) without re-supplying all other keys requires a directconfig.tomledit. The change applies on the next successful reload; no server restart is required.
Environment variable overrides
The following environment variables override the corresponding config.toml settings at runtime. They do not modify the file on disk.
SL_ABAP_SERVER_CONFIG_PATH
Config file path
Server (SLABAPServer.exe) resolution order: this env var → %ProgramData%\…\config\config.toml → {exe}\..\config → ancestor walk.
SL_AGENT_TOKEN
[sealights].token
Server only. Takes precedence over the encrypted token in config.toml.
SL_PROXY_SERVER or SL_PROXY
[proxy].server
C++ CLI and watcher. Takes precedence over the [proxy] section.
SL_PROXY_USERNAME
[proxy].username
C++ CLI and watcher.
SL_PROXY_PASSWORD
[proxy].password
C++ CLI and watcher.
Database locations
All agent databases and artifacts are stored under the userdata directory (default: %ProgramData%\Tricentis\SeaLights\ABAP Agent). This is a change from ABAP Agent 1.x, where databases lived in the install directory.
The directory has two subtrees:
private\— SQLite databases and generated artifacts (agent-internal; encrypted where applicable)public\— Logs and shared output
Database path reference
The following table lists every database file managed by the agent. All paths are relative to the userdata root.
Process state
private\Processes.db
Server startup
ProcessDatabaseOptions.cs
SAP tables cache
private\SapTables\{rfc}\tables_cache.db
buildmap run
pathResolver.cpp
Common pipeline data
private\common\{pipeline}\common.db
buildmap run
pathResolver.cpp
Links (impacted set)
private\Links\{rfc}\{pipeline}\{run}\links.db
Server (link computation)
pathResolver.cpp
Impacted graph
private\Graph\{rfc}\{pipeline}\{run}\impacted_graph.db
Server (upload)
pathResolver.cpp
Build modifications
private\BuildModifications\{rfc}\{pipeline}\{run}\discovered_transports.db
buildmods run
pathResolver.cpp
Build map
private\BuildMapping\{pipeline}\data.db
buildmap run
dbStrings.h (BUILDMAPPING_DIR)
Performance history (PHD)
private\PerfHist\{RFC}_PHD.db
rfc phd
pathResolver.cpp
FLPCA data
private\flpca\{rfc-lowercase}.db
upload_flpca import
FlpcaDatabaseOptions.cs
Path variable key:
{rfc}
RFC Destination name (as configured in [[rfc]].name; case as stored)
{rfc-lowercase}
RFC Destination name lowercased (e.g. S21 → s21)
{RFC}
RFC Destination name uppercased as used by the PHD naming convention (e.g. S21_PHD.db)
{pipeline}
Pipeline effective name (as stored in [[pipeline]].name)
{run}
Run identifier (timestamp-based, generated per execution)
When key and iv in [settings] are empty, config.toml and the SQLite databases are stored without encryption at rest, so their contents can be inspected directly for troubleshooting.
Log locations
Most agent logs are written under the public\ subtree of the userdata directory (default: %ProgramData%\Tricentis\SeaLights\ABAP Agent). For server-backed failures (Initial Build Map, Refresh Links, test-repository search/test, and similar), start with the server per-task folders below. The CLI itself does not write a log file — it logs to the console only. Symptom → log guidance: Troubleshooting — Server task logs.
Server per-task log
public\logs\{taskType}\{yyyy-MM-dd}\{processId}\{processId}.log
Native CAPI agent (per server task)
Same task folder: agent.log
Adapter host (SLABAPAdapterHost.exe)
Same task folder: {processId}_adapter.log
Server (SLABAPServer.exe) daily host log
public\logs\server-YYYYMMDD.log (Serilog daily roll)
Pipeline watcher actions (summaries / watcher-local)
public\Logs\{pipeline}\InitialBuildMapping_YYYY-MM-DD.log, BuildMods_YYYY-MM-DD.log, RefreshLinks_YYYY-MM-DD.log, Footprints_YYYY-MM-DD.log (spdlog daily rotation)
Watcher bootstrap (main_logger)
%ProgramData%\Tricentis\SeaLights\ABAP Agent\public\Logs\watcher\main_logger_<timestamp>_<pid>.log (always ProgramData)
Log purger (purgeLogs.exe)
public\Logs\purger_YYYY-MM-DD.log
CLI (slabapcli.exe)
Console only (stdout/stderr); no log file
C++ components use capital Logs; the .NET server and AdapterHost use lowercase logs. On Windows these resolve to the same folder. Relocating [settings].userdata moves userdata-relative logs; the watcher bootstrap logger stays under ProgramData.
Per-task log layout
When the server runs a background task (initial build map stages, test-repository search/test, and similar), it creates a dedicated folder and log file:
{taskType}— Task kind (see tables below).{yyyy-MM-dd}— UTC date when the task log directory was created.{processId}— Unique ID for that server process/run (see below).
Native CAPI work for that task also writes agent.log in the same folder. For adapter work (test-repository search or connection test), SLABAPAdapterHost.exe writes a sibling file:
{processId}.log
Server (SLABAPServer.exe)
[server.logging].defaultLevel
agent.log
Native CAPI (slabap.agent.dll)
[logging]
{processId}_adapter.log
Adapter host (SLABAPAdapterHost.exe)
[adapters].logLevel
These levels are independent. Raise [adapters].logLevel when diagnosing Tosca/qTest/Excel (and other adapter) connectivity; raise [server.logging].defaultLevel when diagnosing server orchestration; use [logging] for watcher and native CAPI verbosity.
What processId is
processId is the server's identifier for one task run — a short opaque string (typically 12 hexadecimal characters) assigned when the process starts. It is not the Windows OS process ID (PID).
Use it to open the correct per-task folder under public\logs\. Ways to find it:
Server daily log —
public\logs\server-YYYYMMDD.loglines for the task include theprocessId.Folder name — Under
public\logs\{taskType}\{yyyy-MM-dd}\, each subdirectory name is aprocessId.Task / CLI output — Watcher and CLI output for server-backed work (build map stages,
testrepo test,search_testrepo, and similar) surface theprocessIdwhen the server starts or reports the process.Inside the log lines — Server task logs include
[ProcessId]in each line; the adapter log also logsprocessIdat startup.
Initial build map (taskType folders)
An initial build map runs as six server stages orchestrated by the watcher. Each stage has its own taskType directory under public\logs\:
Stage order
taskType folder
1
generate_cache
2
sync_phd
3
generate_common
4
generate_links
5
generate_graph
6
generate_buildmap
For what each stage does and how long IBM can take, see Create an Initial Build Map for your Pipeline. The watcher also writes a pipeline-level daily log at public\Logs\{pipeline}\InitialBuildMapping_YYYY-MM-DD.log.
REFRESH_LINKS reuses four of these taskType folders — generate_cache, sync_phd, generate_links, and generate_graph — and writes a pipeline-level daily log at public\Logs\{pipeline}\RefreshLinks_YYYY-MM-DD.log. See Refresh links and impacted graph.
Scheduled Build Modifications and Footprints are watcher-local: they write only the pipeline daily logs (BuildMods_YYYY-MM-DD.log, Footprints_YYYY-MM-DD.log) and do not create server taskType folders.
Adapter-related taskType folders
taskType
Typical trigger
search_testrepo
Test-repository search (recommended tests / coverage capture flows)
test_testrepo
slabapcli testrepo test (and auto-test after testrepo set when the server is up)
Both produce {processId}.log (server) and, when the adapter host runs, {processId}_adapter.log in the same folder.
Last updated
Was this helpful?