1. Architecture
1.1. ICONIS SMART Bus
1.1.1. Bridge between MDM and External systems
1.1.2. Scallable systems for handling possible MDM
1.1.3. Scalable system for handling multiple transport layer(for Ex ESB).
1.1.4. XML:Manipulation
1.1.4.1. MDM is invariant.
1.1.4.2. External systems interested XMLs scattered over multiple nodes in MDM
1.1.4.3. On the runtime, XML needs to be transformed
1.1.4.3.1. XSLT Engine used for XML transformation
1.1.4.3.2. Multiple XML input cannot be given in XSLT engine.
1.1.4.3.3. Multiple XDTC components provded for transformation and merging purpose
1.1.5. Transport Plugins
1.1.5.1. For every transport, need to write the Transport Plugins
1.1.5.2. Writing Transport plugins needs to follow some interfaces specifications
1.1.6. Validation Engine
1.1.6.1. The output to external systems needs to validated before sending.
1.1.6.2. For XML, we can use the XSD. But it will be useful only on the syntax. But semantics also needs to be verified. For txt file, need seperate validation code.
1.1.7. MDM IO manager
1.1.7.1. Has to query/subscribe to multiple nodes in the MDM
1.1.7.2. Connecting sessions to the MDM will be shared among the multiple MDM plugins(Each has interest on only particular tree nodes)
1.1.7.3. Has Node cache manager for the maintaining the comon node values.
2. Tasks(Could be)
2.1. Direct connection with MDM
2.1.1. Need to Access MDM with OPC UA access tool kit
2.1.2. Need to frame the expected XML/any output
2.1.3. Communicate with the mediume which external system understands.
2.2. with ICONIS SMART Bus
2.2.1. Generating new XSLT script for XDTC component for XML transformation
2.2.2. Coding the Validation engines
2.2.3. Creating new Transport Plugins(Like ESB)