Within the Prolog tab you may define parameters necessary for DocumentRouter to find and use a prolog.
A prolog is an implementation inside a Java-Class residing in a jar file. The prolog mainly is before document router actions take place. In addition a prolog offers the opportunity to define an post action. The post action is called after all document router actions are done.
These actions allow you e.g. to reformat or change index data retrieved from an external source so it can be processed inside your existing workflows.
Please note: In case your workflows require one or more prolog classes you may ask KGS. We’ll gladly help you realize the functionality required by your workflows.
You may provide the following parameters within the Prolog tab.
Parameter name | Type | Description |
|---|---|---|
PrologClass | Textbox | Within the field PrologClass you may provide a Java class name, with the initialization parameters in brackets, separated by a comma ( , ). Input files for the Prolog class will be gathered by KGS DocumentRouter through the parameter PrologFileFilter and handed over one by one to the Prolog class. Example: KGSCold(param1,param2,param3) Depending on your prolog it’s also possible to use a configuration file as a parameter. Example: KGSCold( C:\PrologConfiguration\config.ini ) |
PrologFileFilter | Textbox | The file extension used for input files which shall be handed over to the Prolog class may be defined in the field PrologFileFilter. The files matching the filter working like a trigger. Example: *.pro |
PrologLocation | Textbox | You may enter in the field PrologLocation the path where the compiled Prolog class has been stored. E.g. /opt/tomcat/prolog-classes |