CN1426006A - Distributed case management system and its method - Google Patents
Distributed case management system and its method Download PDFInfo
- Publication number
- CN1426006A CN1426006A CN 01130124 CN01130124A CN1426006A CN 1426006 A CN1426006 A CN 1426006A CN 01130124 CN01130124 CN 01130124 CN 01130124 A CN01130124 A CN 01130124A CN 1426006 A CN1426006 A CN 1426006A
- Authority
- CN
- China
- Prior art keywords
- server
- case
- uncoiling
- central
- line
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The distributed case management system includes one central managing information subsystem and several branched managing information subsystems. Each branched managing information subsystem includes several client ends, one application server and one data base server. In expedite network, all the branched client ends are on-line uncoiled to the central application server, and the central data base server will copy the uncoiled job information to all the branched data base servers for distributed back-up. In case of failed network, each branched client end can off-line uncoiled and the off-line uncoiled information is written to off-line uncoiled list. The branched application server can monitor the network connection to the central data base server regularly, so that after the normal network is restored, the central management information subsystem can copy uncoiled data to all the branched data base servers.
Description
[invention field]
The present invention is about a kind of system and method thereof that is used for managing distributed case, refers to a kind of distributed case management system and method thereof that can each management information subsystem off-line uncoiling data of online recovery especially.
[background of invention]
In recent years, along with the computer and network technology rapid development, modern enterprise is faced with huge opportunities and challenges, each enterprise set up one after another new management information system (Management InformationSystem, MIS) or revise original management information system with in response to it.Four-stage has been experienced in the development of mis system platform model substantially, that is: host terminal pattern, file server pattern, customer end/server mode (C1ient/Server, C/S) and Web browser/server mode (Browser/Server, B/S).
The host terminal pattern is because the hardware selection is limited, and hardware investment can not get guaranteeing, progressively eliminated.And the file server pattern only is applicable to small-scale LAN (Local Area Network), and the situation many for the user, that data quantity is big will produce network " bottleneck ", particularly in the requirement that can not satisfy the user on the Internet.Therefore, modern enterprise mis system platform model mainly adopts C/S model and B/S pattern.
And C/S model also progressively develops into three-tier architecture from two traditional layer architectures.This mainly is because there is following several limitation in the C/S model of traditional two layer architectures: (1) is single server and is the center with the LAN (Local Area Network), so be difficult to extend to large enterprise's Wide Area Network or the Internet; (2) be subject to supplier; (3) combination and integration capability soft, hardware are limited; (4) be difficult to manage a large amount of clients.Therefore three layers of C/S model arise at the historic moment.
As shown in Figure 1, be a kind of hardware structure of three layers of C/S model.In this framework, application function is divided into presentation layer, functional layer and data layer three partly.Presentation layer is the user interface part of using, and it is undertaking the dialogue function between user and application; The body that functional layer is equivalent to use, it enrolls concrete business processing logic in the program; The data layer adopts data base management system (DBMS) (Database ManagementSystem, DBMS), be in charge of read-write to database, along with Relational DBMS (Relational Database Management System, RDBMS) development, the data layer tends to adopt RDBMS now.In this framework, be that functional layer and data layer are positioned over respectively in the different servers, so presentation layer, functional layer are placed in the different separately hardware systems respectively with the data layer, be the corresponding client 1 of presentation layer, the corresponding application server 2 of functional layer, data layer correspondence database server 3, the dirigibility of this framework is very high, can adapt to the change that the number clients purpose increases and handle load.And this framework also have program maintainable high, be beneficial to change and maintenance application technical manual, can carry out tight safety management and hardware system constitutes plurality of advantages such as expandability height.
In some special industries, for example trans-regional or transnational service industry, its branch offices is distributed in all over the world, and information need be shared with combination process by the branch offices of various places, the management of the electronic bits of data of its generation is promptly become an important component part of the sector operation.For these electronic bits of datas are managed, need record is carried out in the change of electronic bits of data each time, and will allow all branch officeses know, so just be necessary each item is found volume management, the everything with this item all is recorded in the folder.And in order to be unlikely to obscure each folder, just need encode to each folder, and to guarantee each folder be coded in be necessary in all branch officeses unique.In addition, carry out information sharing in order to be beneficial to each branch offices, and guarantee that all the other each branch officeses remain with the information of redundant, should allow the uncoiling information in somewhere and follow-up each action that this item is carried out all carry out synchronously with all the other each branch officeses when a certain branch offices has unexpectedly incident.
As shown in Figure 2, be a kind of existing management information system hardware structure synoptic diagram.It comprises a plurality of management information subsystems 4,5,6, and these management information subsystems 4,5,6 lay respectively at three different areas or national, for example belongs to first, second and the third three ground.All include aforesaid three layers of C/S model hardware structure in each management information subsystem.As in second ground management information subsystem 5, include a plurality of clients 51 (only drawing among the figure one), an application server 52 and a database server 53, inner each assembly of these management information subsystems all utilizes network to interrelate.When newly opening a folder on second ground, second ground application server 52 relatively in the second ground database server 53 existing folder sequence number maximal values distribute new reel number (as on maximal value, adding 1) for this volume, with utilizing second then the program in the application server 52 this new uncoiling document copying to first and the database server 43 and 63 on third ground in.Later on all data in this volume are changed action and all can write corresponding position in the database server 53, and can these change the data synchronization replication to first and the database server 43 and 63 on third ground in the corresponding position.In like manner, the operating process on the first ground and third ground is also identical with second ground operating process.
Yet under the Replication Architecture that this multiple spot upgrades, in the process of backup data, conflict is unavoidable.For example first ground and second ground carry out a uncoiling operation simultaneously, because this moment, first ground database server 43 was identical with folder sequence number maximal value in the second ground database server 53, so they are also identical to the reel number that new uncoiling ancestor is distributed, like this, just the situation that the different folder in first and second two places has identical reel number appears, and can't guarantee the uniqueness of various places reel number, then the new uncoiling data on first ground and second ground can produce the puzzlement of obscuring.
In addition, when network breaks down, then the new uncoiling data on somewhere (as first ground) can not copy in all the other various places database servers, if (as second ground) is with the stylish volume of opening in all the other somewheres, the situation that the different folder in first and second two places has identical reel number will occur, the reel number that can not guarantee all folders of various places is unique.When network recovery was communicated with, the reel number that various places uncoiling data can occur produced the puzzlement of conflict.Like this, network break down during this period of time in, occur for fear of above-mentioned puzzlement, method commonly used now is that first and second two places all stop the uncoiling action, treat that network is unimpeded after, just restart operation.So network break down during this period of time in, the various places management information subsystem all sinks into standstill state.This obviously greatly reduces the work efficiency of each branch offices.
So need a kind of new management information system to occur to avoid above-mentioned conflict, and when network breaks down, the various places management information subsystem can off-line operation, and after network recovery is normal, the off-line uncoiling data of various places can be resumed into online uncoiling data at an easy rate, and can guarantee the uniqueness of the reel number of various places folder again.
[summary of the invention]
Fundamental purpose of the present invention is to provide a kind of distributed case management system and method, can be after network recovery be normal, and the off-line uncoiling data that each branch management information subsystem is handled when the off-line changes into online uncoiling data automatically.
Another object of the present invention is to provide a kind of distributed case management system and method, so that being unified in the central management information subsystem, data upgrades, and duplicate to each branch management information subsystem, data in each branch management information subsystem and the data in the central management information subsystem are reached synchronously, avoid the generation that conflicts in the reproduction process.
The invention provides a distributed case management system, the method that it has adopted a kind of centralized management, has disperseed redundant.This system comprises a central management information subsystem and a plurality of branch management information subsystems, these branch management information subsystems are scattered in each area or national, and each management information subsystem all is the three-tier architectures that include a plurality of clients, an application server and a database server.When network was unimpeded, the various places client all was connected to central application server and carries out online uncoiling operation, and central database server utilizes synchronization replication process that the uncoiling job information is copied in the server of branch data storehouse, various places to disperse redundant.When network breaks down, the various places client all can not connect central application server, at this moment, the various places client can be carried out the off-line uncoiling, the various places client writes off-line uncoiling tabulation to off-line uncoiling information, system all is equipped with a recovering process on the application server of various places, this process periodic monitor is connected with the network of central database server, in case network recovery is normal, central application server can change into online data with off-line uncoiling data, equally, central database server can with these document copyings in all the other branch data storehouse, various places servers to disperse redundant.
[description of drawings]
Fig. 1 is a kind of three layers of C/S model basic hardware configuration diagram.
Fig. 2 is a management information system hardware structure synoptic diagram in a kind of prior art.
Fig. 3 is the system hardware configuration diagram of distributed case management system most preferred embodiment of the present invention.
Fig. 4 is the basic document table in the distributed case management system server of the present invention.
Fig. 5 is a distributed case management system case basic document table of the present invention.
Fig. 6 is a distributed case management system case sequence number concordance list of the present invention.
Fig. 7 is a distributed case management system off-line uncoiling record sheet of the present invention.
Fig. 8 is a distributed case management system off-line uncoiling log sheet of the present invention.
Fig. 9 is that distributed case management system of the present invention is judged the process flow diagram that whether network is communicated with between branch management information subsystem and the central management information subsystem.
Figure 10 is the online uncoiling process flow diagram of distributed case management system of the present invention.
Figure 11 is a distributed case management system off-line uncoiling process flow diagram of the present invention.
Figure 12 is the process flow diagram that distributed case management system of the present invention carries out online recovery to off-line uncoiling data.
[embodiment]
As shown in Figure 3, be the system hardware configuration diagram of distributed case management system most preferred embodiment of the present invention.The present invention has adopted a kind of centralized management, disperses the method for redundant.Distributed case management system of the present invention includes a central management information subsystem 7, a plurality of branch management information subsystem 8 and 9 (has only been listed two branch management information subsystems among the figure, number is not subject to the limits) and network system (do not draw, represent network connectivity with straight line in the drawings).These branch management information subsystems 8,9 are scattered in different regions or country, each management information subsystem is the three-tier architecture that comprises a plurality of clients (only having drawn among the figure one, as 81), an application server (as 82 or 92) and a database server (as 83 or 93).Client all is connected with application server in each management information subsystem (comprising central management information subsystem and each branch management information subsystem), and application server is connected with database server again.And the client in the branch management information subsystem all is connected with central application server.Database server in each branch management subsystem also all is connected with central database server.Above-mentioned all connections are all through network system, and these network systems can be Ethernet (Ethernet), corporate intranet (Intranet), can also be Internets (Internet) etc.
In the present invention, operating system adopts the Windows 2000 Server versions that Microsoft company provides in the database server, and wherein Database Systems adopt SQLServer 2000 versions that Microsoft company provides; What the operating system on the application server adopted is the Windows 2000 Server versions that Microsoft company provides; Operating system in client is Windows 98 above versions.Yet, above-mentioned configuration is just adopted in most preferred embodiment of the present invention, any operating system and the database software that can reach requirement of the present invention all can be adopted, and can adopt (SuSE) Linux OS, database server can adopt the related software of Oracle company as operating system.
Below relational language related among the present invention is described as follows:
Uncoiling is meant when the user need found volume management for a case, for this volume distributes a reel number, sets up an electronic record folder, and notifies the action of other each branch management information subsystem.
Online uncoiling, be meant when the network connectivity between each branch management information subsystem and the central management information subsystem just often, each branch's client is directly carried out the activity of uncoiling through the central application server of central management information subsystem.
The off-line uncoiling is meant when the network connectivity between each branch management information subsystem and the central management information subsystem breaks down, and each branch's client sees through the activity that the drop applications server of branch management information subsystem separately carries out uncoiling.
Online recovery, be meant that the central management information subsystem is converted into the off-line uncoiling data in each branch management information subsystem the activity of online uncoiling data automatically after the network connectivity between each branch management information subsystem and the central management information subsystem recovers normally.
As shown in Figure 4, be the server basic document table of distributed case management system of the present invention.This server basic document table 10 is deposited in the database server of various places, and it stores the basic document of all application servers of the present invention.These data comprise department name 101, Hostname 102, host address 103, local code 104, home site sign 105 and off-line uncoiling weights 106.Wherein, department name 101 is application server affiliated function titles; Hostname 102 is Hostnames of each application server, is called the PP01 of A-grade in the first class as first ground application server name; Host address 103 is meant the IP address of server, as 10.153.24.126 etc.; Local code 104 is the codes that are used to indicate each server institute possession, as first or the second grade; Home site indicates 105, be used to indicate the parameter that this application server is central application server or drop applications server, if its value is Y, show that then this application server is a central application server, if its value is shown as sky (NULL), represent that then this server is the drop applications server; Off-line uncoiling weights 106, be that various places are distributed the required weights that add of folder sequence number when carrying out the off-line uncoiling, be mainly used in the off-line uncoiling sequence number that separates each branch management information subsystem, as first ground off-line uncoiling weights is 2000, off-line uncoiling weights in second ground are that the off-line uncoiling weights on 4000, the third ground are 3000.
As shown in Figure 5, be distributed case management system case basic document table of the present invention, this case basic document table 11 is deposited in the database server of various places, and it stores the basic document of each case.In Fig. 5, only listed wherein a part of project: case numbering 111, case time 112, case type code 113, sequence number 114, case reel number 115 and country code 116.Wherein, case numbering 111, be meant the sequence number value of various places case, this value is unique, and the related information of all these cases all will be as reference, as a case folder of being opened on first ground, its case is numbered first 123, and then this case numbering can not change always, even the off-line uncoiling, it is when online recovery, and this case numbering also can not change; The case time 112, the time when being meant this case uncoiling; Case type code 113 is meant the code of the affiliated classification of this case, as in certain patent agency, can represent the patent search folder with S, represents the patented claim folder with A, represents the license folder with P, or the like; Sequence number 114 is meant the sequence number that these files are assigned with, and wherein online sequence number and off-line sequence number all are stored in this hurdle; Case reel number 115, be meant the coding that this folder is carried out, it combines case time 112, case type code 113 and sequence number 114, promptly representing this case as case reel number 2000A2650 is that uncoiling in 2000, case type are that application case, sequence number are 2650, when carrying out online uncoiling, what this hurdle was deposited is online case reel number, and when carrying out the off-line uncoiling, what this hurdle was deposited is off-line case reel number; Country code 116 is meant and handles the code that this case relates generally to country, is a U. S. application case as this case, and then its country code is represented with US, as representing China with CN, represents Japan or the like with JP.Only listed more above-mentioned fields among Fig. 5, also had a lot of information relevant all to be stored in this table, in fact as title of a cause, case grade, date of entrustment, clientage and folder location or the like with this folder.
As shown in Figure 6, it is the case sequence number concordance list of distributed case management system of the present invention, this case sequence number concordance list 12 is stored in the database server of various places, is the relevant information that is used to store the available online sequence number value and the off-line sequence number value of current a certain case type.This table includes case type code 113, online ordinal index value 121, off-line ordinal index value 122, upgrades user 123 and update time 124.Wherein case type code 113 is pointed out the pairing case type of those ordinal index values, because the case type of difference is to there being different case sequence number index; Online ordinal index value 121 is network when unobstructed, and the maximum sequence number in the basic document table 11 adds 1 value that draws; And off-line ordinal index value 122 is when the off-line uncoiling, and the maximum sequence number of off-line (having added the off-line weights) adds 1 value that draws; Upgrade user 123 and be meant the user who carries out operation at last; Be meant the nearest time that this table is upgraded update time 124.
As shown in Figure 7, be the off-line uncoiling record sheet of distributed case management system of the present invention.This off-line uncoiling record sheet 13 is deposited in the branch data storehouse server of various places.In this table, include two contents, i.e. case numbering 131 and off-line time 132.Wherein, case numbering 131 is identical with case numbering noted earlier, and the off-line time 132 is meant the time of carrying out this operation of off-line uncoiling.
As shown in Figure 8, be the off-line uncoiling log sheet of distributed case management system of the present invention, this off-line uncoiling log sheet 14 is stored in the central database server, is the corresponding relation that is used to write down the online case numbering after off-line case numbering and the online recovery.Off-line uncoiling log sheet 14 includes case numbering 141, line case reel number 142, online case reel number 143, off-line time 144 and release time 145.Wherein, off-line case reel number 142, system is the case reel number that it distributed when being the off-line uncoiling; Online case reel number 143 is the pairing case reel numbers in online recovery back; The off-line time 144, be time of off-line uncoiling; Release time 145, be the time that off-line uncoiling data is carried out online recovery.
Following part will be described the detailed process of online uncoiling, off-line uncoiling and online recovery in detail.
See also again shown in Figure 3, the present invention with first ground management information subsystem be the central management information subsystem.Be the whole flow process that example illustrates online uncoiling, off-line uncoiling and online recovery now with second ground.At first need judge the network connection state of second ground branch management information subsystem and central management information subsystem, be and be in line states now and still be in off-line state.
As shown in Figure 9, be the process flow diagram of judging in the distributed case management system of the present invention whether branch management information subsystem and network between the central management information subsystem are communicated with.For example, 2000/1/1, second ground user need newly open the folder of a continent application case, and its activation is installed in the application program of client 81, connects local application server 82 (step S20); It utilizes application server 82 visits to be arranged in the server MSDS 10 (step S21) of database server 83; According to local code second, read the record (step S22) of local server; Judge whether home site sign wherein is Y (step S23), in the present invention, wherein home site is denoted as NULL, illustrate that this application server is non-for central application server, be the drop applications server, so read next bar record (step S25), repeating step S23 is denoted as Y up to home site.Then take out the host address in this record, i.e. the IP address 10.153.24.126 (step S24) of first ground application server.Second ground application server 82 will attempt connecting central application server 72 (step S26) according to this IP address, and in the present embodiment, this step is to utilize the COM+ among the WIN2000SERVER to carry out.If success then illustrate that second ground branch management information subsystem 8 is in line states, second ground client just can see through central application server 72 and carry out online uncoiling, be in off-line state as the unsuccessful second ground branch management information subsystem 8 that then illustrates, second ground user just cannot see through central application server 72 and carry out online uncoiling, and can only carry out off-line uncoiling (step S27) by second ground application server 82.Before supposing uncoiling, the case maximum on second ground is numbered second 234 in the basic document table 11, and the case time is 2000 years; Online ordinal index value in the case sequence number concordance list 12 is 450.
Introduce online uncoiling process and off-line uncoiling process below respectively.At first introduce online uncoiling process, as shown in figure 10, if second ground application server 82 and the success of central application server 72 lines, then second ground client can see through central application server 72 visit central database servers 73 (step S30).At this moment, central application server 73 can read the online ordinal index value 450 (step S31) in the case sequence number concordance list 12, its case sequence number as this new uncoiling, so compile a reel number can for this case is 2000A0450, and its case numbering is to add 1 on original maximum case numbering, i.e. second 235 (step S32).At this moment can in the basic document table of central database server, increase a record, wherein, case is numbered second 235, the case reel number is 2000A0450 (step S33), can upgrade in the case sequence number concordance list 12 online ordinal index value simultaneously, the online ordinal index value in the case sequence number concordance list 12 is become 451 (case sequence number 450 adds 1) (step S34).Then, the user promptly can write other relevant information that this newly opens case by client 81 in basic document table 11, as title of a cause, undertaker, target date etc.At last, central database server 73 can duplicate these change data in each branch data storehouse server, promptly the newly-increased record in the basic document table and case sequence number concordance list are copied to relevant position (step S35) in the database server on the second ground and third ground.So just reached central management, disperseed the effect of redundant, at this moment, judging whether needs to continue uncoiling (step S36), if desired, then can be back to step S31, repeats above-mentioned steps, otherwise whole online uncoiling process finishes.
And later on the user can carry out a series of upkeep operation to this case, as to the increase of case data, deletion, modification etc.These operations all deposit in the central database server, also can see through central database server to other branch data storehouse server replicates.And the data form of case data wherein may be file (documents), video (video), image (image), audio files (wave) or other such as can be by the handled digital material of computing machine (as PC).
Introduce the off-line uncoiling process below.As shown in figure 11, if second ground application server 82 is unsuccessful with central application server 72 lines, then client 81 is just carried out operation on local application server (second ground application server 82).Suppose following for carrying out for the first time the off-line uncoiling, at first, second ground client 81 can be visited local application server 82 (step S40), by the case sequence number concordance list 12 in the second ground application server 82 visit second ground database servers 83, take out online ordinal index value 450 (step S41), add that then this locality (second ground) the off-line uncoiling weights 4000 in the server MSDS obtain 4450 (step S42), the off-line sequence number of this value as this new uncoiling, promptly can generate a new reel number 2000A4450 (step S43), then increase a record in the case basic document table 11 in second ground database server 83: case is numbered second 235 (promptly adding 1 on original maximum case numbering 234), the case time is 2000, case type code is A, sequence number is 4450, the case reel number is 2000A4450, and country code is CN (step S44).Can increase by one in the off-line uncoiling record sheet 13 in the second ground database server 83 simultaneously is recorded as: case numbering second 235,20000101_10:45 update time (referring to system time at that time) (step S45).And the off-line ordinal index value that can upgrade in the case sequence number concordance list 12 in the second ground database server 83 is designated as 4451 (off-line sequence number 4450 adds 1) (step S46).The user just can write into the out of Memory of this case in the second ground database server in 83 the case basic document table 11.Judging whether needs to continue uncoiling (step S47), if do not need, then whole process finishes; Newly open the folder of another one U. S. application case if desired, then second ground application server 82 can take out off-line ordinal index value 4451 in the case sequence number concordance list 12 from second database server 83, off-line sequence number (step S48) as new uncoiling, be back to step S43, all the other processes are as mentioned above above-mentioned, promptly can increase a record again in the basic document table 11 of second ground database server 83: case is numbered that second 236, case time are 2000, sequence number is 4451, the case reel number is that 2000A4451, country code are US.Can increase by one in off-line uncoiling record sheet 13 simultaneously is recorded as: case numbering second 236,20000101_13:45 update time (referring to system time at that time).The off-line ordinal index value that upgrades simultaneously in the case sequence number concordance list 12 in the second ground database server 83 became for 4452 (off-line sequence number 4451 adds 1).The user just can write into the out of Memory of this case in the second ground database server in 83 the case basic document table 11.
As shown in figure 12, be the process flow diagram that distributed case management system of the present invention carries out online recovery to off-line uncoiling data.Online rejuvenation with two off-line uncoiling 2000A4450 in second ground and 2000A4451 is that example describes now.The user can interiorly at any time activate timed sequence Schedule, and this program is a timer, and it can activate the process (step S1) of online recovery off-line uncoiling data at regular intervals.At this moment, second ground application server 82 promptly can connect the database server 83 on second ground, checks in the off-line uncoiling record sheet 13 whether off-line uncoiling record is arranged, and reads off-line uncoiling record number, writes among the variable Count (step S2).Judge that whether Count is greater than zero (step S3).If be not more than zero then the no off-line uncoiling record of expression then makes schedule reset (step S4), then can activate schedule again, the repetition abovementioned steps every a period of time; If greater than zero, then explanation has off-line uncoiling record, then in this process, two records is arranged in the off-line uncoiling record sheet 13, and promptly off-line record number is 2, and the Count value is greater than zero; Second ground application server 82 will read the IP address 10.153.24.126 of central application server in the server MSDS 10 in the second ground database server 83, connect central application server 72 (step S5) according to this IP address.If connection gets nowhere then is back to step S4; If successful connection, illustrate that network connectivity has recovered normal, then second ground application server 82 is according to the case numbering second 235 of article one record in the off-line uncoiling record sheet 13, in case basic document table 11, find corresponding record then, this basic document is write down the relevant position (step S6) that copies in the central Information Service device.The reel number of the off-line uncoiling case that can be replicated this in central application server 72 in the present embodiment, is recovered.These recovery concrete steps are as follows: at first judge the online recovery that whether needs of this case reel number, this is that online uncoiling data might write in the off-line uncoiling record sheet 13 because may be in some cases.The online ordinal index value of supposing the case sequence number concordance list 12 in the central database 73 this moment is 455.The online ordinal index value of central database server 73 is compared with the sequence number 4450 of this off-line uncoiling case, and 455 much smaller than 4450 as can be known, and this record of old friend is the uncoiling ancestor of off-line institute really, so need to recover (step S7).Otherwise be back to step S11 (hereinafter can describe).Then, central application server 72 reads the online ordinal index value 455 in the case sequence number concordance list 12 in the central Information Service device 73, generate the online case reel number 2000A455 of this off-line uncoiling case correspondence, case is numbered the above-mentioned record of second 235 in the renewal central database server 73, promptly wherein sequence number 4450 is become 455, the case reel number becomes 2000A455, all the other constant (step S8).Then in the off-line uncoiling log sheet 14 of central Information Service device 72, newly-increased record, note the recovering information of this case: case numbering second 235, off-line case reel number 2000A4450, online case reel number 2000A455, off-line time 20000101_11:45 and 20000103_11:45 release time (system time at that time), these processes realize in step S9.And the online ordinal index value of the case sequence number concordance list 12 in the central database server 73 was updated to for 456 (case sequence number 455 adds 1), while duplicates the whole piece record that the case after recovering is numbered second 235 to the database server relevant position on the second ground and third ground, promptly case is numbered in the record of second 235 and revises corresponding sequence number value and case reel number value in the case basic document table in second ground database server 83, is the record (step S10) of second 235 and increase by one in the case basic document table in the third ground database server 93.Return off-line uncoiling ground second then, in the deletion second ground database server 83 in the off-line uncoiling record sheet 13 case be numbered the record (step S11) of second 235.And the Count value deducted 1 (step S12).It then is the online rejuvenation end of 2000A4450 off-line uncoiling case to reel number.Be back to step S3 then, because count value at this moment is 1, greater than zero, so can carry out subsequent step, promptly can finish reel number is the online reel number rejuvenation of 2000A4451 off-line uncoiling case.Then can be back to step S3 again, and this moment, the count value was zero, thus can go to step S4, to the reel number rejuvenation end of the off-line uncoiling case in the second ground database server.The online rejuvenation of reel number of the off-line uncoiling case in other branch management information subsystem similarly, so no longer the narration.
Claims (19)
1. distributed case management system that is used to manage the electronic bits of data of trans-regional combination process case is characterized in that including:
One central management information subsystem includes a central database server and a central application server at least, and wherein central database server stores the essential information of all cases, and central application server is used for the case uncoiling business game of process user;
At least one branch management information subsystem, include an at least one client and a branch data storehouse server, wherein client can see through the aforesaid central application server of access to netwoks, use and carry out the case business game and read and write case information in the central database server, each branch data storehouse server is connected with central database server by network, and central database server can be with wherein case information reproduction to each branch data storehouse server;
When network breaks down, but described client mat is visited described drop applications server to carry out off-line uncoiling operation, after network recovery is normal, described central application server can carry out online recovery to the off-line uncoiling case information of drop applications server operation, then by central database server to each branch data storehouse server replicates.
2. distributed case management system as claimed in claim 1 is characterized in that wherein the central management information subsystem also includes at least one client.
3. distributed case management system as claimed in claim 1 is characterized in that, wherein each branch management information subsystem inside connects by corporate intranet.
4. distributed case management system as claimed in claim 1 is characterized in that wherein said network system can be corporate intranet or the Internet.
5. distributed case management system as claimed in claim 1, it is characterized in that wherein said branch data storehouse server and central database server all include the server basic document table of the basic identification data that is used to write down each drop applications server and central application server.
6. distributed case management system as claimed in claim 1 is characterized in that, wherein said branch data storehouse server and central database server include the case basic document table that is used to write down each uncoiling case data.
7. distributed case management system as claimed in claim 1 is characterized in that, wherein said branch data storehouse server and central database server all include and be used to write down the current case sequence number concordance list of opening the maximum sequence number value of case.
8. distributed case management system as claimed in claim 1 is characterized in that, wherein said branch data storehouse server includes the off-line uncoiling record sheet of the basic identification data of the case when being used to write down the off-line uncoiling.
9. distributed case management system as claimed in claim 1 is characterized in that, wherein said central database server includes and is used to write down the online off-line uncoiling log sheet that recovers back and former off-line uncoiling data corresponding relation of off-line uncoiling data.
10. distributed case management method, it can manage the transmission of the uncoiling data between central management information subsystem and a plurality of branch management information subsystem, wherein, each management information subsystem all includes at least one client, an application server and a database server, it is characterized in that this method comprises the steps:
(a) the drop applications server judges whether network is communicated with between management information subsystem and the central management information subsystem;
(b) if network-in-dialing, the client of described branch management information subsystem is connected with central application server, seeing through central application server writes the case business information in the central database server, and in the central database server with described information reproduction to each branch data storehouse server, carry out step (c) if network can not be communicated with;
(c) described client connects local drop applications server and carries out the off-line uncoiling, mat off-line uncoiling data is write in the server of local branch data storehouse, and in off-line uncoiling record sheet, carry out record;
(d) when network recovery is communicated with, in central database server, central application server can capture described off-line uncoiling data and it is carried out online recovery with the off-line uncoiling document copying described in the step (c);
(e) central application server deposits the uncoiling data after recovering in the central database server in, and central database server can be with the relevant position of the uncoiling document copying after recovering in each branch data storehouse server.
11. distributed case management method as claimed in claim 10 is characterized in that, comprises also that wherein central application server judges the step whether described off-line uncoiling data needs to carry out online recovery.
12. distributed case management method as claimed in claim 10 is characterized in that, wherein also is included in the step of setting up an off-line uncoiling log sheet in the central database server.
13. distributed case management method as claimed in claim 12 is characterized in that, comprises also that wherein the uncoiling information after central application server is the online recovery of off-line uncoiling information and correspondence thereof writes the step of off-line uncoiling log sheet.
14. distributed case management method as claimed in claim 10 is characterized in that, wherein after central application server carries out online recovery to described off-line uncoiling data, also comprises the step of the off-line uncoiling record on deletion off-line uncoiling ground.
15. distributed case management method as claimed in claim 10 is characterized in that, wherein step (a) also comprises the steps:
(a1) described client connects local drop applications server, reads a record in the server basic document table in the server of local branch data storehouse;
(a2) judge whether the main frame sign is that central application server indicates in the described record;
(a3) then be back to step (a1) if described main frame sign is non-for central application server indicates, read next bar record, otherwise carry out step (a4);
(a4) host address by central application server in the described record connects central application server.
16. distributed case management method as claimed in claim 15 is characterized in that, wherein the main frame sign is to be used to judge whether a certain application server is the sign of central application server.
17. distributed case management method as claimed in claim 15 is characterized in that, wherein host address is the IP address of each application server.
18. distributed case management method as claimed in claim 10 is characterized in that, wherein said drop applications server carries out the off-line uncoiling process and comprises the steps:
(c1) read the online ordinal index value in the case sequence number concordance list in the server of described branch data storehouse;
(c2) described online ordinal index value is added off-line uncoiling weights;
(c3) generate a new off-line case reel number;
(c4) the off-line ordinal index value in the described case sequence number concordance list of renewal.
19. distributed case management method as claimed in claim 10 is characterized in that, wherein said central application server carries out online rejuvenation to off-line uncoiling data and comprises the steps:
(d1) read the online ordinal index value in the case sequence number concordance list in the described central database server;
(d2) generate a new online case reel number;
(d3) described new online case reel number is replaced reel number in the described off-line uncoiling data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB011301244A CN1185596C (en) | 2001-12-21 | 2001-12-21 | Distributed case management system and its method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB011301244A CN1185596C (en) | 2001-12-21 | 2001-12-21 | Distributed case management system and its method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1426006A true CN1426006A (en) | 2003-06-25 |
| CN1185596C CN1185596C (en) | 2005-01-19 |
Family
ID=4669751
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB011301244A Expired - Fee Related CN1185596C (en) | 2001-12-21 | 2001-12-21 | Distributed case management system and its method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1185596C (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100377156C (en) * | 2005-03-08 | 2008-03-26 | 中国科学院计算技术研究所 | Method and middleware for data base duplicating using middleware in group communication system |
| CN101951382A (en) * | 2010-09-28 | 2011-01-19 | 广州市科传计算机科技股份有限公司 | Three-layer framework-based data transmission system and data transmission method |
| CN101957867A (en) * | 2010-10-29 | 2011-01-26 | 国电南瑞科技股份有限公司 | Data caching method in disconnection state of distributed application of power dispatching automation system |
| CN101114373B (en) * | 2007-01-26 | 2011-07-20 | 浙江杭嘉湖软件技术有限公司 | Court network commitment execution system |
| CN103076994A (en) * | 2012-12-31 | 2013-05-01 | 北京中科大洋科技发展股份有限公司 | Method for realizing off-line file writing in SAN (Storage Area Network) shared-file system |
| WO2014026581A1 (en) * | 2012-08-16 | 2014-02-20 | 腾讯科技（深圳）有限公司 | Information management method, client, and mobile terminal |
| CN107771321A (en) * | 2015-06-10 | 2018-03-06 | 微软技术许可有限责任公司 | Recovery in data center |
-
2001
- 2001-12-21 CN CNB011301244A patent/CN1185596C/en not_active Expired - Fee Related
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100377156C (en) * | 2005-03-08 | 2008-03-26 | 中国科学院计算技术研究所 | Method and middleware for data base duplicating using middleware in group communication system |
| CN101114373B (en) * | 2007-01-26 | 2011-07-20 | 浙江杭嘉湖软件技术有限公司 | Court network commitment execution system |
| CN101951382A (en) * | 2010-09-28 | 2011-01-19 | 广州市科传计算机科技股份有限公司 | Three-layer framework-based data transmission system and data transmission method |
| CN101951382B (en) * | 2010-09-28 | 2013-06-19 | 广州市科传计算机科技股份有限公司 | Three-layer framework-based data transmission system and data transmission method |
| CN101957867A (en) * | 2010-10-29 | 2011-01-26 | 国电南瑞科技股份有限公司 | Data caching method in disconnection state of distributed application of power dispatching automation system |
| CN101957867B (en) * | 2010-10-29 | 2012-10-03 | 国电南瑞科技股份有限公司 | Data caching method in disconnection state of distributed application of power dispatching automation system |
| WO2014026581A1 (en) * | 2012-08-16 | 2014-02-20 | 腾讯科技（深圳）有限公司 | Information management method, client, and mobile terminal |
| CN103076994A (en) * | 2012-12-31 | 2013-05-01 | 北京中科大洋科技发展股份有限公司 | Method for realizing off-line file writing in SAN (Storage Area Network) shared-file system |
| CN103076994B (en) * | 2012-12-31 | 2016-02-03 | 北京中科大洋科技发展股份有限公司 | The method of off-line written document is realized in a kind of SAN shared-file system |
| CN107771321A (en) * | 2015-06-10 | 2018-03-06 | 微软技术许可有限责任公司 | Recovery in data center |
| CN107771321B (en) * | 2015-06-10 | 2021-02-23 | 微软技术许可有限责任公司 | Recovery in a data center |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1185596C (en) | 2005-01-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8214334B2 (en) | Systems and methods for distributed system scanning | |
| US10891067B2 (en) | Fast migration of metadata | |
| US6675177B1 (en) | Method and system for backing up digital data | |
| JP5607059B2 (en) | Partition management in partitioned, scalable and highly available structured storage | |
| CN1096639C (en) | Digital storage system and method having having alternating deferred updating of mirrored storage disks | |
| KR100556594B1 (en) | A method relating to databases | |
| US7831561B2 (en) | Automated disk-oriented backups | |
| EP2144177B1 (en) | System and method for a log-based data storage | |
| CN102016852B (en) | System and method for content addressable storage | |
| CN1272721C (en) | Electronic document management method and program | |
| US20070083563A1 (en) | Online tablespace recovery for export | |
| US20070094312A1 (en) | Method for managing real-time data history of a file system | |
| US7620661B2 (en) | Method for improving the performance of database loggers using agent coordination | |
| CN1904847A (en) | Method and system for determining changes made to a source file to transmit to a target location | |
| CN1653427A (en) | Method and apparatus for creating a virtual data copy | |
| JPH07262058A (en) | System and method for data storage management | |
| CN101046821A (en) | Generic database manipulator | |
| US20010054045A1 (en) | Data management system, server, and data management method | |
| JP2002149454A (en) | Transaction support on logical disk | |
| CN1185596C (en) | Distributed case management system and its method | |
| CN101046822A (en) | Centralized management of data nodes | |
| AU653044B2 (en) | Data processing system | |
| CN102360382B (en) | High-speed object-based parallel storage system directory replication method | |
| US20030115145A1 (en) | System and method for managing distributed files | |
| CN1241119C (en) | Method, system and program for exchanging resource sets continuously |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20050119 Termination date: 20161221 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |