[
https://issues.apache.org/jira/browse/MINIFICPP-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Szasz reassigned MINIFICPP-891:
--------------------------------------
Assignee: (was: Arpad Boda)
> OPC UA Server Implementation
> ----------------------------
>
> Key: MINIFICPP-891
> URL: https://issues.apache.org/jira/browse/MINIFICPP-891
> Project: Apache NiFi MiNiFi C++
> Issue Type: New Feature
> Reporter: Jeremy Dyer
> Priority: Minor
>
> In OPC UA terminology the "server" is typically the processor that sits
> closest to the actual device generating the data. The server then collects
> the data from that "sensor" and makes the data available to upstream OPC UA
> clients. The clients will then consume that data from the server. In a
> nutshell the server is the software that reads data from devices, sensors,
> files, etc and then makes that information available to the clients over the
> OPC communication protocol.
> MiNiFi has a natural advantage at this part since we already have a lot of
> implementations to grab local data. My thought is to make this server
> implementation as something like a "Controller Service" in our world. And
> then introduce a correlating something like "PutOPCUAServer" processor. The
> controller service could be defined at a global level and there could be more
> than one of them. From there flows could be developed using all of the
> processors that are available to MiNiFi. Once the user has acquired the data
> that they want they could make a relationship to that "PutOPCUAServer"
> processor which would have a reference to the desired OPCUAServer controller
> service. This would allow for the flowfile contents and attributes to be
> placed into the server and all connected upstream clients to receive those
> values.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
