SOT
    • Introduction
    • User manual
      • Basic operation
        • Create and delete a device as a favorite
        • Use the filter function
      • Process
        • Compare processes
        • Change axes in the diagram
        • Show and hide axis in the diagram
        • Show special values
        • Display measured values in the diagram
        • Display process data in the diagram
        • Displaying diagram content
        • Permanently highlight a process curve
        • Temporarily highlight a process curve
        • Monitoring processes
        • Configure columns
        • Export process data
    • Operations manual
      • Overview
      • System architecture and interfaces
      • System requirements
        • trinity/static-content
        • trinity/trinity-core-service
        • trinity/trinity-gateway-service
      • Migration from previous versions
        • Influx database migration
        • Deletion of an old CPM installation
      • Setup and configuration
        • AI add-on: Process Intelligence
        • Database configuration
        • Port configuration
        • HELM configuration
        • Application account roles provided
        • Relational database
        • General logging
        • General OpenTelemetry
        • trinity/static-content
        • trinity/trinity-core-service
        • trinity/trinity-gateway-service
      • Start and shutdown
      • Regular operations
      • Failure handling
        • Processes are not received
        • Module is not visible in the Web Portal
        • How to verify if the broker is out of sync
        • Devices are missing
      • Backup and restore
      • Logging and monitoring
        • Observability
        • Logging characteristics
        • Logging format
        • Logging level
        • Required monitoring
        • Request-based logging format
        • Security logging format
        • Lifecycle logging format
        • Health verification endpoints
      • Known limitations
    • API documentation
Process Quality
  • Smart Operations Toolkit
    • Deviation Processor
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Process Quality
    • AI Services
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
  • Enterprise & Shopfloor Integration
    • Information Router
    • Master Data Management

SOT Learning Portal

  • Process Quality
  • Operations manual
  • Setup and configuration
  • trinity/trinity-core-service

trinity/trinity-core-service

Variable Name Required Description Defaults to

TRN_MAX_DB_CONNECTION_LIFETIME

If maxLifetime is configured, create a future End-of-life task with 2.5% variance from the maxLifetime time to ensure there is no massive die-off of Connections in the pool.

110000 ms (110s) which is lower than the AzureSQL default (which is 120s).

DATABASE_VALIDATION_QUERY

Defines the query used to validate the connection to the database.

SELECT 1

RELATIONAL_DB_BATCH_MAX_SIZE

The maximum number records that are to a batch in one transaction before persisting in the database.

10

MACMA_URL

The URL of the MACMA installation with protocol host and port.

-

MACMA_PQM_BACKEND_CLIENT_ID

The Client-ID of PQM which is configured in MACMA.

-

MACMA_PQM_FRONTEND_CLIENT_ID

The MACMA frontend client id of PQM

-

MACMA_PQM_BACKEND_CLIENT_SCOPE

The MACMA private client id of PQM

aud:{{NEXEED_PPM_MACMA_CLIENT_ID}}

MACMA_PQM_BACKEND_CLIENT_SECRET

The Client-Secret of PPM which is configured in MACMA (e.g. <uuid>).

-

MACMA_MACMA_BACKEND_CLIENT_SCOPE

aud:{{NEXEED_MACMA_MACMA_CLIENT_ID}}

MACMA_MMPD_BACKEND_CLIENT_SCOPE

aud:{{NEXEED_MMPD_MACMA_CLIENT_ID}}

MACMA_PORTAL_BACKEND_CLIENT_SCOPE

aud:{{NEXEED_PORTAL_MACMA_CLIENT_ID}}

MACMA_DEVIATION_PROCESSOR_BACKEND_CLIENT_SCOPE

aud:{{DEVIATION_PROCESSOR_CLIENT_ID}}

JAVA_CACERT_FILE

Filename including location of the trusted certificate file (cacerts)

/etc/ssl/java/cacerts

JAVA_CACERT_STORE_PASS

Trust store password

changeit

JAVA_CACERT_KEY_PASS

Key password (cannot be different than trust store password)

changeit

JAVA_SERVER_CERT_FILE

Certificate file for server TLS endpoint

server.crt

JAVA_SERVER_KEY_FILE

Key file for server TLS endpoint in /etc/ssl/server

server.key

JAVA_SERVER_KEY_PASS

Optional password for key file in /etc/ssl/server

secret

JAVA_SERVER_CACERT_FILE

Optional additional trusted certificate in /etc/ssl/trusted

-

JAVA_KEYSTORE_FILE

Filename of keystore (relative to certificate volume)

/etc/ssl/java/java.pfx

JAVA_KEYSTORE_PASS

Key store password

changeit

JAVA_TLS_DISABLE

Optionally disable TLS for Java for specific use-cases

false

TRN_PORT

Service Port

9560

TRN_TOKEN_CACHE_ENABLED

Enables or disables the caching of MACMA tokens.

false

TRN_TOKEN_CACHE_TIME_TO_LIVE

Time a token MACMA token is cached.

30s

MAX_PAYLOAD_SIZE_IN_MB

The maximum payload size in MB that trinity-core-service accepts via HTTP. The payload size is taken from the header and does not cover intentional misuse.

5

PROCESS_FILTER_AUTOCOMPLETION_TIME_LIMITATION_IN_DAYS

This parameter adds a time limitation to the database query for reading data, used in the auto-completion. This can be set for improving performance on environments with a high retention configuration.

NE

PROCESS_FILTER_AUTOCOMPLETION_INFLUX_QUERY_LIMIT

This parameter limits the number points when reading data, used in the auto-completion. This can be set for improving performance on environments with a high retention configuration.

-

PROCESS_METADATA_TIME_BASED_CHUNK_HOURS

This parameter controls the chunk size in hours when querying process meta-data from the InfluxDB. This can be set for improving performance on environments with a high retention configuration.

1

INFLUX_OVERWRITE_PROCESSES

Defines if sending a process with the same timestamp again will override an existing process in the database or not.

true

INFLUX_PROCESS_BATCH_NUMBER_ACTIONS

Number of actions when persisting process messages in the InfluxDB. Consult the InfluxDB documentation for more information.

2000

INFLUX_PROCESS_BATCH_BUFFER_LIMIT

Number of the batch buffer limit when persisting process messages in the InfluxDB. Consult the InfluxDB documentation for more information.

5000

RABBITMQ_HOST

ppm-rabbitmq

RABBITMQ_PORT

5672

RABBITMQ_USER

ppm

RABBITMQ_PASSWORD

ppm

RABBITMQ_VHOST

/

RABBITMQ_TLS_ENABLED

false

TRN_AMQP_PREFETCH

Number of AMQP0.9.1 messages to prefetch.

20

TRN_AMQP_NUMBER_OF_CONSUMERS

Number of AMQP consumers.

5

TRN_AMQP_NUMBER_OF_MAX_CONSUMERS

Maximum number of AMQP consumers.

10

DATABASE_DRIVER

-

DATABASE_URL

-

DATABASE_USER

-

DATABASE_PASSWORD

-

TRN_DATASOURCE_MAXIMUM_POOL_SIZE

Maximum pool size for datasource.

5

INFLUX_URL

-

INFLUX_USER

The InfluxDB user that is used by PQM. It’s recommended to inject a lower privileged user and set the retention policy in the database. See INFLUX_PROCESS_RETENTION_POLICY_DURATION and INFLUX_RETENTION_POLICY_REPLICATION for more information.

-

INFLUX_PASSWORD

The InfluxDB password that is used by PQM.

-

INFLUX_DATABASE_NAME

ppm_core

INFLUX_LOG_LEVEL

NE

INFLUX_RETENTION_POLICY_REPLICATION

The attribute of the retention policy that determines how many copies of the data are stored in the cluster. Replicating copies ensures that data is accessible when one or more data nodes are unavailable. InfluxDB replicates data across N data nodes, where N is the replication factor. Note: This property is only considered when PQM creates the database. PQM only creates the database if the database does not exist at the service startup and if the database user has the relevant permissions. Also, this parameter will be considered only ones on database creation time. Changing this configuration at a later point in time needs to be done in the database.

1

INFLUX_PROCESS_RETENTION_POLICY_DURATION

The process retention policy configuration has two responsibilities: . Setting the retention policy. Retention policy is the part of InfluxDB data structure that describes for how long InfluxDB keeps data. Note: The retention policy is only set when PQM creates the database. PQM only creates the database if the database does not exist at the service startup and if the database user has the relevant permissions. Also, this parameter will be considered only ones on database creation time. Changing this configuration at a later point in time needs to be done in the database. . Defines how far into the past processes are searched for. Important: If the retention policy is set in the database, this configuration must also be set to this configuration property. A mismatch between the database configuration and this property negatively impact the system functionality. E.g. processes cannot be found.

14d

MISSING_PERMISSION_RE_CHECK_SCHEDULER_TIME_IN_MIN

This property sets the scheduler interval where a tenant’s MDM master data synchronization is retried after PQM got a missing permission error.

15

ORPHAN_DETECTION_CRITERIA_IN_HOURS

This property defines after what time a stale migration is considered orphan and picked up by the orphan detection scheduler.

3

ORPHAN_DETECTION_SCHEDULER_TIME_IN_MIN

This property sets the scheduler interval to identify and recover orphan synchronizations. This can occur if a service instance is stopped within a synchronization. A recovery will be started ones detected.

30

CORRUPTED_DETECTION_SCHEDULER_TIME_IN_MIN

This property sets the scheduler interval where a tenant’s MDM master data synchronization is retried after PQM detected a corrupted state.

30

DEVIATION_PROCESSOR_ENABLED

This property enables sending deviations to the Deviation Processor Module via HTTP.

true

DEVIATION_PROCESSOR_URL

The URL of the Deviation Processor installation.

-

TRN_ENABLE_REMOTE_PROFILING

Exposes insecure access to the JVM via JMX/RMI. WARNING: This must not be enabled in any case outside the development.

false

TRN_REMOTE_PROFILING_HOSTNAME

The hostname of instance for remote access to the JVM. WARNING: This must not be enabled in any case outside the development.

-

TRN_REMOTE_PROFILING_PORT

The JMX remote port. WARNING: This must not be enabled in any case outside the development.

-

INTELLIGENCE_BATCH_MAX_SIZE

The maximum number of intelligence records that add added to a batch before persisting in the database. This should be aligned with RELATIONAL_DB_BATCH_MAX_SIZE.

10

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2026, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses