In fact, the project draws its data from various sources created and supported by autonomous structures. This data is stored in databases or is available in digital format.
Factory data reset – Import existing data. The system must take into account the heterogeneity of data sources not only with respect to the type of data (text files, cartographic images, etc.). The optimal situation will correspond to the situation when all databases will be accessible via the Internet. Under these conditions, it would be possible to transfer certain queries to remote databases or to perform processing on particularly suitable remote sites.
This solution is far from feasible in the short term, because the current state of the IP connection of sites participating in the project does not reach the performance required for this approach. However, the network must have the largest number of databases.
Data will be transferred from the source to the centralized site using standard methods:
1. FTP for remote data.
2. Import methods for source databases that interact with a rotary database engine.
3. Link for source databases whose driver is associated. It should be noted the presence of drivers between all standard market. For data that is not connected to the network, information will be transferred to a centralized database using floppy disks, tapes or CDs. Storage and organization of data. In this presentation, we assume that some of the data available on online sites is not duplicated on the main project site.
Reboot vs reset. All available data should be organized in order to optimize the response time to user requests. The following will be stored on a centralized site: Predefined query templates that provide the most representative data results and their processing. It will also provide guidance on the capabilities of the system for users who wish to formulate specific queries.
Big data, such as images often requested by various requests, will be duplicated on the central site. Finally, all the data whose sources are not on the Internet. To ensure the reliability of the results, it will be necessary to determine the frequency of updating information. Indeed, all relevant project data is not completely centralized; large hardware (large amount of memory) and complex procedures are required to update it to ensure that actual data received from remote sites is updated.
Access to project information will be via the Internet through a web interface. The global model of this interface distinguishes three levels: Web client supported by a standard browser. Web server managing HTML pages. A database containing information system information. Between these three components, different gateways and protocols are used, which will be discussed later in this document.
Usually this is the HTTP protocol, which serves as a bridge between the client and the web server, the latter plays two important roles, namely, on the one hand, it stores HTML pages to provide them on demand to web clients. and, on the other hand, invoke applications through an interface to generate dynamic HTML pages for web clients (registration forms). In particular, through the interface, the web server can encapsulate queries (SQL) into databases and generate, as before, dynamic HTML pages containing the desired results. For example, for an application that processes query processing through ODBC, the following steps can be distinguished: – Selecting a data source – Connecting to a source – Sending a query in the form of SQL statements – Receiving and processing possible query results and / or received errors. – Check or cancel the transaction. – Disabling the database. Figure 1 below provides an overview of the proposed system. Note the presence of two channels connecting the application with a centralized database, on the one hand, and a set of industry databases, on the other.
Cyber reboot. In this case, we can create an HTML form that refers to a file into which the entered values are passed as parameters. The SQL file command, in turn, passes parameters to the stored procedure. Thus, stored procedures allow you to develop more complex applications. They provide verification of entered values, insert / update / delete rows in several tables in one transaction, and also increase access security by limiting, for example, permissions granted to an Internet user account.