Small Cause - Major Effect: The "Separator" Problem
The naming of files includes their storage path in the file system, including the complete hierarchical structure of the directories. For example "C:\bill-run\200902\key-account.afp". In a Unix-based system the storage path could thus be named: "/opt/data/bill-run/200902/key-account.afp".
This does make it difficult when configuring DocBridge Mill applications to create universally portable (operating system independent) profiles. This problem can however be solved!
The so called path separator in the configuration files of DocBridge Mill can be written as "/" - in the original Unix system nomenclature. At runtime this will be automatically "translated" into the correct syntax for the target system.
If one writes the top-level node as a variable, one achieves portability for the application, the example shown above would then be "&rootnode;/bill-run/200902/key-account.afp". The value of the variable "rootnode" can either be specified in the profile itself or passed as parameter from the command line. And of course instead of using an absolute path, it is possible to provide a relative path.
So, with some simple methods it is possible to build DocBridge Mill applications which are portable over different machines and platforms. And as a side-effect this approach provides a much more improved configuration method in respect of changes, adaptations and additions through out the entire lifespan of the application!