We have a similar situation to this. All our server admins are running on Windows, but our server architecture is Linux-based. Almost everything works out of the box transferring between the two - the main thing that doesnt being hard-coded file paths. To overcome this on those workflows where this is an issue, we have a wrapped metanode which detects the environment. This works as follows:
Extract system properties extracts a single propert -
The Rule Engine is configured as follows:
$Value$ LIKE "Windows*" => FALSE
TRUE => TRUE
with the result in a new column,
isUnix. The column filter keeps only that result column.
Once you have that value, you can ‘fix’ any windows paths hardcoded to the corresponding linux paths.
Other tips - if you are building file paths manually anywhere in e.g. Java Snippets, dont use string manipulation, use e.g.
File parent = new File(parentPath);
File f = new File(parent, fName);
String newPath = f.toString();
If you need to test on a linux environment, it is possible in e.g. VirtualBox, but it’s pretty slow and clunky if the host PC is doing anything else at all!
Everything else really does just work (and obviously and paths from e.g.
List Files or
List Folders nodes will already be in the format supplied by the local os)