Digital Messaging Server

Important

Digital Messaging Server was called Social Messaging Server in releases prior to 9.0.0. For Social Messaging Server options, refer to the Social Media Solution Guide.

Options for this component have two sources:

• The usual template file that is provided as part of the installation of the component.
• Various .cfg files, which are provided as part of the installation of the following driver components. You install the Driver, then import the file into your Digital Messaging Server. The options thus created are documented in separate chapters in this Options Reference:
  • Genesys Driver for use with Apple Business Chat via Hub
  • Genesys Cloud API Driver for use with Facebook
  • Genesys Cloud API Driver for use with Twitter
  • Genesys Driver for use with WeChat
  • Genesys Driver for use with Genesys Hub
  • Genesys Driver for SMS and MMS
  • Bot Gateway Server

Options for this component are contained in the following configuration sections:

• channel-any_name
• channel-any_name-monitor-any_name
• endpoints:tenant_dbid
• log
• log-extended
• log-filter
• log-filter-data
• settings

Tip

In the summary table(s) below, type in the Search box to quickly find options, configuration sections, or other values, and/or click a column name to sort the table. Click an option name to link to a full description of the option. Be aware that the default and valid values are the values in effect with the latest release of the software and may have changed since the release you have; refer to the full description of the option to see information for earlier releases.

Power users: Download a CSV file containing default and valid values and descriptions.

The following options are configured at the application level (in other words, on the application object).

Section	Option	Default	Changes Take Effect
Section	Option	Default	Changes Take Effect
channel-any_name	business-id	An empty string	After restart
channel-any_name	driver-classname		After restart
channel-any_name	inbound-route	An empty string	After restart
channel-any_name	inbound-route-by-call	An empty string	After restart
channel-any_name	media-origin	generic-media	After restart
channel-any_name	media-type-chat-by-call	An empty string	After restart
channel-any_name	reconnection-timeout	180	After restart
channel-any_name	session-asyncmode	false	After restart
channel-any_name	tenant-dbid		After restart
channel-any_name	ucs-in-use	false	After restart
channel-any_name	ucs-request-timeout	10	After restart
channel-any_name-monitor-any_name	option	An empty string	Depends on an option
endpoints:tenant_dbid	endpoint_name_for_paging		After restart
log	all	stdout	After restart
log	buffering	false	After restart
log	expire	10	After restart
log	log4j2-config-profile	log4j2.xml	After restart
log	messagefile	dmserver.lms	After restart
log	segment	100MB	After restart
log	standard	stdout	After restart
log	time-format	ISO8601	After restart
log	trace	stdout	After restart
log	verbose	standard	After restart
log-extended	logger-instr-id	io.netty.channel.nio.NioEventLoop:level=fatal	After restart
log-extended	logger-psdk	com.genesyslab.platform:level=fatal	After restart
log-filter	default-filter-type	copy	At start/restart
log-filter	string-max-print-size	128	After restart
log-filter-data	sample_name	hide	After restart
settings	esp-proc-timeout	60	After restart
settings	hide-attached-data	true	After restart
settings	logging-filter-active	false	After restart
settings	logging-filter-spec	logging-filter-default.json	After restart
settings	logging-max-message-size	5000	After restart
settings	redis-client-config	redisson-config-file.yaml	After restart
settings	server-mode	single	After restart
settings	session-chat-request-timeout	40	After restart
settings	session-init-number	500	After restart
settings	session-max-number	500	After restart
settings	session-shutdown-timeout	180	After restart
settings	subject-size	25	After restart
settings	workspace-location	./	After restart