Monitoring data exchanges between information systems

Information systems tend to be more and more attached to one another and exchange increasingly more data amongst each other. As the number of data exchanges increases, it becomes more and more challenging to sustain an overview of how these data exchanges are performing. This is particularly an issue for application service providers which host systems for customers since they host multiple systems and each system could have multiple data exchanges. However, there are monitoring tools available which monitor the states of systems, there aren’t any tools available to monitor the functional aspects of data exchanges. For that reason lack of oversight on the functional performance of data exchanges, problems can be unnoticed and customers may become disappointed. The goal of this research is to create a reference architecture for systems which may provide central monitoring of data exchanges with the possibility of aggregating information on different data exchanges into useful diagnostic reports. The scope of this analysis is centered on monitoring only at the target system of a data exchange…


1 Introduction
1.1 Motivation
1.1.1 Background of the topic
1.1.2 About the company
1.1.3 Current situation
1.1.4 Desired situation
1.1.5 Difference between the current and desired situation
1.1.6 Problem definition
1.2 Research objective
1.3 Research approach
1.4 Report structure
2 State of the art
2.1 Data exchanges between information systems
2.1.1 Architectures of data exchanges
2.1.2 Layers of data exchanges
2.1.3 Timeliness of messages
2.2 Possible failures in data exchanges
2.2.1 Failures in network communication
2.2.2 Application failures
2.3 Data quality
2.4 Monitoring concepts for data exchanges
2.4.1 Methods of monitoring Monitoring data exchanges between information systems
2.4.2 Levels of monitoring
2.4.3 Polling versus publish and subscribe
2.4.4 Reporting results of monitoring
3 Case study on failures of data exchanges
3.1 Web service data exchanges of the Hogeschool Utrecht
3.1.1 Reasons for failures that have occurred
3.2 Scribe data exchange Hogeschool Utrecht
3.2.1 Reasons for failures that have occurred
3.3 BizTalk data exchange between Peoplesoft and Microsoft CRM of ROC van Amsterdam… 22
3.3.1 Errors that can occur
3.4 Combined results of this case study
3.4.1 Errors resulting from the contents of data
3.4.2 Errors in middleware
3.4.3 Connection and performance errors
3.5 Mapping of errors to data quality
4 Monitoring reference architecture
4.1 Components of the architecture.
4.2 Monitoring requirements of the architecture
4.3 Monitoring process steps
4.4 Contents of monitoring information
4.5 Events that must be monitored
4.6 Requirements of the central monitoring server
4.7 How this reference architecture improves data quality
5 Assessment of technical alternatives
5.1 Hyperic
5.1.1 Monitoring plugin
5.1.2 Central monitoring server
5.1.3 Monitoring data collection mechanism
5.1.4 Conclusion
5.2 WSMonitor
5.2.1 Monitoring plugin
5.2.2 Conclusion
5.3 SoapKnox
5.3.1 Monitoring plugin
5.3.2 Conclusion
5.4 ManageEngine
5.4.1 Monitoring plugin
5.4.2 Central monitoring server Monitoring data exchanges between information systems
5.4.3 Monitoring data collection mechanism
5.4.4 Conclusion
5.5 Scribe
5.5.1 Monitoring plugin
5.5.2 Monitoring data collection mechanism
5.5.3 Conclusion
5.6 soapUI
5.6.1 Monitoring plugin
5.6.2 Conclusion
5.7 Log4Net
5.7.1 Monitoring plugin
5.7.2 Conclusion
5.8 Microsoft Dynamics CRM
5.8.1 Central monitoring server
5.8.2 Conclusion
5.9 Conclusion on technical alternatives for monitoring
6 Our prototype
6.1 Components and architecture
6.2 Requirements
6.2.1 Aggregate data from different sources which may use different technologies
6.2.2 Monitor syntactic and semantic aspects of data exchanges
6.2.3 Support real time and deferrable messages
6.2.4 Detect patterns in data exchanges
6.2.5 Report different types of failures
6.3 Monitoring web service data exchanges
6.4 Monitoring Scribe data exchanges
6.5 Monitoring semantics
6.6 Central monitoring server
6.7 User experience of the central monitoring server
6.7.1 General interface
6.7.2 Following up alerts
6.7.3 Viewing batch results
6.7.4 Viewing semantic results
6.8 Collection mechanism
6.8.1 Collection of data from web service data exchanges
6.8.2 Collection of data from Scribe data exchanges
6.8.3 Collection of semantic results
6.9 Summary of how the prototype meets the requirements Monitoring data exchanges between information systems
6.10 Monitoring the monitor
6.11 Security aspects
6.12 Interoperability…

Source: University of Twente

Download URL 2: Visit Now

Leave a Comment