Using checkpointing for custom logic

If you want to preserve the state of your customizations or the deduplication over a restart of your application, you must enable checkpointing for the custom or deduplication logic or both. You use the appropriate parameters to do so.

About this task

Enable checkpointing function by switching it on using the provided parameters.

Procedure

  1. In the file <PathToYourApplication>/config/config.cfg, find the ite.businessLogic.group.custom.checkpointing parameter description
  2. Enable the checkpointing function for your custom group logic by setting the parameter to on as follows: ite.businessLogic.group.custom.checkpointing=on

  3. In the file <PathToYourApplication>/config/config.cfg, find the ite.businessLogic.group.custom.timeToKeep parameter description

  4. To specify the number of days after which tuples are removed from the stateful custom group, set the parameter to the wanted value, for example: ite.businessLogic.group.custom.timeToKeep=7d

  5. In the file <PathToYourApplication>/config/config.cfg, find the ite.businessLogic.group.deduplication.checkpointing parameter description

  6. Enable the checkpointing function for the deduplication by setting the parameter to on: ite.businessLogic.group.deduplication.checkpointing=on

You find committed checkpoint files at custom/<groupId>/committed/<input-filename>.bin for the custom logic and <groupId>/committed/<input-filename>.chk for deduplication data. Both file types are under the output directory that is specified with the ite.checkpointing.directory.

CAUTION: If the checkpointing for the group logic is enabled, the ITE application regularly runs internal maintenance tasks that pause the file processing for a few seconds up to several minutes.