Tie the folders on 100 devices into a single collection target
Define the per-device folders scattered across plants, branches and sites as a single Dataset in INNORIX Studio. Manage several devices and paths as one logical set of files without copying the real files to one place first, and reuse that set as the source of a collection Flow. When the devices or folders change, edit the Dataset to keep or extend the collection target.
Comment c'est construit
- Prepare the devices you collect from.
In Studio Devices, confirm the branch and plant servers that hold the files and the central collection server are connected. Check the permission to reach the source folder on each device as well.
- Create a new Dataset.
In Studio Datasets, give it a name that shows what it is for, such as
Factory Daily Reports. - Add the folders from several devices.
Register the path to collect from on each device as a Device + Path entry. At a scale of 100 devices, set it up so a different folder path per device can still sit in one Dataset.
- Use it as the source of a collection Flow.
In Flows, select the Dataset you created as the source set of files and set the target path on the central collection server and the storage rules. Split folders per device in case identical file names collide.
- Verify the run result and what the target covers.
On a test Run, check the devices and paths actually included, the file count and the failed items. When a new device is added, reflect it in the Dataset and test again that the Flow includes that device as intended.
Où c'est utilisé
- Consolidating production results from 100 plants
Different folders on the MES server at each plant,
/export/production/and/results/for example, are defined as one production results Dataset and collected to a central analytics server. - Standardising the log collection target across branches
Even where the log path differs by branch, each device path is registered in a
Branch Application LogsDataset, so the collection Flow is not maintaining a list of individual paths. - Consolidating result files from research and inspection equipment
The data folder on each measurement device is tied into one Dataset, and the same set of files is reused by whichever collection job needs it.
- Changing the collection target as sites open and close
Add a new site device to the Dataset or drop a device that has been retired, then review how the existing collection Flow is configured and what it actually runs against.
- Using the same set of files for different jobs
Referencing one Dataset from several Flows, central collection and delivery to another server for instance, saves writing the same target definition twice.
- Managing non-standard folder paths per site
Register the real path on a legacy server that was never standardised, exactly as it is, and the collection target holds together logically without reorganising the server directory structure.
Guides d'utilisation
Questions fréquentes
Is there a way to manage folders scattered across 100 servers as one file collection target?
A Dataset in INNORIX Studio defines the folders on several devices as one logical set of files. Use a Dataset with its devices and paths registered as the source of a collection Flow and large-scale distributed folders are managed as a single unit of work.
If folders on several servers are tied into a Dataset, are the files actually copied to one place?
No. A Dataset is a logical set of the files that sit on several devices. To gather the files on a central server, you build and run a separate collection Flow that uses the Dataset as its source.
Can devices with different folder paths still be tied together?
Yes. A Dataset registers Device + Path combinations, so the path can differ per device. Which paths can be registered, and the access permissions, have to be confirmed against the connection environment of each device.
When collecting from 100 devices, do the source devices have to be selected again in every Flow?
Define a Dataset as the shared source set and it can be reused across several Flows. Which file conditions and storage paths each Flow uses is still set per job.
When a new site is added, does the existing file collection job have to be built again from scratch?
Usually not: adding the new device and folder to the Dataset extends the existing logical collection target. How an existing Flow references the changed Dataset, and whether the schedule, permissions or storage rules need further changes, has to be confirmed by testing.
How is a Dataset different from ordinary folder synchronisation?
A Dataset defines file locations across several devices as one logical target. Folder synchronisation is a transfer action that moves and updates file content to match a nominated target. Creating a Dataset does not synchronise files on its own.
If some of the devices are offline, is the whole Dataset unusable?
The logical makeup of a Dataset and the state of an actual transfer run are separate. When a collection Flow runs, a transfer may succeed, wait or fail depending on the connection state of each device, and you check that run in Runs and recover the devices that need it.
Can identical file names from hundreds of devices be kept from colliding on the central server?
Configure a target folder per device, a folder per date or a stored file name rule in the collection Flow as appropriate. Do not assume a Dataset renames files for you; verify collision handling with the storage rules in the actual Flow.