Each IIoT IS Import widget needs to know what java class (i.e., program) to run, in order to process the input file and store to 4D Analytics.
The choices of java classes available are provided by the IIoT Framework page.
All the available classes are listed here. New classes can be added, and redundant ones removed.
- eB Data Collector:
- Exor Inspections DC:
- GenericCSVFileImporter_1:
- GenericCSVFileImporter_2:
- GenericCSVFileImporter_3:
- GenericCSVFileImporter_4:
- JCalc Wrapper:
- PI DA IoT IS:
- PI AF IoT IS:
- SSRS Data Collector:
- Template & Replication DC:
- Standard Alarm Notification:
- Report e-mailer:
- Open Scripting Process:
- High Volume Data Ingester:
- Generic Structure Manager:
- Influx to SQL Importer:
- Azure IoT Data Ingestion:
- Weather Service:
- Post Defined Calcs Processor:
- High Volume Data Ingester - SQL Variant:
- APM Export Event Processor:
- Data Workpack Save In Background:
- OPC HDA Data Collector:
To Link Ingestion Services within the IIoT IS Widget:
Use this functionality to run a linked ingestion service when the current importer finishes.
- To set this up, expand the drop-down and select the IIoT IS widget to which you wish to link.
- Set the Run Status.
- The linked importer can be run if the current one fails, completes, or completes with errors. If none are selected, it will not run.
- Give the IIoT IS widget a heading that will appear in the list of available importers to which you may link.
- On the pop-up, review all linked importers and their chains.
This is the same dashboard, showing the Schedule tab of each widget.
In this example, only the first in the chain has a schedule configured, then triggers the 2nd IIoT Framework , which triggers the 3rd and then the 4th. Note that there are options of which Status is required for the next IIoT Framework to be triggered. In this example they are all On Success or On Completed with Errors.
Once the IIoT Framework chain is configured, view a summary of it by clicking one of the VIEW LINKED IIoT IS buttons.
