Management visualization system based on Linux
By designing a Linux-based management visualization system, the cumbersome problems of server-side file operations and database result verification process are solved, and the file operations and database operations are simplified and intuitive.
Patent Information
- Application Number
- CN202411769876.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-04
- Publication Date
- 2025-02-28
AI Technical Summary
In the prior art, the server-side file operation and database result verification process is complicated, and the existing clients are not good at displaying file content, making it difficult to intuitively view and analyze file content.
Design a management visualization system based on Linux, including front-end and back-end. The front-end provides user interaction interface, and the back-end is divided into display layer, logic layer and data persistence layer. The logic layer includes file processing visualization module and database operation visualization module, and file operations and database operations are implemented through JAVA native methods and SpringBoot components.
Through the collaborative work of the front-end and back-end, users can perform complex file and database operations through an intuitive user interaction interface, without deep understanding of command line syntax, significantly simplifying the cumbersome process of file operations and database results verification.
Smart Images

Figure CN119537658A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of data management, and in particular to a management visualization system based on Linux. Background Art
[0002] The Linux operating system is one of the most widely used operating systems in the server field, and many large enterprise-level software rely on it to run. However, for server-side program developers, when performing operations such as adding, deleting, modifying, and checking server files, they usually need to use a specific access client and enter complex commands. This operation method is not only cumbersome, but the existing client is not good at displaying file content, making it difficult to intuitively view and analyze file content.
[0003] During program development and testing, especially in long-term system integration testing, developers often need to verify the accuracy of a business function through database data. This usually requires repeatedly using the same SQL statement to query the database results. Most current database clients focus on providing comprehensive database management functions and lack convenient application scenario function design, which requires developers to manage and maintain commonly used SQL statements by themselves.
[0004] Therefore, how to simplify the tedious process of file operation and database result verification has become a technical problem that technical personnel in this field urgently need to solve. Summary of the invention
[0005] In view of the above problems, the present invention provides a management visualization system based on Linux that overcomes the above problems or at least partially solves the above problems. The technical solution is as follows:
[0006] A management visualization system based on Linux, the system includes a front end and a back end, the front end is used to provide a user interaction interface, and the back end system logically includes a presentation layer, a logic layer and a data persistence layer;
[0007] The presentation layer is used to collect files or SQL operation information input by users and communicate with the logic layer through the Http protocol;
[0008] The logic layer includes a file processing visualization module and a database operation visualization module, which are used to receive and process requests from the presentation layer, wherein the file processing visualization module is used to implement file operations through JAVA native methods and SpringBoot components, and the database operation visualization module is used to implement database operations by executing SQL statements through the database access interface;
[0009] The data persistence layer is used to persistently store the user data from the logic layer, including XML file storage of protocol file parsing rules.
[0010] Optionally, the file processing visualization module is used to manage file operations, including creation, access, copying, cutting, renaming, uploading, downloading and file parsing and viewing functions.
[0011] Optionally, the file parsing and viewing function supports configuring parsing rules through a user interface, wherein the parsing rules include a file name regular expression, a file parsing method and field information, and the file parsing method includes delimiter parsing and fixed-length parsing.
[0012] Optionally, the delimiter parsing uses the read method of the JAVA native BufferedReader to read the file line by line, and divides the line data into a string array according to the delimiter.
[0013] Optionally, the fixed-length parsing supports byte and character formats, uses the read method of BufferedReader to read file lines, and intercepts data according to the field start and end subscripts.
[0014] Optionally, the database operation visualization module includes an SQL operation area and a business query area, wherein the SQL operation area is used to execute SQL statements input by a user, and the business query area is used to manage business query templates.
[0015] Optionally, the business query template includes template information including a business name, an SQL query statement, and display table information, and the template information is persistently stored in an XML file.
[0016] Optionally, the logic layer reads and executes the SQL query statement of the business query template from the XML file, and returns the query result to the presentation layer.
[0017] Optionally, the database stores user authority configuration, and the configuration items of the user authority configuration include file directory permissions and data encryption control.
[0018] Optionally, in the user authority configuration, a high-authority role has the authority to view all files and data, and a low-authority role can only view specific files and desensitized or encrypted data.
[0019] By means of the above technical scheme, the present invention provides a management visualization system based on Linux, including a front end and a back end, wherein the front end is used to provide a user interaction interface, and the back end system logic includes a display layer, a logic layer and a data persistence layer; the display layer is used to collect the file or SQL operation information input by the user, and communicate with the logic layer through the Http protocol; the logic layer includes a file processing visualization module and a database operation visualization module, which are used to receive and process requests from the display layer, wherein the file processing visualization module is used to implement file operations through JAVA native methods and SpringBoot components, and the database operation visualization module is used to implement database operations by executing SQL statements through the database access interface; the data persistence layer is used to persistently store user data from the logic layer, including XML file storage of protocol file parsing rules. The present invention works through the collaborative work of the front end and the back end, the front end provides an intuitive user interaction interface, so that users can perform complex file and database operations through simple operations without in-depth understanding of command line syntax, and the back end provides more efficient and stable file management capabilities through efficient inter-layer communication and block processing, realizes the automation and visualization of database operations, and significantly simplifies the cumbersome process of file operations and database result verification.
[0020] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:
[0022] Figure 1 A schematic diagram of a system architecture of a management visualization system based on Linux provided by an embodiment of the present invention is shown;
[0023] Figure 2 A schematic diagram showing a file parsing process provided by an embodiment of the present invention is shown;
[0024] Figure 3 A schematic diagram showing the composition of the SQL operation area provided by an embodiment of the present invention is shown;
[0025] Figure 4 A timing diagram of the interaction between a user and a system provided by an embodiment of the present invention is shown. DETAILED DESCRIPTION
[0026] The exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present invention and to enable the scope of the present invention to be fully communicated to those skilled in the art.
[0027] The Linux operating system is one of the most popular operating systems in the current server field. Many large enterprise-level software services rely on the Linux system to run. However, for server-side program developers, it is frequently necessary to add, delete, modify, and query files in the server. Usually, developers need to use a specific access client and enter cumbersome commands to complete a file operation. In addition, most clients have deficiencies in file content display and cannot intuitively view and analyze file content.
[0028] During program development and testing, especially during inter-system joint debugging, it is often necessary to verify the accuracy of a certain business function of the system through the data in the database. This usually requires repeatedly using the same SQL statement to query the database results. Currently, most database clients focus on providing comprehensive database management and operation functions, but do not design convenient functions for actual application scenarios, which requires program developers to manage and maintain commonly used SQL statements by themselves.
[0029] The existing solution is based on the BS-structured database management system, which mainly solves the problem that traditional relational databases cannot process unstructured data such as images and hypertext. However, it mainly focuses on the display of unstructured data, and it is difficult to provide database users with more convenient business scenario verification functions based on actual application scenarios, and it cannot support comprehensive management operations at the server file level.
[0030] In addition, the existing Linux file management and database operation methods rely on specific access clients, which need to be installed on the user's computer, increasing the performance burden on the user side. In terms of file management, when using a Linux server to access the client, complex commands need to be entered to access specific files, and the display effect of the file content is poor, especially when processing files in specific formats, users expect a clearer display. In terms of database operations, the existing database clients are complex to use and require users to have certain operating skills. The operations of different databases vary significantly, increasing the user's learning and operating costs.
[0031] Based on this, in order to simplify the tedious process of file operation and database result verification, the present invention proposes a management visualization system based on Linux. Through the visualization interface, users can input the corresponding server IP and port, manage files under the Linux server, operate the database, and parse the files in different ways according to specific data exchange protocols. This method is not only suitable for specific scenarios, but also for any visualization scenario that requires integrated file processing and database operation.
[0032] like Figure 1 As shown, a system architecture diagram of a Linux-based management visualization system provided by an embodiment of the present invention, the system includes a front end and a back end, the front end is used to provide a user interaction interface, and the back end system logically includes a presentation layer, a logic layer and a data persistence layer.
[0033] The front end can be built using technologies such as HTML, JavaScript, and Vue, and the back end can be developed using JAVA. The system is logically divided into a display layer, a logic layer, and a data persistence layer.
[0034] The present invention allows users to intuitively perform file and database operations through the front-end user interaction interface, reducing the reliance on command lines, making operations simpler and more efficient. At the same time, the system backend is divided into a display layer, a logic layer, and a data persistence layer, with clear functions and separation of responsibilities between each layer. This design improves the maintainability and scalability of the system, making it easier to expand and update the system.
[0035] The presentation layer is used to collect files or SQL operation information input by users and communicate with the logic layer through the Http protocol.
[0036] The presentation layer provides a visual human-computer interaction interface, where users can input operation information, such as deleting files or entering SQL statements to be executed, and submit this information to the logic layer for processing. The presentation layer and the logic layer exchange data through the HTTP protocol.
[0037] The present invention provides a visual interface, through which a user can easily operate multiple files and perform multiple data operations, thereby achieving a lightweight design of the system.
[0038] The logic layer includes a file processing visualization module and a database operation visualization module, which are used to receive and process requests from the presentation layer. The file processing visualization module is used to implement file operations through JAVA native methods and SpringBoot components, and the database operation visualization module is used to execute SQL statements through the database access interface to implement database operations.
[0039] The logic layer is responsible for processing requests from the presentation layer, which include file operations and database operations. For file operations, JAVA native methods and SpringBoot components are used for file processing. For database operations, the database is accessed through the database access interface and SQL statements are executed, and the execution results are finally returned to the presentation layer.
[0040] The logic layer integrates file processing and database operation functions. Through JAVA native methods and SpringBoot components, the file processing visualization module can efficiently perform file operations; the database operation visualization module executes SQL statements through the database access interface and supports complex database queries and data management tasks.
[0041] The data persistence layer is used to persistently store user data from the logic layer, including XML file storage of protocol file parsing rules.
[0042] The data persistence layer is responsible for storing user data. For example, when a user creates a parsing rule for a certain type of protocol file, the data persistence layer will persist the protocol file's file name regular expression, file parsing method, and field information used in the parsing process into an XML file.
[0043] The data persistence layer is responsible for the persistent storage of user data, ensuring the security and persistence of data. At the same time, it can also save the XML file of the protocol file parsing rules, thereby supporting complex data parsing requirements and improving the flexibility of the system.
[0044] The visualization system design provided by the present invention is not only suitable for file and database management in Linux environment, but can also be extended to other scenarios that require visualization management and operation, and has good versatility and adaptability.
[0045] The present invention provides a management visualization system based on Linux, including a front end and a back end, wherein the front end is used to provide a user interaction interface, and the back end system logic includes a display layer, a logic layer and a data persistence layer; the display layer is used to collect files or SQL operation information input by users, and communicate with the logic layer through the Http protocol; the logic layer includes a file processing visualization module and a database operation visualization module, which are used to receive and process requests from the display layer, wherein the file processing visualization module is used to implement file operations through JAVA native methods and SpringBoot components, and the database operation visualization module is used to implement database operations by executing SQL statements through the access interface of the database; the data persistence layer is used to persistently store user data from the logic layer, including XML file storage of protocol file parsing rules. The present invention works through the collaborative work of the front end and the back end, the front end provides an intuitive user interaction interface, so that users can perform complex file and database operations through simple operations without in-depth understanding of command line syntax, and the back end provides more efficient and stable file management capabilities through efficient inter-layer communication and block processing, realizes the automation and visualization of database operations, and significantly simplifies the cumbersome process of file operations and database result verification.
[0046] Optionally, a file processing visualization module is used to manage file operations, including creation, access, copying, cutting, renaming, uploading, downloading and file parsing and viewing functions.
[0047] The file processing visualization module provides a complete set of file management functions, including visual creation, access and traversal of file directories, as well as file upload, download, copy, cut, decompression and renaming. At the same time, it supports file parsing and viewing according to specific data exchange protocols.
[0048] Users can freely switch Linux system directories through the visual interface. When a user selects a file or directory under a directory and submits an operation request, the logic layer will process it accordingly. If the request involves creating, deleting, copying, cutting, decompressing, or renaming, the system will use the methods of the JAVA native File class to perform the operation and return the results to the presentation layer. For file upload and download requests, the system implements file upload based on SpringBoot's transferTo method and uses file output stream to implement file download.
[0049] Traditional Linux server access requires the use of command lines, and the present invention simplifies this operation through a visual interface. Users can specify the file directory to be accessed on the interface, and traverse the upper and lower level directories, and can also create directories, upload and download files, decompress files, and rename files. By providing a visual interface, the present invention allows users to perform complex file management operations such as creating, accessing, copying, cutting, renaming, uploading, and downloading without using command lines. This greatly reduces the user's operating threshold and improves operating efficiency.
[0050] Optionally, the file parsing and viewing function supports configuration of parsing rules through a user interface, wherein the parsing rules include file name regular expressions, file parsing methods and field information, and the file parsing methods include delimiter parsing and fixed-length parsing.
[0051] Under the specified protocol, the file parsing and viewing function supports two file parsing methods: delimiter parsing and fixed-length parsing. Users need to configure the parsing rules in advance on the visual interface, including the file name regular expression, parsing method and parsing field information of the protocol file, which are stored in the data persistence layer.
[0052] The file parsing process provided by the embodiment of the present invention is as follows Figure 2 As shown, it may include:
[0053] S200: The user switches to a directory through an interactive interface, selects a file and initiates a viewing request.
[0054] S210, after receiving the viewing request, the logic layer obtains the complete file parsing rules from the data persistence layer, traverses all the rules, and uses the file name regular expression in the rule to match the file name selected by the user. Once the match is successful, the parsing rule of the file is determined.
[0055] S220: After determining the parsing rules, parse the file according to the parsing method in the rules.
[0056] For delimiter parsing, users need to pre-configure the Chinese meaning of each array subscript. For fixed-length parsing, users need to pre-configure whether to split by character or byte, as well as the Chinese meaning of each field and the start and end position of the field in the file line. After receiving the data, the presentation layer will present it in a table on the interactive interface for users to view.
[0057] The present invention supports two parsing modes, delimiter parsing and fixed-length parsing, so that the system can adapt to files of different formats. This flexibility enables users to process diverse data files and meet different protocols and business requirements. At the same time, through the interaction and configuration of the visual interface, users do not need to deeply understand the underlying parsing logic to complete complex file parsing tasks, which reduces the threshold for technical use and broadens the scope of application of the system.
[0058] Optionally, delimiter parsing uses the read method of JAVA native BufferedReader to read the file line by line and split the line data into a string array according to the delimiter.
[0059] Specifically, for the delimiter parsing method, the logic layer uses the read method of the Java native class BufferedReader to read the file data line by line and convert it into characters. Each time a line of data is read, the logic layer splits the line of data into a string array according to the specified delimiter. After that, the logic layer returns the parsed array and the Chinese meaning of each corresponding array subscript to the presentation layer for display.
[0060] By using the Java native BufferedReader class and its read method, the system can efficiently read files line by line, thereby reducing memory usage and improving the speed and efficiency of file reading. At the same time, the line data is divided into string arrays using the specified delimiter, so that the system can adapt to different file formats and data structures, allowing users to parse various types of delimiter files to meet different business needs.
[0061] Optionally, fixed-length parsing supports byte and character forms, using the read method of BufferedReader to read file lines and intercept data based on the field start and end subscripts.
[0062] Specifically, for fixed-length parsing, parsing can be divided into byte parsing and character parsing. The logic layer uses the read method of the Java native class BufferedReader to read the file line by line and convert each line of data into bytes or characters. According to the field start and end subscripts defined in the parsing rules, the logic layer intercepts the corresponding data and stores it in a Map, where the key is the Chinese name of the field and the value is the parsing result of the corresponding field. Finally, these parsing results will be returned to the presentation layer for display.
[0063] The present invention supports two parsing modes, byte and character, so that the system can process fixed-length files of different encodings and formats, thereby being able to adapt to the needs of different business scenarios, especially when processing diversified data formats. At the same time, through the start and end subscripts of the field definition, the system can accurately intercept specific data in the file, thereby ensuring the accuracy of data parsing and effectively avoiding data errors caused by position deviation.
[0064] In the visual interface, the present invention supports parsing the file content of a specific data exchange protocol, including the parsing of field names, field order and field length. The parsed content is displayed in the form of lines, which is convenient for users to view and verify the file content.
[0065] Optionally, the database operation visualization module includes an SQL operation area and a business query area, wherein the SQL operation area is used to execute SQL statements input by the user, and the business query area is used to manage business query templates.
[0066] like Figure 3 As shown, a schematic diagram of the composition of the SQL operation area provided by an embodiment of the present invention, the SQL operation area can be further divided into an SQL statement input area and a result display area. After the user enters the SQL statement in the input area, he can click the execute button to send the SQL execution request to the logic layer. After receiving the request, the logic layer interacts with the database through the database access interface to execute the corresponding SQL statement. The execution result is then transmitted back to the display layer and displayed in the result display area. The separation of the SQL statement input area and the result display area in the SQL operation area enables users to input and view SQL execution results in real time. This instant feedback mechanism helps users quickly verify and adjust query operations.
[0067] The business query area allows users to dynamically add or delete business query templates to perform more flexible query operations. The business query area allows users to dynamically add or delete query templates, providing more flexible query operation capabilities. This enables users to customize queries according to actual business needs and improves the adaptability of the tool.
[0068] The present invention divides the SQL operation area and the business query area, so that users can execute SQL statements and manage query templates in a clear interface, thereby improving the clarity and convenience of user interaction. At the same time, through the design of the visualization module, users can perform complex database operations without in-depth understanding of the background implementation, thereby simplifying and reducing the learning cost and usage threshold, and is suitable for all types of users. In addition, the centralized management of business query templates allows users to easily maintain and reuse common queries, which helps to reduce duplication of work and optimize the workflow.
[0069] Optionally, the business query template includes template information including a business name, an SQL query statement, and display table information, and the template information is persistently stored in an XML file.
[0070] The business query template consists of three parts: business name, SQL query statement and data display table. In the business query area, users need to fill in the business name and the corresponding SQL query statement when adding a new business query template. After completion, the user submits the request to the logic layer. After receiving the request, the logic layer will persist the business query template in an XML file.
[0071] The embodiment of the present invention uses XML format to store template information, so that users and systems can easily read, edit and extend templates, and utilizes the readability and extensibility of XML format to facilitate the management and migration of business query templates. At the same time, through the interface of the business query area, users can intuitively add and manage query templates, simplifying the process of complex operations and configurations, and lowering the learning and usage threshold.
[0072] Optionally, the logic layer reads and executes the SQL query statement of the business query template from the XML file, and returns the query result to the presentation layer.
[0073] Specifically, when a user enters the business query area, the system automatically initiates a query request. The logic layer first reads the XML file, obtains all stored templates, and executes the SQL statements therein to obtain the corresponding data sets. Subsequently, the logic layer returns the business name, SQL query statement, and its corresponding data set to the presentation layer for display.
[0074] The present invention enhances the modular design of the system by separating the query logic from the display logic, which is helpful for the maintenance, expansion and upgrade of the system. At the same time, users can obtain the corresponding data set without manually entering SQL statements, which simplifies the interaction process and reduces the difficulty of use, making it more friendly to non-technical users.
[0075] Optionally, the database stores user permission configuration, and the configuration items of the user permission configuration include file directory permissions and data encryption control.
[0076] In the system, the database can selectively store user permission configurations, which determine the scope of resources that users can access and the security processing of data. Specifically, user permission configuration includes two main aspects: file directory permissions and data encryption control. File directory permissions determine which files and directories users can access. Data encryption control involves how to handle data security.
[0077] Optionally, in the user permission configuration, a high-privilege role has the permission to view all files and data, and a low-privilege role can only view specific files and desensitized or encrypted data.
[0078] In file and directory permissions, high-privilege roles are granted access to all files and directories in the system, regardless of the sensitivity of these files or directories. In contrast, low-privilege roles can only access clearly defined files and directories, usually those related to their job functions.
[0079] In data encryption controls, high-privilege users can view raw, unprocessed data, which means they are not subject to encryption or desensitization restrictions. However, data accessed by low-privilege users is usually desensitized or encrypted to protect sensitive information. This control ensures the security of sensitive data while meeting compliance requirements such as privacy protection and data security regulations.
[0080] By configuring these permissions in the database, the system can flexibly manage the access permissions of different user roles, ensuring that the security and privacy of data are protected to the greatest extent without affecting the operational efficiency. Such a configuration not only improves the security of the system, but also provides a centralized way to manage permissions, making permission management more controllable and transparent.
[0081] The present invention encapsulates database client operations. Users can customize query conditions according to data verification scenarios and input query parameters through a visual interface, thereby improving data operation efficiency. In addition, the system supports access control based on user authority levels. High-authority roles can view all files and data, while low-authority roles can only access specified files and desensitized or encrypted data.
[0082] For ease of understanding, here we combine Figure 4 The interactive process of the management visualization system based on Linux provided by the embodiment of the present invention is described as follows: Figure 4The timing diagram of the user-system interaction provided in the embodiment of the present invention, the user performs certain operations through the front-end interface, and these operations can be file operations or input SQL statements. The front-end passes the user's request to the back-end logic layer through the HTTP protocol. After the back-end receives the request, it is necessary to first determine the type of request (file operation, SQL execution or business query). If the request is a file operation, the back-end uses the Java native method to process it, and after the processing is completed, the back-end returns the result to the front-end. If the request involves uploading or downloading a file, the back-end uses the SpringBoot component to process it, and after completion, the result is fed back to the front-end. If the request is file parsing, the back-end first obtains the parsing rules from the data persistence layer, and after parsing the file according to the rules, the result is returned to the front-end. After the front-end receives the processing result, it displays the result to the user, whether it is the result of the file operation or the result of the SQL execution. If the request is SQL execution, the front-end sends the SQL request to the back-end, the back-end uses the database interface to execute these SQL statements, and the execution results are returned to the front-end, and the front-end displays these results to the user. If the request involves business query, the front-end is responsible for managing and sending query templates. The back-end interacts with the data persistence layer to read or store these templates, and the back-end executes the SQL statements in the template and returns the query results to the front-end.
[0083] The present invention realizes the management of Linux server files and database operations through a lightweight visual interface. Users only need to enter the corresponding server IP and port to perform these operations. In addition, it supports multiple parsing methods for files under the protocol according to a specific data exchange protocol. Moreover, the method is not only applicable to the current scenario, but also can be widely used in other similar scenarios, that is, any scenario that needs to process files and perform database operations simultaneously in a visual interface.
[0084] Although operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order.Multitasking and parallel processing may be advantageous under certain circumstances.
[0085] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.
[0086] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the present invention are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.
[0087] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.
[0088] In the present invention, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0089] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0090] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.
[0091] The above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.
Claims
1. A management visualization system based on Linux, characterized in that: The system includes a front end and a back end, wherein the front end is used to provide a user interaction interface, and the back end system logically includes a presentation layer, a logic layer, and a data persistence layer; The presentation layer is used to collect files or SQL operation information input by users and communicate with the logic layer through the Http protocol; The logic layer includes a file processing visualization module and a database operation visualization module, which are used to receive and process requests from the presentation layer, wherein the file processing visualization module is used to implement file operations through JAVA native methods and SpringBoot components, and the database operation visualization module is used to implement database operations by executing SQL statements through the database access interface; The data persistence layer is used to persistently store the user data from the logic layer, including XML file storage of protocol file parsing rules.
2. The system according to claim 1, characterized in that The file processing visualization module is used to manage file operations, including creation, access, copying, cutting, renaming, uploading, downloading and file parsing and viewing functions.
3. The system according to claim 2, characterized in that The file parsing and viewing function supports configuring parsing rules through a user interface, wherein the parsing rules include a file name regular expression, a file parsing method, and field information, and the file parsing method includes delimiter parsing and fixed-length parsing.
4. The system according to claim 3, characterized in that The delimiter parsing uses the read method of the JAVA native BufferedReader to read the file line by line, and divides the line data into a string array according to the delimiter.
5. The system according to claim 3, characterized in that The fixed-length parsing supports byte and character forms, uses the read method of BufferedReader to read file lines, and intercepts data according to the field start and end subscripts.
6. The system according to claim 1, characterized in that The database operation visualization module includes an SQL operation area and a business query area, wherein the SQL operation area is used to execute SQL statements input by a user, and the business query area is used to manage business query templates.
7. The system according to claim 6, characterized in that The business query template includes template information including business name, SQL query statement and display table information, and the template information is persistently stored in an XML file.
8. The system according to claim 6, characterized in that The logic layer reads and executes the SQL query statement of the business query template from the XML file, and returns the query result to the presentation layer.
9. The system according to claim 1, characterized in that The database stores user authority configuration, and the configuration items of the user authority configuration include file directory authority and data encryption control.
10. The system according to claim 9, characterized in that In the user authority configuration, high-authority roles have the authority to view all files and data, and low-authority roles can only view specific files and desensitized or encrypted data.