Send a new file to another device the moment it is created
Nobody has to watch the source folder, and nothing has to wait for the next scheduled run. In INNORIX Studio, connect the source and target devices and make a new file event in a named folder the condition that starts the transfer. New files that match your conditions go to the other server, and whether it ran and what it did are in Runs.
This guide covers event-driven transfer on file creation, not transfer on a time schedule. Unlike the Daily Schedule in guide 10, it shows on the real UI how a transfer starts once a file is ready. The readiness condition that keeps a transfer from starting while a file is still being written has to be verified against the detection and wait features actually supported and against how the source application writes its files.
Cómo se construye
- Choose the source folder that new files land in.
Confirm the watched path on the source server and how the files get created there. Decide which extensions are in scope and what rules exclude temporary files.
- Connect the two devices in Devices.
Register the source server where files are created and the receiving server, and confirm that each path is reachable.
- Build the transfer in Flows.
Set the source and target folders and, where you need them, include conditions such as
*.csvor an exclusion for.tmpfiles. - Make the new file event the run condition.
From the supported event triggers, choose new file creation in the source folder, review the options your product version offers for duplicate runs and file readiness, then save.
- Create a new file and verify the automatic run.
Drop a test file into the source folder and confirm the transfer starts on its own. Check completion in Runs, then verify the file in the receiving folder.
Dónde se usa
- Order files from an ERP, delivered at once
When the ERP writes a new order CSV to
/exports/orders/, it goes straight to the gateway server instead of waiting for the next batch window. Confirm first that the ERP finishes the file before saving it under its final name. - Production results from factory equipment
The output file a machine writes when a job ends moves from the factory server to the central analysis server. If the equipment keeps writing to the file, account for a completion signal or a temporary-filename convention as well.
- Delivering rendered video
When a new video file lands in the finished folder on the render server, it moves to the review server automatically. Verify that the point a large file finishes writing and the point the transfer starts are kept apart.
- Sharing inspection and quality reports between teams
When the quality inspection system produces a PDF report, it goes to the quality management server so nobody has to copy files by hand.
- Feeding files to data analysis
When an internal data processing server saves a new Parquet or CSV result, it goes to the analysis server or to supported object storage, ready as input for the work that follows.
- External receipt, then on to the internal business server
When a partner file arrives in a named folder on the existing SFTP receiving server, it is passed to the internal business server. The external SFTP receipt stays as it is, and only the internal hop becomes event-driven.
- Collecting measurements from research equipment
Every new measurement file written on a lab PC goes to the central research server, with filename and extension conditions selecting only what is to be analysed.
Guías de uso
Preguntas frecuentes
Is there a solution that sends a file to another server as soon as it appears in a folder?
INNORIX is an enterprise file transfer platform where transfer Flows between connected devices can use events such as new file creation as their run condition. Name the source folder and the target server and the transfer follows the file arriving.
Can a transfer run only when a file appears, instead of at a fixed time every day?
Yes. Event-driven transfer can be built separately from a repeating schedule. Whether new file creation in the source folder acts as the trigger, and whether detection is supported on that device and file system, has to be confirmed in your own environment.
What if the transfer starts while the new file is still being copied or written?
A file creation event and a finished file are not always the same moment. Define readiness through a method such as writing with a temporary extension and renaming to the final name, a completion signal from the program that writes the file, or supported file-stabilisation and wait conditions. Do not build on an option the product does not actually provide.
Can it transfer only when a certain kind of file, such as CSV or PDF, is created?
Include and exclude conditions let you select the extensions or filename patterns the job needs. Configure it to leave out what you do not want, such as temporary files and logs, and test the filter rules for real.
Does it still work when several files are created in one folder at the same time?
A transfer job can run in an environment where several files arrive, but the result depends on how events are detected, how parallel the runs are, how duplicate runs are handled and what the source device can cope with. Test a real burst of files and adjust the run policy if you need to.
If a new file is created while the target server is offline, is the file lost?
INNORIX provides retry and recovery for interruptions and connection problems. Event re-detection, waiting and rerun policies vary with the configuration, though, so test the offline case and confirm in Runs that nothing is missing or failed.
Does it transfer automatically when a file is modified or renamed?
The base scenario in this guide is new file creation. Whether modify and rename events are available as separate triggers has to be checked against your product version and the support in your connected environment. Do not configure new file creation alone and assume every change is detected.
Can the transfer to the other server and the record of each run be managed in one place?
INNORIX Studio manages the transfer Flows, and Runs shows run status and results. A successful transfer and successful handling of the file by the target application should be verified separately.