Configuration settings
This section describes the SeaLights ABAP Agent’s configuration settings, stored in the <SLABAPAgent dir>\config\config.toml file. You can edit some of these settings as described below by modifying this file directly.
Configuration file sections
The <SLABAPAgent dir>\config\config.toml file has the following sections:
[settings]
This section stores the command-line interface’s installation settings. It has the following fields:
userdata
The name of the ABAP Agent’s userdata directory.
install
The path of the bin, config and userdata directories to the install directory.
key
Used for encryption. This field should be empty if there is no encryption.
iv
Used for encryption. This field should be empty if there is no encryption.
You can modify the userdata and install fields if you want to rename the userdata directory or change the location of the bin, config and userdata directories. Do not modify the key or iv fields.
[[rfc]]
These sections store the details for each of your RFC Destinations. They have the following fields:
name
The name of the RFC Destination.
router
The router string used for the connection.
hostname
The hostname of the SAP server.
sysnr
The system number used for the connection.
client
The client number used for the connection.
username
The username used for the connection.
password
The password used for the connection.
cachedusage
Indicates whether usage data is cached for this RFC Destination.
You can rename an RFC Destination by modifying its name field. However, you’ll also need to update each of [[Pipelines]] sections to use the new RFC Destination name.
Do not modify the username and password fields. These values are encrypted.
If you modify the connection details for an RFC Destination, you don’t need to rerun the command-line interface’s Initial Build Map or Build Modification commands. However, you will need to recreate any Footprints task that use the RFC Destination.
Run:
PS C:\apps\SLABAPAgent\bin> .\slabapcli.exe footprints stop –pipeline <Pipeline name>… to stop the collection of Footprints data for a Pipeline, and:
PS C:\apps\SLABAPAgent\bin>.\slabapcli.exe footprints run –pipeline <Pipeline name>… to restart the collection of Footprints data.
[rfcdata.prd]
These section defines how data is retrieved from each PRD system. They have the following fields:
retentionperiod (N)
The Agent retains the most recent N months of data from each PRD system.
typequeries
The queries used to retrieve data from each PRD system.
separators
The field separators used when retrieving usage data from the PRD system.
mnemonicfieldtokens
The mnemonic field tokens used when retrieving usage data from the PRD system.
descriptionfieldtokens
The description field tokens used when retrieving usage data from the PRD system.
stepfieldtokens
The step field tokens used when retrieving usage data from the PRD system.
You can modify the retentionperiod and separators fields as required. Don’t modify the other fields unless Tricentis support asks you to.
[rfcdata.qas]
This section defines how data is retrieved from the PRD system. They have the following fields:
retentionperiod (N)
The Agent retains the most recent N months of data from each QAS system.
tables
The SAP table from which to retrieve SCMON data.
You can modify the retentionperiod field as required. Don’t modify the tables field unless Tricentis support asks you to.
[[pipeline]]
These sections store details for each of your Pipelines. They have the following fields:
name
The name of the Pipeline.
qas
The Pipeline’s QAS RFC Destination.
prd
The Pipeline’s PRD RFC Destination.
labid
The Tosca lab ID to be associated with this Pipeline.
If you modify the connection details for a Pipeline, you don’t need to rerun the command-line interface’s Initial Build Map or Build Modification commands. However, you will need to recreate any Footprints task that use the Pipeline.
Run:
PS C:\apps\SLABAPAgent\bin> .\slabapcli.exe footprints stop –pipeline <Pipeline name>… to stop the collection of Footprints data for a Pipeline, and:
PS C:\apps\SLABAPAgent\bin>.\slabapcli.exe footprints run –pipeline <Pipeline name>… to restart the collection of Footprints data.
[logging]
This section defines the ABAP Agent’s logging settings. It has the following fields:
level
The logging level.
flushinterval
The interval in seconds after which logging messages are written to the log files (optional).
flushlevel
The logging flush level (optional). If you don’t set this field, the Agent uses info as the default value.
consolelevel
The logging console level (optional). If you don’t set this field, the Agent uses info as the default value.
You can modify any of these settings as required. The …level fields may have the following values:
trace
The Agent logs detailed trace information (where available).
debug
The Agent logs detailed debug details.
info
The Agent logs information details.
warning
The Agent logs warning details.
error
The Agent logs error details.
critical
The Agent logs critical messages.
off
The Agent logs no messages.
[sealights]
This section defines how the ABAP Agent communicates with SeaLights.
token
The SeaLights bearer token.
delaybetweenmods
The time in seconds after which each Build Modification is sent to SeaLights. If you don’t set this field, the Agent uses 300 as the default value.
clientattempts
The number of attempts the Agent makes at calling the SeaLights REST_API method. If you don’t set this field, the Agent uses 5 as the default value.
You can modify the delaybetweenmods and clientattempts fields as required. Do not modify the token field. This value is encrypted.
[footprints]
This section defines how the ABAP Agent processes Footprints data. It has the following fields:
readstartdate
Not used.
readstarttime
Not used.
readtime
Not used.
labid
The lab ID for which to process Footprints data.
testexecutionqueryingfreq
The frequency in seconds with which SeaLights checks Tosca to find new test executions.
You can modify the labid and testexecutionqueryingfreq fields as required. Do not modify the other fields.
Last updated
Was this helpful?