As of Friday October 16th, access to restricted content on this site now requires you to log in with your Genesys account. If you don't have an account, you can request one at these locations: Request MyPartner Portal Account or Request My Support Account.
Jump to: navigation, search

Digital Messaging Server Configuration Options

See the Digital Messaging Server Options Reference for information on the configuration options available.

Options for a particular monitor override the general channel options.

You must set the following Java VM properties according to which DMS channels are used in your environment:

Channel(s) Options
Chat mode only is used in all DMS channels
  • -Dgenesys.mcr.stdserverex.itxrequired = false
  • -Dgenesys.mcr.stdserverex.scsrequired = true
  • -Dgenesys.mcr.stdserverex.chatrequired = true
Paging mode only is used in all DMS channels
  • -Dgenesys.mcr.stdserverex.itxrequired = true
  • -Dgenesys.mcr.stdserverex.scsrequired = false
  • -Dgenesys.mcr.stdserverex.chatrequired = false
Both chat and paging modes are used in DMS channels
  • -Dgenesys.mcr.stdserverex.itxrequired = true
  • -Dgenesys.mcr.stdserverex.scsrequired = true
  • -Dgenesys.mcr.stdserverex.chatrequired = true
DMS channels do not post messages to DMS (for example, a channel for bots)
  • -Dgenesys.mcr.stdserverex.itxrequired = false
  • -Dgenesys.mcr.stdserverex.scsrequired = false
  • -Dgenesys.mcr.stdserverex.chatrequired = false

Masking sensitive data in log files

Although values for sensitive data such as passwords are masked in key-value lists, these values are not masked when users view or modify the related configuration options.

You can use the internal log-filtering mechanism in Digital Messaging Server to properly mask these values, based on the logging-filter-default.json configuration file that you put into the directory where your DMS jar file resides. Specify the configuration file to use in the value for logging-filter-spec. Click here to download a sample for logging-filter-default.json.

First, define a set of filters that are applied to the server's log messages before they are passed to a logging system. The filters intercept the original message's content and produce new content (possibly empty values) for specific messages in a log file (for example, a message that has specific identification information).

There are three types of filter procedures:

  • Skip—Produces empty new content,
  • Hide—Produces standard placeholder as a new content,
  • Edit—Produces new content as a transformation of an original content.

The filter can modify content as part of a series of steps. For example, it can mask one category of information before masking a separate category.

Modification of content is based on a search-and-replace approach using regular expressions and replace expressions (“search” predicate and “replace” action). See the following links for more information:

You must extensively test regular expressions to ensure they perform as expected in all cases. The following tools might be useful for testing:

The following are examples and definitions of typical sensitive data:

This page was last edited on May 31, 2019, at 14:38.

Feedback

Comment on this article:

blog comments powered by Disqus