Jump to: navigation, search

Configure the Integrated Capture Point

The procedures in this section are applicable to all types of capture points. Differences in configuration between the capture points are mentioned specifically in the procedures where necessary.

Creating the capture point application

The capture point functionality is built within Interaction Server 8.1, which means that there is no separate installation package for any type of capture points. An Application object for the capture point must be configured in Configuration Manager or Genesys Administrator, however. One Application object must be configured for each instance of the capture point. Interaction Server supports multiple capture points.

Prerequisites

  • Interaction Server must be installed as described earlier in this guide.
  • iWD 8.0 must be installed as described in the iWD 8.0 Deployment Guide.
  1. Login to Configuration Manager or Genesys Administrator, and import the required capture point application template from <Interaction Server installation location>\CapturePointTemplates\.
    2. Important
    Configuration Server 8.0.3 supports the Capture Point application type. Earlier releases of Configuration Server should use the Third Party Server application type for capture points. Also, if a version of Configuration Server earlier than 8.0.3 is being used, you should modify the corresponding XML metadata file when you import metadata into Genesys Administrator. In the XML metadata file, replace type="163" with type="23".
  2. Create a new Application object based on the template you imported. The CapturePointId will be automatically set to the name of the capture point application as configured in Configuration Manager or Genesys Administrator. In iWD compatibility mode, it will also be saved as the IWD_capturePointId property in user data. When the capture point is later configured in iWD Manager, the Capture Point ID must be the same as the application name in order to ensure accurate events history reporting and accurate filtering. (The capture point Name can be anything).
    3. Important
    The name of the Capture Point Application object must start with a letter, contain only alpha-numeric characters and underscores, and cannot be longer than 16 characters and cannot contain spaces.
  3. Because the capture point is integrated with Interaction Server, the host and port information is taken from Interaction Server (which must be listed as a connection on the Connections tab). On the Server Info tab, you can enter the host and port of Interaction Server in the Host field, but the information will actually be taken from the connection to Interaction Server, not the information entered on this tab.
  4. There is no installation package, so the Application object does not correspond to an installed component. Therefore, the information entered in the Start Info tab are not read. In order to save the Application object, the fields cannot be left blank, so you can enter any text in these fields.
  5. If you are using a version of Configuration Server that does not support the Capture Point application type, then you must configure the following section and option for the Third Party Server Application object in order for Interaction Server to recognize it as a Capture Point:
    1. In the properties for the Third Party Server application, create a configuration option section called settings.
    2. In the settings section, add the option capture-point-type and set its value to:
  • jms for the JMS Capture Point.
  • kafka for the Kafka Capture Point.
  • file for the File Capture Point.
  • db for the Database Capture Point.
  • webservice for the Web Service Capture Point.

    • If you do not create this option, the Third Party Server application will not be treated like a capture point.

Tip
For information about all configuration options for the Capture Point application and configuration options for Interaction Server that are related to the capture point functionality, refer to the Configuration options warehouse.
  • Add a connection to Interaction Server. Multiple Capture Point Application objects can connect to the same Interaction Server.
  • Save the Application object.

    • Next Steps

    Configuring the capture point service

    The following procedure creates the service in iWD Manager.

    1. Log into iWD Manager.
      2. Important
      For a detailed description of the iWD Manager interface, including logging in, the interface layout, and available functionality, refer to the iWD Deployment Guide.
    2. In iWD Manager, select the Services navigation section.
    3. Locate your Solution in the navigation tree. Expand the Services node in the navigation tree (if necessary), and click New Service.
    4. From the templates drop down list,
      1. For iWD 8.1.0 or higher, select the Generic Capture Point service. The Capture Point ID must match the name of the Capture Point Application object that you configured in Creating the capture point application. Configure the remaining properties of the service. All other configuration for the capture point is done in Configuration Manager or Genesys Administrator by using configuration options.
      2. For iWD 8.0, select any Capture Point service. The service that you are creating will serve as a "dummy" Capture Point Service. The Capture Point ID must match the name of the Capture Point Application object that you configured in Creating the capture point application. The rest of the properties can be left at their default values, as they will not be used. All configuration for the Capture Point is done in Configuration Manager or Genesys Administrator by using configuration options.
    5. When configuration is complete, click Save. Remember to deploy your changes in iWD Manager.

    Starting or stopping the Capture Point Service

    You can set an Integrated Capture Point (ICP) to stopped mode by changing the state of the corresponding configuration object to disabled; changing the state to enabled restarts the inbound cycle of the ICP.

    This page was last edited on February 14, 2022, at 08:39.
    Comments or questions about this documentation? Contact us for support!