Jump to: navigation, search

File Capture Point Configuration Options

This page briefly describes some of the File Capture Point configuration options. Refer to the eServices 8.1 Reference Manual for detailed descriptions of all Capture Point-related configuration options. The following options should be configured in the settings section of the Capture Point application:

  • capture-point-type (mandatory)—A file capture point is instantiated only if this option is set to file.
  • inbound-directory (mandatory)—Defines the path to the inbound directory in the file system.
  • notification-directory (optional)—Defines the path to the notification directory. If it exists, it must be different from all other directories specified in the options.
  • error-directory (optional)—Defines the path to the error directory. If it exists, it must be different from all other directories specified in the options.
  • processed-directory (optional)—Defines the path to the processed directory. If it exists, it must be different from all other directories specified in the options.
  • inbound-scan-interval (optional)—Specifies the time interval (in seconds) at which the File Capture Point scans the inbound directory for new files. The minimum value is 5, and the maximum value is 120. The default value is 10.
  • notification-naming-mode (optional)—Specifies the mode of notifications file naming. The possible values are sequential and by-id. The default value is by-id. If this option is set to sequential, the notification file names will follow the pattern <counter>.xml, no matter which notifications directory they are written. If this option is set to by-id, the notification file names will be set to either <InteractionId>.xml, or, if the previous file name is already present in the directory, <InteractionId>_<counter>.xml, so that each new notification for this interaction id in this directory sequentially increments the <counter>.
  • rollback-on-transformation-fail (optional)—If this option is set to false (the default) or no, if transformation of a message fails, the file containing the message will be placed into the error directory. Otherwise, if this option is set to true or yes, if transformation of a message fails, the file containing the message will stay the inbound directory, and the processing of the files from the inbound directory will resume after a delay specified by the option after-rollback-delay.
  • after-rollback-delay (optional)—Specifies the time interval (in seconds) for which the File Capture Point pauses processing files from the inbound directory if a rollback occurred. The default value is 30, the minimum value is 0, and the maximum value is 300.
  • move-non-xml-from-inbound (optional)—If set to false or no, the non-xml files in the inbound directory are ignored. Otherwise, non-xml files from the inbound directory are moved to the error directory, and are overwritten in the error directory if files with the same name exists in the error directory. If the error-directory option is not configured, or its value is empty, and the move-non-xml-from-inbound option is set to true, non-xml files will be deleted from the inbound directory. The default value for this option is true.

Note also the following:

  • The Interaction Server jvm-path option (java-config section) is required for message transformation.
  • The jvm-options section must be properly configured; most notably the -Djava.class.path option.
  • If using iWD compatibility mode, Genesys suggests disabling the schemaDocumentPath option (inbound-transformer-parameters section) because the iwd_messages.xsd schema is extremely restrictive. To disable the option, you can either remove it or alter its name, e.g. to //SchemaDocumentPath. This applies to both the XML File Capture Point and the JMS Capture Point.
This page was last edited on June 19, 2020, at 12:03.
blog comments powered by Disqus