Info: Performing the step described in this article requires direct server access. Depending upon how your system is hosted and the level of access you have to that system, coordination may be required with your Partner or WoodWing Support team. For a full overview of the steps that need to be done by WoodWing and how to request them, see WoodWing Cloud - Change management.
Studio Server can play the role of an Application Server but also the role of a File Transfer Server. Physically they are the same: they originate from the same package and they are installed in the same way. Logically, once installed, they can change role any time just by configuration. Studio Server can even play both roles at the same time (this is the way in which Studio Server is configured by default).
The performance of the File Transfer Server is much higher compared to the DIME file transfer method used in previous versions.
Should there be a need to further increase performance (for instance for large systems with many Server machines where load balancing is important) the File Transfer Server folder can be moved to its own machine.
Note: Scenarios in which you want to move the File Transfer Folder to another system are:
Step 1. Create the folder which is going to serve as the File Transfer Folder.
Note: Make sure that the the Web Server user (“IUSR_<servername>”) has read & write access to that folder.
Step 2. Mount the Transfer Folder from the Studio Server machine.
Note: Make sure that:
Step 3. Edit the following option in the File Transfer Server section of the configserver.php file (recommended: config_overrule.php file):
- FILE_TRANSFER_LOCAL_PATH. The transfer folder accessible from the Transfer Server. Default value:
IMPORTANT: Note that the File Store and the Transfer Server Folder should be on the same disk; only then can files be moved from one location to another. When the File Store and the Transfer Server Folder are located on separate disks, files will be copied instead of moved, which has a big impact on performance.