Splicer Development and Troubleshooting Tips

For most day-to-day operations, there's a simplified wrapper process }APQ.C3.FIN.Splicer.Splice to run Splicer. If you need to manually operate Splicer, it's preferable to use this process instead of running Splicer from the command line.

If you want to include a custom cube in Splicer's operational range, add the cube to the list in the fpm.json file. Also, incorporate necessary regions based on the replacement logic you wish to apply in your custom rule and introduce splicing directives that reference your regions.

You can test Splicer's operation on a single cube by specifying the cube name as --cube parameter value of Splicer when running from the command line. Although the aforementioned wrapper doesn't provide an option to specify the cube explicitly, it can help you understand the Splicer command line syntax.

In the event of a rule file compilation error, all modifications made by Splicer will be undone. If Splicer crashes during the rollback operation, you can still refer to the rules subfolder in the Splicer installation location and manually recover any rule from the backup files stored in that location before any alteration.

To troubleshoot the cause of rule compilation errors, you can look into the proposed rule file found in the rules subfolder. Paste this file into the Arc rule editor to check syntax. This method helps quickly identify why the rule isn't compiling.

If you need to examine the specifics of errors occurring during Splicer's operation, refer to the application.log file located in the logs folder of the Splicer installation. This file contains debug information that can assist in determining the root cause of the error.