Importing data stored locally on server file system
By default, import jobs in Columbus require the Helper to be active for the duration of the job. When using the Helper, the images are requested using remote procedure calls and then served to Columbus via the client workstation, i.e. the images pass through the client on their way to the server.
In contrast, it is possible to import data into Columbus which is stored on the Columbus server itself, or on a share which is accessible via the Columbus servers filesystem. When importing locally stored data, the remote procedure call API is not used. Instead Columbus uses the local filesystem to access the data, the images are transferred directly, not via the client workstation. This is more efficient and so tends to be much faster. The downside being that it's not possible to browse the servers file system using the Columbus UI, meaning absolute paths must be specified manually in the Import path, hence local imports are less user friendly.
Further details on how to set this up can be found in:
Please sign in to leave a comment.