3.4.6 Evaluating the working folders and execution directories for the operation-target devices
You need to evaluate the working folders and execution directories that are used when a plug-in is executed.
When the OS on the operation-target device is Windows
You can change the default execution directory used when a content plug-in is executed, to any directory you want. Specify the execution directory in the connection-destination property file (connection-destination-name.properties) or user-specified properties file (config_user.properties).
You can also change the working folder used when a general command plug-in, File-transfer plug-in, or content plug-in (when Execution Method is Script) is executed, to any directory you want. Specify the working folder in the connection-destination property file (connection-destination-name.properties).
However, note the following when you specify the working folders and execution directories:
The execution directories and working folders must be placed on the same drive.
If the OS on the operation-target device is Windows Server 2012 or Windows Server 2012 R2 in a cluster environment, you must specify the working folders.
If you execute a script for a content plug-in when the OS on the operation-target device is Windows Server 2012 or Windows Server 2012 R2 in a cluster environment, you must specify the execution directory.
When the OS on the operation-target device is UNIX
You can change the execution directory when a content plug-in is executed, to any directory you want. Specify the execution directory in the connection-destination property file (connection-destination-name.properties) or user-specified properties file (config_user.properties).
If you execute a File-transfer plug-in or content plug-in (when Execution Method is Script), the working folder is created. You can change the working folder to any directory you want, in the connection-destination property file (connection-destination-name.properties)