CN107153539B - File interface system - Google Patents
File interface system Download PDFInfo
- Publication number
- CN107153539B CN107153539B CN201710253183.1A CN201710253183A CN107153539B CN 107153539 B CN107153539 B CN 107153539B CN 201710253183 A CN201710253183 A CN 201710253183A CN 107153539 B CN107153539 B CN 107153539B
- Authority
- CN
- China
- Prior art keywords
- file
- customer service
- interface
- module
- function library
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Abstract
The invention relates to a file interface system, which comprises a main function module and a function library, wherein the main function module is used for acquiring an interface number, reading a function library name to be called and an execution step from an interface parameter configuration table according to the interface number, and loading a corresponding function library according to the function library name; the function library is used for storing the packaged functional modules and executing the corresponding functional modules according to the execution steps. The file interface system provided by the invention has the following advantages: when meeting the requirement of a first-level customer service file interface, developers do not need to rewrite the same code, and the code reuse rate is high; the scheduling strategy is configurable, and can be dynamically and flexibly executed according to the sequence of configuration steps; the technical specifications of the file interfaces are unified, maintenance personnel can maintain the file interfaces only by mastering the use modes of sqlplus and sqlldr tools, and the maintenance is convenient.
Description
Technical Field
The invention relates to the field of file interface development, in particular to a file interface system.
Background
The existing file interface system has the following disadvantages that the file interface scheduling policy is managed by crontab:
1. when meeting the requirement of a first-level customer service file interface, developers need to rewrite the same code, and the reuse rate is low;
2. the file interface scheduling strategy is managed by the crontab, so that too many crontab configuration files are very disordered, and the execution sequence is easy to make mistakes;
3. the operation logs are disordered to be not beneficial to monitoring, and a unified management scheme is lacked;
4. the file interface has no uniform technical specification, the technical architecture of the interface program is disordered, and the maintenance is difficult after the online process.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a file interface system aiming at the defects of the prior art.
The technical scheme for solving the technical problems is as follows:
a file interface system comprising a master function module and a function library, wherein:
the main function module is used for acquiring an interface number, reading a function library name to be called and an execution step from an interface parameter configuration table according to the interface number, and loading a corresponding function library according to the function library name;
the function library is used for storing the encapsulated function module and executing the corresponding function module according to the execution step.
The invention has the beneficial effects that: the invention provides a file interface system, which comprises a main function module and a function library, acquires an interface number through the main function module, reads a function library name to be called and an execution step from an interface parameter configuration table according to the interface number, loads a corresponding function library according to the function library name, and calls a function module stored in the function library to realize different file interface functions, and has the following advantages:
when meeting the requirement of a first-level customer service file interface, developers do not need to rewrite the same code, and the code reuse rate is high;
the problem that too many and very chaotic crontab configuration files are caused due to the fact that a file interface scheduling strategy is managed by the crontab, and the execution sequence is easy to make mistakes is solved, the scheduling strategy is changed into a configurable strategy, and the scheduling strategy can be dynamically and flexibly executed according to the sequence of configuration steps;
the technical specifications of the file interfaces are unified, maintenance personnel only need to master the use modes of sqlplus and sqlldr tools to achieve the maintenance purpose, and the maintenance is convenient.
On the basis of the technical scheme, the invention can be further improved as follows.
Further, the functional module includes:
and the acquisition module is used for acquiring customer service data and writing the customer service data into the interface table.
Further, the functional module further includes:
and the generating module is used for reading the customer service data from the interface table, reading a file naming rule from the interface parameter configuration table, generating a customer service file from the customer service data in the interface table according to the file naming rule, and storing the customer service file in a file directory.
Further, the functional module further includes:
and the transmission module is used for transmitting the customer service file.
Further, the transmission module includes:
the uploading unit is used for uploading the customer service file to a superior server;
and the downloading unit is used for downloading the file in the superior server to a local server.
Further, the functional module further includes:
and the scanning and warehousing module is used for scanning the customer service file, judging whether the customer service file meeting the file naming rule exists or not, and writing the customer service data in the customer service file into a physical table.
Further, the scanning and warehousing module comprises:
the scanning unit is used for scanning whether a customer service file meeting the file naming rule exists in the file directory or not, and if not, warning information is sent out;
and the warehousing unit is used for judging whether the customer service file is configured with a pre-warehousing storage process or not when the customer service file meeting the file naming rule exists in the file directory, calling the pre-warehousing storage process if the customer service file is configured, cleaning or initializing the interface table, introducing the customer service file into the interface table, judging whether the customer service file is configured with a post-warehousing storage process or not, and outputting the customer service file in the interface table to a physical table if the customer service file is configured.
Further, the functional module further includes:
and the background program starting module is used for acquiring the background program to be executed and directly starting the background program.
Further, the function module is further configured to automatically generate an operation log of the corresponding function module when the function library executes the corresponding function module according to the execution step, and store the operation log in a database log table.
The beneficial effect of adopting the further scheme is that: the problem that log storage is disordered and is not beneficial to monitoring is solved, the program execution result is output to a database or a file server and is output into logs with a uniform format, and monitoring and alarming are convenient to add according to the execution result.
Further, the main function module and the function module are both shell scripts.
Further, the functional modules can be added or deleted according to requirements.
Further, the function library is named as a version of the function library, the versions of the function library are different, and the number and types of the function modules in the function library can also be different.
Advantages of additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
Fig. 1 is a structural framework diagram of a file interface system according to an embodiment of the present invention.
Detailed Description
The principles and features of this invention are described below in conjunction with the following drawings, which are set forth by way of illustration only and are not intended to limit the scope of the invention.
As shown in fig. 1, a structural framework diagram of a file interface system provided in an embodiment of the present invention includes a main function module 110 and a function library 120, where:
the main function module 110 is configured to obtain an interface number, read a name of a function library to be called and an execution step from an interface parameter configuration table according to the interface number, and load a corresponding function library 120 according to the name of the function library, where the interface number is a unique identifier of an interface, and is transmitted when a program to be accessed to the interface is started, the name of the function library is version information of the function library 120 to be loaded by a file interface corresponding to the interface number, and the execution step is a step of a function module to be executed by the file interface corresponding to the interface number;
the function library 120 is used for storing the encapsulated function modules and executing the corresponding function modules according to the execution steps, a developer needs to encapsulate the public codes into the shell script function library 120, upload the shell script function library 120 to a server in a script file form, and then write the function library name into a field corresponding to the interface number in the interface parameter configuration table.
For example, when the interface number is 0001, the field value of the STEP OP _ STEP is executed to be 4, 1, 2, 3, the modules that need to be called for reading the main function are the generation module, the scanning and warehousing module, and the transmission module, and the sequence that needs to be executed is as follows:
start → upload/download → scan file → parse warehouse → generate file → end.
The called modules and the steps to be executed can be freely configured according to actual requirements, and the sequence and the number of the executed modules and the sequence and the number of the executed functions are not fixedly limited.
The file interface system provided in the above embodiment includes the main function module 110 and the function library 120, and obtains an interface number through the main function module 110, reads a name of the function library to be called and an execution step from the interface parameter configuration table according to the interface number, loads the corresponding function library 120 according to the name of the function library, and calls the function module stored in the function library 120 to implement different file interface functions, and the system has the following advantages:
when meeting the requirement of a first-level customer service file interface, developers do not need to rewrite the same code, and the code reuse rate is high;
the problem that too many and very chaotic crontab configuration files are caused due to the fact that a file interface scheduling strategy is managed by the crontab, and the execution sequence is easy to make mistakes is solved, the scheduling strategy is changed into a configurable strategy, and the scheduling strategy can be dynamically and flexibly executed according to the sequence of configuration steps;
the technical specifications of the file interfaces are unified, maintenance personnel only need to master the use modes of sqlplus and sqlldr tools to achieve the maintenance purpose, and the maintenance is convenient.
Further, the functional module specifically includes:
and the acquisition module 121 is configured to acquire customer service data through the sql script and write the customer service data into the interface table, where the sql script is a service module and is written in advance by a developer.
The acquisition module 121 needs to read the following data from the interface parameter configuration table:
interface numbering: the unique identifier of the interface is transmitted when a program to be accessed into the interface is started;
file naming rules: file naming rules of customer service files;
file name: the file name format of the customer service file;
the file type: generating different file headers and file name suffixes according to file types;
interface table: storing the collected customer service data;
file content delimiter: a content separator, typically a separator of '|';
file header inspection rules: detecting whether a file header exists;
checking a file checking rule: detecting whether a check file exists;
file naming rule checking rules: detecting whether the file naming rule is correct or not;
storage process for acquired data: the main function module 110 calls a storage process for collecting data to collect customer service data, and writes the collected customer service data into the interface table.
The generating module 122 is configured to read customer service data from the interface table, where the customer service data may be data acquired by the acquiring module 121 or data pre-stored in the interface table, read a file naming rule from the interface parameter configuration table, generate a customer service file according to the file naming rule from the customer service data in the interface table through an sql script, and store the customer service file in a file directory of a disk file, where the sql script is a service module and is written in advance by a developer.
The transmission module 123 is configured to transmit the customer service file through an ftp script, where the ftp script is a service module and is written in advance by a developer, and the transmission module 123 specifically includes:
the uploading unit is used for uploading the customer service file to a superior server;
and the downloading unit is used for downloading the file in the superior server to the local server.
The transmission module 123 also needs to read the following data from the interface parameter configuration table:
IP address, port number: the host IP address and port number of the upper server to be accessed remotely;
login user name and password: login user name and password of host of superior server;
remote path: the path and the position of a host of a superior server for storing files;
local path: the path and the position of a host of the local server for storing files;
the operation type is as follows: uploading or downloading.
A scanning and warehousing module 124, configured to scan the customer service file, determine whether the customer service file meeting the file naming rule exists, and write the customer service data in the customer service file into a physical table, where the scanning and warehousing module 124 specifically includes:
the scanning unit is used for scanning whether a customer service file meeting a file naming rule exists in the file directory or not, and if not, warning information is sent out;
and the warehousing unit is used for judging whether the customer service file is configured with a pre-warehousing storage process when the customer service file meeting the file naming rule exists in the file directory, calling the pre-warehousing storage process if the customer service file is configured, cleaning or initializing the interface table, calling the sqlldr script to introduce the customer service file into the interface table, judging whether the customer service file is configured with a post-warehousing storage process, and outputting the customer service file in the interface table to a real entity table if the customer service file is configured.
The scan-in-store module 124 also needs to read the following data from the interface parameter configuration table:
scanning file alarm short message sending rules: when the customer service file does not exist, judging whether an alarm short message needs to be issued or not;
controlling a file: an sqlldr script used when the customer service file is imported into the interface table;
storage process before warehousing: the field is a storage process name, and if the field is configured with a corresponding storage process name, the main function module 110 will call the storage process to complete the initialization action before the customer service file is imported into the interface table;
and (4) storage process after warehousing: the field is a name of a storage process, and if the field is configured with a corresponding name of a storage process, the main function module 110 calls the storage process to perform an import operation when the service file is imported into the interface table.
And the background program starting module 125 is used for acquiring the background program to be executed and calling the shell script through the main function module 110 to directly start the background program.
The daemon launch module 125 also needs to read the following data from the interface parameter configuration table:
name of background program: the filename of the daemon when the main function module 110 starts.
Further, the function module is also configured to automatically generate an operation log of the corresponding function module when the function library 120 executes the corresponding function module according to the execution step, and store the operation log in the database log table.
Further, the main function module 110 and the function module are both shell scripts.
Further, the functional modules can be added or deleted according to requirements, for example, a monitoring detection module can be added for monitoring and monitoring the fault of the file interface system and feeding back the fault in time.
Further, the name of the function library is the version of the function library 120, the versions of the function library 120 are different, and the number and types of the function modules in the function library may also be different, for example, when the name of the function library is 2.0, the function modules may include an acquisition module 121, a generation module 122, and a transmission module 123; when the name of the function library is 3.0, the functional modules may include an acquisition module 121, a generation module 122, a transmission module 123, a scan-in library module 124, and a background program starting module 125.
Another embodiment provided by the present application is as follows:
the invention is further explained and illustrated by taking the function of the calling acquisition module as an example.
Starting a main function module, initializing a file interface system, and loading configuration parameters initialized by the system;
acquiring an interface number in the configuration parameter, reading a function library name to be called and an execution step from an interface parameter configuration table according to the interface number, wherein the execution step is to execute only an acquisition module;
loading a function library according to the name of the function library, and calling an acquisition module;
searching a storage process for acquired data required by the acquired data according to the interface number;
according to the storage process for the collected data, customer service data formed after statistics and analysis are written into an interface table according to file content separators, for example, the data in the interface table can be 1|02|20160909|001001|03|02|01 …;
and recording the operation log of the collected data into a database log table.
Another embodiment provided by the present application is as follows:
the invention is further explained and illustrated by taking the function of the calling generation module as an example.
Starting a main function module, initializing a file interface system, and loading configuration parameters initialized by the system;
acquiring an interface number in the configuration parameter, reading a function library name to be called and an execution step from an interface parameter configuration table according to the interface number, wherein the execution step is to execute only a generation module;
loading a function library according to the name of the function library, and calling a generating module;
calling an interface table, a file naming rule and an sqlplus script from an interface parameter configuration table according to the interface number;
generating a customer service file by the customer service data in the interface table according to a file naming rule through an sqlplus script;
storing the customer service file in a file directory of the disk file;
and recording the operation log of the generation module into a database log table.
Another embodiment provided by the present application is as follows:
the invention will be further explained and explained by taking the function of the transmission module as an example.
Starting a main function module, initializing a file interface system, and loading configuration parameters initialized by the system;
acquiring an interface number in the configuration parameter, reading a function library name to be called and an execution step from an interface parameter configuration table according to the interface number, wherein the execution step is to execute only a transmission module;
loading a function library according to the name of the function library and calling a transmission module;
reading the operation type in the interface file configuration table, if the operation type is an uploading operation, executing an uploading unit, accessing a superior server according to the IP address and the port number, and uploading the customer service file according to a remote path;
if the downloading operation is carried out, a downloading unit is executed, the superior server is accessed according to the IP address and the port number, a host computer in the superior server is logged in according to the login user name and the password, a file needing to be downloaded is obtained from the host computer, and the file is stored in a local server according to a local path;
and recording the operation log of the transmission module into a database log table.
Another embodiment provided by the present application is as follows:
the invention is further explained and explained by taking the function of calling the scanning and warehousing module as an example.
Starting a main function module, initializing a file interface system, and loading configuration parameters initialized by the system;
acquiring an interface number in the configuration parameter, reading a function library name to be called and an execution step from an interface parameter configuration table according to the interface number, wherein the execution step is to execute only a scanning warehousing module;
loading a function library according to the name of the function library, and calling a scanning and warehousing module;
scanning whether a file meeting a file naming rule exists in a file directory;
if the warning short message does not exist, judging whether the warning short message needs to be issued according to a scanning file warning short message sending rule, and if the warning short message needs to be issued, issuing the warning short message according to an interface number and a reserved number;
if yes, continuing to execute the warehousing unit;
judging whether the customer service file exists according to a file naming rule, if the customer service file exists and the customer service file is configured with a storage process before warehousing, calling the storage process before warehousing, and cleaning or initializing an interface table;
calling an sqlldr script to import the customer service file into the interface table;
if the storage process after warehousing is configured, outputting the customer service file in the interface table to the entity table;
and recording the operation log of the scanning and warehousing module into a database log table.
Another embodiment provided by the present application is as follows:
taking the function of calling a background program starting module as an example, the invention is further explained and explained, the background program to be executed needs to be uploaded to a specified directory in advance, and the specified directory is defined by developers in advance;
starting a main function module, initializing a file interface system, and loading configuration parameters initialized by the system;
acquiring an interface number in the configuration parameter, reading a function library name to be called and an execution step from an interface parameter configuration table according to the interface number, wherein the execution step is to execute only a background program starting module;
loading a function library according to the name of the function library, and calling a background program starting module;
reading a start _ backup field in an interface parameter configuration table;
acquiring a background program name to be executed according to the start _ background field;
directly starting a background program through a shell script;
and recording the operation log of the background program starting module into a database log table.
In the several embodiments provided in the present application, it should be understood that the disclosed system and method may be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, a division of modules is merely a logical division, and an actual implementation may have another division, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may also be an electrical, mechanical or other form of connection.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (9)
1. A file interface system comprising a master function module and a function library, wherein:
the main function module is used for acquiring an interface number, reading a function library name to be called and an execution step from an interface parameter configuration table according to the interface number, and loading a corresponding function library according to the function library name;
the function library is used for storing the encapsulated function modules and executing the corresponding function modules according to the execution steps;
the main function module and the function module are both shell scripts.
2. The interface system of claim 1, wherein the functional module comprises:
and the acquisition module is used for acquiring customer service data and writing the customer service data into the interface table.
3. The interface system of claim 2, wherein the functional module further comprises:
and the generating module is used for reading the customer service data from the interface table, reading a file naming rule from the interface parameter configuration table, generating a customer service file from the customer service data in the interface table according to the file naming rule, and storing the customer service file in a file directory.
4. The interface system of claim 3, wherein the functional module further comprises:
and the transmission module is used for transmitting the customer service file.
5. The interface system of claim 4, wherein the transmission module comprises:
the uploading unit is used for uploading the customer service file to a superior server;
and the downloading unit is used for downloading the file in the superior server to a local server.
6. The interface system according to any one of claims 3 to 5, wherein the functional module further comprises:
and the scanning and warehousing module is used for scanning the customer service file, judging whether the customer service file meeting the file naming rule exists or not, and writing the customer service data in the customer service file into a physical table.
7. The interface system of claim 6, wherein the scan-binning module comprises:
the scanning unit is used for scanning whether a customer service file meeting the file naming rule exists in the file directory or not, and if not, warning information is sent out;
and the warehousing unit is used for judging whether the customer service file is configured with a pre-warehousing storage process or not when the customer service file meeting the file naming rule exists in the file directory, calling the pre-warehousing storage process if the customer service file is configured, cleaning or initializing the interface table, introducing the customer service file into the interface table, judging whether the customer service file is configured with a post-warehousing storage process or not, and outputting the customer service file in the interface table to a physical table if the customer service file is configured.
8. The interface system according to any one of claims 1 to 5, wherein the functional module further comprises:
and the background program starting module is used for acquiring the background program to be executed and directly starting the background program.
9. The interface system according to claim 8, wherein the function module is further configured to automatically generate an operation log of the corresponding function module when the function library executes the corresponding function module according to the executing step, and store the operation log in a database log table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710253183.1A CN107153539B (en) | 2017-04-18 | 2017-04-18 | File interface system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710253183.1A CN107153539B (en) | 2017-04-18 | 2017-04-18 | File interface system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107153539A CN107153539A (en) | 2017-09-12 |
| CN107153539B true CN107153539B (en) | 2021-03-30 |
Family
ID=59793497
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710253183.1A Active CN107153539B (en) | 2017-04-18 | 2017-04-18 | File interface system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107153539B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108205497A (en) * | 2018-01-02 | 2018-06-26 | 郑州云海信息技术有限公司 | A kind of shell reads the method and system of input |
| CN110795413A (en) * | 2019-10-30 | 2020-02-14 | 珠海港联科技有限公司 | Database operation interface service system with log recording function |
| CN112099772A (en) * | 2020-08-21 | 2020-12-18 | 深圳市元征科技股份有限公司 | Communication interface packaging method, device, equipment and storage medium |
| CN114978888B (en) * | 2022-04-25 | 2024-02-06 | 平安付科技服务有限公司 | Message forwarding method and device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101630285A (en) * | 2009-08-07 | 2010-01-20 | 华南理工大学 | Software performance testing method applied in embedded system |
| CN103226592A (en) * | 2013-04-15 | 2013-07-31 | 浪潮(北京)电子信息产业有限公司 | Database-based file system and file storage method |
| CN103377079A (en) * | 2012-04-16 | 2013-10-30 | 展讯通信（上海）有限公司 | Terminal, device and method for terminal application running and application program running method |
| CN104143069A (en) * | 2014-08-04 | 2014-11-12 | 上海斐讯数据通信技术有限公司 | Method and system for protecting system file |
| US9256603B1 (en) * | 2013-06-28 | 2016-02-09 | Emc Corporation | File system over fully provisioned volume file in direct mode |
| CN106383742A (en) * | 2016-09-23 | 2017-02-08 | 郑州云海信息技术有限公司 | Linux-based IO scheduling method |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9158788B2 (en) * | 2009-12-16 | 2015-10-13 | International Business Machines Corporation | Scalable caching of remote file data in a cluster file system |
| CN101706737B (en) * | 2009-12-18 | 2012-10-03 | 湖南大学 | Method for constructing synergic function library of software and hardware |
| CN101763265B (en) * | 2010-01-19 | 2012-10-03 | 湖南大学 | Procedure level software and hardware collaborative design automatized development method |
| US20120078966A1 (en) * | 2010-09-29 | 2012-03-29 | International Business Machines Corporation | File System With Content Identifiers |
| CN103676900B (en) * | 2013-12-23 | 2016-08-31 | 广西大学 | A kind of reconfigurable open type movement-control system |
| CN104317601B (en) * | 2014-10-31 | 2017-10-17 | 北京思特奇信息技术股份有限公司 | A kind of file interface development approach and system |
-
2017
- 2017-04-18 CN CN201710253183.1A patent/CN107153539B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101630285A (en) * | 2009-08-07 | 2010-01-20 | 华南理工大学 | Software performance testing method applied in embedded system |
| CN103377079A (en) * | 2012-04-16 | 2013-10-30 | 展讯通信（上海）有限公司 | Terminal, device and method for terminal application running and application program running method |
| CN103226592A (en) * | 2013-04-15 | 2013-07-31 | 浪潮(北京)电子信息产业有限公司 | Database-based file system and file storage method |
| US9256603B1 (en) * | 2013-06-28 | 2016-02-09 | Emc Corporation | File system over fully provisioned volume file in direct mode |
| CN104143069A (en) * | 2014-08-04 | 2014-11-12 | 上海斐讯数据通信技术有限公司 | Method and system for protecting system file |
| CN106383742A (en) * | 2016-09-23 | 2017-02-08 | 郑州云海信息技术有限公司 | Linux-based IO scheduling method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107153539A (en) | 2017-09-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107153539B (en) | File interface system | |
| US6167358A (en) | System and method for remotely monitoring a plurality of computer-based systems | |
| CN101013968B (en) | Automated interface testing method and system | |
| CN106294102B (en) | Application program testing method, client, server and system | |
| CN105429826A (en) | Fault detection method and device for database cluster | |
| CN105141448B (en) | A kind of acquisition method and device of daily record | |
| CN105786998A (en) | Database middleware system and method for processing data through database middleware system | |
| CN109460343A (en) | System exception monitoring method, device, equipment and storage medium based on log | |
| CN110287696B (en) | Detection method, device and equipment for rebound shell process | |
| CN112000741A (en) | Intranet and extranet data exchange system, method, device, computer equipment and medium | |
| CN112799925A (en) | Data acquisition method and device, electronic equipment and readable storage medium | |
| CN111597089B (en) | Linux system call event acquisition and caching device and method | |
| CN116204438A (en) | Test case generation method, automatic test method and related device | |
| CN109739704A (en) | A kind of interface test method, server-side and computer readable storage medium | |
| CN115904419A (en) | Method and device for installing application software based on automatic script | |
| CN115576649A (en) | Container operation safety detection method based on behavior monitoring | |
| CN103778024A (en) | Server system and message processing method thereof | |
| CN113220572A (en) | Data testing method and device and storage medium | |
| CN113656357A (en) | File management method, device, system and storage medium | |
| CN114610597A (en) | Pressure testing method, device, equipment and storage medium | |
| CN111367686A (en) | Service interface calling method and device, computer equipment and storage medium | |
| CN111611138A (en) | Log data capturing method and device, computer equipment and storage medium | |
| CN116431443A (en) | Log recording method, device, computer equipment and computer readable storage medium | |
| Kleindienst | Building a real-world logging infrastructure with Logstash, Elasticsearch and Kibana | |
| CN110990237B (en) | Information collection system, method and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |