Jump to: navigation, search

Genesys Web Engagement Server Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
01/27/16 General X X

Helpful Links

What's New

This release contains the following new features and enhancements:

  • All Web Engagement–specific libraries required for tuning an external Cassandra cluster are now located in a dedicated folder at Web Engagement installation directory\tools\pulse\lib\es-index.
  • Each newly created Web Engagement application now includes the default Geo-IP database, GeoLite2-City.mmdb. The database is located in Web Engagement installation directory\apps\your application\resources\geo. The Web Engagement sample applications, playground and docs.genesys.com, also contain this database. If you need to update the database to the latest version, follow these instructions.
  • Starting with Web Engagement, you do not have to have a Chat Server connection in order to use the provisioning tool.
  • Starting with version, Web Engagement provides access to metrics and other key performance indicators (KPIs). It also includes the ability to configure Message Server alarms when a KPI passes its threshold value.
  • Starting with version, Web Engagement supports the optional mediaServerURL parameter in the Webengagement_Qualified.Routing script. If this URL is specified, Web Engagement uses it to process calls to the Web Engagement Chat Server API. If absent, Web Engagement uses the URL specified in the serverURL parameter for those calls. The serverURL parameter is also used for accessing the Web Engagement SCXML strategies.
  • Starting with Web Engagement, the file containing the default GRDT templates is located at Web Engagement installation dir/apps/your application/resources_composer-projects/WebEngagement_CEPRule_Templates/import/gwe_default_grat_template.xml.
  • Starting with version of Web Engagement, you can configure Elasticsearch indexing in the same way for both external and embedded Cassandra clusters. In most cases, you can use the default configuration options, which means that you probably don't need to configure these parameters explicitly.
  • Web Engagement now protects personally identifiable information (PII) in direct HTTP requests to Elasticsearch.

Resolved Issues

This release contains no resolved issues.

Upgrade Notes

No special procedure is required to upgrade to release

This page was last edited on January 27, 2016, at 19:55.
Comments or questions about this documentation? Contact us for support!