If you want to store output files e.g. PDF files generated by InterformNG2, then you have many options. One of them is the To filesystem. If you want to store an output file onto the file system of another machine, then you can e.g. consider to e.g. map a network drive to the other server. If that is not an option, then you can also consider to use the To Windows share workflow component as described below.
Like many other functions in InterformNG2 this require a license code which enables this function.
Please notice, that this saves the current payload, so if you e.g. want to save a PDF file, then you first need to run the workflow component,
Create PDF document prior to the To Windows share component.
One scenario, where this workflow is especially useful is for those, that run InterformNG2 on the IBM i platform and are unable to get a good, stable connection to other file servers via QNTC. For those this component is an excellent alternative.
A related workflow input type is: Read from Windows share.
The To Windows Share has these parameters:
- Share
The name of the Windows Share connection, that you want to use. - Path
The path and file name on the remote server relatively to the shared directory. This is the relative path from the shared folder (and directory) in the referred Windows Share connection. If you e.g. setup a Windows Share connection to a file share named sharetest and in the Windows share connection also refer to the subdirectory, inbox. Then the path specified here is the relative path from the inbox folder. If you now in this scenario as the path above as below:
Then the file, myfile.xml will be created in the folder, NewFolder (which will be created if it does not already exist) inside the inbox directory like:
\\server\sharetest\inbox\NewFolder\myfile.xml
- File name conflict resolution
This is covered here.
Related workflow components: