RxNetworking App). The article Reactive Networking of Semantic-Data Library covers a description of the architecture supporting the reactive communication design pattern. The
RxNetworking Appis an aggregation of
Consumerentities derived from
DataRepository. They must provide interconnection to real-time process data, hence they are recognized as an extension of the
AzureGatewaypart fulfills the
Consumerrole and uses out-of-band communication to push telemetry data to the cloud.
Consumerrole of the
RxNetworkingapplication. It is an example of
Semantic-Datareactive networking based on OPC UA PubSub specification. The document OPC UA PubSub Main Technology Features covers a description of selected fetuses relevant to this specification.
DataRepositoryconcept. This workout will be described in an independent article. To get the full story and your copy check out the preprint from Research Gateway: Object-Oriented Internet - Azure Interoperability. Main purpose of this preprint it to enable an early community review. We will consider your contribution to be applied to the final version of the article.
Consumerrole in the application:
DataManagementSetup: this class has been overridden by the
PartDataManagementSetupclass and it initializes the communication and binds data fields recovered form messages to local resources.
IMessageHandlerFactory: have been implemented in external common libraries and
Consumerdoesn't depend on this implementation - current implementation of the interfaces is localized as services using an instance of the CommonServiceLocator.IServiceLocator interface.
IBindingFactory: has been implemented in the class
PartBindingFactorythat is responsible to gather the data recovered from the
Messageinstances pulled from the
Distribution Channel. The received data is driven to the Azure services using configured out-of-band protocol.
IConfigurationFactory: the class
PartConfigurationFactoryimplements this interface to be used for the configuration file opening.
PartDataManagementSetupconstructor initializes all properties, which are injection points of all parts composing this role.
DataManagementSetup.Start()method is called to initialize the infrastructure, enable all associations and start pumping the data.
DataRepositoryrepresents data holding assets in the
RxNetworking Appand, following the proposed approach, the
IBindingFactoryinterface is implemented by an external part. It captures functionality responsible for accessing the process data represented by the
LocalResourcesrepresents the external part that has a very broad usage purpose. For example, it may be any kind of process data source/destination, and to name a few
OPC UA Address Space Management,
Azurecloud-based front-end, etc.
AzureGatewayfunctional package has been implemented based on the
Consumerconcept. This particular
PartBindingFactory) implements the
IBindingFactoryinterface to gather the data recovered from the
Messageinstances pulled from the
Distribution Channel. The received data is driven to the Azure services using configured out-of-band' protocol. An instance of the
IBindingFactoryis responsible to create objects implementing
IBindingthat can be used by the
Consumerto forward the data retrieved from
NetworkMessagreceived over the wire to Azure services.
DataRepositoryand associated entities, i.e.
Producercan be implemented as external parts, and consequently, the application scope may cover practically any concern that can be separated from the core OPC UA PubSub communication engine implementation.
UAOOI.Configuration.Networking. In a typical scenario, this implementation should not be considered for further modification. The only open question is how to provide the name of the file containing the configuration of this role. This role uses an independent configuration file: