Tracking method, device, medium and system for life complete cycle flow of bank number marking file

Abstract

The invention provides a method, a device, a medium and a system for tracking a life complete cycle flow of a bank number marking file. The method comprises the following steps: according to the type of a bank number-marking file, carrying out warehousing processing on the bank number-marking file, or carrying out preset processing on the bank number-marking file and then uploading the bank number-marking file to a static resource server; the method comprises the following steps: recording process data of initialization processing into node data before each processing stage in a life cycle flow of a bank number marking file, and after each processing stage is ended, calling a preset tool to update the node data so as to track the life cycle flow of the bank number marking file; and when the whole life cycle process of the bank number marking file is finished, calling the JSON tool class to convert the format of the node data into the JSON format, and splitting all elements of the node data and storing the elements in the whole life cycle process table. Therefore, the problem that the problem is difficult to track in the traditional bank number marking file processing flow is solved.

Description

Technical Field

[0001] The present application relates to the technical field of banking system data processing, and in particular to a method for tracking the full life cycle process of a bank numbering file, a device for tracking the full life cycle process of a bank numbering file, a computer-readable storage medium, and a banking system. Background Art

[0002] Bank-numbered files are a crucial data source within banking systems, recording transaction and customer information. They play a crucial role in bank operations, management, and decision support. Real-time and accurate processing of bank-numbered files to ensure data timeliness and integrity is crucial for banking operations.

[0003] Traditional bank numbering file processing often tracks process problems by analyzing program code in combination with logs. However, because logs are not systematic records of the entire life cycle process, they are relatively scattered, making it difficult to track problems in the traditional bank numbering file processing process. Summary of the Invention

[0004] The main purpose of this application is to provide a method for tracking the entire life cycle process of bank numbering files, a device for tracking the entire life cycle process of bank numbering files, a computer-readable storage medium and a bank system, so as to at least solve the problem that traditional bank numbering file processing processes are difficult to track problems.

[0005] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for tracking the life cycle process of a bank number file is provided, the method comprising: obtaining a bank number file, and according to the type of the bank number file, performing storage processing on the bank number file, or performing preset processing on the bank number file and uploading it to a static resource server, wherein the bank number file is a data file with actual business meaning and used for data interaction between systems, the type of the bank number file is a resource file or a data file, the resource file includes multimedia data, and the data file includes structured data; before each processing stage in the life cycle process of the bank number file, calling a preset tool to initialize the node data The process data of the initialization processing is recorded in the node data, and after each processing stage, the preset tool is called to update the node data to track the life cycle process of the bank number file. The node data includes processing results, processing time and exception information, and the process data of the initialization processing includes the start time of the initialization processing; at the end of the entire life cycle process of the bank number file, the JSON tool class is called to convert the format of the node data into JSON format, and store it in the file synchronization record table, and all elements of the node data are split and stored in the full life cycle process table, and the full life cycle process table supports SQL statement analysis.

[0006] Optionally, before calling the preset tool to initialize the node data and recording the process data of the initialization processing into the node data, the method also includes: generating a unique identification of the processing process by calling the identifier generation method of the preset tool, and the unique identification of the processing process is used to associate all processing stage information in the synchronization process of the bank number file; creating a node data to record the key information of the current processing stage, and the key information includes the unique identification of the processing process, the processing stage description, and the primary key of the file synchronization record.

[0007] Optionally, after each of the processing stages ends, the preset tool is called to update the node data, including: calling a first recording tool to record the end time and processing result of the current processing stage into the node data, wherein the end time is the specific timestamp of the completion of the processing of the current processing stage, and the processing result represents whether the processing of the current processing stage is successful; calling a second recording tool to calculate the processing time, and the processing time is the time difference between the start time and the end time of the current processing stage; if an exception occurs during the execution of the current processing stage, calling a third recording tool to record the exception information, the exception information includes the exception type and exception stack information, and the exception stack information is an error report automatically generated by the runtime environment when an error or exception is encountered during the program running; calling a complete record verification tool to determine whether the information of the current processing stage is completely recorded, and at the same time initialize the processing node data of the next stage to form a coherent life cycle tracking record.

[0008] Optionally, calling a JSON tool class to convert the format of the node data into JSON format and store it in the file synchronization record table includes: calling a summary tool to summarize the node data of all the processing stages so that the data fields of each processing stage are fully recorded, and the data fields include the start time, end time, the processing result, the processing time and the exception information; converting the data structure of the node data into a string of a JSON object to obtain a JSON string; using the JSON string as the value of a field and writing it into the corresponding row of the file synchronization record.

[0009] Optionally, according to the type of the bank number file, the bank number file is put into storage, or the bank number file is preset-processed and then uploaded to the static resource server, including: when the type of the bank number file is the resource file, the bank number file is preset-processed and then uploaded to the static resource server, and the preset processing includes image parsing processing and PDF parsing processing; when the type of the bank number file is the data file, and the configuration information of the bank number file does not contain information that requires target preset processing, the bank number file is put into storage; when the type of the bank number file is the data file, and the configuration information of the bank number file contains information that requires target preset processing, the bank number file after the target preset processing is put into storage, or the bank number file after the target preset processing is uploaded to the static resource server.

[0010] Optionally, the bank number file after the target preset processing is put into storage, or the bank number file after the target preset processing is uploaded to a static resource server, including: when the target preset processing is field adjustment processing, the bank number file after the target preset processing is put into storage; when the target preset processing is image parsing processing, the bank number file after the target preset processing is uploaded to a static resource server.

[0011] Optionally, the bank number file is processed for storage, including: according to the format characteristics, storage method, file attributes and target database stored in the configuration information of the bank number file, the bank number file is processed for storage into the target database using a corresponding processing method, the format characteristics include XML format and TXT format, the storage method is CSV, mybatis and sql splicing, the file attributes include incremental files and full files, and the target database includes a business library and a monitoring library.

[0012] According to another aspect of the present application, a device for tracking the life cycle process of a bank number file is provided, comprising: an acquisition unit, for acquiring a bank number file, and warehousing the bank number file according to the type of the bank number file, or uploading the bank number file to a static resource server after pre-processing, wherein the bank number file is a data file with actual business meaning and used for data interaction between systems, the type of the bank number file is a resource file or a data file, the resource file includes multimedia data, and the data file includes structured data; a first processing unit, for calling a preset tool to initialize the node data before each processing stage in the life cycle process of the bank number file , and record the process data of the initialization processing into the node data, and after each of the processing stages, call the preset tool to update the node data to track the life cycle process of the bank number file, the node data includes processing results, processing time and exception information, and the process data of the initialization processing includes the start time of the initialization processing; the second processing unit is used to call the JSON tool class to convert the format of the node data into JSON format at the end of the entire life cycle process of the bank number file, and store it in the file synchronization record table, and split all elements of the node data and store them in the full life cycle process table, and the full life cycle process table supports SQL statement analysis.

[0013] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute any one of the methods described.

[0014] According to another aspect of the present application, a banking system is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include methods for executing any one of the methods described.

[0015] By applying the technical solution of the present application, after the system automatically obtains the bank number file, it automatically calls the corresponding processing flow according to the file type, thereby improving processing efficiency and accuracy. Through the real-time recording mechanism (i.e., before each processing stage in the life cycle process of the bank number file, the preset tool is called to initialize the node data, and the process data of the initialization processing is recorded in the node data, and after each processing stage, the preset tool is called to update the node data), the present application can immediately understand the status of each stage, providing data support for subsequent analysis and optimization. At the end of the full life cycle process of file synchronization, the node data in the entire process is converted into JSON format and stored in the file synchronization record table. The use of JSON format, on the one hand, ensures the structuring of the data, and on the other hand, makes the reading and parsing of the data extremely simple. Since each step of the processing flow is recorded, once an exception occurs in the file synchronization, the problem can be quickly located at which specific processing stage the problem occurred by querying the JSON data and the full life cycle process table in the file synchronization record table, without the need to check the code line by line, which greatly shortens the problem troubleshooting time. This solves the problem that the traditional bank number file processing flow is difficult to track problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings that constitute part of this application are used to provide a further understanding of this application. The illustrative embodiments of this application and their descriptions are used to explain this application and do not constitute an improper limitation on this application. In the drawings:

[0017] Figure 1 A schematic diagram of a method for tracking the entire life cycle of a bank numbered document provided in accordance with an embodiment of the present application is shown;

[0018] Figure 2 A schematic diagram showing the life cycle of a bank numbering file provided according to an embodiment of the present application is shown;

[0019] Figure 3The present invention shows a structural block diagram of a device for tracking the entire life cycle of a bank numbered document provided in accordance with an embodiment of the present application. DETAILED DESCRIPTION

[0020] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0021] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] As introduced in the background technology, the traditional bank numbering file processing process often tracks process problems by analyzing the program code in combination with logs. Because the logs are not systematic records of the entire life cycle process, the logs are relatively scattered, which makes it difficult to track problems in the traditional bank numbering file processing process. In order to solve the problem that the traditional bank numbering file processing process is difficult to track problems, the embodiments of the present application provide a method for tracking the entire life cycle process of a bank numbering file, a device for tracking the entire life cycle process of a bank numbering file, a computer-readable storage medium and a bank system.

[0024] The technical solutions in the embodiments of the present invention will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present invention.

[0025] In this embodiment, a method for tracking the entire life cycle of a bank numbered file is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0026] Figure 1 This is a flow chart of a method for tracking the life cycle of a bank number file provided in accordance with an embodiment of the present application. Figure 1 As shown, the method includes the following steps:

[0027] Step S101: Obtain a bank number file and, depending on the type of the bank number file, perform storage processing on the file, or perform preset processing on the file and then upload it to a static resource server. The bank number file is a data file with actual business significance and used for data exchange between systems. The type of the bank number file is a resource file or a data file. The resource file includes multimedia data, and the data file includes structured data.

[0028] Step S102: Before each processing stage in the life cycle of the bank number file, call a preset tool to initialize node data and record the process data of the initialization process in the node data. After each processing stage, call the preset tool to update the node data to track the life cycle of the bank number file. The node data includes the processing result, processing time and exception information. The process data of the initialization process includes the start time of the initialization process.

[0029] Step S103: At the end of the entire life cycle process of the above-mentioned bank number file, call the JSON tool class to convert the format of the node data into JSON format, and store it in the file synchronization record table, and split all elements of the above-mentioned node data and store them in the full life cycle process table. The above-mentioned full life cycle process table supports SQL statement analysis.

[0030] Problem tracking is achieved by using sql statements for analysis.

[0031] In the above steps, after the system automatically obtains the bank number file, it automatically calls the corresponding processing flow according to the file type, thereby improving processing efficiency and accuracy. Through the real-time recording mechanism (i.e., before each processing stage in the life cycle process of the above bank number file, the preset tool is called to initialize the node data, and the process data of the above initialization processing is recorded in the above node data, and after each of the above processing stages is completed, the above preset tool is called to update the above node data), the application can immediately understand the status of each stage, providing data support for subsequent analysis and optimization. At the end of the full life cycle process of file synchronization, the node data in the entire process is converted into JSON format and stored in the file synchronization record table. The use of JSON format, on the one hand, ensures the structuring of data, and on the other hand, makes the reading and parsing of data extremely simple. Since each step of the processing flow is recorded, once an exception occurs in the file synchronization, the problem can be quickly located at which specific processing stage the problem occurred by querying the JSON data and the full life cycle process table in the file synchronization record table, without the need to check the code line by line, which greatly shortens the problem troubleshooting time. This solves the problem that the traditional bank number file processing flow is difficult to track problems. In addition, it is convenient for data statistics and subsequent targeted optimization processing, that is, it is convenient for subsequent data analysis.

[0032] In one embodiment of the present application, before calling the preset tool to initialize the node data and recording the process data of the above initialization processing into the above node data, the above method also includes: generating a unique identification of the processing process by calling the identifier generation method of the preset tool, and the above unique identification of the processing process is used to associate all processing stage information in the synchronization process of the above bank number file; creating the above node data to record the key information of the current processing stage, and the above key information includes the above unique identification of the processing process, the processing stage description, and the primary key of the file synchronization record.

[0033] The introduction of a unique process identifier allows for unified association of all processing stage information throughout the entire file synchronization process. Even if a file synchronization process may involve multiple retries or multiple processing branches, the DealPrcsId allows maintenance personnel to easily trace and analyze the complete path of the entire process, improving the efficiency and accuracy of troubleshooting. By recording the unique process identifier in the node data, a file synchronization process can serve as a template or case study for analyzing and optimizing the processing of other similar files. This case-based learning and optimization approach can help the system continuously evolve, improving processing efficiency and success rates.

[0034] Among them, after each of the above-mentioned processing stages is completed, the above-mentioned preset tool is called to update the above-mentioned node data, including: calling the first recording tool to record the end time and processing result of the current processing stage into the above-mentioned node data, wherein the above-mentioned end time is the specific timestamp of the completion of the processing of the above-mentioned current processing stage, and the above-mentioned processing result represents whether the processing of the above-mentioned current processing stage is successful; calling the second recording tool to calculate the above-mentioned processing time, and the above-mentioned processing time is the time difference between the start time and the end time of the above-mentioned current processing stage; in the case that an exception occurs during the execution of the above-mentioned current processing stage, calling the third recording tool to record the above-mentioned exception information, the above-mentioned exception information includes the exception type and exception stack information, and the above-mentioned exception stack information is an error report automatically generated by the runtime environment when an error or exception is encountered during the program running; calling the complete record verification tool to determine whether the information of the above-mentioned current processing stage is completely recorded, and at the same time initialize the processing node data of the next stage to form a coherent life cycle tracking record.

[0035] Specifically, recording the end time and processing results of each stage allows for precise identification of any issues within the processing flow. Compared to traditional, bulk logging, this approach directly pinpoints the specific stage and time point where a problem occurred, accelerating troubleshooting and resolution. By calculating the processing time (the difference between the start and end time of the current processing stage), the efficiency of each stage can be quantitatively assessed. This helps identify bottlenecks in the processing flow and provides data support for optimization and upgrades. Exception information, including the exception type and stack trace, provides the specific context of the exception, making it transparent and easy to track. Maintenance personnel can quickly understand the nature and location of the exception, accelerating problem remediation. Verification using a full record verification tool ensures that all critical information from the current processing stage is recorded, preventing data omissions and ensuring data integrity and consistency. Furthermore, the processing node for the next stage is initialized, forming a complete lifecycle record chain from beginning to end, enhancing process traceability and auditability.

[0036] This application provides a specific use case in which the preset tool is invoked to update the node data after each processing phase. For example, a bank needs to regularly synchronize data files to ensure consistency and real-time performance of basic data across its subsystems. This process involves multiple steps, including file download, data conversion, database update, and cache refresh. Each step is subject to potential exceptions, such as network errors, data parsing failures, and database connection issues. In this complex business scenario, the aforementioned logging and verification tools are crucial. For example, when the bank system attempts to download the latest branch information file from a remote server, the download fails due to network fluctuations. A preset first logging tool records the end time of the file download and marks the result as a failure. Subsequently, a second logging tool calculates the duration of the download attempt, and a third logging tool details the exception type (network timeout) and the complete exception stack trace. After the data file is successfully downloaded, the system enters the data conversion phase, attempting to convert the XML-formatted branch information into a CSV file for subsequent processing. If, during this process, certain fields in the file do not conform to the expected structure, resulting in conversion failure, the first logging tool will record the end time of the data conversion phase and the result of the failed processing. The second recording tool calculates the time required for data conversion, while the third recording tool records the exception type and specific exception stack information of the data structure mismatch. After the file data conversion is successful, the system prepares to update the data into the database. If there is a problem with the database connection at this time, the preset tool will record the end time and failed processing results of this stage, calculate the time required, and record the exception information of the database connection exception in detail, including the exception type and complete stack information. Regardless of whether the current stage is successful or not, the system will call the full record verification tool to ensure that all key information of this stage, such as start time, end time, time required, processing results and exception information, are fully recorded. At the same time, the tool will also initialize the processing node data of the next stage to ensure the consistency and integrity of the records throughout the life cycle.

[0037] After each processing phase, the pre-configured tool is invoked to update the node data. The benefits of this specific use case are: This recording and verification mechanism helps staff quickly pinpoint the precise stage and time point where anomalies occurred, as well as the specific cause, thereby reducing troubleshooting time and accelerating problem resolution. By recording the results and duration of each phase, the bank's IT operations staff and business analysts can clearly visualize the entire synchronization process, including successes and failures, significantly improving transparency and understanding. The collected node data can be used to analyze the success rate, average duration, and common anomaly types for each phase. This data enables targeted process optimization and troubleshooting, such as adjusting network timeout settings, optimizing data conversion algorithms, or enhancing database connection robustness. For bank management, this detailed node data and analytical reports provide crucial decision-making support. Based on data-driven insights, they can formulate more effective resource allocation strategies, such as dynamically increasing network bandwidth or database resources during peak periods to ensure smooth data synchronization.

[0038] Among them, calling the JSON tool class to convert the format of the node data into JSON format and store it in the file synchronization record table, including: calling the summary tool to summarize the above node data of all the above processing stages, so that the data fields of each of the above processing stages are fully recorded, and the above data fields include the start time, end time, the above processing results, the above processing time and the above exception information; converting the data structure of the above node data into a string of JSON objects to obtain a JSON string; using the above JSON string as the value of a field, and writing it into the corresponding row of the above file synchronization record.

[0039] JSON (JavaScript Object Notation) utilities are libraries or collections of functions used to process JSON-formatted data in programming. JSON is a lightweight data exchange format that's easy for humans to read and write, as well as for machines to parse and generate data. It's based on a subset of JavaScript but is widely used in various programming languages ​​to serialize and deserialize data.

[0040] The use of JSON format provides flexibility and standardization of data structure, making recorded data easy to process through automated tools. The key-value pair format of JSON can easily accommodate fields that may change in the processing node data, and the standardized format ensures uniform data processing and simplifies the complexity of data parsing; the JSON string of node data is written as a field value in the file synchronization record. Compared with storage as multiple fields or independent files, this centralized storage method improves the efficiency of data storage. At the same time, JSON fields support efficient database queries, making the query and analysis of file synchronization records faster and improving overall query performance; operation and maintenance personnel can quickly view the complete life cycle record of a file synchronization without switching and searching in multiple tables or log files, simplifying system operation and maintenance work. Quickly locate problems: When an exception occurs in file synchronization, operation and maintenance personnel can directly use the exception information and processing stage description in the JSON field to quickly locate the stage where the problem occurred, reducing the time and cost of problem troubleshooting.

[0041] Among them, according to the type of the above-mentioned bank number file, the above-mentioned bank number file is put into storage for processing, or the above-mentioned bank number file is preset-processed and then uploaded to the static resource server, including: when the type of the above-mentioned bank number file is the above-mentioned resource file, the above-mentioned bank number file is preset-processed and then uploaded to the above-mentioned static resource server, and the above-mentioned preset processing includes image parsing processing and PDF parsing processing; when the type of the above-mentioned bank number file is the above-mentioned data file, and the configuration information of the above-mentioned bank number file does not contain information that requires target preset processing, the above-mentioned bank number file is put into storage for processing; when the type of the above-mentioned bank number file is the above-mentioned data file, and the configuration information of the above-mentioned bank number file contains information that requires the above-mentioned target preset processing, the above-mentioned bank number file after the above-mentioned target preset processing is put into storage for processing, or the above-mentioned bank number file after the above-mentioned target preset processing is uploaded to the static resource server.

[0042] Specifically, when the bank's number file is a resource file (such as an image, PDF, etc.), the system converts the file content into a format that the system can recognize and store through a preset processing flow (such as parsing images and PDF processing), and then uploads it to the static resource server. This processing method ensures the rapid and accurate conversion of resource files, avoids processing failures due to incompatible file formats, and improves the processing efficiency of resource files and system stability. For data files, the system can adopt different processing strategies based on whether there are preset processing requirements in its configuration information. If no specific preprocessing is specified in the configuration, the data file will be directly put into storage for processing, which simplifies the processing flow and speeds up data synchronization. If there is a preprocessing requirement in the configuration, the system will first perform preprocessing (such as data cleaning, format conversion, etc.) and then put it into storage, ensuring the accuracy and consistency of the data; the flexible application of configuration information enables the system to adjust the processing strategy according to different file types and specific requirements, enhancing the adaptability and scalability of the system. This means that even when faced with new types of bank number files or complex processing requirements, the system can be quickly adjusted without the need for large-scale modifications to the core code; by pre-processing resource files and data files for type matching, processing failures caused by mismatches in file formats and data structures are reduced, thereby significantly improving the success rate of file synchronization and reducing subsequent troubleshooting and data repair work; resource files are uploaded to the static resource server instead of directly into the database, avoiding excessive database space occupation, optimizing storage strategies, and saving storage resources. At the same time, the high concurrent access capability of the static resource server also ensures rapid access and distribution of resource files; through pre-processing, data files are formatted and cleaned to ensure data compliance and security. For example, for the processing of sensitive information, encryption or desensitization can be performed at this stage to avoid the risk of directly exposing the original data in subsequent processing links.

[0043] Among them, the step S101 of warehousing the above-mentioned bank number file after the above-mentioned target preset processing, or uploading the above-mentioned bank number file after the above-mentioned target preset processing to the static resource server, includes: when the above-mentioned target preset processing is field adjustment processing, warehousing the above-mentioned bank number file after the target preset processing; when the above-mentioned target preset processing is image parsing processing, uploading the above-mentioned bank number file after the above-mentioned target preset processing to the static resource server.

[0044] Specifically, when the target preset processing is field adjustment, the system standardizes, cleans, or converts the fields in the data file to ensure that the incoming data meets the database's structural requirements and business rules. This precise data preprocessing effectively avoids data quality issues that could lead to data entry failures or database anomalies, improving data consistency and integrity, and thus ensuring reliable and efficient data synchronization. For resource files, such as images or PDFs, pre-defined processing, such as image parsing, can be used to convert these files into a format that is convenient for storage and quick access before uploading them to a static resource server. Static resource servers typically offer superior file storage and distribution capabilities, enabling rapid response to external requests, improving resource file access speed and user experience. Centralized storage and management of these resource files also facilitates subsequent maintenance and data security. By separating resource file processing and storage from the database, database read and write operations are reduced, avoiding performance bottlenecks that can arise when processing large amounts of unstructured data. This helps maintain efficient database operation and enhances overall system stability and responsiveness. By implementing preprocessing and differentiated processing strategies, problems at any stage of processing can be precisely identified. For example, if a data file fails to be stored, it can be quickly determined whether the problem lies in data cleaning or field adjustments during the pre-processing phase. This greatly simplifies troubleshooting and reduces problem resolution time.

[0045] In one embodiment of the present application, the above-mentioned bank number file is processed for storage, including: according to the format characteristics, storage method, file attributes and target database stored in the configuration information of the above-mentioned bank number file, the above-mentioned bank number file is processed for storage into the above-mentioned target database using the corresponding processing method, the above-mentioned format characteristics include XML format and TXT format, the above-mentioned storage method is CSV, mybatis and sql splicing, the above-mentioned file attributes include incremental files and full files, and the above-mentioned target database includes a business library and a monitoring library.

[0046] Different file formats and attributes require different processing methods. For example, XML files may require parsing tags and attributes, while TXT files focus on field delimiters. Using the format characteristics in the configuration information, the system can intelligently select the most appropriate parser and conversion tools to ensure efficient and accurate conversion of file data, reducing data processing errors and time consumption. Based on the type of target database (business database or monitoring database) and the specified storage method (such as CSV import, MyBatis batch insert, or SQL splicing execution), the system can flexibly adjust the data writing strategy to store data in the most suitable manner. This not only improves the versatility of data synchronization but also reduces processing delays caused by database characteristics and limitations. By distinguishing the attributes of incremental and full files, the system can select the appropriate storage mechanism. For incremental files, the system can implement update and incremental load strategies, while for full files, it performs clearing and full load. This approach reduces unnecessary data redundancy and optimizes data storage, while also improving database query performance and data management efficiency.

[0047] The definition of the processing stage is shown in Table 1.

[0048] Table 1

[0049]

[0050]

[0051] The data fields and their meanings for each stage are shown in Table 2.

[0052] Table 2

[0053]

[0054]

[0055] The definition of the DealStageAssmbler tool is shown in Table 3.

[0056] Table 3

[0057]

[0058] For the existing historical code, sort out the processing flow, define the processing stages, and simply call the DealStageAssmbler tool class (i.e., the preset tool) before and after the processing stages. Execute the corresponding methods at the beginning of the full life cycle process, the beginning of each stage, and the end of the entire life cycle, so that the existing processing logic can be transformed without logic intrusion.

[0059] Define the interface class AbsStage and the interface method protected abstract DealStageEnumcurrentDealStage(). For the newly added file processing logic class, inherit this AbsStage and reuse the DealStageAssmbler tool class to complete the access to the lifecycle logic.

[0060] At the end of file synchronization, in the completionProcess of DealStageAssmbler, the list of processing stages, DealStageInfoList, is converted into JSON format and stored in the file synchronization record through the JSON tool class. This allows you to view the entire process at once using only the file synchronization record.

[0061] At the same time, each element of DealStageInfoList is split and stored in the full life cycle processing flow table, which supports SQL statement analysis of the full life cycle processing flow table, thereby realizing data statistical analysis for different processing stages.

[0062] like Figure 2 The figure shows a schematic diagram of the life cycle of a bank numbering document, which includes:

[0063] Download the bank's marking file and determine the type of the bank's marking file;

[0064] If it is a data file, determine whether preset processing is required. The preset processing includes adjusting fields and parsing images. After parsing the images, upload the processed bank number file to the static resource server. After adjusting the fields, perform subsequent data processing on the processed bank number file. Subsequent data processing includes warehousing the bank number file into the target database using the corresponding processing method according to the format characteristics, storage method, file attributes and target database stored in the configuration information of the bank number file. The format characteristics include XML format and TXT format, the storage method is CSV, mybatis and sql splicing, the file attributes include incremental file and full file, and the target database includes the business library and the monitoring library;

[0065] If it is a resource file, the image or PDF will be parsed and the processed bank number file will be uploaded to the static resource server.

[0066] For example, a typical stage structured data of refreshing Redis data is as follows:

[0067] {

[0068] "bgnTime": "Year Month Day Time",

[0069] "curLocationHandler":"RefreshRedisHandler",

[0070] "dataNum":1393,

[0071] "dealPrcsId":"b36f320e2c644f2abdf47975e43f20e",

[0072] "dealstage":"STAGE_REFRESH_REDIS_HANDLER",

[0073] "dealstageDesc": "Refresh redis cache",

[0074] "dealstageRslt":"1",

[0075] "dealstageseqNo":7,

[0076] "dealstageUstm":6082,

[0077] "endTime":"Year Month Day Time",

[0078] "fileDldRcdId":"Year Month Day Time 393826068806871",

[0079] "filesize":0

[0080] }.

[0081] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0082] The embodiment of the present application also provides a device for tracking the life cycle process of a bank numbering file. It should be noted that the device for tracking the life cycle process of a bank numbering file in the embodiment of the present application can be used to execute the method for tracking the life cycle process of a bank numbering file provided in the embodiment of the present application. The device is used to implement the above-mentioned embodiments and preferred implementation methods, and the details that have been explained will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and conceivable.

[0083] The following introduces the tracking device for the entire life cycle process of the bank number file provided in the embodiment of the present application.

[0084] Figure 3 This is a structural block diagram of a device for tracking the life cycle of a bank numbered document according to an embodiment of the present application. Figure 3 As shown, the device includes:

[0085] The acquisition unit 31 is used to acquire a bank number file and, based on the type of the bank number file, perform storage processing on the bank number file, or perform preset processing on the bank number file and then upload it to a static resource server, wherein the bank number file is a data file with actual business meaning and used for data interaction between systems, and the type of the bank number file is a resource file or a data file, and the resource file includes multimedia data, and the data file includes structured data; the first processing unit 32 is used to call a preset tool to initialize the node data before each processing stage in the life cycle process of the bank number file, and record the process data of the initialization processing to In the above-mentioned node data, and after each of the above-mentioned processing stages is completed, the above-mentioned preset tool is called to update the above-mentioned node data to track the above-mentioned life cycle process of the above-mentioned bank number file. The above-mentioned node data includes processing results, processing time and exception information, and the above-mentioned process data of the above-mentioned initialization processing includes the start time of the above-mentioned initialization processing; the second processing unit 33 is used to call the JSON tool class to convert the format of the node data into JSON format at the end of the entire life cycle process of the above-mentioned bank number file, and store it in the file synchronization record table, and split all elements of the above-mentioned node data and store them in the full life cycle process table. The above-mentioned full life cycle process table supports SQL statement analysis.

[0086] In the above-mentioned device, after the system automatically obtains the bank number file, it automatically calls the corresponding processing flow according to the file type, thereby improving processing efficiency and accuracy. Through the real-time recording mechanism (i.e., before each processing stage in the life cycle process of the above-mentioned bank number file, the preset tool is called to initialize the node data, and the process data of the above-mentioned initialization processing is recorded in the above-mentioned node data, and after each of the above-mentioned processing stages is completed, the above-mentioned preset tool is called to update the above-mentioned node data), the present application can immediately understand the status of each stage, and provide data support for subsequent analysis and optimization. At the end of the full life cycle process of file synchronization, the node data in the entire process is converted into JSON format and stored in the file synchronization record table. The use of JSON format, on the one hand, ensures the structuring of data, and on the other hand, makes the reading and parsing of data extremely simple. Since each step of the processing flow is recorded, once an exception occurs in the file synchronization, the problem can be quickly located at which specific processing stage the problem occurred by querying the JSON data and the full life cycle process table in the file synchronization record table, without the need to check the code line by line, which greatly shortens the problem troubleshooting time. This solves the problem that the traditional bank number file processing flow is difficult to track problems.

[0087] In one embodiment of the present application, the above-mentioned device also includes a third processing unit and a fourth processing unit. The third processing unit is used to generate a unique identification of the processing process by calling the preset tool to initialize the node data and record the process data of the above-mentioned initialization processing into the above-mentioned node data. The above-mentioned unique identification of the processing process is used to associate all processing stage information in the synchronization process of the above-mentioned bank number file; the fourth processing unit is used to create the above-mentioned node data to record the key information of the current processing stage. The above-mentioned key information includes the above-mentioned unique identification of the processing process, the processing stage description, and the primary key of the file synchronization record.

[0088] The introduction of a unique process identifier allows for unified association of all processing stage information throughout the entire file synchronization process. Even if a file synchronization process may involve multiple retries or multiple processing branches, the DealPrcsId allows maintenance personnel to easily trace and analyze the complete path of the entire process, improving the efficiency and accuracy of troubleshooting. By recording the unique process identifier in the node data, a file synchronization process can serve as a template or case study for analyzing and optimizing the processing of other similar files. This case-based learning and optimization approach can help the system continuously evolve, improving processing efficiency and success rates.

[0089] In one embodiment of the present application, the above-mentioned device also includes a fifth processing unit, a sixth processing unit, a seventh processing unit and an eighth processing unit. The fifth processing unit is used to call the first recording tool after each of the above-mentioned processing stages to record the end time and processing result of the current processing stage into the above-mentioned node data, wherein the above-mentioned end time is the specific timestamp of the completion of the processing of the above-mentioned current processing stage, and the above-mentioned processing result indicates whether the processing of the above-mentioned current processing stage is successful; the sixth processing unit is used to call the second recording tool to calculate the above-mentioned processing time, and the above-mentioned processing time is the time difference between the start time and the end time of the above-mentioned current processing stage; the seventh processing unit is used to determine that if an exception occurs during the execution of the above-mentioned current processing stage, call the third recording tool to record the above-mentioned exception information, the above-mentioned exception information includes the exception type and exception stack information, and the above-mentioned exception stack information is an error report automatically generated by the runtime environment when an error or exception is encountered during the program running; the eighth processing unit is used to call the complete record verification tool to determine whether the information of the above-mentioned current processing stage is completely recorded, and at the same time initialize the processing node data of the next stage to form a coherent life cycle tracking record.

[0090] Specifically, recording the end time and processing results of each stage allows for precise identification of any issues within the processing flow. Compared to traditional, bulk logging, this approach directly pinpoints the specific stage and time point where a problem occurred, accelerating troubleshooting and resolution. By calculating the processing time (the difference between the start and end time of the current processing stage), the efficiency of each stage can be quantitatively assessed. This helps identify bottlenecks in the processing flow and provides data support for optimization and upgrades. Exception information, including the exception type and stack trace, provides the specific context of the exception, making it transparent and easy to track. Maintenance personnel can quickly understand the nature and location of the exception, accelerating problem remediation. Verification using a full record verification tool ensures that all critical information from the current processing stage is recorded, preventing data omissions and ensuring data integrity and consistency. Furthermore, the processing node for the next stage is initialized, forming a complete lifecycle record chain from beginning to end, enhancing process traceability and auditability.

[0091] In one embodiment of the present application, the second processing unit includes a first processing module, a second processing module and a third processing module. The first processing module is used to call a summary tool to summarize the above-mentioned node data of all the above-mentioned processing stages, so that the data fields of each of the above-mentioned processing stages are completely recorded, and the above-mentioned data fields include start time, end time, the above-mentioned processing results, the above-mentioned processing time and the above-mentioned exception information; the second processing module is used to convert the data structure of the above-mentioned node data into a string of a JSON object to obtain a JSON string; the third processing module is used to use the above-mentioned JSON string as the value of a field and write it into the corresponding row of the above-mentioned file synchronization record.

[0092] The use of JSON format provides flexibility and standardization of data structure, making recorded data easy to process through automated tools. The key-value pair format of JSON can easily accommodate fields that may change in the processing node data, and the standardized format ensures uniform data processing and simplifies the complexity of data parsing; the JSON string of node data is written as a field value in the file synchronization record. Compared with storage as multiple fields or independent files, this centralized storage method improves the efficiency of data storage. At the same time, JSON fields support efficient database queries, making the query and analysis of file synchronization records faster and improving overall query performance; operation and maintenance personnel can quickly view the complete life cycle record of a file synchronization without switching and searching in multiple tables or log files, simplifying system operation and maintenance work. Quickly locate problems: When an exception occurs in file synchronization, operation and maintenance personnel can directly use the exception information and processing stage description in the JSON field to quickly locate the stage where the problem occurred, reducing the time and cost of problem troubleshooting.

[0093] In one embodiment of the present application, the acquisition unit includes a fourth processing module, a fifth processing module and a sixth processing module. The fourth processing module is used to, when the type of the above-mentioned bank number file is the above-mentioned resource file, perform preset processing on the above-mentioned bank number file and then upload it to the above-mentioned static resource server, and the above-mentioned preset processing includes image parsing processing and PDF parsing processing; the fifth processing module is used to, when the type of the above-mentioned bank number file is the above-mentioned data file and the configuration information of the above-mentioned bank number file does not contain information that requires target preset processing, perform warehousing processing on the above-mentioned bank number file after the above-mentioned target preset processing; the sixth processing module is used to, when the type of the above-mentioned bank number file is the above-mentioned data file and the configuration information of the above-mentioned bank number file contains information that requires the above-mentioned target preset processing, perform warehousing processing on the above-mentioned bank number file after the above-mentioned target preset processing, or upload the above-mentioned bank number file after the above-mentioned target preset processing to the static resource server.

[0094] When the bank's numbered file is a resource file (such as an image, PDF, etc.), the system converts the file content into a format that the system can recognize and store through a preset processing flow (such as parsing images and PDF processing), and then uploads it to the static resource server. This processing method ensures the fast and accurate conversion of resource files, avoids processing failures due to incompatible file formats, and improves the processing efficiency of resource files and system stability. For data files, the system can adopt different processing strategies based on whether there are preset processing requirements in its configuration information. If no specific preprocessing is specified in the configuration, the data file will be directly put into storage for processing, which simplifies the processing flow and speeds up data synchronization. If there is a preprocessing requirement in the configuration, the system will first perform preprocessing (such as data cleaning, format conversion, etc.) before warehousing, ensuring the accuracy and consistency of the data; the flexible application of configuration information enables the system to adjust the processing strategy according to different file types and specific requirements, enhancing the adaptability and scalability of the system. This means that even when faced with new types of bank number files or complex processing requirements, the system can be quickly adjusted without the need for large-scale modifications to the core code; by pre-processing resource files and data files for type matching, processing failures caused by mismatches in file formats and data structures are reduced, thereby significantly improving the success rate of file synchronization and reducing subsequent troubleshooting and data repair work; resource files are uploaded to the static resource server instead of directly into the database, avoiding excessive database space occupation, optimizing storage strategies, and saving storage resources. At the same time, the high concurrent access capability of the static resource server also ensures rapid access and distribution of resource files; through pre-processing, data files are formatted and cleaned to ensure data compliance and security. For example, for the processing of sensitive information, encryption or desensitization can be performed at this stage to avoid the risk of directly exposing the original data in subsequent processing links.

[0095] In one embodiment of the present application, the sixth processing module includes a first processing module and a second processing module. The first processing module is used to perform warehousing processing on the above-mentioned bank number file after the target preset processing when the above-mentioned target preset processing is field adjustment processing; the second processing module is used to upload the above-mentioned bank number file after the above-mentioned target preset processing to the static resource server when the above-mentioned target preset processing is image parsing processing.

[0096] When the target preset is field adjustment, the system standardizes, cleans, or converts the fields in the data file to ensure that the incoming data meets the database's structural requirements and business rules. This precise data preprocessing effectively avoids data quality issues that could lead to data entry failures or database anomalies, improving data consistency and integrity, and thus ensuring reliable and efficient data synchronization. For resource files, such as images or PDFs, pre-defined processing, such as image parsing, converts these files to a format that is convenient for storage and quick access before uploading them to a static resource server. Static resource servers typically offer superior file storage and distribution capabilities, enabling rapid response to external requests, improving resource file access speed and user experience. Centralized storage and management of these resource files also facilitates subsequent operations and data security. By separating resource file processing and storage from the database, database read and write operations are reduced, avoiding performance bottlenecks that can arise when processing large amounts of unstructured data. This helps maintain efficient database operation and enhances overall system stability and responsiveness. By implementing preprocessing and differentiated processing strategies, problems at any stage of processing can be precisely identified. For example, if a data file fails to be stored, it can be quickly determined whether the problem lies in data cleaning or field adjustments during the pre-processing phase. This greatly simplifies troubleshooting and reduces problem resolution time.

[0097] In one embodiment of the present application, the acquisition unit includes a seventh processing module, which is used to process the above-mentioned bank number file into the above-mentioned target database using a corresponding processing method according to the format characteristics, storage method, file attributes and target database stored in the configuration information of the above-mentioned bank number file. The above-mentioned format characteristics include XML format and TXT format, the above-mentioned storage method is csv, mybatis and sql splicing, the above-mentioned file attributes include incremental files and full files, and the above-mentioned target database includes a business library and a monitoring library.

[0098] Different file formats and attributes require different processing methods. For example, XML files may require parsing tags and attributes, while TXT files focus on field delimiters. Using the format characteristics in the configuration information, the system can intelligently select the most appropriate parser and conversion tools to ensure efficient and accurate conversion of file data, reducing data processing errors and time consumption. Based on the type of target database (business database or monitoring database) and the specified storage method (such as CSV import, MyBatis batch insert, or SQL splicing execution), the system can flexibly adjust the data writing strategy to store data in the most suitable manner. This not only improves the versatility of data synchronization but also reduces processing delays caused by database characteristics and limitations. By distinguishing the attributes of incremental and full files, the system can select the appropriate storage mechanism. For incremental files, the system can implement update and incremental load strategies, while for full files, it performs clearing and full load. This approach reduces unnecessary data redundancy and optimizes data storage, while also improving database query performance and data management efficiency.

[0099] The device for tracking the full lifecycle of bank numbered documents includes a processor and memory. The acquisition unit, first processing unit, and second processing unit are stored as program units in the memory. The processor executes the program units stored in the memory to implement the corresponding functions. The modules can all be located in the same processor, or the modules can be located in different processors in any combination.

[0100] The processor contains a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be configured, and adjusting kernel parameters can solve the problem of difficulty in tracking issues in traditional bank number file processing.

[0101] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0102] An embodiment of the present invention provides a computer-readable storage medium, which includes a stored program, wherein when the program is running, the device where the computer-readable storage medium is located is controlled to execute a method for tracking the entire life cycle process of the bank number file.

[0103] An embodiment of the present invention provides a processor, which is used to run a program, wherein the program, when running, executes a method for tracking the full life cycle process of the bank number file.

[0104] An embodiment of the present invention provides a device, which includes a processor, a memory, and a program stored in the memory and capable of running on the processor. When the processor executes the program, at least the following steps are implemented: obtaining a bank number file, and according to the type of the bank number file, performing a storage process on the bank number file, or performing a preset process on the bank number file and then uploading it to a static resource server, wherein the bank number file is a data file with actual business meaning and used for data interaction between systems, the type of the bank number file is a resource file or a data file, the resource file includes multimedia data, and the data file includes structured data; before each processing stage in the life cycle process of the bank number file, calling a preset tool to process the node The data is initialized and the process data of the initialization processing is recorded in the node data. After each of the above processing stages, the preset tool is called to update the node data to track the life cycle of the bank number file. The node data includes the processing results, processing time and exception information. The process data of the initialization processing includes the start time of the initialization processing. At the end of the life cycle of the bank number file, the JSON tool class is called to convert the node data format into JSON format and store it in the file synchronization record table. All elements of the node data are split and stored in the full life cycle process table. The full life cycle process table supports SQL statement analysis. The devices in this article can be servers, PCs, PADs, mobile phones, etc.

[0105] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program having at least the following method steps: obtaining a bank number file, and according to the type of the above bank number file, performing storage processing on the above bank number file, or performing preset processing on the above bank number file and uploading it to a static resource server, wherein the above bank number file is a data file with actual business meaning and used for data interaction between systems, the type of the above bank number file is a resource file or a data file, the above resource file includes multimedia data, and the above data file includes structured data; before each processing stage in the life cycle process of the above bank number file, calling a preset tool to initialize the node data Processing, and record the process data of the above initialization processing into the above node data, and after the end of each of the above processing stages, call the above preset tool to update the above node data to track the above life cycle process of the above bank number file. The above node data includes processing results, processing time and exception information, and the above process data of the above initialization processing includes the start time of the above initialization processing; at the end of the entire life cycle process of the above bank number file, call the JSON tool class to convert the format of the node data into JSON format, and store it in the file synchronization record table, and split all elements of the above node data and store them in the full life cycle process table. The above full life cycle process table supports SQL statement analysis.

[0106] The present application also provides a banking system, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include means for executing any one of the above methods.

[0107] Obviously, those skilled in the art will appreciate that the various modules or steps of the present invention described above can be implemented using a general-purpose computing device, can be centralized on a single computing device, or can be distributed across a network of multiple computing devices. They can be implemented using program code executable by the computing device, and thus, can be stored in a storage device and executed by the computing device. In some cases, the steps shown or described herein can be performed in a different order than that shown, or can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0108] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0109] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0110] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0111] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0112] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0113] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0114] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0115] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0116] The above description is merely a preferred embodiment of the present application and is not intended to limit the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A method for tracking the life cycle of bank numbered documents, characterized in that: include: Obtaining a bank number file and, based on the type of the bank number file, performing storage processing on the bank number file, or performing preset processing on the bank number file and then uploading it to a static resource server, wherein the bank number file is a data file with actual business significance and used for data exchange between systems, and the type of the bank number file is a resource file or a data file, wherein the resource file includes multimedia data, and the data file includes structured data; Before each processing stage in the life cycle of the bank number file, a preset tool is called to initialize the node data, and the process data of the initialization processing is recorded in the node data. After each processing stage, the preset tool is called to update the node data to track the life cycle of the bank number file. The node data includes processing results, processing time and exception information, and the process data of the initialization processing includes the start time of the initialization processing; At the end of the entire life cycle process of the bank number file, the JSON tool class is called to convert the node data format into JSON format and store it in the file synchronization record table, and all elements of the node data are split and stored in the full life cycle process table. The full life cycle process table supports SQL statement analysis.

2. The method according to claim 1, characterized in that Before calling a preset tool to perform initialization processing on the node data and recording the process data of the initialization processing into the node data, the method further includes: Generate a unique process identifier by calling an identifier generation method of a preset tool. The unique process identifier is used to associate all process stage information during the synchronization process of the bank number file; Create a node data to record key information of the current processing stage, wherein the key information includes the unique identifier of the processing process, the processing stage description, and the primary key of the file synchronization record.

3. The method according to claim 1, characterized in that After each processing stage, calling the preset tool to update the node data includes: Invoking a first recording tool to record the end time and processing result of the current processing stage into the node data, wherein the end time is a specific timestamp of the completion of the processing of the current processing stage, and the processing result indicates whether the processing of the current processing stage is successful; Invoking a second recording tool to calculate the processing time, where the processing time is the time difference between the start time and the end time of the current processing stage; In the event that an exception occurs during execution of the current processing stage, a third recording tool is called to record the exception information, wherein the exception information includes the exception type and exception stack information. The exception stack information is an error report automatically generated by the runtime environment when an error or exception is encountered during program execution; A complete record verification tool is called to determine whether the information of the current processing stage is completely recorded, and at the same time, the processing node data of the next stage is initialized to form a coherent life cycle tracking record.

4. The method according to claim 1, wherein Call the JSON tool class to convert the node data format into JSON format and store it in the file synchronization record table, including: Invoking a summary tool to summarize the node data of all the processing stages so that the data fields of each processing stage are completely recorded, the data fields including the start time, the end time, the processing result, the processing time and the exception information; Convert the data structure of the node data into a string of a JSON object to obtain a JSON string; The JSON string is used as the value of a field and written into the corresponding row of the file synchronization record.

5. The method according to claim 1, wherein According to the type of the bank number file, the bank number file is stored in the database, or the bank number file is pre-processed and then uploaded to the static resource server, including: In the case where the type of the bank number file is the resource file, performing preset processing on the bank number file and uploading it to the static resource server, the preset processing including image parsing and PDF parsing; If the type of the bank number file is the data file and the configuration information of the bank number file does not contain information requiring target preset processing, the bank number file is put into storage; When the type of the bank number file is the data file and the configuration information of the bank number file contains information that requires the target preset processing, the bank number file after the target preset processing is put into storage, or the bank number file after the target preset processing is uploaded to the static resource server.

6. The method according to claim 5, characterized in that The bank number file after the target preset processing is stored in the warehouse, or the bank number file after the target preset processing is uploaded to the static resource server, including: In the case where the target preset processing is field adjustment processing, the bank number file after the target preset processing is put into storage; In the case where the target preset processing is image parsing processing, the bank number file after the target preset processing is uploaded to a static resource server.

7. The method according to any one of claims 1 to 6, characterized in that The bank numbering file is put into storage, including: According to the format characteristics, storage method, file attributes and target database stored in the configuration information of the bank number file, the bank number file is stored in the target database using the corresponding processing method. The format characteristics include XML format and TXT format, the storage method is CSV, mybatis and sql splicing, the file attributes include incremental files and full files, and the target database includes a business library and a monitoring library.

8. A device for tracking the life cycle of bank numbered documents, characterized by: include: an acquisition unit, configured to acquire a bank number file and, based on the type of the bank number file, perform storage processing on the bank number file, or perform preset processing on the bank number file and then upload it to a static resource server, wherein the bank number file is a data file having actual business significance and used for data exchange between systems, and the type of the bank number file is a resource file or a data file, wherein the resource file includes multimedia data, and the data file includes structured data; a first processing unit configured to call a preset tool to perform initialization processing on node data before each processing stage in the life cycle of the bank number file, and record process data of the initialization processing in the node data; and, after each processing stage, call the preset tool to update the node data to track the life cycle of the bank number file, wherein the node data includes processing results, processing time, and exception information, and the process data of the initialization processing includes the start time of the initialization processing; The second processing unit is used to call the JSON tool class to convert the format of the node data into JSON format at the end of the entire life cycle process of the bank number file, and store it in the file synchronization record table, and split all elements of the node data and store them in the full life cycle process table. The full life cycle process table supports SQL statement analysis.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 7.

10. A banking system, characterized in that: include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for executing the method of any one of claims 1 to 7.

Images