Configuration of the helm chart :: Nexeed Learning Portal

Database configuration

The Helm chart of Maintenance Management does export multiple database connections which can be configured (mm.databases.mm and mm.databases.mmc). This split is only due to technical restrictions within the Helm chart and both connections can be configured to point to the same database or schema and can have the same credentials.

Logging configuration

Description	Various log levels can be adjusted to get a better insight into the running container
Required	no
Sources	helm chart local values

The following settings are available:

mm:
  local:
    logging:
      microsoft: WARN # For everything regarding the .NET request pipeline
      quartz: WARN    # For scheduling related topics (task template)
      system: WARN    # For everything regarding the .NET request pipeline
      spring: WARN    # For everything regarding the Spring request pipeline (mm-connector)
      hibernate: WARN # For everything regarding the Spring request pipeline (mm-connector)
      amqp: WARN      # For AMQP communication within mm-connector

Solace configuration

The solace connection is being utilized by the MM-Connector to connect to SAP Systems via AMQP1.0.

`mm.solaceUserName`

Description	The username for accessing the messaging queue to connect to SAP
Required	no
Sources	helm chart exported values

`mm.solacePassword`

Description	The password for accessing the messaging queue to connect to SAP
Required	no
Sources	helm chart exported values

`mm.solaceUrl`

Description	The address of the messaging queue to connect to SAP
Required	no
Sources	helm chart exported values

`mm.solaceIntegrationQueue`

Description	The queue name for events from SAP
Required	no
Sources	helm chart exported values

Notification Settings

Those settings affect how notification events are registered to the IAS Notification Service

`mm.notificationFromAddress`

Description	The sender address for notifications sent by email
Required	no
Sources	helm chart exported values

`mm.notificationType`

Description	The preferred notification type used
Required	no
Sources	helm chart exported values
Default	Push

Indira Settings

Those settings configure the connection to the Indira service

`mm.indiraBaseUrl`

Description	The Indira base URL that is being used in MM Connector
Required	yes
Sources	helm chart exported values

`mm.indiraApiKey`

Description	The Indira API Key that is being used in MM Connector
Required	yes
Sources	helm chart exported values

MM Connector SAP Client Settings

`mm.local.sapClient.maxRetryTimeInSeconds`

Description	The max retry time in seconds for doing SAP calls in MM Connector
Required	no
Sources	helm chart exported values
Default	60

MM Connector INDIRA Sync Settings

`mm.local.indira.numMaterialsPerRequest`

Description	The number of materials that are being requested from Indira in one request during the sparepart synchronization. This value determines the length of the REST API URL to Indira, which is limited by the HTTP protocol. 200 is the current maximum value and can be lowered if the URL is too long.
Required	no
Sources	helm chart exported values
Default	200

`mm.local.indira.maxRetryTimeInSeconds`

Description	The max retry time in seconds for doing Indira sync call for JobUUID in MM Connector
Required	no
Sources	helm chart exported values
Default	60

Open ID configuration

`mm.local.oidc.acl.refreshInterval`

Description	The frequency at which Access Control Lists should be fetched in the background in seconds
Required	no
Sources	helm chart exported values
Default	900

`mm.local.oidc.introspection.enableCaching`

Description	Whether or not the introspection results, which are the results of checking the validity of tokens or access permissions, should be cached.
Required	no
Sources	helm chart exported values
Default	true

`mm.local.oidc.introspection.cachingDuration`

Description	The duration in seconds for which the results of introspection requests are considered valid before they need to be refreshed or revalidated
Required	no
Sources	helm chart exported values
Default	15

OTEL configuration

`observability.enabled`

Description	Specifies whether observability traces and metrics data should be exported using OpenTelemetry.
Required	no
Sources	helm chart exported values

`observability.enableLoggingTelemetry`

Description	Specifies whether observability logging data should be exported using OpenTelemetry.
Required	no
Sources	helm chart exported values

Sync Configuration

`mm.local.sync.macmaSyncOptions.quartzOptions.isEnabled`

Description	Specifies whether the Quartz scheduler for MACMA sync is enabled.
Required	no
Sources	helm chart exported values
Default	true

`mm.local.sync.macmaSyncOptions.quartzOptions.interval`

Description	The interval at which the MACMA sync job should run, in the format `days.hours:minutes:seconds`.
Required	no
Sources	helm chart exported values
Default	"0.00:05:00"

`mm.local.sync.macmaSyncOptions.quartzOptions.fireOnStartup`

Description	Specifies whether the MACMA sync job should run immediately on startup.
Required	no
Sources	helm chart exported values
Default	true

`mm.local.sync.macmaSyncOptions.isRabbitMqEnabled`

Description	Specifies whether RabbitMQ is enabled for MACMA sync.
Required	no
Sources	helm chart exported values
Default	true

`mm.local.sync.macmaSyncOptions.batchSize`

Description	The batch size for MACMA sync operations. Should not exceed 1000.
Required	no
Sources	helm chart exported values
Default	1000

`mm.local.sync.mdmSyncOptions.quartzOptions.isEnabled`

Description	Specifies whether the Quartz scheduler for MDM sync is enabled.
Required	no
Sources	helm chart exported values
Default	true

`mm.local.sync.mdmSyncOptions.quartzOptions.interval`

Description	The interval at which the MDM sync job should run, in the format `days.hours:minutes:seconds`.
Required	no
Sources	helm chart exported values
Default	"1.00:00:00"

`mm.local.sync.mdmSyncOptions.quartzOptions.fireOnStartup`

Description	Specifies whether the MDM sync job should run immediately on startup.
Required	no
Sources	helm chart exported values
Default	true

`mm.local.sync.mdmSyncOptions.isRabbitMqEnabled`

Description	Specifies whether RabbitMQ is enabled for MDM sync.
Required	no
Sources	helm chart exported values
Default	true

`mm.local.sync.mdmSyncOptions.batchSize`

Description	The batch size for MDM sync operations. Should not exceed 1000.
Required	no
Sources	helm chart exported values
Default	1000

`mm.local.sync.mdmSyncOptions.incrementalSyncWithoutDeletion`

Description	This flag controls synchronization behavior by skipping the deletion of local entities during sync operations, significantly improving performance for large datasets. When enabled, the system only processes additions and updates during regular synchronization, relying entirely on event-based mechanisms to handle deletions and relationship changes. This optimization currently only affects MDM errors, where it reduces database operations during routine synchronization while maintaining eventual consistency through separate event handlers.
Required	no
Sources	helm chart exported values
Default	false

`mm.local.sync.tomaSyncOptions.quartzOptions.isEnabled`

Description	Specifies whether the Quartz scheduler for TOMA sync is enabled.
Required	no
Sources	helm chart exported values
Default	true

`mm.local.sync.tomaSyncOptions.quartzOptions.interval`

Description	The interval at which the TOMA sync job should run, in the format `days.hours:minutes:seconds`.
Required	no
Sources	helm chart exported values
Default	"0.00:10:00"

`mm.local.sync.tomaSyncOptions.quartzOptions.fireOnStartup`

Description	Specifies whether the TOMA sync job should run immediately on startup.
Required	no
Sources	helm chart exported values
Default	true

`mm.local.sync.tomaSyncOptions.isRabbitMqEnabled`

Description	Specifies whether RabbitMQ is enabled for TOMA sync.
Required	no
Sources	helm chart exported values
Default	true

`mm.local.sync.tomaSyncOptions.batchSize`

Description	The batch size for TOMA sync operations. Should not exceed 1000.
Required	no
Sources	helm chart exported values
Default	1000

BCS configuration

`mm.local.bcs.host`

Description	The address of the BCS API service host.
Required	no
Sources	helm chart exported values
Default	"https://patrec.azure-api.net/api/v1/pipelines"

`mm.local.bcs.timeoutInSeconds`

Description	The timeout limit for BCS API requests in seconds.
Required	no
Sources	helm chart exported values
Default	60