Digital Messaging Server Release Notes 9.0.x 12/22/2017
Table of Contents Digital Messaging Server 9.0.x Release Note 3 Known Issues and Recommendations 5 7 Digital Messaging Server 9.0.0 Deployment Procedure 8 9.0.000.07 12
Digital Messaging Server 9.0.x Release Note 9.0 Digital Messaging Server is part of 9.0 starting in 9.0.000.07. This Release Note applies to all 9.0.x releases of Digital Messaging Server. Links in the Available Releases section enable you to access information regarding a specific release. Available Releases [+] Note about release order Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering. : Release Release Date Release Type Restrictions AIX Linux Solaris Windows 9.0.000.07 09/19/17 General X X This Release Note lists the supported operating systems for each release at a high level. For more detailed information about the supported versions for each operating system, see the Genesys Supported Operating Environment Reference Guide. In previous releases, this component was called Social Messaging Server. For information about 8.5.x releases of Social Messaging Server, see the Social Messaging Server 8.5 Release Note (Cumulative). Discontinued Support [+] Note about discontinued items The Discontinued Support section is cumulative. It lists functionality that is no longer supported in this software and the release number or date when support was discontinued. This cumulative list is in release-number order with the most recently discontinued features at the top of the list. Windows 2008 operating system Solaris operating system AIX operating system Digital Messaging Server 3
Java 1.7 Discontinued as of: 9.0.0 Known Issues You can find a cumulative list of the Known Issues and Recommendations for all 9.0.x releases of Digital Messaging Server, including the issues that are specific to Localized (International) releases, at the following links: Known Issues and Recommendations Internationalization Issues Related Resources For additional information about Digital Messaging Server, see the following documentation: See the Deployment Procedure. eservices Deployment Guide describes deployment procedures for all eservices components. It also contains a highlevel description of the eservices system, its architecture, and a list of new features in the current release. eservices Administrator's Guide presents recommendations for monitoring and adjusting your eservices configuration, plus detailed explanations of procedures to use for selected special purposes. eservices Reference Manual provides a reference listing of configuration options; see also the eservices Options Reference below. eservices Social Media Solution Guide describes deployment and use of the Genesys Social Messaging product. The eservices page in the Genesys Supported Operating Environment Reference Guide provides detailed information about the supported operating environments, including requirements, supported versions, and any conditions or limitations for eservices components. Release Notes for other Genesys components are available here. Digital Messaging Server 4
Known Issues and Recommendations Known Issues and Recommendations Digital Messaging Server The Known Issues and Recommendations section is a cumulative list for all 9.0.x releases of Digital Messaging Server. This section provides the latest information on known issues and recommendations associated with this product. It includes information on when individual items were found and, if applicable, corrected. The Resolved Issues section for each release describes the corrections and may list additional issues that were corrected without first being documented as Known Issues. See also Internationalization Issues. In the DigitalMessagingServer.xml file, the [Log] messagefile default value is empty, but the value should be dmserver.lms, as in the template. ID: DMS-69 Found In: 9.000.07 Fixed In: The DigitalMessagingServer.apd template does not specify values for the following options in the channelany_name configuration section: ucs-in-use reconnection-timeout ucs-request-timeout The application uses the default values described in the Digital Messaging Server/Social Messaging Server Configuration Options Reference. ID: DMS-66 Found In: 9.000.07 Fixed In: Digital Messaging Server may show the wrong status in the following cases: If the driver-classname or inbound-route option is set to an invalid value, the server shows its status as Service Unavailable. If the value of any of the other options is changed, the Server shows its status as Started. ID: DMS-65 Found In: 9.000.07 Fixed In: The x-media-type-chat option must have the value wechatsession. Otherwise Digital Messaging Server cyclically reconnects to Chat Server. Digital Messaging Server 5
Known Issues and Recommendations ID: DMS-62 Found In: 9.000.07 Fixed In: The ESP strategy object in the sample Business Processes uses an outdated type of server: 3rd party server. It must be replaced with the SM Server type. ID: SMD-2104 Found In: 8.5.101.07 Fixed In: Social Messaging Server may receive an ESP request when the corresponding drivers are not ready to execute it, and thus a consistent response to ESP requests is not guaranteed. ID: SMD-1062 Found In: 8.1.201.06 Fixed In: Internationalization Issues Information in this section is included for international customers. Release numbers in the Found In and Fixed In fields refer to the English (US) release of Digital Messaging Server unless otherwise noted in the issue description. There are no internationalization issues for this product. Digital Messaging Server 6
Digital Messaging Server Release Notes 9.0 Digital Messaging Server is part of 9.0 starting in 9.0.000.07. You can find links to Release Notes for particular releases of Digital Messaging Server, if available, in the tree menu on the left or in the list of Available Releases. Digital Messaging Server 7
Digital Messaging Server 9.0.0 Deployment Procedure This deployment procedure applies to all 9.0.0 releases of Digital Messaging Server listed in the 9.0.0 Release table. Most releases use the same standard deployment procedure. Create a Digital Messaging Server Application Object Create an Application object for Digital Messaging Server if it does not already exist. 1. Import the Digital Messaging Server application template from the CD. 2. Create a new Application object, based on the template: Open the Properties dialog box of the Application object. On the Server Info tab: 3. In the Host box, enter the name of the desired host. In the Communication Port box, enter the port Digital Messaging Server will use. 4. On the Start Info tab enter some characters in the Working Directory, Command Line, and Command Line Arguments fields. These characters will be over-written with the correct values during the installation, but they cannot be left blank at this point. 5. On the Connections tab, add a connection to Interaction Server. 6. If this is for a multi-tenant environment, add the tenant(s) on the Tenants tab. 7. Open your Interaction Server Application and add a connection to Digital Messaging Server, then specify the Connection Protocol as either simple or addp. Install Digital Messaging Server (DMS) Windows Prerequisites MS Windows Server 2012 Java 1.8 Digital Messaging Server 8
To install on Windows 1. Locate the Setup.exe for Digital Messaging Server on the product CD. 2. Double-click Setup.exe. 3. Select Java. 4. Enter the login information for your Configuration Server: Host Port User Password 5. Select the appropriate Digital Messaging Server Application object from the list. 6. Confirm selection of JDK 7. Click Install. Linux Prerequisites Red Hat Enterprise/CentOS 7 Java 1.8 To install on Linux 1. Locate the install.sh file for Digital Messaging Server. 2. Use the command >install.sh to start the installation script. 3. On request, enter the absolute path for the directory of the Java executable. 4. Press Enter to confirm the host name for the installation. 5. Enter the login information for your Configuration Server: Host Port User Password 6. From the list of applications, select one and enter its number in the list. 7. Press Enter to confirm the suggested destination directory, or choose another one. 8. Answer other questions, if required. Digital Messaging Server 9
TLS Connection as Windows Service Prerequisite: TLS 1.2 or higher When Digital Messaging Server has Transport Layer Security (TLS) configured, either as a server on its ESP port, or as a client in its connection to Configuration Server, Interaction Server, Message Server, Chat Server, and UCS, follow these steps to enable it as a Windows Service: 1. Select the Windows service related to Digital Messaging Server. 2. Select the Log On tab. The default setting is Log on as local system account. 3. Select Log on as this account and provide the login/password of a local host user. Proxy Server Support for Digital Messaging Server 1. Edit the appropriate file by adding these Java runtime startup options: If using Genesys Cloud API Driver for Facebook 8.5.300.09 or earlier, or Genesys Cloud API Driver for Twitter 8.5.300.07 or earlier: -DproxySet=true -DproxyHost=<host of proxy server> -DproxyPort=<port of proxy server> If using Genesys Cloud API Driver for Facebook 8.5.300.10 or later, or Genesys Cloud API Driver for Twitter 8.5.300.08 or later: -Dhttp.proxyHost=<host of proxy server> -Dhttp.proxyPort=<port of proxy server> -Dhttps.proxyHost=<host of proxy server> -Dhttps.proxyPort=<port of proxy server> 2. To enable authentication for the proxy server, add these options as well: If using Genesys Cloud API Driver for Facebook 8.5.300.09 or earlier, or Genesys Cloud API Driver for Twitter 8.5.300.07 or earlier: -DproxyUser=<username> -DproxyPassword=<password> If using Genesys Cloud API Driver for Facebook 8.5.300.10 or later, or Genesys Cloud API Driver for Twitter 8.5.300.08 or later: -Dhttp.proxyUser=<username> -Dhttp.proxyPassword=<password> 3. Edit the following file: Windows: In JavaServerStarter.ini, the [JavaArgs] section Digital Messaging Server 10
Unix and related systems: In dmserver.sh, the last string, namely "$JAVA_EXECUTABLE_PATH/java" - classpath $CLASSPATH $JVMPARAMS $MAINCLASS $* Digital Messaging Server 11
9.0.000.07 Digital Messaging Server Release Notes 9.0 This is the first release of Digital Messaging Server as part of 9.0. Release Date Release Type Restrictions AIX Linux Solaris Windows 09/19/17 General X X What's New This release contains the following new features and enhancements: In addition to Genesys Social Engagement, the initial 9.0.x release of Digital Messaging Server supports Genesys WeChat Messaging Apps connector. Supports Java 1.8. See "Prerequisites for: eservices" on the Supported Operating Environment: eservices page for more detailed information and a list of all prerequisites. Helpful Links Releases Info List of 9.0.x Releases 9.0.x Known Issues Deployment Procedure 9.0.0 Deployment Procedure Product Documentation eservices Resolved Issues This release contains no resolved issues. Genesys Products List of Release Notes Digital Messaging Server 12
Upgrade Notes Refer to the Deployment Procedure for this release to deploy the installation package within your environment. Digital Messaging Server 13