The deliverable D3.3 “1st Data collection from resources virtualization: legacy systems integration” focuses on a methodology to specify the set of necessary tools for the development of a continuous data collection system from legacy systems interconnected to the C2NET platform. It addresses data acquisition according to two principles: the first is to acquire data as soon as it is available on legacy systems, the second is to use advanced research queries to find data.
Results arising from this work will contribute to a plug-and-play component that will be integrated in the T3.4 platform “Cloud enabled Collaborative Manufacturing Business”.
The solution presented in this document relies in the concept of a legacy system hub that will act as a subcomponent of C2NET company middleware, responsible for addressing the interactions made with legacy systems. In contrast, IoT hub presented in D3.1 “1st Data Collection from real-world resources: IoT devices” will focus on data gathering from IoT devices.
The legacy system Hub is composed by a set of two sub-components that tackle different issues: enterprise service bus (ESB) and data adaptation. ESB is used for enabling the communication between both legacy systems and C2NET platform, granting interoperability between different protocols, while data adaptation component is used to provide a unified view of data coming from heterogeneous legacy systems.
Furthermore, legacy system hub ensures that data obtained from legacy systems is trusted and secure. On one hand, one or more solutions, already defined in the deliverable D2.5 “Security policies specification”, can be used to prevent C2NET platform from attacks and unauthorized data access. On the other hand, legacy systems should, in turn, provide non-repudiation contracts as well as secure and trust options.
In short, this deliverable provides a solution based on ESB technology and data adaptation technics to collect data from legacy systems. It also discusses ways to acquire data using such approach. However, it does not give a detailed list of operations that legacy system hub component should provide as this depends on the needs and capabilities of other components. For instance, automatic discovery of legacy systems in the network will depend on the availability of features in Pilots’ legacy system software enabling such operation. Next WP3 efforts will respond to these concerns among other tasks.
The deliverable is organized according to the two following parts:
- Part I represents a synthesis of the deliverable and gives a quick overview of its content;
- Part II presents the deliverable contributions which cover:
- An analysis of data collection requirements coming from other project deliverables;
- A literature review on data virtualization techniques;
- A solution for legacy systems data virtualization;
And finally a conclusion is provided with a summary and hints at future work directions.