Maintenance Notice - PDF Generation
Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.

Note: Access to static files, including PDF files that are not dynamically generated from our web-based content, is unaffected.

Jump to: navigation, search

Installation Phase Overview


Installation results in a fully functional iWD Manager application and prepared iWD Runtime Node and iWD History Node. Almost all the configuration is carried out using the Genesys Administrator Extension (GAX) component and the iWD Plug-in for GAX component (from now on referred to as iWD GAX Plugin).

The iWD Runtime Node is a container in which the iWD runtime services run, and in which iWD Data Mart is packaged.

The iWD History Node utilizes Interaction Server's ability to provide EventLog data via the Java Messaging Service (JMS) queue to filter uninteresting records before they enter the database. It also splits the source datastream into separate tables, one for Data Mart and one for the Global Task List.

The installation phase requires knowledge of the system infrastructure in which iWD is being deployed, such as Java web application server and database configuration. This phase is typically implemented by IT personnel.

iWD installation consists of two steps:

  • Preparing databases
  • Installing applications

JMS Configuration

The JMS driver is not supplied in the iWD software distribution. Make sure that you have installed a suitable driver for the JMS queue. Supported JMS queues are:

  • ActiveMQ; supported driver: activemq-client 5.15.4 or above.
The JMS queue driver must be placed in the History Node installation directory:
The JMS URL configured in Interaction Server must have following option:

Example URL:


Preparing Databases

A basic iWD deployment uses three operational databases:

  • Genesys Rules System (GRS) rule repository—GRS stores business rule templates and business rules. For more information, see the Genesys Rules System 8.5 Deployment Guide.
  • Interaction Server databases—Interaction Server database stores iWD tasks. Make sure that you have installed and configured the Interaction Server and its associated databases, as described in the eServices Deployment Guide.
  • History Node database—The History Node database stores a filtered subset of iWD events. The History Node database and JMS drivers are not supplied in the iWD software distribution. Make sure that you have installed and configured a suitable database and JDBC driver for it, as well as the JMS queue driver for the JMS used by Interaction Server.

Supported databases are:

  • PostgreSQL 9.3+
  • Oracle 12c
  • MSSQL 2012
  • MS SQL 2016
  • MS SQL 2016 Cluster & AlwaysOn

JDBC and JMS drivers do not require any configuration. However their .jar files must be put into the {HISTORY NODE INSTALLATION DIR}/lib directory.

  • Data Mart database—Uses Fact tables, aggregates, dimension and measures to provide sophisticated reporting options.

For a list of the database engines that are supported by the iWD application, Genesys Rules System, and Interaction Server, refer to the Genesys Supported Operting Environment Guide. Please note that the iWD application might not support all of the databases that are supported by Interaction Server or the Genesys Rules System.

Application Installation

After the iWD operational databases have been prepared, the iWD GAX Plugin component, the iWD Manager application, the iWD History Node and the iWD Runtime Nodes should be installed manually.

From release 9.0, all iWD components operate as stand-alone Java applications.

All three can be configured in release 9.0 by using Genesys Administrator Extension (GAX).

A basic iWD deployment, such as in a lab environment, utilizes a single instance of iWD Manager, as well as a single instance of an iWD Runtime Node and an iWD History Node. In more complex scenarios, such as multi-tenant, high-volume or high-availability deployments, multiple iWD Runtime Node instances can be installed. These deployments provide more controlled resource partitioning and allow load distribution across multiple physical servers.

In addition to the iWD GAX Plugin, the iWD Manager and iWD Runtime Node installation and iWD History Node, Genesys Rules System must be installed. This installation includes:

  • Genesys Rules Development Tool, which is a Genesys component for business rule template development
  • Genesys Rules Authoring Tool, which is used for authoring and deploying business rules
  • Genesys Rules Engine, which is an engine that receives and processes requests for business rule evaluation from clients, such as the routing strategies in the iWD Business Process (IWDBP).
This page was last edited on June 18, 2019, at 11:15.


Comment on this article:

blog comments powered by Disqus