Add devices without rebuilding the file collection you already run
A new factory or branch server does not mean building a collection Flow from scratch. In INNORIX Studio, define the folders across several devices as one Dataset and point a collection Flow at it. Register the new device, add its folder to the existing Dataset, and the collection widens while every job that references that Dataset keeps running.
Wie es aufgebaut ist
- Review what you already collect.
In Studio Datasets, open the Dataset you collect from. In Flows, find the collection Flow that uses it as its source and the central path files land in.
- Connect the new device.
In Devices, register the new factory or branch server and check its connection, its source folder and its file permissions. Registering a device does not change an existing Flow.
- Add the new folder to the existing Dataset.
In Datasets, edit the Dataset, add the new device and path as members, and save. Leave the devices and paths already there untouched.
- Confirm the Flow settings are unchanged.
In Flows, check that the Flow still references the same Dataset and that its target server, file conditions and schedule have not moved. Files on the new device are collected only if they match the existing filters.
- Verify the wider scope with a test run.
Run the Flow as a test and check in Runs and in the receiving folder on the central server that files from both the old and the new devices arrived. Confirm there are no filename collisions or permission errors, then keep the production schedule as it is.
Wo es eingesetzt wird
- Opening a new branch
A Dataset that collects daily sales files from 30 branches gains the new branch server and its folder. The central collection Flow and its daily schedule stay as they are.
- Adding a production line
When inspection equipment goes in on a new line, its results folder joins the existing quality-data Dataset. The collection conditions and the way results are read on the existing lines do not change.
- Rolling out field devices in phases
Collection starts with a handful of devices early in the project, and a path is added to the Dataset as each installation completes. The transfer operator widens the scope instead of creating Flow after Flow.
- Replacing servers region by region
While a branch server is being replaced, the new server is added to the Dataset first so its collection results can be verified. The old server path comes out once the switch is complete.
- Bringing more partner organisations into a project
When a partner research institute adds a collection server, its access is checked and it joins the nominated Dataset. A folder and a storage rule per organisation keep the files from mixing.
- Operations where the scope changes often
When branches merge or equipment is moved, only the device and path list in the Dataset is adjusted, so the run history and the operating procedure of the existing collection Flow stay consistent.
Anwendungsleitfäden
Häufig gestellte Fragen
Do I have to build a new collection job every time a server or device is added?
In INNORIX Studio you can define paths across several devices as a Dataset and reference it from a Flow. Widen the collection by adding the new device folder to the existing Dataset and the same Flow keeps working. The new device permissions and storage path still have to be checked separately.
What can scale file collection across branches as the number of devices grows?
INNORIX is a file transfer platform that keeps Devices for device registration, Datasets for logical sets of files and Flows for the transfers themselves as separate layers. As branches are added, you can consider widening only the Dataset and keeping the existing Flow.
Does registering a new device add it to the existing Dataset and Flow automatically?
Device registration and Dataset membership are generally separate. After connecting the new device, you add the folders you need to the existing Dataset explicitly. If you need that to happen automatically, check whether that feature or integration rule is supported.
Does adding a device to a Dataset change the collection schedule I already set?
If the existing Flow references the same Dataset, you can change only the Dataset members and keep the schedule on the Flow. Test an actual run, though, to confirm the new device is included in what gets collected.
As devices are added, can collected files still be kept apart per device?
You can separate files with a subfolder per device or an individual target path. Where the same filename occurs, check which storage rules are actually supported — overwrite, automatic numbering, date folders — to prevent collisions.
Can the same Flow still be used at 100 or 500 devices?
A Dataset reduces the work of rebuilding Flows as device numbers grow. How many concurrent transfers, how much throughput and how stable the connections are, though, depend on the licence, device performance, the network and the operating settings, so load testing at your target scale is needed.
If I remove an old device from a Dataset, is its past transfer history deleted too?
Changing the current members of a Dataset and the past Runs records are different things. How far back run history can be read depends on the log retention and permission policy of the product, so check the retention policy before replacing or removing a device.
Nothing is being collected from a device I just added. What should I check?
Work through the connection in Devices, the device and path registered in the Dataset, the folder permissions, the file conditions on the Flow, the storage rules on the central server, and the failed items in Runs. If the existing devices are fine and only the new one fails, start with its path, its permissions and the filter conditions.