CN106649729A - Log running method and system, client and server - Google Patents
Log running method and system, client and server Download PDFInfo
- Publication number
- CN106649729A CN106649729A CN201611206252.5A CN201611206252A CN106649729A CN 106649729 A CN106649729 A CN 106649729A CN 201611206252 A CN201611206252 A CN 201611206252A CN 106649729 A CN106649729 A CN 106649729A
- Authority
- CN
- China
- Prior art keywords
- log information
- type
- file
- client
- log
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/35—Clustering; Classification
- G06F16/355—Class or cluster creation or modification
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention is applicable to the technical field of banking log running and provides a log running method and system, a client and a server. The method comprises the steps that log information sent from the client is received, wherein the log information comprises a log ID and type IDs, and the type IDs comprise at least one of trading time, a system ID, a business ID, an institution ID and a teller ID; the log information is stored in configuration documents corresponding to the type IDs and cached in a message queue; based on the message queue, and a plurality of service threads are adopted to classify the log information stored in each configuration document, so that at least one sort file corresponding to the type IDs is formed; a log file is formed based on the at least one sort file and is sent to the client. By means of the method, the chaotic problem generated when a log is asynchronously written to a log module can be solved.
Description
Technical field
The invention belongs to bank's daily record running technology field, more particularly to a kind of daily record operation method and system, client
And server.
Background technology
The existing middleware KCBP of gold card possesses independent log pattern, and daily record is also to support asynchronous write and by different daily records
The attributes such as rank asynchronous write.But in the case where multithreading or multi-process run, due to KCBP log pattern asynchronous writes
Log Sequence occurs that the information in rambling state, and the preposition node of daily record also cannot mark what machine daily record is belonging to
Structure or which teller's operation so that in production maintenance and developing reading daily record in debugging process, tracking BUG at ordinary times becomes very
It is difficult.
Therefore, it is necessary to a kind of new technical scheme is proposed, to solve above-mentioned technical problem.
The content of the invention
In consideration of it, the embodiment of the present invention provides a kind of daily record operation method and system, client and server, it is existing to solve
Rambling problem occurs when having log pattern asynchronous write daily record.
A kind of first aspect of the embodiment of the present invention, there is provided the method for daily record operation, method include that server performs as
Lower step：
The log information that client sends is received, the log information includes daily record ID and type ID；The type ID bag
Include at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID；
The log information is respectively stored in the configuration documentation corresponding with type ID, and the daily record is believed
Breath is buffered in message queue；
According to the message queue, using multiple service threads day respectively to storing in each configuration documentation
Will information is classified, and forms at least one sort file corresponding with type ID；
Journal file is formed based at least one sort file, and the journal file is sent into the client.
A kind of second aspect of the embodiment of the present invention, there is provided the method for daily record operation, method include client executing as
Lower step：
Log information is generated, the log information includes daily record ID and type ID；Type ID includes exchange hour, is
At least one of system ID, traffic ID, mechanism ID and teller ID；
The log information is sent into server；
Receive the journal file that the server sends；The journal file includes at least one sort file, Mei Yisuo
State sort file carries out classification process by a service thread to the log information in the configuration documentation that formed based on type ID
Formed；
Show the journal file.
The third aspect of the embodiment of the present invention, there is provided a kind of server, the server includes：
First receiver module, for receiving the log information of client transmission, the log information includes daily record ID and class
Type ID；Type ID includes at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID；
Cache module, for the log information to be respectively stored in the configuration documentation corresponding with type ID,
And the log information is buffered in message queue；
Processing module, for according to the message queue, using multiple service threads respectively to each configuration documentation
The log information of middle storage is classified, and forms at least one sort file corresponding with type ID；
First sending module, for forming journal file based at least one sort file, and the journal file is sent out
Give the client.
The fourth aspect of the embodiment of the present invention, there is provided a kind of client, client includes：
Generation module, for generating log information, the log information includes daily record ID and type ID；The type ID bag
Include at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID；
Second sending module, for the log information to be sent into server；
Second receiver module, for receiving the journal file that the server sends；The journal file includes at least one
Individual sort file, each sort file is by a service thread to the daily record in the configuration documentation that formed based on type ID
Information carries out classifying what process was formed；
Display module, for showing the journal file.
A kind of 5th aspect of the embodiment of the present invention, there is provided daily record operation method, it is characterised in that comprise the steps：
Client generates log information, and the log information is sent into server；The log information includes daily record
ID and type ID；Type ID includes at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID；
Server receives the log information, and the log information is respectively stored in into corresponding with type ID matching somebody with somebody
In putting document, and the log information is buffered in message queue；
Server according to the message queue, using multiple service threads respectively to storing in each configuration documentation
The log information is classified, and forms at least one sort file corresponding with type ID；
Server forms journal file based at least one sort file, and the journal file is sent into the client
End；
Client receives and shows the journal file.
A kind of 6th aspect of the embodiment of the present invention, there is provided daily record runtime, it is characterised in that including client kimonos
Business device；
The client, for generating log information, and is sent to server by the log information；The log information
Including daily record ID and type ID；Type ID is included in exchange hour, system identifier, traffic ID, mechanism ID and teller ID extremely
It is few one；
The server, for receiving the log information, the log information is respectively stored in and type ID
In corresponding configuration documentation, and the log information is buffered in message queue；
The server, for according to the message queue, using multiple service threads respectively to each configuration text
The log information stored in shelves is classified, and forms at least one sort file corresponding with type ID；
The server, for forming journal file based at least one sort file, and the journal file is sent
To the client；
The client, for receiving and shows the journal file.
The beneficial effect that the embodiment of the present invention is present compared with prior art is：The embodiment of the present invention is according to type ID by institute
There is log information to be respectively stored in the configuration documentation corresponding with type ID, then using multiple service threads in message queue
The log information of caching is processed, and each service thread can be made only need to carry out at classification to the log information in a configuration documentation
Reason, so as to corresponding journal file is presented in order.And, the type ID includes exchange hour, system identifier, traffic ID, mechanism ID
At least one of with teller ID, when fileinfo is classified based on type ID, it is capable of achieving one or more dimensions classification, day
Will information classification is more flexible.
Description of the drawings
Technical scheme in order to be illustrated more clearly that the embodiment of the present invention, below will be to embodiment or description of the prior art
Needed for the accompanying drawing to be used be briefly described, it should be apparent that, drawings in the following description be only the present invention some
Embodiment, for those of ordinary skill in the art, without having to pay creative labor, can be with according to these
Accompanying drawing obtains other accompanying drawings.
Fig. 1 is the flowchart of the daily record operation method that the embodiment of the present invention one is provided；
Fig. 2 is the flowchart two of the daily record operation method that the embodiment of the present invention one is provided；
Fig. 3 is the flowchart of the daily record operation method that the embodiment of the present invention two is provided；
Fig. 4 is the flowchart two of the daily record operation method that the embodiment of the present invention two is provided；
Fig. 5 is the structured flowchart of the server that the embodiment of the present invention three is provided；
Fig. 6 is the structured flowchart of the client that the embodiment of the present invention four is provided；
Fig. 7 is the flowchart of the daily record operation method that the embodiment of the present invention five is provided；
Fig. 8 is the schematic block diagram of the daily record runtime that the embodiment of the present invention six is provided.
Specific embodiment
In order that the objects, technical solutions and advantages of the present invention become more apparent, it is right below in conjunction with drawings and Examples
The present invention is described in detail.It should be appreciated that specific embodiment described herein is not used to only to explain the present invention
Limit the present invention.
The embodiment of the present invention provides a kind of method of daily record operation.In order to illustrate method provided by the present invention, below
Illustrated by specific embodiment.
Embodiment one
Fig. 1 shows the flowchart of the daily record operation method that the embodiment of the present invention one is provided.As shown in figure 1, the day
Will operation method includes the following steps that server is performed：
S101：The log information that client sends is received, log information includes daily record ID and type ID；Type ID includes handing over
At least one of easy time, system identifier, traffic ID, mechanism ID and teller ID.
Wherein, server receives the log information that client sends, and client includes but is not limited to computer client and shifting
Dynamic client.Log information refers to the user corresponding file for producing and/or data when client is traded, including daily record ID
With type ID.Daily record ID is unique, and for uniquely determining the identity of the daily record, type ID is used to that daily record to be classified.
When log information is sent to server by server, can be by communication transfers such as the connection of TCP length, UPD, pipe-line communications
Agreement.
Client is asynchronous link block, and it is that primary system API of LINUX, WINDOWS supports that agreement supports TCP to adopt
The communication transfer agreements such as long connection, UPD, pipe-line communication, the selection of communication transfer agreement need to be matched with service end.
S102：Log information is respectively stored in the configuration documentation corresponding with type ID, and log information is cached
In message queue.
Wherein, configuration documentation includes public journal file, financing journal file and investment journal file.Every time in client
Corresponding log information can all be produced when concluding the business, server receives these log informations and by day according to time order and function order
Will information cache is processed in message queue with treating next step.
S103：According to message queue, using multiple service threads log information respectively to storing in each configuration documentation
Classified, formed at least one sort file corresponding with type ID.
Server is cached to the log information for receiving in message queue in S102.According to the performance of server
Preset the length of the accessible message queue of multiple service threads.According to message queue, multiple service threads can be simultaneously to each
The log information stored in configuration documentation is processed, to form at least one sort file corresponding with type ID.
S104：Journal file is formed based at least one sort file, and journal file is sent into client.
Journal file is formed based at least one sort file, the journal file for obtaining is sent to client by server.
In the daily record operation method that the present embodiment is provided, all log informations are respectively stored in and class according to type ID
In the corresponding configuration documentation of type ID, the log information cached in using multiple service threads to message queue is processed,
Each service thread can be made only need to carry out classification process to the log information in a configuration documentation, so as to corresponding day is presented in order
Will file, to avoid journal file after traditional approach is processed that rambling situation is presented.And, when the type ID includes transaction
Between, system identifier, traffic ID, at least one of mechanism ID and teller ID, when fileinfo is classified based on type ID,
Achievable one or more dimensions classification, log information classification is more flexible.
Fig. 2 shows the flowchart two of the daily record operation method that the embodiment of the present invention one is provided.As shown in Fig. 2 should
Daily record operation method also includes：
S105：The log query instruction that client sends is received, log query instruction includes at least one type ID.
Wherein, log query instruction can be the multiple ID in type ID, be conducive to reducing according to multiple ID inquiries and search model
Enclose, be quickly found out required daily record and carry out respective handling, the process includes reading or repairs.
S106：Journal file is called to generate Query Result file according to query statement.
The relevant information of journal file is called to generate Query Result according to query statement.For example, the query statement for receiving
For the teller ID in type ID, information related to the ID in journal file is called according to the teller ID, read the relevant information
Query Result is generated, the Query Result includes the information of all clients being traded at here teller.
S107：Query Result file is sent into client.
The present embodiment is by inquiry input any kind ID, you can the Query Result text of journal file is understood needed for knowing
Part, so as to understand the Query Result of correlation log file when arbitrary exchange hour, mechanism, system, business, teller are processed
File.
Embodiment two
Fig. 3 shows the flowchart of the daily record operation method that the embodiment of the present invention two is provided.As shown in figure 3, the day
Will operation method includes the following steps of client executing：
S201：Log information is generated, log information includes daily record ID and type ID；Type ID includes exchange hour, system
At least one of ID, traffic ID, mechanism ID and teller ID.
Wherein, log information refers to the user corresponding file for producing and/or data when client is traded, including day
Will ID and type ID.Daily record ID is unique, and for uniquely determining the identity of the daily record, type ID is used to carry out daily record point
Class.User generates log information when client is traded, and log information includes daily record ID and type ID.
S202：Log information is sent into server.
The log information generated in S101 is sent to server by client.
S203：The journal file that the reception server sends；Journal file includes at least one sort file, each classification text
Part carries out what classification process was formed by a service thread to the log information in the configuration documentation that formed based on type ID.
The journal file that client the reception server is sended over, journal file includes at least one sort file, this day
Will file includes at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID.Exchange hour refers to that user exists
The time of transaction log is generated when client is traded, ID refers to identification sequence number.Each sort file is by a service
Thread carries out classifying what process was formed to the log information in the configuration documentation based on the formation of type ID.
S204：Show log file.
In the content of client show log file.
In the daily record operation method that the present embodiment is provided, by the cooperation of client and server, will according to type ID
All log informations are respectively stored in the configuration documentation corresponding with type ID, using multiple service threads to message queue
The log information of middle caching is processed, and each service thread can be made only need to classify to the log information in a configuration documentation
Process, so as to corresponding journal file is presented in order, to avoid journal file after traditional approach is processed that rambling shape is presented
Condition.And, the type ID includes at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID, is being based on
When type ID is classified fileinfo, one or more dimensions classification is capable of achieving, log information classification is more flexible.
Fig. 4 shows the flowchart two of the daily record operation method that the embodiment of the present invention two is provided.As shown in figure 4, should
Daily record operation method also includes：
S205：The log query instruction of receiving user's input, log query instruction includes at least one type ID.
The log query instruction of client receiving user's input, log query instruction includes at least one type ID, i.e., extremely
Include in exchange hour, system identifier, traffic ID, mechanism ID and teller ID less.Related personnel can be input into one in client
Individual or multiple types ID carry out inquiry operation.
S206：Log query instruction is sent into server.
Related personnel can be when client be input into one or more types ID and carries out inquiry operation, and client receives daily record
Log query instruction is simultaneously sent to server by query statement.
S207：The Query Result file corresponding with log query instruction that the reception server sends.
The Query Result file corresponding with log query instruction that client the reception server sends, receives mode usual
By the way of reading.
S208：Show Query Result file.
The present embodiment is inquired about by being input into any kind ID in client, you can journal file is understood needed for knowing
Query Result file, so as to understand arbitrary exchange hour, mechanism, system, business, teller is processed when correlation log file
Query Result file.Production maintenance can be carried out according to Query Result file or follow the trail of the BUG in exploitation debugging process.
Embodiment three
Corresponding to the daily record operation method of foregoing embodiments one, Fig. 3 shows the server that the embodiment of the present invention three is provided
Structured flowchart, details are as follows：
With reference to Fig. 5, the server includes：
First receiver module 31, for receiving the log information of client transmission, log information includes daily record ID and type
ID；Type ID includes at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID.
Cache module 32, for log information to be respectively stored in the configuration documentation corresponding with type ID, and by day
Will information cache is in message queue.
Processing module 33, for according to message queue, using multiple service threads respectively to storing in each configuration documentation
Log information classified, form at least one sort file corresponding with type ID.
First sending module 34, for forming journal file based at least one sort file, and journal file is sent
To client.
Alternatively, server also includes：
First receiver module 31, is additionally operable to receive the log query instruction that client sends, and log query instruction includes
At least one type ID.
Calling module 35, for calling journal file to generate Query Result file according to query statement.
First sending module 34, is additionally operable to for Query Result file to be sent to client.
Example IV
Corresponding to the daily record operation method of foregoing embodiments two, Fig. 4 shows the client that the embodiment of the present invention four is provided
Structured flowchart, details are as follows：
With reference to Fig. 6, the client includes：
Generation module 41, for generating log information, log information includes daily record ID and type ID；Type ID includes transaction
At least one of time, system identifier, traffic ID, mechanism ID and teller ID.
Second sending module 42, for log information to be sent into server.
Second receiver module 43, for the journal file that the reception server sends；Journal file includes at least one classification
File, each sort file carries out classification by a service thread to the log information in the configuration documentation that formed based on type ID
What reason was formed.
Display module 44, for show log file.
Alternatively, client also includes：
Second receiver module 43, is additionally operable to the log query instruction of receiving user's input, and log query instruction is included at least
One type ID.
Second sending module 42, is additionally operable to for log query instruction to be sent to server.
Second receiver module 43, is additionally operable to the Query Result text corresponding with log query instruction of the reception server transmission
Part.
Display module 44, is additionally operable to show Query Result file.
Embodiment five
Fig. 7 shows the flowchart of the daily record operation method that the embodiment of the present invention five is provided.As shown in fig. 7, the day
Will operation method comprises the steps：
S501：Connect client and generate log information, and log information is sent into server.Log information includes daily record ID
With type ID.Type ID includes at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID.
S502：Server receives log information, and log information is respectively stored in into the configuration documentation corresponding with type ID
In, and log information is buffered in message queue.
S503：Server foundation message queue, using multiple service threads day respectively to storing in each configuration documentation
Will information is classified, and forms at least one sort file corresponding with type ID.
S504：Server forms journal file based at least one sort file, and journal file is sent into client.
S505：Client is received and show log file.
Embodiment six
Fig. 8 shows the schematic block diagram of the daily record runtime that the embodiment of the present invention six is provided.As shown in figure 8, the daily record
Daily record runtime, it is characterised in that including client and server.
Client 61, for generating log information, and is sent to server by log information.Log information includes daily record ID
With type ID.Type ID includes at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID.
Server 62, for receiving log information, by log information the configuration text corresponding with type ID is respectively stored in
In shelves, and log information is buffered in message queue.
Server 62, for according to message queue, using multiple service threads respectively to storage in each configuration documentation
Log information is classified, and forms at least one sort file corresponding with type ID.
Server 62, for forming journal file based at least one sort file, and is sent to client by journal file
End.
Client 61, for receiving simultaneously show log file.
In embodiment provided by the present invention, it should be understood that disclosed apparatus and method, can pass through other
Mode is realized.For example, system embodiment described above is only schematic, for example, the division of the unit or unit,
It is only a kind of division of logic function, there can be other dividing mode when actually realizing, such as multiple units or component can be with
With reference to or be desirably integrated into another system, or some features can be ignored, or not perform.It is another, it is shown or discussed
Coupling each other or direct-coupling or communication connection can be INDIRECT COUPLING by some interfaces, device or unit or
Communication connection, can be electrical, mechanical or other forms.
The unit as separating component explanation can be or may not be it is physically separate, it is aobvious as unit
The part for showing can be or may not be physical location, you can with positioned at a place, or can also be distributed to multiple
On NE.Some or all of unit therein can according to the actual needs be selected to realize the mesh of this embodiment scheme
's.
In addition, each functional unit in each embodiment of the invention can be integrated in a processing unit, it is also possible to
It is that unit is individually physically present, it is also possible to which two or more units are integrated in a unit.Above-mentioned integrated list
Unit both can be realized in the form of hardware, it would however also be possible to employ the form of SFU software functional unit is realized.
If the integrated unit is realized using in the form of SFU software functional unit and as independent production marketing or used
When, during a computer read/write memory medium can be stored in.Based on such understanding, the technical scheme of the embodiment of the present invention
The part for substantially contributing to prior art in other words or all or part of the technical scheme can be with software products
Form embody, the computer software product is stored in a storage medium, including some instructions use so that one
Computer equipment (can be personal computer, server, or network equipment etc.) or processor (processor) perform this
The all or part of step of bright embodiment each embodiment methods described.And aforesaid storage medium includes：USB flash disk, portable hard drive,
Read-only storage (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic
Dish or CD etc. are various can be with the medium of store program codes.
Embodiment described above only to illustrate technical scheme, rather than a limitation；Although with reference to aforementioned reality
Apply example to be described in detail the present invention, it will be understood by those within the art that：It still can be to aforementioned each
Technical scheme described in embodiment is modified, or carries out equivalent to which part technical characteristic；And these are changed
Or replace, the spirit and scope of the essence disengaging various embodiments of the present invention technical scheme of appropriate technical solution are not made, all should
It is included within protection scope of the present invention.
Claims (10)
1. a kind of daily record operation method, it is characterised in that including the following steps that server is performed：
The log information that client sends is received, the log information includes daily record ID and type ID；Type ID includes handing over
At least one of easy time, system identifier, traffic ID, mechanism ID and teller ID；
The log information is respectively stored in the configuration documentation corresponding with type ID, and the log information is delayed
In there is message queue；
According to the message queue, using multiple service threads daily record letter respectively to storing in each configuration documentation
Breath is classified, and forms at least one sort file corresponding with type ID；
Journal file is formed based at least one sort file, and the journal file is sent into the client.
2. method as claimed in claim 1, it is characterised in that also include：
The log query instruction that the client sends is received, the log query instruction includes type described at least one
ID；
Journal file is called to generate Query Result file according to the query statement；
The Query Result file is sent into client.
3. a kind of daily record operation method, it is characterised in that including the following steps of client executing：
Log information is generated, the log information includes daily record ID and type ID；Type ID includes exchange hour, system
At least one of ID, traffic ID, mechanism ID and teller ID；
The log information is sent into server；
Receive the journal file that the server sends；The journal file includes at least one sort file, each described point
Class file is carried out classification process and is formed by a service thread to the log information in the configuration documentation that formed based on type ID
's；
Show the journal file.
4. method as claimed in claim 3, it is characterised in that also include：
The log query instruction of receiving user's input, the log query instruction includes at least one type ID；
Log query instruction is sent into the server；
Receive the Query Result file corresponding with log query instruction that the server sends；
Show the Query Result file.
5. a kind of daily record operation method, it is characterised in that comprise the steps：
Client generates log information, and the log information is sent into server；The log information include daily record ID and
Type ID；Type ID includes at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID；
Server receives the log information, and the log information is respectively stored in into the configuration text corresponding with type ID
In shelves, and the log information is buffered in message queue；
Server according to the message queue, using multiple service threads respectively to described in storage in each configuration documentation
Log information is classified, and forms at least one sort file corresponding with type ID；
Server forms journal file based at least one sort file, and the journal file is sent into the client；
Client receives and shows the journal file.
6. a kind of server, it is characterised in that include：
First receiver module, for receiving the log information of client transmission, the log information includes daily record ID and type ID；
Type ID includes at least one of exchange hour, system identifier, traffic ID, mechanism ID and teller ID；
Cache module, for the log information to be respectively stored in the configuration documentation corresponding with type ID, and will
The log information is buffered in message queue；
Processing module, for according to the message queue, using multiple service threads respectively to depositing in each configuration documentation
The log information of storage is classified, and forms at least one sort file corresponding with type ID；
First sending module, for forming journal file based at least one sort file, and the journal file is sent to
The client.
7. server as claimed in claim 6, it is characterised in that also include：
First receiver module, is additionally operable to receive the log query instruction that the client sends, and the log query refers to
Order includes type ID described at least one；
Calling module, for calling journal file to generate Query Result file according to the query statement；
First sending module, is additionally operable to for the Query Result file to be sent to client.
8. a kind of client, it is characterised in that include：
Generation module, for generating log information, the log information includes daily record ID and type ID；Type ID includes handing over
At least one of easy time, system identifier, traffic ID, mechanism ID and teller ID；
Second sending module, for the log information to be sent into server；
Second receiver module, for receiving the journal file that the server sends；The journal file includes at least one point
Class file, each sort file is by a service thread to the log information in the configuration documentation that formed based on type ID
Carry out classifying what process was formed；
Display module, for showing the journal file.
9. client as claimed in claim 8, it is characterised in that also include：
Second receiver module, is additionally operable to the log query instruction of receiving user's input, log query instruction include to
Few type ID；
Second sending module, is additionally operable to for log query instruction to be sent to the server；
Second receiver module, is additionally operable to receive the inquiry corresponding with log query instruction that the server sends
Destination file；
The display module, is additionally operable to show the Query Result file.
10. a kind of daily record runtime, it is characterised in that including client and server；
The client, for generating log information, and is sent to server by the log information；The log information includes
Daily record ID and type ID；Type ID includes at least in exchange hour, system identifier, traffic ID, mechanism ID and teller ID
It is individual；
The server, for receiving the log information, the log information is respectively stored in relative with type ID
In the configuration documentation answered, and the log information is buffered in message queue；
The server, for according to the message queue, using multiple service threads respectively in each configuration documentation
The log information of storage is classified, and forms at least one sort file corresponding with type ID；
The server, for forming journal file based at least one sort file, and is sent to institute by the journal file
State client；
The client, for receiving and shows the journal file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611206252.5A CN106649729A (en) | 2016-12-23 | 2016-12-23 | Log running method and system, client and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611206252.5A CN106649729A (en) | 2016-12-23 | 2016-12-23 | Log running method and system, client and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106649729A true CN106649729A (en) | 2017-05-10 |
Family
ID=58828148
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611206252.5A Pending CN106649729A (en) | 2016-12-23 | 2016-12-23 | Log running method and system, client and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106649729A (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107608860A (en) * | 2017-09-29 | 2018-01-19 | 郑州云海信息技术有限公司 | A kind of method, apparatus, the equipment of error log classification storage |
| CN108134824A (en) * | 2017-12-19 | 2018-06-08 | 深圳马可孛罗科技有限公司 | A kind of travel products running log recording method and system |
| CN108205476A (en) * | 2017-12-27 | 2018-06-26 | 郑州云海信息技术有限公司 | A kind of method and device of multithreading daily record output |
| CN108319543A (en) * | 2018-01-24 | 2018-07-24 | 广州江南科友科技股份有限公司 | A kind of asynchronous processing method and its medium, system of computer log data |
| CN109558756A (en) * | 2018-12-13 | 2019-04-02 | 艾体威尔电子技术(北京)有限公司 | A kind of EMV packet parsing tool |
| CN110188246A (en) * | 2019-05-27 | 2019-08-30 | 四川大学 | A kind of multivalence value assets classes storage method of block chain |
| CN110505238A (en) * | 2019-09-06 | 2019-11-26 | 杭州安恒信息技术股份有限公司 | The processing unit and method of message queue based on EDR |
| CN110968561A (en) * | 2018-09-30 | 2020-04-07 | 北京国双科技有限公司 | Log storage method and distributed system |
| CN111061628A (en) * | 2019-11-21 | 2020-04-24 | 世纪龙信息网络有限责任公司 | Data analysis method, system, device, computer equipment and storage medium |
| CN111198892A (en) * | 2019-12-24 | 2020-05-26 | 泰康保险集团股份有限公司 | Information processing method, information processing device, electronic equipment and storage medium |
| CN111522952A (en) * | 2020-04-26 | 2020-08-11 | 厦门美图之家科技有限公司 | Log data processing method, device, equipment and storage medium |
| CN115086206A (en) * | 2022-06-14 | 2022-09-20 | 工银科技有限公司 | Client software debugging method and device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101969386A (en) * | 2010-11-09 | 2011-02-09 | 道有道(北京)科技有限公司 | Log acquisition device and log acquisition method |
| CN102480489A (en) * | 2010-11-30 | 2012-05-30 | 北京千橡网景科技发展有限公司 | Logging method and device used in distributed environment |
| CN103678089A (en) * | 2012-09-20 | 2014-03-26 | 北京南车时代信息技术有限公司 | Log output method and system for distributed software system |
| CN104580310A (en) * | 2013-10-21 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Log processing method and server |
| CN104883365A (en) * | 2015-05-14 | 2015-09-02 | 浪潮电子信息产业股份有限公司 | Method and device for storing and reading security logs and security control system |
| CN105530299A (en) * | 2015-12-12 | 2016-04-27 | 天津南大通用数据技术股份有限公司 | Directory service log realization method |
| CN105760398A (en) * | 2014-12-18 | 2016-07-13 | 中兴通讯股份有限公司 | Log recording system and log record operating method |
| CN106202305A (en) * | 2016-06-30 | 2016-12-07 | 北京北信源软件股份有限公司 | A kind of log processing method, device and Database Systems |
-
2016
- 2016-12-23 CN CN201611206252.5A patent/CN106649729A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101969386A (en) * | 2010-11-09 | 2011-02-09 | 道有道(北京)科技有限公司 | Log acquisition device and log acquisition method |
| CN102480489A (en) * | 2010-11-30 | 2012-05-30 | 北京千橡网景科技发展有限公司 | Logging method and device used in distributed environment |
| CN103678089A (en) * | 2012-09-20 | 2014-03-26 | 北京南车时代信息技术有限公司 | Log output method and system for distributed software system |
| CN104580310A (en) * | 2013-10-21 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Log processing method and server |
| CN105760398A (en) * | 2014-12-18 | 2016-07-13 | 中兴通讯股份有限公司 | Log recording system and log record operating method |
| CN104883365A (en) * | 2015-05-14 | 2015-09-02 | 浪潮电子信息产业股份有限公司 | Method and device for storing and reading security logs and security control system |
| CN105530299A (en) * | 2015-12-12 | 2016-04-27 | 天津南大通用数据技术股份有限公司 | Directory service log realization method |
| CN106202305A (en) * | 2016-06-30 | 2016-12-07 | 北京北信源软件股份有限公司 | A kind of log processing method, device and Database Systems |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107608860B (en) * | 2017-09-29 | 2021-04-23 | 郑州云海信息技术有限公司 | Method, device and equipment for classified storage of error logs |
| CN107608860A (en) * | 2017-09-29 | 2018-01-19 | 郑州云海信息技术有限公司 | A kind of method, apparatus, the equipment of error log classification storage |
| CN108134824A (en) * | 2017-12-19 | 2018-06-08 | 深圳马可孛罗科技有限公司 | A kind of travel products running log recording method and system |
| CN108205476A (en) * | 2017-12-27 | 2018-06-26 | 郑州云海信息技术有限公司 | A kind of method and device of multithreading daily record output |
| CN108319543A (en) * | 2018-01-24 | 2018-07-24 | 广州江南科友科技股份有限公司 | A kind of asynchronous processing method and its medium, system of computer log data |
| CN110968561B (en) * | 2018-09-30 | 2024-02-13 | 北京国双科技有限公司 | Log storage method and distributed system |
| CN110968561A (en) * | 2018-09-30 | 2020-04-07 | 北京国双科技有限公司 | Log storage method and distributed system |
| CN109558756A (en) * | 2018-12-13 | 2019-04-02 | 艾体威尔电子技术(北京)有限公司 | A kind of EMV packet parsing tool |
| CN109558756B (en) * | 2018-12-13 | 2022-04-12 | 艾体威尔电子技术(北京)有限公司 | EMV message analysis tool |
| CN110188246A (en) * | 2019-05-27 | 2019-08-30 | 四川大学 | A kind of multivalence value assets classes storage method of block chain |
| CN110505238B (en) * | 2019-09-06 | 2022-01-21 | 杭州安恒信息技术股份有限公司 | EDR-based message queue processing device and method |
| CN110505238A (en) * | 2019-09-06 | 2019-11-26 | 杭州安恒信息技术股份有限公司 | The processing unit and method of message queue based on EDR |
| CN111061628A (en) * | 2019-11-21 | 2020-04-24 | 世纪龙信息网络有限责任公司 | Data analysis method, system, device, computer equipment and storage medium |
| CN111061628B (en) * | 2019-11-21 | 2023-09-01 | 天翼数字生活科技有限公司 | Data analysis method, system, device, computer equipment and storage medium |
| CN111198892A (en) * | 2019-12-24 | 2020-05-26 | 泰康保险集团股份有限公司 | Information processing method, information processing device, electronic equipment and storage medium |
| CN111522952A (en) * | 2020-04-26 | 2020-08-11 | 厦门美图之家科技有限公司 | Log data processing method, device, equipment and storage medium |
| CN115086206A (en) * | 2022-06-14 | 2022-09-20 | 工银科技有限公司 | Client software debugging method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106649729A (en) | Log running method and system, client and server | |
| US20240152754A1 (en) | Aggregated embeddings for a corpus graph | |
| CN106911780A (en) | Traffic ID generation method, apparatus and system | |
| US20080228602A1 (en) | Credit card lost-and-found notification | |
| US8825798B1 (en) | Business event tracking system | |
| CN104063293A (en) | Data backup method and streaming computing system | |
| CN103310460A (en) | Image characteristic extraction method and system | |
| CN109447641A (en) | To the method and apparatus of block chain browser transport block chain data | |
| CN105701112A (en) | Data processing method, apparatus and system | |
| US11823026B2 (en) | Artificial intelligence system employing graph convolutional networks for analyzing multi-entity-type multi-relational data | |
| CN106503020A (en) | Daily record data processing method and processing device | |
| US20090157832A1 (en) | How to enable "out of box" messages tracking in messaging system | |
| CN110196759A (en) | Distributed transaction processing method and device, storage medium and electronic device | |
| CN106776795A (en) | Method for writing data and device based on Hbase databases | |
| US8560698B2 (en) | Allocating unique identifiers using metadata | |
| CN107635012A (en) | A kind of match messages method, server and computer-readable recording medium | |
| CN109919683A (en) | A kind of system of advertisement pushing, method and device | |
| CN109213745A (en) | A kind of distributed document storage method, device, processor and storage medium | |
| CN112817919A (en) | Data merging method and device and computer readable storage medium | |
| CN112788108A (en) | Cross-block-chain distributed message processing method, platform and storage medium | |
| CN106021597A (en) | Data sheet updating method and system for account transactions | |
| CN113630476B (en) | Communication method and communication device applied to computer cluster | |
| CN110266610B (en) | Traffic identification method and device and electronic equipment | |
| CN105389355B (en) | Data processing method and terminal | |
| CN107071057A (en) | A kind of user's request processing method and system based on bank's API server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170510 |