Jump to: navigation, search

IWD Setup Utility


In release 8.5.0, the Setup Utility does not ship in a separate IP. It ships as part of iWD Manager IP.

The iWD Setup utility performs the following functions:

  • Imports iWD business processes to Genesys Configuration Server. The iWD Setup Utility includes the following business processes:
    • IWDBP—the default business process. See Working with the iWD Business Process (IWDBP) - 8.1.document.
    • Standard Genesys to IWD adapter—the business process used to insert into IWDBP to serve Genesys standard open media channels. These business processes are also provided as a .wie file that can be imported manually through the Genesys Interaction Routing Designer. This is useful when you are upgrading from one iWD release to another and you do not have to run the iWD Setup Utility. The iWD business process .wie file is saved to your file system when the iWD Manager Installation Package is installed.
    • ABC IWD Simple BP—the business process used to insert into existing business processes.
  • Creates an Agent Group called IWD in your Genesys Configuration Database. This is the name of the Agent Group that is used in the example Distribution routing strategy that is included in the standard iWD Business Process (IWDBP). Although all customers are expected to modify this Distribution routing strategy for their own needs, having the IWD Agent Group created out of the box will make it easier to use IWDBP to process interactions for testing purposes.
  • Creates the capacity rule that includes the media type workitem and provides the option to assign it to the Tenant.
  • Enables you to select and configure the Stat Server to use with iWD Stat Extensions.
  • Configures the iWD Stat Server Java Extensions into the specified Stat Server.
  • Creates the two List Objects—Iwd_Esp_List and Iwd_Package_List—that are necessary to ensure business rules are invoked from business processes, such as IWDBP.
Iwd_Esp_List also defines the list of Universal Contact Servers to be used with Interaction Server that allow the iWD business process (IWDBP) to update the interaction record in the Universal Contact Server, to mark the interaction as done.
  • Creates the connector objects for the iWD solution.

Installing and Using the Setup Utility

This procedure configures the objects required in Configuration Server for your iWD installation.


The iWD Setup Utility can be run multiple times, as it is possible to have multiple iWD Solutions in your environment. The following procedure outlines the steps taken the first time the utility is run. Subsequent runs of the utility may result in some screens not being displayed, as the information has already been configured. Therefore, when you run the iWD Setup Utility it might not follow the exact procedure outlined below.

The iWD Setup Utility will not over-write the iWD business process if it has already been imported by a previous run of the iWD Setup Utility. So, if any customization has been made on the business process, running the iWD Setup Utility will not impact your customization, provided all strategy names are the same.

If you have made changes to the iWD business process, but would like to see the business process that is included in the iWD Setup Utility, you must export the customized business process from IRD, delete it, and then run the iWD Setup Utility again. Or, you can run the iWD Setup Utility against a different Tenant.


  • iWD Manager is installed (iWD Setup Utility is shipped with the iWD Manager IP).
  • iWD Runtime Node is installed.
  • The iWD Data Mart has been installed and the iWD Data Mart database has been created.
  • Interaction Server 8.0.1 or later has been installed. If you are not an existing eServices customer, you will need to install an instance of Interaction Server to use with iWD.


  1. In GAX, navigate to Administration > Solution Definitions.
  2. Click on the + button.
  3. In the New window, click the Choose File button.
  4. Navigate to the iWD installation directory; for example—C:\Program Files (x86)\GCTI\iWD Manager\config\ASD—and select the iWD_setup_utility.xml file.
  5. When you have uploaded it successfully, the iWD Setup Utility option will become available for selection.
  6. Select iWD Setup Utility from the displayed list. Your screen should look like this: IWD SetupUtil1.png
  7. Check the Deployable check box. If for any reason your Setup Utility is not deployable, you will be prompted at this point.
  8. From the Settings menu (indicated on the screen above) select Install. This action opens the Automated Service Deployment Wizard, which is a sequence of configuration screens in which you will define your iWD solution instance. Click Next to begin deployment. Deloyment consists of the following:
    1. Tenant Selection—Browse and select the Tenant where you plan to install the iWD Solution components.
    2. Multimedia Switch Selection—Add the name of a multimedia switch if appropriate. A Multimedia Switching Office and Multimedia Switch must be created in Genesys Configuration Database, to support Stat Server and URS operations. Refer to the eServices 8.1 Deployment Guide for more details on these topics.
    3. Universal Router Server Selection—Select the URS for this iWD Solution.
    4. Samples Placement—Enter the name of the directory where routing strategy files for sample import will be placed.
    5. Resource Capacity Rules Selection—To select the capacity rule. This action will create a capacity rule that can be used immediately.
      The default capacity rule that will be created by the iWD Setup Utility will be based on the media type workitem. You are not required to use workitem as the media type. You can create new media types in Configuration Manager or Genesys Administrator (as Business Attribute objects) and you can use the new media types in any Capture Points you create, as well as in any capacity rules you configure.
    6. Interaction Server Selection—Browse to and select the Interaction Server you plan to use to process interactions for this iWD Solution.
    7. Database Access Point Selection—Browse to the Database Access Point that is configured for the Interaction Server Event Log database, or create a new one if necessary.
    8. Stat Server Selection—Select an existing Stat Server to configure the iWD Stat Server Java Extension for this solution.
    9. Important
      Each iWD Solution requires its own dedicated Stat Server. For more information about installing and configuring Stat Server, refer to the Framework 8.1 Stat Server Deployment Guide.
    10. Universal Contact Server Selection—Select an existing UCS to use with this iWD Solution. If this does not exist, you can skip this step. Having the Universal Contact Server name associated with your iWD Solution ensures that the business logic in the out-of-box iWD business process (IWDBP) will update the interaction record in the UCS database when an interaction is considered done (that is, the value of the Status column in the Interaction table in the UCS database will be set to 3). Normally such an update is done in a routing strategy when processing is stopped for an interaction and the interaction is deleted in the Interaction Server database. However, in the case of the iWD business process, even though interactions may persist in the Interaction Server database for a long period of time, they should still be considered done from an interaction history standpoint in the UCS database. Selecting a Universal Contact Server application on this screen will cause the iWD Setup Utility to update the Iwd_Esp_List list object with an association between your iWD Solution name and this UCS application name.
    11. iWD Manager Creation—Add the name of the iWD Manager application, and browse and select the parent applications folder where the iWD Manager application is located.
    12. Genesys Rules Engine Application Selection—Browse and elect an existing Genesys Rules Engine, or cluster, to evaluate iWD rules.
    13. iWD Solution Selection—Enter the enter the Solution ID for the solution.

This page was last edited on October 17, 2014, at 11:47.
blog comments powered by Disqus