Skip to main content

Configuration improvements

The following configuration improvements have been made.

6.17.1.0​

Configurable timeout for connecting to the SMTP server (#632322)​

It is now possible to configure the timeout for connecting to the SMTP server. Two new settings have been added to the Settings tab of the Email configuration page of the Web Admin Suite for this purpose:

  • Timeout for connecting to the SMTP server (in milliseconds): Saved to the new system property mail.smtp.connectiontimeout of the module cmas-core-server
  • Timeout for sending an email (in milliseconds): Saved to the new system property mail.smtp.timeout of the module cmas-core-server

Improved notifications for failed incoming emails (#656873)​

The email, which is sent to the administrator when the processing of an incoming email fails, has been improved. The notifications are more user-friendly and informative now because they include as many details as are available. The template mail-process-failure-template of the type Email has been introduced for this purpose.

The template includes the following information:

  • Reason for the notification
  • Description of the situation
  • Details about the email
  • Suggestions for troubleshooting
  • Stacktrace
info

The template is added automatically during setup and update. You can adapt it as needed.

Possibility to use more than one datasource in a task (#661007)​

The configuration files cm6-standalone.xml and cm6-domain.xml have been extended, so that it is possible to use a second database connection in a task script. The following line was added:

<property name = "com.arjuna.ats.arjuna.allowMultipleLastResources" value = "true" />

New log file for ETL Runner (#661164)​

A specific log file for ETL Runner has been introduced to gather all log messages from ETL Runner in one file. The name of the log file depends on the deployment mode:

  • Standalone deployment (JAR file): etlRunner.log
  • Overlay deployment (WAR file): etl-runner.log

You need to update the XML configuration files cm6-<DB>.xml and cm6-dwh-<DB>.xml with the following code:

<periodic-size-rotating-file-handler name="ETL_RUNNER" autoflush="true">
    <formatter>
        <pattern-formatter pattern="%d %-5.5p [%30.-30c] [%X{username}-%X{context}-%X{sessionId}] %m%n"/>
    </formatter>
    <file relative-to="jboss.server.log.dir" path="etl-runner.log"/>
    <suffix value=".yyyy.MM.dd"/>
    <max-backup-index value="${handler.etl-runner.max.backup.index:10}"/>
    <rotate-size value="${handler.etlrunner.rotate.size:50m}"/>
    <append value="true"/>
</periodic-size-rotating-file-handler>

<logger category="org.pentaho" use-parent-handlers="true">
    <level name="${logger.org.pentaho.level:INFO}"/>
    <handlers>
        <handler name="ETL_RUNNER"/>
    </handlers>
</logger>

<logger category="com.consol.cmas.etl" use-parent-handlers="true">
    <level name="${logger.org.pentaho.level:INFO}"/>
    <handlers>
        <handler name="ETL_RUNNER"/>
    </handlers>
</logger>

In addition, some unneeded log entries about the map size and the logging registry status have been removed.

Improved notifications for workflow timer failures (#661317)​

The email, which is sent to the administrator when the processing of a workflow timer fails, has been improved. The notifications are more user-friendly and informative now because they include as many details as are available. The template workflow-timer-failure-template of the type Email has been introduced for this purpose.

The template includes the following information:

  • Reason for the notification
  • Description of the situation
  • Details about the workflow timer
  • Affected case
  • Suggestions for troubleshooting
  • Stacktrace
info

The template is added automatically during setup and update. You can adapt it as needed.

QA scene removed from distribution (#661627)​

The Test and Demo Scene has been removed from the ConSol CM distribution because it is rarely used and therefore increases the size of the distribution package unnecessarily.

Labels for password policy violations streamlined (#661661)​

When a user tries to change his password to one which is not allowed due to the password policy, the following validation messages are shown.

  • policy.password.age.violated: The validity of the password has expired.
  • policy.password.rotation.violated: The new password matches a previously used password.
  • policy.password.pattern.violated: The password does not meet the complexity requirements.

The labels for these messages are now added automatically on setup and update.

The previously used label cmweb.auth.password.validation.failed has been removed. On update, its value is written to policy.password.pattern.violated if this label did not exist previously.

Information about email interception improved (#661728)​

When emails are intercepted on a system because the value of mailSender.testArchive.flavour includes the system's flavour (property system.flavour), this is now visible in two places:

  • Log files: Whenever an email is intercepted, an entry is written to the log files.
  • Email configuration in the Web Admin Suite: When checking the SMTP connection by clicking the Test connection button in the Settings tab, the toast message states that emails are intercepted.

This prevents confusion if emails are not delivered and the administrator is not aware that the feature is active.

Logging configuration for CM/Track V3 (#662169)​

Log entries from CM/Track V3 are now written to the new log file trackv3.log. A new logger has been added to the ConSol CM configuration files to configure this log file.

By default, the log level is INFO. You can change this by adding the following line to the cm6-config.properties or cm6-domain-config.properties file:

logger.com.consol.cmas.track.v3.level=DEBUG

If you use the standalone version of CM/Track V3, the configuration is done in the trackv3.properties file:

logging.level.com.consol.cmas.track.v3=DEBUG

This improves clarity as all the logs from CM/Track V3 are gathered in a dedicated log file. In addition, the logging in the signin / signout area has been extended to facilitate troubleshooting of related problems.

info

If CM/Track V3 is deployed in the same application server as ConSol CM, you need to update the cm6-<DB>.xml or cm6-dwh-<DB>.xml file in standalone/configuration or cm6-<DB>.xml in domain/configuration for the CM/Track V3 logging to become active.

New names for application executables (#662335)​

The executables of the ConSol CM main product and its extensions have been renamed to follow a consistent naming scheme:

  • Applications for deployment on an application server have the extension .war.
  • Applications for standalone execution have the extension .jar and the suffix standalone.
  • All application names start with cm- for correct grouping and easy distinction, except for cm6.ear, cmrf.jar and cmrf.war.

Example:

  • cm-track-v3-standalone-6.17.1.0.jar: standalone application for CM/Track V3 in version 6.17.1.0
  • cm-track-v3-6.17.1.0.war: overlay application for CM/Track V3 in version 6.17.1.0

Logging configuration for scripts (#662433)​

Log entries which originate from scripts are now written to the new log file scripts-output.log. A new logger for scripts has been added to the ConSol CM configuration files to configure this log file.

By default, the log level is INFO. You can change this by adding the following line to the cm6-config.properties or cm6-domain-config.properties file:

scriptlogger.logging.level=DEBUG

This improves clarity as the log output defined in scripts is gathered in a dedicated log file, which can be set to the desired log level separately from the general logging configuration.

info

You need to update the cm6-<DB>.xml or cm6-dwh-<DB>.xml file in standalone/configuration or cm6-<DB>.xml in domain/configuration for the script logging to become active.

MaxMetaSpaceSize setting removed (#662636)​

The MaxMetaSpaceSize setting has been removed from the XML configuration files and the cm6-domain-config.properties file of ConSol CM to provide the required metaspace for the new applications deployed on the application server.

Remove MaxMetaSpaceSize

As it is not required to limit the metaspace used by ConSol CM, it is recommended that you remove this setting from your configuration.

Scene for CM/Ticketing updated (#662805)​

The scene for the CM/Ticketing product, which can be selected when setting up a new ConSol CM system, has been updated to use several new features introduced in this version.

6.17.1.1​

Logging of ID tokens for SSO troubleshooting added (#663273)​

The ID tokens which are received from external SSO providers are now logged to facilitate troubleshooting of authentication problems.

  • The ID token is logged on ERROR level in case of an authentication error.

  • The ID token is logged on DEBUG level for each authentication attempt if DEBUG is enabled for the logging category com.consol.cmas.core.security. You need to add the following line to the cm6-config.properties or cm6-domain-config.properties file:

      logger.com.consol.cmas.core.security.level=DEBUG