Skip to main content

We have a Linux server with a couple of Docker containers running Indicium and Universal. We plan to move systemflows from IIS to this new server but for now we want to have the option to run them in both environments if needed. All relevant files and folders for the systemflows are reachable from the Indicium container but because file paths on Linux are different from those on Windows the correct path needs to be determined from the systemflow.

An idea to solve this problem is to include two file read connectors that try to read a simple check file using two different absolute paths. The two possible absolute paths would look something like this:

Windows: \\share\checkfile.txt
Linux: /share/checkfile.txt

The correct path depends on which of the two connectors can successfully access the text file.

Is this the best way to reach the goal?

Hi Roland,

One way of going about this would probably by simply trying the Windows one first for example, then if that fails, do the Linux one after (Red arrow). So if the Windows one succeeds, the Linux read file is skipped. Would that suffice?

Optionally, the Read file connector status codes can help you determine whether the file was found or not if you are using Process logic on the Read file process action.

Hi Mark,

Indeed that would be an efficient method. In that case I’ll be testing this soon.

Reply


Terms & ConditionsCookie settings