RU2324974C1 - System of interaction automatic control system databases - Google Patents

Abstract

FIELD: computer engineering.

SUBSTANCE: system includes input, registration, statement, data processing and collection units from remote users, and input, registration, statement, data processing and collection units within central database, as well as central and local databases change units. System is additionally provided with tributary unit between system levels. This unit is two-way connected with every system unit mentioned above, with synchronization control unit with inputs connected to inputs of central and local databases change units, as well as to channel access delimiter, unit of central and remote SQL sever databases synchronization, unit of information input-output within database exchange in file server local database. The result is achieved due to separation of channels and interaction of central and local database from remote users.

EFFECT: effective and reliable information interchange within automated control of budgetary process.

11 cl, 12 dwg

Description

The invention relates to computer technology, and in particular to data collection and processing tools designed to manage the budget process at the regional level (the level of the subject of the Russian Federation and the municipality), and can be used, in particular, in the implementation of budget planning processes (including medium-term), financing, accounting, reporting, including the treasury method of budget execution, for the level of the financial authority, the main managers of budget funds and budgetary institutions.

One of the tasks of the budget process management system at the regional (municipal) level, which is an information system of the OLTP (OnLine Transaction Processing) class with a complex information base structure, large central database volumes and a large number of both local and geographically remote users, is the need to ensure a coordinated the work of several thousand users in data update modes in the absence or high cost of high-speed channels that provide acceptable characteristics for I have the highest possible schedule. Implementation of such a system by the traditional mechanisms of client-server applications has not yet seemed possible due to technical and financial constraints.

This necessitated the development of an original system for the interaction of central and local databases of remote users in the context of a continuously continuing growth in volumes and complexity of the information structure, an increase in the number of users and an increase in their information needs.

Numerous information systems are known, including a central server (central database) and a large number of remote users, including those connected to local networks, between which information flows are exchanged.

So, the Automated system for providing information on debts and payments of consumers of services according to the patent of the Russian Federation No. 2252515, G06F 17/60, publ. 07/10/2005, designed to create and store a central information database on a database server, generate and transfer requests from users to this database, process them using the appropriate system units and present them in one form or another (in electronic or on paper) results (responses to inquiries).

In this automated system, each of the terminals installed at payment acceptance points from service consumers and service providers is connected via a data transmission network to a unit for storing and processing information about debts and payments of service consumers, which includes the first means of communication with the terminals installed in payment reception centers, a second means of communication with terminals installed at service providers, and a database server comprising a system for registering system participants, a data storage unit, a control unit I invoices and payment documents forming unit, which interfaces are connected to the first communication means, and further comprising forming unit outbound registers, registers incoming processing unit and forming unit of payment documents.

The known device allows for the entire exchange of information, including the formation of requests and receiving answers, via electronic communication channels, which greatly facilitates the process of making payments for subscribers.

However, the known system is characterized by limited functionality and speed, high time and material costs for collecting, processing and providing information, low reliability of the system, which is due to the fact that user requests are implemented by searching the entire database and their subsequent processing in the buffer database server memory, which with large amounts of data, and most importantly, with a large number of users of the system, inevitably leads to a significant sweat time frame to get the result.

Also known is a System for managing transactions under the patent of the Russian Federation No. 2158956, G06F 17/60, G06F 157: 00, publ. November 10, 2000, chosen as a prototype in its technical essence, which consists in the presence of many remote users of the system, a central computer with a central database installed on us, between which information flows in the form of concluding contractual relationships and conducting financial transactions.

The known system comprises a plurality of control devices for system participants connected via a communication channel with a certificate storage and verification device and a centralized management device, which includes a system participants registration device, a database generation and storage device for operations performed between system participants, a device for generating and storing a database of agreements concluded between participants in the system, a data management device related to financial marketing operations, a device for monitoring and analyzing the transaction process between system participants, a device for managing the transaction process, as well as devices for generating and storing databases for system participants, for goods and services, and a document management device. In this system, each of the control devices for the participants of the system, together with the device for storing and verifying the certificates of participants, designed to identify the participant, functionally represents a block for input, registration and processing of the initial information of remote users, i.e. centralized control device data is functionally similar to devices (blocks) for making changes to these databases.

However, this well-known system is characterized by the same drawbacks as the previous one, namely, the limited speed and low reliability of the system, due to the fact that the fulfillment of user requests with constantly increasing volumes of information, as well as with a large number of participants in the system (in particular, exceeding 1500 -2000) requires a large investment of time and technical means to obtain a result. To reduce time costs, each of the participants in the system can use high-speed, but at the same time very expensive communication channels, but this will lead to a significant increase in the cost of using the information system, which ultimately reduces the overall performance of the system, especially for budgetary institutions.

The claimed invention solves the problem of creating a highly efficient and reliable automated budget process management system at the regional (municipal) level, which at the same time has a fairly high speed, by optimizing the ratio of quality and cost of information exchange between the participants of the system by separating communication channels and ensuring the interaction of central and local databases remote user data.

The technical result is achieved by introducing interconnected blocks and modules into the system that provide such a separation of channels and optimizing the synchronization process of local and central database data, thereby creating the ability to access central database information via low-speed switched channels.

The problem is achieved in that the automated control system, comprising at least two blocks of input, registration, approval, processing and compilation of information of remote users and block input, registration, approval, processing and code of information in a central database, which are respectively the first, second and third information inputs into the system, as well as the unit for making changes to the central database and the unit for making changes to the local database, is additionally equipped with a data transfer unit between the levels of the system, connected by two-way connections with each of the above system units, the synchronization process control unit, the inputs of which are connected to the outputs of the unit for making changes to the central database and the unit for making changes to the local database, as well as the unit for sharing access to communication channels, a synchronization unit for central and remote SQL server databases, an input / output unit for exchange database information with a file-server local database, each of which is connected by two Oron communication with the control unit synchronization process, and block the interaction of the primary server and server replicas-connected bilateral connections to database synchronization unit and the central SQL server and the remote unit IO base exchange data information with file-server local database.

In addition, each of the two blocks of input, registration, approval, processing and collection of information of remote users is made in the form of series-connected by two-way communication device for collecting and issuing information, including a series-connected recording device, data input module, data receiving module and control module, devices version descriptions of the local database, transaction execution device, and information storage and collection device, including a control module and xp module connected by two-way communication neniya and data vault.

In addition, the data input, registration, approval, processing and data compilation unit in the central database is made in the form of information collection and output devices connected in series with two-way communication, including a registration device, data input module, data receiving module and control module, storage devices and a code of information, including a control module connected by a two-way communication and a data storage and code module and a transaction execution device.

In addition, the data transfer unit between the levels of the system is made in the form of series-connected devices for registering a user, a device for determining the last session for a given user, a device for starting a new session and a device for performing operations, the device for registering a user and a device for determining the last session for a given user connected by two-way .

In addition, the unit for making changes to the central database is made in the form of series-connected devices for saving changes and updating the database, devices for updating and generating tables and devices for updating routine reports, as well as devices for controlling the sequence of procedure calls connected by two-way communication with the device for saving changes and updates base and device updates and table formation.

In addition, the unit for making changes to the local database is made in the form of series-connected devices for creating table replicas for creating LBDs and performing synchronization procedures on the replica server, devices for receiving LBD changes on the replica server and transferring LBD changes from the replica server to the main server , devices for creating on the replica server copies of the local database tables and devices for transmitting changes to the LBD.

In addition, the synchronization process control unit is made in the form of series-connected devices for creating handlers in the client application, devices for creating an operation manager in the client application, devices for creating a meta-information base for the synchronization process, central server load control devices, and queue management devices.

In addition, the unit for sharing access to communication channels is made in the form of series-connected devices for identifying the rights and authorities of user groups, a device for sharing access to individual communication channels, an access control device and a device for synchronizing technological processes and remote access sessions, the output of which is also connected to the second input access sharing devices over separate communication channels, and an access control device and a sharing device are accessible pas over separate communication channels are connected to two-way communication.

In addition, the database synchronization unit of the central and remote SQL servers is made in the form of a series-connected device for updating the layout structure located on the remote server, a device for transmitting data to the central database, and a device for receiving data from the central database.

In addition, the input / output block of the exchange database information for the file-server LBD is made in the form of series-connected devices for fixing the status of the local database, a device for transmitting LBD changes to the central database server, a device for making changes to the CBD server, and devices for making changes to the CBD server and devices for creating and storing copies of the LBD at the time of synchronization, and the output of the device for making changes from the server of the CDB is also connected to the input of the device for making changes to the server of the CBD, and the output of the device is created I keep copies LBD at the time synchronization is also connected to an input device changes to the CDB server.

In addition, the interaction unit between the main server and the replica server is made in the form of series-connected devices for generating a list of replica database objects by types, devices for copying object descriptions from the main database to the replica database, devices for creating or re-creating descriptions for replication, data loading devices a copy of the local database on the replica server, as well as the request description device in the meta-information tables and the device for generating record identifiers in the buffer tables, and the copier device Nia descriptions of objects from the primary database to the replica database, device creation or re-creation of descriptions for replication and device for loading data into a local copy of the database on the server-connected replica of bilateral relations with the main database and database replica servers.

The essence of the claimed invention lies in the fact that by introducing into the system such interconnected units as a synchronization process control unit, a database synchronization unit of central and remote SQL servers and a unit for sharing access to communication channels, such an organization of the data exchange process is achieved that provides separation information flows and, at the same time, optimization of the process of synchronizing data of local and central databases. In addition, the use in the system of the interaction block between the main server and the replica server with the corresponding database reduces (distributes) the load on the central server, which also helps to increase the speed and reliability of the system.

The invention solves the problem - to provide for the class of "remote" users (that is, those users for whom it is impossible (or not required) to directly work with the central database server) the process of synchronizing data from the local and central databases, thereby creating the ability to access information central database for low-speed dial-up channels. At the same time, the creation of a highly efficient and reliable automated budget process management system is ensured, which allows it to operate in the context of continuously continuing growth in volumes and complexity of the information structure, an increase in the number of users and an increase in their information needs.

The invention is illustrated by drawings, in which Fig. 1 shows a general block diagram of a database interaction system, Fig. 2 shows an example of a specific implementation of an input, registration, approval, processing and information consolidation unit (AWP of the main managers of budget funds), Fig. 3 is an example of a specific implementation of the input, registration, approval and information processing unit (AWP of an employee of a budget institution), and FIG. 4 is an example of a specific implementation of the input, registration, approval, processing and information gathering unit in the center Fig. 5 is an example of a specific implementation of the data transfer unit between the levels of the system, Fig. 6 is an example of a specific implementation of the unit for making changes to the central database, and Fig. 7 is an example of a specific implementation of the unit for making changes to the local database , Fig. 8 is an example of a specific embodiment of a synchronization process control unit, Fig. 9 is an example of a specific embodiment of a unit for sharing access to communication channels, and Fig. 10 is an example of a specific embodiment of a central database synchronization unit Fig. 11 shows a diagram of an input and output block of exchange database information at a file-server local database (LBD), Fig. 12 is an example of a specific implementation of an interaction block between a main server and a replica server.

The database interaction system contains a unit 1 for input, registration, approval, processing and a set of information (AWP of the main budget funds manager), a unit 2 for input, registration, approval, processing and a set of information (AWP for an employee of a budget institution) and storage of central objects and information database and unit 3 for input, registration, approval, processing and collection of information in a central database, each of which is connected by two-way communication with unit 4 for data transfer between system levels. Moreover, each of blocks 1, 2, and 3 performs the function of the information input of the system.

In block 4, the registration of data (documents) coming from each of blocks 1, 2 and 3, their identification, recording to appropriate devices, further storage and transfer between levels of the system.

From the data transmission unit 4 between the levels of the system, information signals are fed to the synchronizing input of the unit 5 for making changes to the central database or unit 6 for making changes to the local database, depending on the level of input, registered and stored data (documents) of the system, and the synchronizing outputs blocks 5 and 6 are connected to the inputs of the block 7 control the synchronization process. During synchronization, devices are used to identify entered documents, their status, and to identify changes made.

The first output of the synchronization process control unit 7 is connected to the second input of the local database modification unit 6, the second output and the first input of unit 7 are connected to the access channel for the communication channels 8, the third output and the second input of unit 7 are connected to the base synchronization unit 9 data of the central and remote SQL servers, the fourth output and the third input of block 7 are connected to the input block 10, output information exchange database with a file server local database (LBD), and the fourth input of block 7 is connected to toromu output unit 5 changes to a central database.

The input / output block 10 of the exchange database information at the file server local database (LBD) is connected by the second synchronizing input and the second synchronizing output to the interaction block 11 of the main server and the replica server, which, in turn, is its second synchronizing input and the second the synchronizing output is connected to the block 9 for synchronizing the databases of the central and remote SQL servers with the server database of the remote user.

All blocks of the claimed system in the above example of its implementation are implemented using software and hardware on standard personal computers.

Specific examples of the execution of individual blocks of the system are given below.

Block 1 input, registration, approval, processing and arching of information (AWP of the main managers of budget funds) (Figure 2) contains sequentially connected by two-way communication device 1.1 for collecting and issuing information, device 1.2 for describing versions of the local database, device 1.3 for storing and collecting information and device 1.4 transaction execution.

At the input of block 1, through the device 1.1 for collecting and issuing information in electronic form, information is entered on the functional complexes of AWSs of remote users - the main managers of budget funds. To do this, the source data from paper media through module 1.1.2 data entry is loaded into a local database (LBD). When entering, the user is registered through the registration device 1.1.1. Then the data is transmitted through the data receiving device 1.1.3, where all the details of the input fields are filled in, to the control device 1.1.4, where the control is carried out on the completeness and correctness of filling in the input forms.

Device 1.1 for collecting and issuing information is based on the description of the created local database (LBD). Such a description is stored on the device 1.2 of the local database version descriptions in the form of a relationship system, which includes:

- table tables

- Table field tables

- table index tables

- Table index table fields

- Table link tables

- Table of table link fields.

To reflect changes in the structure of the base there is the concept of a version of the base. Information from the device 1.2 of the description of the versions of the database is transmitted to the input of the device 1.1 of collecting and issuing information and, thereby, ensures the operation of a specific version of the client application with the database of a specific version, i.e. with specific modules for input, reception and control of data. Device 1.2 of the local database version descriptions automatically fills in a new version of the LBD structure descriptions (descriptions for all versions of the local database structures are stored in the central database), comparing the current structure of the central database with the latest version of the structure description.

Data from the device 1.1 for collecting and issuing information is fed to the input of the device 1.3 for storing and collecting information, where, getting into the module 1.3.1 control, control is carried out on the conformity of the data storage structures with the entered data. Then, the monitored data goes to the input of the data storage module 1.3.2, where, depending on the storage organization (server or file-server organization of the storage module) and in accordance with the version of the local database, it is stored on the corresponding storage media. In addition to the actual data transferred to this module, a description of the database version is also stored, as well as the previous state of the database at the time of the last synchronization.

All actions related to changing the database data and database descriptions are performed in the transaction execution device 1.4. All procedures that lead to a change in the database go to the input of the transaction execution device and are logged, in particular, the called procedures and their parameters are logged, as well as the contents of the worksheets received from the client and used by the procedure during execution.

After the synchronization process, the data is updated on the device 1.3 storage and data vault. Data compilation is carried out at the level of the main managers of budgetary funds in accordance with their role in the technological process. At the output of the information storage module 1.3.2, in accordance with the rights of a registered user, output results are generated that are received at the input of the control module 1.1.4 of the information collection and delivery device 1.1, and then output to paper and electronic media in the form of reports or viewing forms ( processing non-regulatory requests).

Block 2 input, registration, approval and processing of information (AWP employee budgetary institution) (Figure 3) contains sequentially connected by two-way communication device 2.1 for collecting and issuing information, device 2.2 for describing versions of the local database, device 2.3 for storing and compiling information and device 2.4 for execution transactions. At the input of block 2, through the device 2.1 for collecting and issuing information, information is entered on the functional complexes of AWSs of remote users - budget institutions. To do this, the source data from paper media through module 2.1.1 data entry is loaded into a local database (LBD). When entering, the user is registered through the registration device 2.1.2. Then the data is transmitted through the data receiving module 2.1.3, where all the details of the input fields are filled in, to the control module 2.1.4, where the control is carried out for the completeness and correctness of filling in the input forms.

Device 2.1 of collecting and issuing information is based on the description of the created local database. Such a description is stored on the version description device of the local database in the form of the following relationship system:

- table tables

- Table field tables

- table index tables

- Table index table fields

- Table link tables

- Table of table link fields.

As mentioned above, to reflect changes in the structure of the database there is the concept of a version of the database. Information from the device 2.2 of the description of the versions of the database is transmitted to the input of the device 2.1 of collecting and issuing information and, thereby, ensures the operation of a specific version of the client application with the database of a specific version, i.e. with specific modules for input, reception and control of data. The device 2.2 of the local database version descriptions automatically fills in the new version of the LBD structure descriptions (the central database stores descriptions for all versions of the local database structures), comparing the current structure of the central database with the latest version of the structure description.

Data from the device 2.1 for collecting and issuing information is fed to the input of the information storage device 2.3, where, getting into the control module 2.3.1, control is carried out on the compliance of the data storage structures with the entered data. Next, the controlled data goes to the input of the data storage module 2.3.2, where, depending on the storage organization (server or file server organization of the storage module) and in accordance with the version of the local database, it is stored on the respective storage media. In addition to the actual data transferred to this module, a description of the database version is also stored, as well as the previous state of the database at the time of the last synchronization.

All actions related to changing the database data and database descriptions are performed in the transaction execution device 2.4. All procedures that lead to a change in the database go to the input of device 2.4 and are logged, in particular, the called procedures and their parameters are logged, as well as the contents of the worksheets received from the client and used by the procedure during execution.

After the synchronization process, data is updated on the data storage device 2.3. At the output of the information storage module 2.3.2, in accordance with the rights of the registered user, output results are generated that are received at the input of the device 2.1 for collecting and issuing information to the control module 2.1.4, and then output to paper and electronic media in the form of reports or viewing forms (processing of non-regulatory requests).

Block 3 input, registration, approval, processing and arching of information in a central database (Figure 4) contains sequentially connected by two-way communication device 3.1 for collecting and issuing information, device 3.2 for storing and collecting information and device 3.3 for transactions.

At the input of block 3, through the device 3.1 for collecting and issuing information, information is entered on the functional complexes of workstations of users of the local network. To do this, the source data from paper media through the module 3.1.1 data entry is loaded into a central database (SQL). When entering, the user is registered through the device 3.1.2 registration. Then the data is transmitted through the data receiving module 3.1.3, where all the details of the input fields are filled in, to the control module 3.1.4, where the control is carried out on the completeness and correctness of filling in the input forms.

Data from the device 3.1 for collecting and issuing information is fed to the input of the information storage device 3.2, where, getting into the control module 3.2.1, control is carried out on the compliance of the data storage structures with the entered data. Next, the monitored data goes to the input of the data storage module 3.2.2, where it is stored on the corresponding data carriers.

The actions associated with changing the data of the central database and the database descriptions are performed in the transaction execution device 3.3. All procedures that lead to a change in the database are received at the input of device 3.3 and are logged.

Block 4 data transfer between the levels of the system (Figure 5) contains a series of series-connected devices that provide the process of transferring data between the levels of the system. The first and second inputs of block 4 receive data from block 1 for input, registration, approval, processing and collection of information (AWP of the main managers of budget funds) and block 2 for input, registration, approval and processing of information (AWP of an employee of a budget institution).

At the input of the user registration device 4.1, the user of the system from whom the information is received is identified and the information on the rights of the user in the database is analyzed. This information is transmitted to the input of the device 4.2 for determining the last session of a given user, in which according to the table of sessions (the process of synchronizing information of the central and local database for a given user) containing the session identifier, user name, date, session start time, operation completion code and several others details, the analysis of the results of the last session is carried out, user information is generated about the possibilities of starting a new session. This information is transmitted to the input of the device 4.3 starting a new session. In the session table, the completion code received from the client is updated and a decision is made about the possibility of a new synchronization process.

The result (completion code) obtained at the output of the device 4.3 is fed to the input of the device 4.4 operations. Based on the analysis of the obtained result, either the current operation is selected and the processing is completed (repeat of the unfinished operation if the transition number is specified in the session table and there is no completion code), or the next operation is selected according to the state parameters received from the remote user and the previous completion code operations, or the next table for table operations, and if the tables are over, then the next operation. After that, the session table is updated and, if the transition number is not specified or there is a completion code, the session end time is stamped.

Unit 5 for making changes to the central database (Fig. 6) contains sequentially connected device 5.1 for saving changes and updating the database, device 5.2 for updating and generating tables, device 5.3 for updating routine reports and device 5.4 for managing the sequence of procedure calls connected by two-way communication with devices 5.1 and 5.2.

The input of the device 5.1 for saving changes and updating the database receives information from the data transfer unit 4 between the levels of the system, namely, data on the user identification and the session held by him. Then the changes in the history tables sent from the client, which are structurally a copy of the change tables with the addition of the session number into which the changes were received, are analyzed, and the central database updates from the local database are performed according to the procedure log. At the same time, the device 5.1 saves the document, changes the attributes of the state of the document, deletes the document, changes the properties of the document.

In the device 5.2 updating and generating tables, depending on the type of procedure, a sequence of procedures is called that simulate the interaction of the type “client - server”. So, to perform the procedure for saving a document, it is necessary to perform the loading procedure, a special procedure that changes the contents of the worksheets in accordance with the information sent from the remote user to the change tables and forms the call parameters for the save procedure according to the contents of the worksheets sent from the remote user, and then call the save procedure.

All messages received as a result of the procedures are recorded in the message table and in the session log, and the record from the procedure log is deleted.

In order to generate a sequence of procedure calls, the following meta-information is carried out in device 5.4 for controlling the sequence of procedure calls:

- table of procedures,

- Table of types of procedures

- Table of the relationship of procedures with types of procedures and types of documents

- Application objects table with object types

- table tables

- A table linking procedures with application objects and tables.

From the output of block 5, information is supplied to one of the inputs of the block 7 for controlling the synchronization process.

Block 6 for making changes to the local database (Fig. 7) contains sequentially connected table replica creation device 6.1, intended for LBD generation and synchronization procedures on the replica server, module 6.2, for receiving LBD changes on the replica server and transferring the changes LBD from the replica server to the main server, device 6.3 creating on the replica server copies of the local database tables and device 6.4 transferring changes to the LBD.

The input of block 6 receives information from block 4 for transmitting data between the levels of the system, as well as information from block 7 for controlling the synchronization process.

This block contains partial replicas of the central database on a number of servers, one of which, for making changes to the LBD, provides access for remote users performing synchronization operations of local databases.

To do this, using device 6.1 for creating a table replica for LBD generation and performing synchronization procedures, a server creates a replica of all the tables necessary for the formation of a local database, and user joins are registered on it. During synchronization, all procedures that synchronize are performed on the server containing the replica.

Modified data in the local database using module 6.2 is received and sent to the server with the replica, and then, in accordance with the procedure, the data from the table on the replica server is transferred to the corresponding table on the main server. A procedure is launched on the replica server, which, in a cycle through the table of operations, executes the database changes transferred in this table. In order to determine which server and database to run the procedures on, additional database properties are used - replicas. At the end of the cycle of saving procedures, a record is made in a special record synchronization table containing the server name and session identifier. This table is replicated to the replica database.

Data about the end of server synchronization is transferred to device 6.3 to create a copy of the local database tables on the replica server. On the replica base, the procedure of creating a copy of the local database tables is started, which according to the replica database generates the corresponding tables for generating records of the local database change tables compared to the previous session.

Then, using the device 6.4 transferring changes to the LBD, the changes to the local database of the previous session are transferred to the table and the indices and connections on the local database are built.

The synchronization process control unit 7 (Fig. 8) contains sequentially connected device 7.1 for creating handlers in the client application, device 7.2 for creating an operation manager in the client application, device 7.3 for generating a meta-information base for the synchronization process, central server load control device 7.4, and queue management device 7.5.

The device 7.1 for creating handlers in the client application is designed to perform exchange process operations. The list of these handlers includes handlers for the following operations:

- Database creation

- table forwarding

- Performing the procedure

- Rename file

- Delete file

- Copy file

- Database compression

- Reception table

- Creating links

- Deleting copies of local databases.

The device 7.2 for creating an operation manager in the client application is designed to provide a procedure call on the server in a cycle and pass parameters such as the completion code of the previous operation and a table of files with databases to it. From the procedure, the server receives the name and parameters of the next operation or the flag to complete synchronization.

Using the device 7.3 forming a meta-information base in block 7, a meta-information base is formed to control the synchronization process, which contains the following tables:

- Conversion graph

- Operation table

- table tables

- Link table tables with table operations for table operations.

The vertices of a directed cyclic graph are the states of the exchange process, and the arcs are transitions from state to state by performing an operation. If the transition is made to the beginning of the graph, then the session end time is put down and the synchronization process ends.

The central server load control device 7.4 is designed to adjust the central server load and provides client applications with service expectation regardless of server load, thereby implementing an external queuing system.

Recording, deleting, updating data is performed by the queue management device 7.5, in which a special queue management procedure is called from the processes processed in order of priority. At the start of such a procedure, an appeal is made to the queue management procedure for queuing. Depending on the result, the execution of the procedure either continues or ends. When processing is completed, the procedure also calls the queue management procedure for removal from the queue.

Block 8 sharing access to communication channels (Fig. 9) includes a device 8.1 for identifying the rights and authorities of user groups, the output of which is connected to a device 8.2 for sharing access to individual communication channels, which, in turn, is connected by two-way communication with the access control device 8.3, the output of which, like the output of the device 8.2, is connected to the input of the device 8.4 synchronization of technological processes and remote access sessions.

The input of this block 8 receives information from the block 7 control the synchronization process, containing meta-information about the signals received from users initiating the synchronization process.

Block 8 provides direct user access to the central database during synchronization operations of local databases on dial-up channels with the possibility of dynamic separation and access to various phone numbers. When a signal is received from the synchronization process control unit 7, the device 8.1 for identifying the rights and authorities of user groups checks for the possibility of establishing a connection using one of the remote access connections. The signal is transmitted to the device 8.2 sharing access through separate communication channels, where the choice of connection in the loop. The access control unit starts or restarts the connection with the stored input parameters in the event of a disconnection. The device for synchronizing technological processes and remote access sessions monitors the status of the connection (is the connection being used by other processes), and also ensures the end of the remote access session. In addition, the device allows automatic synchronization of databases without user intervention, as well as when transferring individual processes to another server (s), the databases on which are a full or partial replica of the central database, priority procedures are provided for individual procedures and user groups and source selection, which reduces the load on the central server.

Block 9 of the database synchronization of the central and remote SQL servers (Figure 10) contains a number of devices that provide the synchronization process of the central database and the local database located at the remote user. Block 9 includes a series-connected device 9.1 updating the layout structure located on the remote server, device 9.2 for transmitting data to the central database and device 9.3 for receiving data from the central database.

The first input of block 9 receives data from the synchronization process control block 7, the second input of this block 9 receives data from the main server and replica server interaction block 11, and the outputs of block 9 are also connected to the synchronization process control block 7 and to the interaction block 11 primary server and replica server.

The device 9.1 updates the layout structure provides updating the database structure of the remote SQL server according to the data of the central database server, initiated by the start of the synchronization process between the two servers. The device also ensures the continuation of the synchronization process in the event of a break in communication with the SQL server of the central database.

Device 9.2 for transmitting data to the central database ensures that the synchronization process starts from any workstation on the local network (in accordance with the rights set at the registration name level) and transfers the database changes of the remote SQL server to the SQL server of the central database.

The device 9.3 for receiving data from the central database provides the transfer of changes to the database of the SQL server of the central database to the database of the remote SQL server.

Block 10 input, output information of the exchange database when the file-server LBD (Fig. 11) contains sequentially connected device 10.1 for fixing the state of the local database, device 10.2 for transmitting to the server of the central database LBD changes, device 10.3 for making changes to the server of the central database, device 10.4 for making changes from the server of the CDB and the device 10.5 creating and storing copies of the LBD at the time of synchronization.

The input of this block 10 receives information from the synchronization process control block 7, which contains meta-information that provides control of the synchronization process, for example, the description of the database synchronization sequence, as well as information from the interaction block 11 of the main server and the replica server.

After receiving the signal from the synchronization process control unit 7, in the device 10.1 fixing the state of the local database (LBD), the LBD state is locked (terminating access to the database). To do this, a tabular comparison is made of the current state of the local database at the time of locking and its state at the time of one of the previous synchronizations. In device 10.2, changes (deletions, additions, changes) to the local database are transferred to the central database server in special work tables. In addition, a table with the protocol of procedures is also transmitted.

Then, using the device 10.3 to make changes to the CDB server, in block 10, the procedures sent in the procedure protocol are executed, a copy of the local database tables is created on the server, and the change tables are filled in comparison with the moment of the previous synchronization. At the same time, an empty local database is created on the remote user's computer with a description of the tables. The data on the structure of the tables is transferred to the device 10.4 for making changes from the server of the central database, where the data is copied from the copy of the local database at the time of the previous synchronization, and thereby the changes are applied from the server of the central database. The results of the changes are transferred to the device 10.5 creating and storing copies of the LBD, in which the keys, indexes, links are built and a copy is created at the time of synchronization, while the current database is deleted from the storage device and the newly created one is announced.

Block 11 of the interaction between the main server and the replica server (Fig. 12) contains sequentially connected device 11.1 for generating a list of replica database objects by types, device 11.2 for copying object descriptions from the main database to the replica database, device 11.3 for creating or creating descriptions for replication, a device 11.4 for loading data into a copy of the local database on the replica server, as well as a device 11.5 for describing queries in meta-information tables, the input of which is connected to the output of device 11.4, and the output to the input of device 11.6 identifiers of entries in the buffer tables, while devices 11.2, 11.3, and 11.4 are connected by two-way communications with the servers of the main database and the replica database.

In this block 11, the interaction of the central database server, which provides database modification operations, and the replica server, which provides operations related directly to synchronization of the local database, is provided.

The first input of block 11, in accordance with the formed structure of the replica server, receives data from the input block 10, outputting information from the exchange database at the file-server LBD, and the second input of block 11 receives data from the block 9 for synchronizing the central and remote SQL server databases , when the servers are at the second level.

A device 11.1 for forming a list of replica database objects by types provides the generation of these objects in the corresponding database object (table), forming their type, name and replication method. This description is then transmitted to the input of the device 11.2 copying the description of objects from the main database to the replica database, which provides such copying.

Using the device 11.3 to create or recreate descriptions for replication, the main database server, the distribution server are configured, the publisher server containing the main database and subscriber servers containing replica databases are described. Creation or re-creation of descriptions for replication is carried out using a special procedure with parameters.

At the input of device 11.4 loading data into a copy of the local database from the output of device 11.3 for creating or re-creating descriptions for replication, information with descriptions of replica server objects is received, according to which a copy of the local database tables is created. At the same time, in block 11, information about the copies of the local database available for the remote user is generated and stored, according to which you can set the session and server copy of the local database and by which, in turn, synchronization will be carried out. The output of this block generates information about which of the copies of the local database should load data.

This information is then fed to the input of device 11.5, with the help of which a series of queries is described in specially formed database objects - in meta-information tables. The parameter for executing queries is the identifier of the user group for which the local database is being created. Next, it is established to which of the copies of the local database the data should be loaded, after which a series of requests are executed in the block loading the data into this copy.

At the output of device 11.5, information is generated in the form of a copy of the LBD, which is then transmitted to the input of the device 11.6 for generating record identifiers in the buffer tables, in which the current and previous copies of the LBD are compared. As a result of the comparison, records are established to be added, changed or deleted from the local database, their identifiers are formed. The received identifiers are recorded in the transmission buffer tables and supplemented with information about other fields of the tables.

From the output of block 11, the generated identifiers are transmitted through the buffer tables to the input of input block 10 and output of information from the exchange database at the file-server LBD for the further synchronization process.

The following is an example of the operation of the database interaction system in the implementation of one of the ad hoc queries.

Suppose you want to transfer payment orders to a central database (hereinafter CBD) located in a financial authority.

An employee of a budget institution from his terminal generates documents in the local database (hereinafter referred to as LBD) of block 2. An employee of the main manager of budget funds using his terminal also generates documents in the LBD of block 1. These documents must be transferred to the central database of the financial authority.

In blocks 2 and 1, information is entered containing the relevant details (depending on the type of documents being transferred). In this case, the information goes to device 2.1 (or 1.1, respectively), where the user is registered, data is entered and received. From device 2.1 (1.1), information enters device 2.3 (1.3), is stored in the LBD, and transmitted to device 2.4 (1.4). Device 2.1 (1.1), when entering and receiving data, uses the data of device 2.2 (1.2), which contains a description of the data structures that are entered on device 2.1 (1.1). If the structures described in device 2.2 (1.2) do not coincide with the structures of objects (forms) into which data is entered, on device 2.1. (1.1) error messages appear during the monitoring process.

From block 2 (1), according to the available output, the information goes to block 4. On block 4, on device 4.1, the user is registered, on device 4.2, the last session for this user is determined, on device 4.3, the beginning of a new session, on device 4.4, the order and number of operations performed. From block 4, at the first output, the signal enters block 5 to device 5.4, which provides control over the sequence of procedure calls. From device 5.4, the signal is transmitted to block 7, to device 7.1, where various handlers are created in the client application. Then, on the device 7.2, an operation manager is created in the client application, on the device 7.3, a meta-information base for the synchronization process is formed, on the device 7.4, the load management strategy of the central server is determined and, if necessary, the device 7.5 is connected to control the queue. From block 7, the second output transfers control to block 8 to device 8.1 to identify the rights and authorities of user groups, then the signal goes to module 8.2 for sharing access via separate communication channels. Device 8.3 controls access to device 8.4 to synchronize processes and remote access sessions. At the first input from block 8, the control information is returned to block 7. The signal output from the block can be carried out in two directions.

If the work is carried out in a file-server architecture, then the signal at the first output goes to block 10. In the case of work in the server-server architecture, the signal at the third output goes to block 9. After receiving the signal from block 7 to block 10 in module 10.1, locking is performed (termination of access to the database) of the LBD state and a tabular comparison of the current state of the local database at the time of locking and its state at the time of one of the previous synchronizations. In module 10.2, changes (deletions, additions, changes), as well as a table with the protocol of procedures, are transferred to special working tables on the central database server. Device 10.3 implements the procedures sent in the protocol of procedures, a copy of the local database tables is created on the server, and the change tables are filled in comparison with the moment of the previous synchronization.

If the signal from block 7 enters block 9, then it goes to device 9.1, where the layout structure located on the remote server is updated. Then, the device 9.2 initiates the transfer of data to the central database, which falls on the device 9.3 receiving data from the central database. Upon the first exit from block 10 or block 9, the control signal is transmitted to block 11, where the information is sequentially transferred to device 11.1 to form a list of replica database objects by types, to device 11.2 to copy the description of objects from the main database to the replica database, to the device 11.3 to create or recreate descriptions for replication, to device 11.4 for downloading data to a copy of the local database on the replica server, to device 11.5 for describing queries in meta-information tables, and to device 11.6 for generating identities fikatorov in the buffer table. In this way, information is prepared for the process of reverse data transmission from the central server to the local station. Using device 5.4, the control signal is fed to the input of module 5.1, where data is generated on the identification of the user and his session. The information obtained from block 2 is analyzed, and the central database information is updated according to the procedure log. Further, in device 3.2, information is saved, information is changed, information is deleted in a central database located in a financial authority.

In addition to the described, it is possible to carry out other processes using this scheme, for example, transferring information from a central database to the level of the main managers of budget funds; transfer of information from a central database to the level of budgetary institutions, etc.

The advantages of the claimed database interaction system over the prototype and other devices of similar purpose are as follows:

- provides a reduction in the amount of data transmitted during synchronization due to their optimization (transfer of changes);

- provides a reduction in transmission time by optimizing the transmitted data structures (reducing the duration of the synchronization session);

- Optimization of the information flow between user levels is ensured through the introduction of electronic standardized forms of documents involved in the synchronization process;

- the introduction of a new technology for the operational management of financial resources based on the principles of the treasury system at all levels of users of the system is ensured due to the ability to quickly obtain information in the synchronization process;

- the ability of several thousand geographically remote users to operate in data update modes in the absence or high cost of high-speed channels providing acceptable characteristics for data transfer between user levels, i.e. created the ability to access central database information via low-speed dial-up channels;

- automatic selection of the connection in the loop during the synchronization process is provided, namely, the access control performs the start or restart of the connection for synchronization with the stored input parameters in the event of a connection break;

- Provided control over the state of the connection (whether the connection is used by other processes), as well as the process of correctly terminating the remote access session.

Claims (11)

1. The database interaction system of the automated control system, comprising at least two blocks of input, registration, approval, processing and compilation of information of remote users and a block of input, registration, approval, processing and code of information in a central database, which are respectively the first, second and third information inputs into the system, as well as a unit for making changes to the central database and a unit for making changes to the local database, characterized in that it is additionally equipped with a bl com of data transfer between system levels, connected by two-way connections with each of the above system units, a synchronization process control unit, the inputs of which are connected to the outputs of the unit for making changes to the central database and the unit for making changes to the local database, as well as the unit for sharing access to communication channels, a synchronization unit for central and remote SQL server databases, an input / output unit for exchange database information with a file-server local database, each of toryh connected bilateral communication with the control over the synchronization process unit and block the interaction of the primary server and the server replica connected bilateral connections to database synchronization block data central and remote SQL servers and block IO base exchange data information with file-server local database. 2. The system according to claim 1, characterized in that each of the two blocks of input, registration, approval, processing and consolidation of information of remote users is made in the form of series-connected by two-way communication device for collecting and issuing information, including a series-connected recording device, data input module , a data receiving module and a control module, a device for describing versions of a local database, a device for executing transactions, and a device for storing and collecting information including two-way connected m modulus control and storage module and data vault. 3. The system according to claim 1, characterized in that the unit for input, registration, approval, processing and compilation of information in the central database is made in the form of a series-connected two-way communication device for collecting and issuing information, including a series-connected recording device, a data input module, a data receiving module and a control module, a storage device and a data arch, including a control module connected by a two-way communication and a data storage and data arch, and a transaction execution device. 4. The system according to claim 1, characterized in that the data transfer unit between the levels of the system is made in the form of a series-connected device for registering a user, a device for determining the last session for a given user, a device for starting a new session and a device for performing operations, wherein the user registration device and device definitions of the last session for this user are connected by two-way communication. 5. The system according to claim 1, characterized in that the unit for making changes to the central database is made in the form of series-connected devices for saving changes and updating the database, devices for updating and generating tables, and devices for updating routine reports, as well as devices for controlling the sequence of procedure calls, connected by two-way communication with the device for saving changes and updating the database and the device for updating and creating tables. 6. The system according to claim 1, characterized in that the unit for making changes to the local database is made in the form of series-connected devices for creating replicas of tables, devices for receiving and transmitting LBD changes on the replica server, devices for creating copies of local database tables on the replica server and devices for transmitting changes to the LBD. 7. The system according to claim 1, characterized in that the synchronization process control unit is made in the form of series-connected devices for creating handlers in the client application, devices for creating an operation manager in the client application, devices for generating a meta-information base for the synchronization process, devices for controlling the loading of the central server and device queue management. 8. The system according to claim 1, characterized in that the unit for sharing access to communication channels is made in the form of series-connected devices for identifying the rights and authorities of user groups, devices for sharing access to individual communication channels, an access control device and a device for synchronizing technological processes and remote sessions access, the second input of which is also connected to the output of the device for sharing access via separate communication channels, and the access control device troystvo division access over separate communication channels are connected two-way communication. 9. The system according to claim 1, characterized in that the synchronization unit of the databases of the central and remote SQL servers is made in the form of series-connected devices for updating the layout structure located on the remote server, a device for transmitting data to a central database, and a device for receiving data from a central database data. 10. The system according to claim 1, characterized in that the input / output block of the exchange database information for the file-server LBD is made in the form of series-connected devices for fixing the state of the local database, a device for transmitting LBD changes to the server of the central database, and devices for making changes to the server The CDB, the device for making changes from the server of the CDB and the device for creating and storing copies of the LBD at the time of synchronization, and the output of the device for making changes from the server of the CDB is also connected to the input of the device for making changes to the server of the CBD, and the output of the device for creating and storing copies of the LBD at the time of synchronization is also connected to the input of the device for making changes from the server of the CBD. 11. The system according to claim 1, characterized in that the interaction unit of the main server and the replica server is made in the form of series-connected devices for generating a list of replica database objects by types, devices for copying object descriptions from the main database to the replica database, device for creating or recreation of descriptions for replication, a device for loading data into a copy of a local database on the replica server, as well as a device for describing requests in meta-information tables and a device for generating record identifiers in buffer tables, moreover, the device for copying descriptions of objects from the main database to the replica database, the device for creating or re-creating descriptions for replication, and the device for loading data into a copy of the local database on the replica server are connected by two-way communications with the servers of the main database and the replica database.

Images