List of System Properties by Area

This chapter lists the system properties which are relevant for the following areas.

CMRF & DWH Configuration

autocommit.cf.changes

Module: cmas-dwh-server
Description: Defines whether DWH tasks which result from configurational changes on ticket fields are executed automatically without manual interaction in the Admin Tool. Can be also set in the Admin Tool in the navigation item DWH. The default and recommended value is false.
Type: boolean
Restart required: no
System: yes
Optional: no
Example value: false (default value)
Since: 6.7.0

batch-commit-interval

Module: cmas-dwh-server
Description: Number of objects in a DWH message. Larger values mean better transfer performance at the cost of higher memory usage.
Starting with ConSol CM version 6.11, this property is only used if the package size of a DWH operation is not set. This can only happen when the command is directly addressed to the Java MBean consol.cmas.global.dwh.synchronizationService, e.g. using the update() method. When a DWH operation is started using the Admin Tool, there is always a value for the package size. If not explicitly set, the default value of 1000 is used as value for batch.commit.interval.
Default value: 1000
Type: integer
Restart required: no
System: yes
Optional: yes
Example value: 100
Since: 6.0.0

communication.channel

Module: cmas-dwh-server
Description: Communication channel. Only possible value since CM version 6.11.0.0: DIRECT
Type: string
Restart required: no
System: yes
Optional: no
Example value: DIRECT
Since: 6.8.5.0
Removed in: 6.11.0.0 (DIRECT mode is the only available mode and is set automatically)

dwh.mode

Module: cmas-dwh-server
Description: Current mode for DWH data transfer. Possible values are OFF, ADMIN, LIVE
Type: string
Restart required: no
System: yes
Optional: no
Example value: OFF
Since: 6.0.1

ignore-queues

Module: cmas-dwh-server
Description: A comma-separated list of queue names which are not not transferred to the DWH.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: QueueName1,QueueName2,QueueName3
Since: 6.6.19
Removed in: 6.8.1

is.cmrf.alive

Module: cmas-dwh-server
Description: As a starting point, the time the last message was sent to CMRF should be used. If a response from CMRF is not received after the set value (in seconds), it should create a DWH operation status with an error message indicating that CMRF is down.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 1200
Since: 6.7.0

java.naming.factory.initial

Module: cmas-dwh-server
Description: Factory class for the DWH context factory.
Type: string
Restart required: no
System: yes
Optional: no
Example value: org.jnp.interfaces.NamingContextFactory
Since: 6.0.1
Removed in: 6.11.0.0

java.naming.factory.url.pkgs

Module: cmas-dwh-server
Description:
Type: string
Restart required: no
System: yes
Optional: no
Example value: org.jboss.naming:org.jnp.interfaces
Since: 6.0.1
Removed in: 6.11.0.0

java.naming.provider.url

Module: cmas-dwh-server
Description: URL of naming provider.
Type: string
Restart required: no
System: yes
Optional: no
Example value: localhost
Since: 6.0.1
Removed in: 6.11.0.0

notification.error.description

Module: cmas-dwh-server
Description: Text for error emails from the DWH.
Type: string
Restart required: no
System: yes
Optional: no
Example value: Error occurred
Since: 6.0.1

notification.error.from

Module: cmas-dwh-server
Description: From address for error emails from the DWH
Type: string
Restart required: no
System: yes
Optional: yes
Example value: myuser@consol.de
Since: 6.0.1

notification.error.subject

Module: cmas-dwh-server
Description: Subject for error emails from the DWH
Type: string
Restart required: no
System: yes
Optional: no
Example value: Error occurred
Since: 6.0.1

notification.error.to

Module: cmas-dwh-server
Description: To address for error emails from the DWH
Type: string
Restart required: no
System: yes
Optional: no
Example value: myuser@consol.de
Since: 6.0.1

notification.finished_successfully.description

Module: cmas-dwh-server
Description: Text for emails from the DWH when a transfer finishes successfully.
Type: string
Restart required: no
System: yes
Optional: no
Example value: Transfer finished successfully
Since: 6.0.1

notification.finished_successfully.from

Module: cmas-dwh-server
Description: From address for emails from the DWH when a transfer finishes successfully.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: myuser@consol.de
Since: 6.0.1

notification.finished_successfully.subject

Module: cmas-dwh-server
Description: Subject for emails from the DWH when a transfer finishes successfully.
Type: string
Restart required: no
System: yes
Optional: no
Example value: Transfer finished successfully
Since: 6.0.1

notification.finished_successfully.to

Module: cmas-dwh-server
Description: To address for emails from the DWH when a transfer finishes successfully.
Type: string
Restart required: yes
System: yes
Optional: no
Example value: myuser@consol.de
Since: 6.0.1

notification.finished_unsuccessfully.description

Module: cmas-dwh-server
Description: Text for emails from the DWH when a transfer finishes unsuccessfully.
Type: string
Restart required: no
System: yes
Optional: no
Example value: Transfer finished unsuccessfully
Since: 6.0.1

notification.finished_unsuccessfully.from

Module: cmas-dwh-server
Description: From address for emails from the DWH when a transfer finishes unsuccessfully.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: myuser@consol.de
Since: 6.0.1

notification.finished_unsuccessfully.subject

Module: cmas-dwh-server
Description: Subject for emails from the DWH when a transfer finishes unsuccessfully.
Type: string
Restart required: no
System: yes
Optional: no
Example value: Transfer finished unsuccessfully
Since: 6.0.1

notification.finished_unsuccessfully.to

Module: cmas-dwh-server
Description: To address for emails from the DWH when a transfer finishes unsuccessfully.
Type: string
Restart required: no
System: yes
Optional: no
Example value: myuser@consol.de
Since: 6.0.1

notification.host

Module: cmas-dwh-server
Description: Email (SMTP) server hostname for sending DWH emails.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: myserver.consol.de
Since: 6.0.1

notification.password

Module: cmas-dwh-server
Description: Password for sending DWH emails (optional).
Type: string
Restart required: no
System: yes
Optional: yes
Since: 6.0.1

notification.port

Module: cmas-dwh-server
Description: SMTP port for sending DWH emails.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: 25
Since: 6.0.1

notification.protocol

Module: cmas-dwh-server
Description: The protocol used for sending emails from the DWH.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: pop3

notification.tls.enabled

Module: cmas-dwh-server
Description: Activates SMTP via SSL/TLS (SMTPS) for sending notification emails from the DWH. The default value is false. If it is set to true, SMTPS is activated for sending notifications from the DWH.
Type: string
Restart required: yes
System: no
Optional: yes
Example value: false (default value)
Since: 6.11.1.6

notification.username

Module: cmas-dwh-server
Description: (SMTP) user name for sending DWH emails.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: myuser
Since: 6.0.1

recoverable.exceptions

Module: cmas-dwh-server
Description: Comma-separated list of exception definitions: CLASS[+][:REGEX]. The exceptions included in the list do not stop CM from sending to the CMRF process, but force it to try again. If optional '+' after CLASS is present, classes which extend CLASS are matched.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: java.sql.SQLRecoverableException,java.lang.RuntimeException+:.*T.1\,2T.*
Since: 6.8.4.6

skip-ticket

Module: cmas-dwh-server
Description: Tickets are not transferred during transfer/update.
Type: boolean
Restart required: no
System: yes
Optional: no
Example value: false
Since: 6.6.19
Removed in: 6.8.1

skip-ticket-history

Module: cmas-dwh-server
Description: History of ticket is not transferred during transfer/update.
Type: boolean
Restart required: no
System: yes
Optional: no
Example value: false
Since: 6.6.19
Removed in: 6.8.1

skip-unit

Module: cmas-dwh-server
Description: Units are not transferred during transfer/update.
Type: boolean
Restart required: no
System: yes
Optional: no
Example value: false
Since: 6.6.19
Removed in: 6.8.1

skip-unit-history

Module: cmas-dwh-server
Description: History of unit is not transferred during transfer/update.
Type: boolean
Restart required: no
System: yes
Optional: no
Example value: false
Since: 6.6.19
Removed in: 6.8.1

split.history

Module: cmas-dwh-server
Description: Changes the SQL that fetches the history for the tickets during DWH transfer so that the history is not fetched for all tickets at once but only for one ticket per SQL.
Type: boolean
Restart required: no
System: yes
Optional: yes
Example value: false
Since: 6.8.0

unit.transfer.order

Module: cmas-dwh-server
Description: Defines in which order customer field groups should be transferred to the DWH.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: company;customer
Since: 6.6.19
Removed in: 6.8.1

Indexer and Search Configuration

Indexer

big.task.minimum.size

Module: cmas-core-index-common
Description: Indicates the minimum size of index task (in parts, each part has 100 entities) to qualify this task as a big one. Big tasks have a lower priority than normal tasks.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 15 (default value)
Since: 6.8.3

database.notification.redelivery.delay.seconds

Module: cmas-core-index-common
Description: If the notification channel “database” is used for index updates, this property indicates the delay for notification redelivery when an exception occurs.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 60
Since: 6.8.4.7

database.notification.redelivery.max.attempts

Module: cmas-core-index-common
Description: In case of index update database notification channel, indicates maximum redelivery attempts when an exception occurs.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 60
Since: 6.8.4.7

disable.admin.task.auto.commit

Module: cmas-core-index-common
Description: All tasks created for index update will be automatically executed right after creation.
Type: boolean
Restart required: no
System: yes
Optional: no
Example value: false
Since: 6.6.1

index.attachment

Module: cmas-core-index-common
Description: Specifies whether the content of attachments is indexed.
Type: boolean
Restart required: no
System: yes
Optional: no
Example value: true
Since: 6.4.3

index.history

Module: cmas-core-index-common
Description: Specifies whether unit and ticket history are indexed.
Type: boolean
Restart required: no
System: yes
Optional: no
Example value: false
Since: 6.1.0
Removed in: 6.11.0

index.status

Module: cmas-core-index-common
Description: Status of the Indexer, possible values RED, YELLOW, GREEN, will be displayed in the Admin Tool.
Type: string
Restart required: no
System: yes
Optional: no
Example value: GREEN
Since: 6.6.1

index.task.worker.threads

Module: cmas-core-index-common
Description: How many threads will be used to execute index tasks (synchronization, administrative and repair tasks). We recommend to use a value not larger than 2.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 1 (default value)
Since: 6.6.14, 6.7.3. Since 6.8.0 and exclusively in 6.6.21 also normal (live) index updates are affected by this property.

index.version.current

Module: cmas-core-index-common
Description: Holds information about the current (possibly old) index version.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 1 (default value)
Since: 6.7.0

index.version.newest

Module: cmas-core-index-common
Description: Holds information about which index version is considered newest.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 1 (default value)
Since: 6.7.0

indexed.assets.per.thread.in.memory

Module: cmas-core-index-common
Description: Determines how many assets should be loaded into memory at once, per thread, during indexing.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 200 (default value)
Since: 6.8.0

indexed.engineers.per.thread.in.memory

Module: cmas-core-index-common
Description: Determines how many engineers should be loaded into memory at once, per thread, during indexing.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 300 (default value)
Since: 6.6.14, 6.7.3

indexed.resources.per.thread.in.memory

Module: cmas-core-index-common
Description: Determines how many resources should be loaded into memory at once, per thread, during indexing.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 200 (default value)
Since: 6.10.0.0

indexed.tickets.per.thread.in.memory

Module: cmas-core-index-common
Description: Determines how many tickets should be loaded into memory at once, per thread, during indexing.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 100 (default value)
Since: 6.6.14, 6.7.3

indexed.units.per.thread.in.memory

Module: cmas-core-index-common
Description: Determines how many units should be loaded into memory at once, per thread, during indexing.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 200 (default value)
Since: 6.6.14, 6.7.3

synchronize.master.address

Module: cmas-core-index-common
Description: Value of -Dcmas.http.host.port specifying how to connect to the indexing master server. The default value is null. Since 6.6.17 this value is configurable in set-up to designate the initial indexing master server. Since 6.12.0.0 it is possible to switch the node acting as master node by entering the address of the new master node. The index updates are archived for the time configured in the property cmas-core-index-common, synchronize.archive.timeout.minutes, so the new master can recover missing data in case it had not been fully synchronized with the previous master indexing server at the moment of switch.
Type: integer
Restart required: no
System: yes
Optional: yes
Example value: 127.0.0.1:80
Since: 6.6.0

synchronize.master.security.token

Module: cmas-core-index-common
Description: The password for accessing the index snapshot via URL, e.g., for index synchronization or for backups.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: token
Since: 6.6.0

synchronize.master.security.user

Module: cmas-core-index-common
Description: The user name for accessing the index snapshot via URL, e.g., for index synchronization or for backups.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: user
Since: 6.6.0

synchronize.master.timeout.minutes

Module: cmas-core-index-common
Description: Determines how long the master server may continually fail until a new master gets elected. Since 6.6.17, this value is configurable in setup, where 0 means that master server will never change (failover is disabled).
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 5 (default value)
Since: 6.6.0

synchronize.megabits.per.second

Module: cmas-core-index-common
Description: Determines how much bandwidth the master server may consume when transferring index changes to all slave servers. Do not use all available bandwidth to transfer index changes between hosts, as doing so will most probably partition the cluster due to some subsystems being unable to communicate.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 85 (default value)
Since: 6.6.0

synchronize.sleep.millis

Module: cmas-core-index-common
Description: Determines how often each slave server polls the master server for index changes.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 1000 (default value)
Since: 6.6.0

Search Results

globalSearchResultSizeLimit

Module: cmweb-server-adapter
Description: Maximum number of items in Quick Search result.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 10
Since: 6.0

searchPageSize

Module: cmweb-server-adapter
Description: Default page size for search results.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 20
Since: 6.0

searchPageSizeOptions

Module: cmweb-server-adapter
Description: Options for the page size for search results.
Type: string
Restart required: no
System: yes
Optional: no
Example value: 10|20|30|40|50|75|100
Since: 6.0

unitIndexSearchResultSizeLimit

Module: cmweb-server-adapter
Description: Maximum number of units in unit search result (e.g. when searching for contact).
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 5
Since: 6.0

LDAP Configuration

LDAP Configuration (if LDAP is Used as Authentication Mode in the CM Web Client)

LDAP parameters apply only if the authentication mode for the CM Web Client has been set to LDAP:

authentication.method

Module: cmas-core-security
Description: User authentication method (internal CM database or LDAP authentication). Allowed values are LDAP or DATABASE.
Type: string
Restart required: no
System: yes
Optional: no
Example value: DATABASE
Since: 6.0

ldap.authentication

Module: cmas-core-security
Description: Authentication method used when using LDAP authentication. Possible values are anonymous and simple.
Type: string
Restart required: yes
System: yes
Optional: no
Example value: simple (default value)
Since: 6.0

ldap.basedn

Module: cmas-core-security
Description: Base DN used for looking up LDAP user accounts when using LDAP authentication.
Type: string
Restart required: no
System: yes
Optional: no
Example value: ou=accounts,dc=consol,dc=de
Since: 6.0

ldap.initialcontextfactory

Module: cmas-core-security
Description: Class name for the initial context factory of the LDAP implementation when using LDAP authentication. If it is not set, com.sun.jndi.ldap.LdapCtxFactory is used.
Type: string
Restart required: yes
System: yes
Optional: no
Example value: com.sun.jndi.ldap.LdapCtxFactory
Since: 6.0

ldap.password

Module: cmas-core-security
Description: Password for connecting to LDAP to look up users when using LDAP authentication. Only needed if look-up cannot be performed anonymously.
Type: password
Restart required: no
System: yes
Optional: yes
Since: 6.1.2

ldap.providerurl

Module: cmas-core-security
Description: LDAP provider when using LDAP authentication.
Type: string
Restart required: no
System: yes
Optional: no
Example value: ldap://myserver.consol.de:389
Since: 6.0

ldap.searchattr

Module: cmas-core-security
Description: Search attribute for looking up LDAP entry associated with a CM login.
Type: string
Restart required: no
System: yes
Optional: no
Example value: uid
Since: 6.0

ldap.userdn

Module: cmas-core-security
Description: LDAP user for connecting to LDAP to look up users when using LDAP authentication. Only needed if look-up cannot be performed anonymously.
Type: string
Restart required: no
System: yes
Optional: yes
Since: 6.1.2

LDAP Configuration (if LDAP is Used as Authentication Mode in CM/Track)

LDAP parameters apply only if the authentication mode for CM/Track has been set to LDAP:

contact.authentication.method

Module: cmas-core-security
Description: Indicates contact authentication method, where possible values are DATABASE or LDAP or LDAP,DATABASE or DATABASE,LDAP.
Type: string
Restart required: no
System: yes
Optional: no
Example value: LDAP
Since: 6.9.3.0

ldap.contact.name.basedn

Module: cmas-core-security
Description: Base path to search for contact DN by LDAP ID.
Type: string
Restart required: no
System: no
Optional: yes
Example value: ou=accounts,dc=consol,dc=de
Since: 6.9.3.0

ldap.contact.name.password

Module: cmas-core-security
Description: Password to look up contact DN by LDAP ID. If not set, the anonymous account is used.
Type: string
Restart required: no
System: no
Optional: yes
Since: 6.9.3.0

ldap.contact.name.providerurl

Module: cmas-core-security
Description: Address of the LDAP server (ldap[s]://host:port).
Type: string
Restart required: no
System: no
Optional: yes
Example value: ldap://ldap.consol.de:389
Since: 6.9.3.0

ldap.contact.name.searchattr

Module: cmas-core-security
Description: Attribute to search for contact DN by LDAP ID.
Type: string
Restart required: no
System: no
Optional: yes
Example value: uid
Since: 6.9.3.0

ldap.contact.name.userdn

Module: cmas-core-security
Description: User DN to look up contact DN by LDAP ID. If not set, the anonymous account is used.
Type: string
Restart required: no
System: no
Optional: yes
Since: 6.9.3.0

ldap.initialcontextfactory

Module: cmas-core-security
Description: Class name for the initial context factory of the LDAP implementation when using LDAP authentication. If it is not set, com.sun.jndi.ldap.LdapCtxFactory is used.
Type: string
Restart required: yes
System: yes
Optional: no
Example value: com.sun.jndi.ldap.LdapCtxFactory
Since: 6.0

Email Configuration

Outgoing Email

mail.smtp.email

Module: cmas-core-server
Description: SMTP email URL for outgoing emails
Type: string
Restart required: no
System: yes
Optional: no
Example value: smtp://mail.mydomain.com:25
Since: 6.0

mail.smtp.envelopesender

Module: cmas-core-server
Description: Email address used as sender in SMTP envelope. If not set, the From address of the email is used.
Type: string
Restart required: no
System: yes
Optional: no
Example value: mysender@mydomain.com
Since: 6.5.7

mail.from

Module: cmweb-server-adapter
Description: This email address is used instead of the engineer’s email address during email conversations.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: consolcm@example.com
Since: 6.1.2

mail.reply.to

Module: cmweb-server-adapter
Description: When set, the Ticket Email Editor in the Web Client displays a Reply-To field prefilled with this value.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: consolcm@example.com
Since: 6.0.1

Please read the detailed information about ConSol CM Reply-To addresses in section Scripts of Type Email.

mailTemplateAboveQuotedText

Module: cmweb-server-adapter
Description: Determines the behavior of the email template in the Ticket Email Editor when another email is quoted, i.e. forwarded or replied to. Often used to place the signature correctly.
Type: boolean
Restart required: no
System: yes
Optional: no
Example value: false
Since: 6.2.4

mail.sender.address

Module: cmas-workflow-jbpm
Description: From address for emails from the workflow engine.
Type: string
Restart required: no
System: yes
Optional: no
Example value: myuser@consol.de
Removed in: 6.8.0
Replaced by: jobExecutor.mailFrom

mail.smtp.tls.enabled

Module: cmas-core-server
Description: Activates SMTP via SSL/TLS (SMTPS) for sending emails from the Web Client and scripts. The default value is false. If it is set to true, SMTPS is activated for sending emails.
Type: boolean
Restart required: yes
System: no
Optional: yes
Example value: true
Since: 6.11.1.6

Incoming Email

nimh.enabled

Module: cmas-core-server
Description: Enables the NIMH service. Must be suffixed with the cluster node ID, e.g., nimh.enabled.NODEID = true.
Type: boolean
Restart required: no
System: no
Optional: yes
Example value: false
Since: 6.9.4.0

filesystem.polling.threads.number

Module: cmas-nimh
Description: Number of threads started for database emails' queue polling. The default value is 1
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 10
Since: 6.4.0

filesystem.polling.threads.shutdown.timeout.seconds

Module: cmas-nimh
Description: Waiting time after the shutdown signal. When the timeout is reached, the thread will be terminated.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 60 (default value)
Since: 6.4.0

filesystem.polling.threads.watchdog.interval.seconds

Module: cmas-nimh
Description: Determines the interval in seconds to execute the watchdog which checks the activity of the threads of the file system poller.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 30 (default value)
Since: 6.4.0

filesystem.task.enabled

Module: cmas-nimh
Description: With this property the service thread related to a given poller can be disabled.
Type: boolean
Restart required: no
System: no
Optional: yes
Example value: true (default value)
Since: 6.4.0

filesystem.task.interval.seconds

Module: cmas-nimh
Description: Default interval for polling mailboxes in seconds.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 60 (default value)
Since: 6.4.0

filesystem.task.polling.folder

Module: cmas-nimh
Description: Polling folder location which will be scanned for emails in the format of eml files. The default value is the mail subdirectory of the ConSol CM data directory
Type: string
Restart required: no
System: no
Optional: yes
Example value: c://cmas//mail
Since: 6.4.0

filesystem.task.timeout.seconds

Module: cmas-nimh
Description: After this time (of inactivity) the service thread is considered damaged and automatically restarted. Default: 120 seconds
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 60
Since: 6.4.0

filesystem.task.transaction.timeout.seconds

Module: cmas-nimh
Description: Default transaction timeout (in seconds) for email fetching transactions. Should be correlated with number of messages fetched at once.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 60 (default value)
Since: 6.4.0

mailbox.<number>.name

Module: cmas-nimh
Description: Identifier (name) of the mailbox.
Type: string
Restart required: no
System: no
Optional: yes
Example value: myEmailAccount
Since: 6.11.2.0

mailbox.default.connection.host

Module: cmas-nimh
Description: Host (server name) of a given mailbox from which the poller reads emails.
Type: string
Restart required: no
System: no
Optional: yes
Example value: 10.10.1.157
Since: 6.4.0

mailbox.default.connection.password

Module: cmas-nimh
Description: Password for given mailbox from which the poller reads emails.
Type: password
Restart required: no
System: no
Optional: yes
Example value: consol
Since: 6.4.0

mailbox.default.connection.port

Module: cmas-nimh
Description: Port for a given mailbox from which the poller reads emails.
Type: string
Restart required: no
System: no
Optional: yes
Example value: 143
Since: 6.4.0

mailbox.default.connection.protocol

Module: cmas-nimh
Description: Poller's protocol e.g., IMAP or POP3. No default value
Type: string
Restart required: no
System: no
Optional: yes
Example value: imap
Since: 6.4.0

mailbox.default.connection.username

Module: cmas-nimh
Description: User name for a given mailbox from which the poller reads emails.
Type: string
Restart required: no
System: no
Optional: yes
Example value: username
Since: 6.4.0

mailbox.default.session.mail.debug

Module: cmas-nimh
Description: JavaMail property, see JavaMail API documentation for further information. Allows for more detailed JavaMail session debugging.
Type: boolean
Restart required: no
System: no
Optional: yes
Example value: true
Since: 6.4.0

mailbox.default.session.mail.mime.address.strict

Module: cmas-nimh
Description: JavaMail property, see JavaMail API documentation for further information. If this property is set to false, the parsing of the email headers is less strict. Therefore, more emails with non-RFC-compliant headers will be imported into the system, instead of being stored in the Backups section of the Admin Tool.
Type: boolean
Restart required: no
System: no
Optional: yes
Example value: false (default value)
Since: 6.4.0

mailbox.default.session.mail.<PROTOCOL>.connectiontimeout

Module: cmas-nimh
Description: JavaMail property, see JavaMail API documentation for further information. Determines the connection timeout in milliseconds.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 3000
Since: 6.4.0 (IMAP and POP3) / 6.11.2.0 (IMAPS and POP3S)

mailbox.default.session.mail.<PROTOCOL>.fetchsize

Module: cmas-nimh
Description: JavaMail property, see JavaMail API documentation for further information. Determines the size of partial fetch in bytes for the indicated protocol.
For IMAP systems: in CM versions 6.10.7.0 and up, the value of mailbox.default.session.mail.imap.fetchsize is set to 1048576 (equals 1 MB) during the initial setup of a ConSol CM system. During an update of an existing ConSol CM system, the value of the property is left unchanged, if the property is already present. In case the property is not yet present, it is added with the default value.
Type: integer
Restart required: no
System: yes
Optional: yes
Example value: 1048576
Since: 6.9.4.0 (IMAP and POP3) / 6.11.2.0 (IMAPS and POP3S)

mailbox.default.session.mail.<PROTOCOL>.partialfetch

Module: cmas-nimh
Description: JavaMail property, see JavaMail API documentation for further information. Determines whether the protocol’s partial fetch capability should be used.
For IMAP systems: in CM versions 6.10.7.0 and up, the value of mailbox.default.session.mail.imap.partialfetch is set to false during the initial setup of a ConSol CM system. During an update of an existing ConSol CM system, the value of the property is left unchanged, if the property is already present. In case the property is not yet present, it is added with the default value.
Type: boolean
Restart required: no
System: no
Optional: yes
Example value: true
Since: 6.9.4.0 (IMAP and POP3) / 6.11.2.0 (IMAPS and POP3S)

mailbox.default.session.mail.<PROTOCOL>.timeout

Module: cmas-nimh
Description: JavaMail property, see JavaMail API documentation for further information. Determines the I/O timeout in milliseconds.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 120 for IMAP(S) and 3000 for POP3(S)
Since: 6.4.0 (IMAP and POP3), 6.11.2.0 (IMAPS and POP3S)

mailbox.default.task.delete.read.messages

Module: cmas-nimh
Description: This defines whether messages should be removed from the mailbox after processing. For IMAP protocol messages are marked as SEEN by default. For the POP3 protocol, this property is ignored and the emails are always deleted from the email server after they were processed successfully.
Type: boolean
Restart required: no
System: no
Optional: yes
Example value: false (default value)
Since: 6.4.0, changed in 6.12.1.0

mailbox.default.task.enabled

Module: cmas-nimh
Description: With this property, the service thread related to the given poller can be disabled.
Type: boolean
Restart required: no
System: no
Optional: yes
Example value: true (default value)
Since: 6.4.0

mailbox.default.task.interval.seconds

Module: cmas-nimh
Description: Default interval for polling mailboxes in seconds.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 60 (default value)
Since: 6.4.0

mailbox.default.task.max.message.size

Module: cmas-nimh
Description: Maximum size of email messages (i.e., email plus attachment). Emails exceeding the size limit will not be automatically processed by NIMH but will be stored in the database (table cmas_nimh_archived_mail) and will therefore appear in the email backups in the Admin Tool (see section Email Backups). From there they can be resent, downloaded to the file system, or deleted. For those operations the message size is not relevant.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 10485760 (default value, 10 MB)
Since: 6.4.0

mailbox.default.task.max.messages.per.run

Module: cmas-nimh
Description: Number of messages fetched at once from mailbox. Must be correlated with transaction timeout. The default value is 20
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 60
Since: 6.4.0

mailbox.default.task.timeout.seconds

Module: cmas-nimh
Description: After this time (of inactivity) the service thread is considered damaged and automatically restarted. The default value is 120 seconds.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 60
Since: 6.4.0

mailbox.default.task.transaction.timeout.seconds

Module: cmas-nimh
Description: Default transaction timeout (in seconds) for email fetching transactions. Should be correlated with number of messages fetched at once.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 60 (default value)
Since: 6.4.0

mailbox.polling.threads.mail.log.enabled

Module: cmas-nimh
Description: Enables email logging which is especially crucial in cluster environment (used as semaphore there)
Type: boolean
Restart required: no
System: no
Optional: yes
Example value: true (default value)
Since: 6.9.4.1

mailbox.polling.threads.number

Module: cmas-nimh
Description: Number of threads for accessing mailboxes.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 1 (default value)
Since: 6.4.0

mailbox.polling.unstorable.backup.folder

Module: cmas-nimh
Description: Folder on the file system which is used to store emails whose processing failed and which could not be stored in the database either. The value of the property should be the path to the data directory followed by /mail/unstorable.
Type: string
Restart required: no
System: no
Optional: yes
Example value: c:/cmas/mail/unstorable
Since: 6.11.2.7

queue.polling.threads.number

Module: cmas-nimh
Description: Number of threads started for polling the email queue in the database.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 1 (default value)
Since: 6.4.0

queue.polling.threads.shutdown.timeout.seconds

Module: cmas-nimh
Description: Waiting time after the shutdown signal. When the timeout is reached, the thread will be terminated.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 60 (default value)
Since: 6.4.0

queue.polling.threads.watchdog.interval.seconds

Module: cmas-nimh
Description: Determines the interval in seconds to execute the watchdog which checks the activity of the threads of the email queue poller.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 30 (default value)
Since: 6.4.0

queue.task.error.pause.seconds

Module: cmas-nimh
Description: Maximum number of seconds, the queue poller waits after infrastructure (e.g. database) error.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 180 (default value)
Since: 6.4.0

queue.task.interval.seconds

Module: cmas-nimh
Description: Main emails' queue polling thread interval.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 15 (default value)
Since: 6.4.0

queue.task.max.retries

Module: cmas-nimh
Description: Maximum number of email processing retries after an exception. When reached, the email is moved to the email archive. This email can be rescheduled again using NIMH API (or the Admin Tool).
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 10
Since: 6.4.0

queue.task.timeout.seconds

Module: cmas-nimh
Description: After this time of inactivity (in seconds), the service thread is considered damaged and automatically restarted.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 600 (default value)
Since: 6.4.0

queue.task.transaction.timeout.seconds

Module: cmas-nimh
Description: Transaction timeout for email processing in the pipe.
Type: integer
Restart required: no
System: no
Optional: yes
Example value: 60 (default value)
Since: 6.4.0

mail.attachments.validation.info.sender

Module: cmas-nimh-extension
Description: Sets the From header for error notification emails which are sent when the validation of the attachment type fails.
Type: string
Restart required: no
System: yes
Optional: no
Example value: admin@mail.com
Since: 6.7.5

mail.attachments.validation.info.subject

Module: cmas-nimh-extension
Description: Sets the subject for error notification emails which are sent when the validation of the attachment type fails.
Type: string
Restart required: no
System: yes
Optional: no
Example value: Email was not processed because its attachments were rejected!
Since: 6.7.5

mail.db.archive

Module: cmas-nimh-extension
Description: If property is set to true, incoming emails are archived in the database.
Type: boolean
Restart required: no
System: yes
Optional: yes
Example value: false (default value)
Since: 6.8.5.5

mail.error.from.address

Module: cmas-nimh-extension
Description: From address for error emails from NIMH
Type: email
Restart required: no
System: yes
Optional: no
Example value: myuser@consol.de
Since: 6.4.0

mail.error.to.address

Module: cmas-nimh-extension
Description: To address for error emails from NIMH. As a default the email address of the administrator which you have entered during system setup is used.
Type: email
Restart required: no
System: yes
Optional: no
Example value: myuser@consol.de
Since: 6.4.0

mail.on.error

Module: cmas-nimh-extension
Description: If set to true an error email is sent to the above configured address in case the email message could not be processed.
Type: boolean
Restart required: no
System: no
Optional: yes
Example value: true (default)
Since: 6.4.0

mail.ticketname.pattern

Module: cmas-nimh-extension
Description: Regular expression pattern used to identify the ticket name in the subject of incoming mails.
Type: string
Restart required: no
System: yes
Optional: no
Example value: .*?Ticket\s+\((\S+)\).*
Since: 6.4.0
Removed in: 6.12.0.5

Attachments for Incoming Emails

attachment.allowed.types

Module: cmas-core-server
Description: Comma-separated list of allowed file name extensions. If the property does not exist, all file extensions are allowed. If the property exists, but no value is provided, all file extension are blocked.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: txt,zip,doc
Since: 6.5.0

attachment.max.size

Module: cmas-core-server
Description: Maximum attachment size, in MB. This property controls the size of attachments at tickets, customers, and resources. It also controls the size of incoming (not outgoing) email attachments. The value of this property needs to be aligned with the respective setting in the application server configuration (add the parameter max-post-size to the http listener in cm6.xml, cm6-cmrf.xml or domain.xml). In addition you might need to increase the value of cmas-nimh, mailbox.default.task.max.message.size. The value of this property is displayed in the Web Client when adding a new attachment.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 100 (default value)
Since: 6.4.0

Email Encryption (Outgoing and Incoming)

These settings only apply if email encryption is active (true).

mail.encryption

Module: cmas-core-server
Description: If the property is set to true, the encrypt checkbox in the Ticket Email Editor is checked by default. The default value of the property is false.
Type: boolean
Restart required: no
System: yes
Optional: no
Example value: true
Since: 6.8.4.0

In case certificates are stored in an LDAP directory, the following settings have to be made:

ldap.certificate.basedn

Module: cmas-core-server
Description: Base DN for certificates location in the LDAP tree. If not provided, cmas-core-security, ldap.basedn is used.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: ou=accounts,dc=consol,dc=de
Since: 6.8.4

ldap.certificate.content.attribute

Module: cmas-core-server
Description: LDAP attribute name used where certificate data is stored in the LDAP tree.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: usercertificate (default value)
Since: 6.8.4

ldap.certificate.password

Module: cmas-core-server
Description: LDAP Certificates manager password. If not set, cmas-core-security, ldap.password is used.
Type: string
Restart required: no
System: yes
Optional: yes
Since: 6.8.4

ldap.certificate.providerurl

Module: cmas-core-server
Description: LDAP Certificates provider URL. If not set, cmas-core-security, ldap.providerurl is used.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: ldap://ldap.consol.de:389
Since: 6.8.4

ldap.certificate.searchattr

Module: cmas-core-server
Description: LDAP attribute name used to search for certificate in the LDAP tree.
Type: string
Restart required: no
System: yes
Optional: yes
Example value: mail (default value)
Since: 6.8.4

ldap.certificate.userdn

Module: cmas-core-server
Description: LDAP Certificates manager DN. If not set, cmas-core-security, ldap.userdn is used.
Type: string
Restart required: no
System: yes
Optional: yes
Since: 6.8.4

Activity Interval Configuration

admin.tool.session.check.interval

Module: cmas-app-admin-tool
Description: Configures the time interval (in seconds) in which the system checks for inactive (ended) Admin Tool sessions.
Type: integer
Restart required: yes
System: yes
Optional: no
Example value: 30
Since: 6.7.5

server.session.timeout

Module: cmas-core-server
Description: Server session timeout (in seconds) for connected clients (database table cmas_user_session). Each client can overwrite this timeout with custom value using its ID (ADMIN_TOOL, WEB_CLIENT, WORKFLOW_EDITOR, TRACK (before 6.8, please use PORTER), ETL, REST) appended to property name, e.g., server.session.timeout.ADMIN_TOOL.
Please see also the Page Customization attributes updateTimeServerSessionActivityEnabled and updateTimeServerSessionActivity, both of type cmApplicationCustomization.
Type: integer
Restart required: no
System: yes
Optional: no
Example value: 1800
Since: 6.6.1, 6.7.1

Detailed explanation for the Admin Tool:

server.session.timeout.ADMIN_TOOL
Defines the time interval how long the server considers a session valid while there is no activity from the Admin Tool holding the session. The Admin Tool is not aware of this value, it only suffers having an invalid session, if the last activity has been longer in the past.
admin.tool.session.check.interval
Defines the time between two checks done by the Admin Tool, if the server still considers its session valid.

For example, if admin.tool.session.check.interval = 60, the Admin Tool queries the server every minute if its session is still active/valid. In case server.session.timeout.ADMIN_TOOL = 600 the Admin Tool will get the response that the session is now invalid after ten minutes of inactivity.

Administrator Email Addresses

ConSol CM can use different administrator email addresses, depending on the subsystem. Please see Administrator and Notification Email Addresses for detailed explanations concerning admin email addresses. If no specific admin email addresses are configured, the global admin email address (that you have defined during system set-up) is used.

HTTP Header Configuration

It is possible to configure the HTTP response header returned with the web page in the Web Client. This allows, for example, to define security-related response headers according to the requirements dictated by policy or environment. These properties are managed in the module cmweb-server-http-headers. The name of the property is the field of the response header and the value of the property is the field value sent in the header.

Both name and value must match the exact spelling of the HTTP specification for the desired response header field. The correct interpretation and handling of the header lies in the responsibility of the client browser.

Example Property: X-Frame-Options

Module: cmweb-server-http-headers
Description: Example property to illustrate the configuration of HTTP headers. In this case the delivered HTTP header contains the field X-Frame-Options with the value SAMEORIGIN.
Each property in the module cmweb-server-http-headers represents one header field. The property name/key identifies the response header field and the value of the property is the field value sent in this header.
Please be aware that additional HTTP response headers must be correctly defined with the exact spelling as officially specified! Please note also that the correct interpretation and application of these headers is fully in the realm and responsibility of the client browser which requested the page!
Type: string
Restart required: no
System: no
Optional: yes
Example value: SAMEORIGIN
Since: 6.10.8