Meteorological Information Service System Based On Middleware

Since 1990s, with the development of high performance computer and meteorological communication network,the meteorological information system has made great progress. Many real-time and professional information systems has been built. People have conducted fruitful researches in the process of informatization construction. Many information systems have been developed to promote the development of meteorological data research work, take full advantage of meteorological data, provide more perfect real-time and historical meteorological data services, make the full benefits of the meteorological data. Meteorological informatization construction has made great progress in our country, but there are many defects and deficiencies:(1) Heterogeneous software and hardware platform,various database system make meteorological resource sharing more difficult.(2) With the progress of the society, the emergency of various applications, repeated development becomes more and more serious in meteorological industry.(3) The complexity of original data seriously hindered meteorological data could not be used sufficiently(4) Various meteorological information service systems are wasting resources and bring inconvenience.So, data sharing and businesses integration are two major requirements in the current meteorological industry. Middleware is independent systems software or service procedures used by distributed applications to share resources between different technologies. It locates above client/server operation system, rules the computing resources and network communications, and connects two independent applications or system software together. Through the middleware, applications can work in different operation system platforms. Users and researchers could get the desired data conveniently, without caring where the data located in. The information service system based on middleware lows the threshold for users to use the existing data resources. The MVC design pattern requires that the input, processing and output must be divided into three independent parts. According to MVC pattern, applications are divided into three core parts: model, view and controller, which deal with its own tasks. So, it brings low coupling, high reusing and strong applicability to the software system. Model layer could be divided into business layer and lasting layer also. This layered policy offers two choice options for business integration. It could be integrated in two layers, view layer and business layer. In this paper, latter one is selected. That is, all of the business system component-based designs are deployed to business layer.As meteorological expert systems and numerical weather forecasting systems are complex applications, the implementation of component-based design is feasible. With expert system for example, it includes six core parts: knowledge library, reasoning machine, database, man-machine interface, interpretation and knowledge acquisition machine. Reasoning machine can be divided into six models: interaction management, rule processing, variable processing, sentence processing, knowledge library scanning and data maintenance. All of these models could be designed and deployed in the form of components. Some technologies as Java expert system shell guarantee for the implementation of layered design. Similarly, the other business systems in the meteorological industry can also be designed and deployed in the form of components. Through the analysis of middleware technology and research, a layering design scheme based on MVC is proposed in this thesis. And many existing meteorological service systems are componented and deployed to the bussiness layer of system respectively.