Method, system and device for supporting multiple security business varieties to realize security transaction automatic operation and maintenance management, processor and storage medium

Abstract

The invention relates to a method for supporting multiple security business varieties to realize security transaction automatic operation and maintenance management, which comprises the following steps: a product configuration module constructs a product, process and component instance relationship to realize automatic deployment and automatic operation and maintenance of a business system; the automatic upgrade deployment module deploys uninstalled components through different product information; and the automatic business operation and maintenance module carries out operation and maintenance according to a product customized operation and maintenance process. By adopting the method, the system, the device, the processor and the computer readable storage medium for supporting multiple security business varieties to realize security transaction automatic operation and maintenance management, lightweight configuration is realized, i.e., distributed node operation and maintenance management of single business online expansion is realized, and through the design of business operation and maintenance and system management modules, the security transaction automatic operation and maintenance management is realized. The system operation and maintenance scene is covered in all directions, high customization and elastic capacity expansion are supported, a multi-service distributed node system is managed in a unified mode, and intelligent operation and maintenance management with high flexibility, convenience and stability is achieved.

Description

Technical Field

[0001] The present invention relates to the field of computer application technology, and in particular to the field of operation and maintenance management of securities trading systems. Specifically, it refers to a method, system, device, processor and computer-readable storage medium thereof that support multiple securities business types and realize automated operation and maintenance management of securities trading. Background Art

[0002] With the rapid development of global financial markets, securities trading is becoming increasingly diverse, encompassing a wide range of business types, including stocks, bonds, funds, options, futures, and derivatives. The complexity and scale of securities trading systems are also increasing, and traditional operations and management methods are no longer able to meet the demands of modern securities trading.

[0003] Traditional securities trading systems are typically designed for a single business type and struggle to adapt to multi-product, high-concurrency trading scenarios. The operation and maintenance of securities trading systems relies heavily on manual operations, including component deployment, troubleshooting, and resource allocation. Manual operation and maintenance is not only inefficient but also prone to system failures or trading interruptions due to operational errors, impacting securities trading operations. Traditional capacity expansion methods implement the operation and maintenance of independent business lines by synchronously adding operation and maintenance management nodes. This lack of flexible deployment and response leads to increased instability, high redundancy, and difficulty in unified management and scheduling. This lack of flexible deployment and response compromises the timeliness of business expansion and feature rollout. Increased instability and the proliferation of operation and maintenance nodes increase the scope and scope of node management and maintenance, increasing risk exposure and increasing the instability of system operations. This high level of redundancy leads to wasted software and hardware resources and increased development and maintenance manpower costs. Traditional checklist-based operation and maintenance solutions impose fixed procedures, are inflexible, and cannot dynamically add steps or execute the operation and maintenance of multiple securities products simultaneously. Summary of the Invention

[0004] The purpose of the present invention is to overcome the shortcomings of the above-mentioned prior art and provide a method, system, device, processor and computer-readable storage medium thereof that have good stability, low risk and a wide range of applicability, support multiple securities business types and realize automated operation and maintenance management of securities transactions.

[0005] To achieve the above objectives, the present invention provides a method, system, device, processor, and computer-readable storage medium thereof that supports multiple securities business types and implements automated operation and maintenance management of securities transactions as follows:

[0006] The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions is characterized in that the method comprises the following steps:

[0007] (1) The product configuration module builds the relationship between products, processes, and component instances to achieve automated deployment and automated operation and maintenance of business systems;

[0008] (2) The automated upgrade deployment module deploys the uninstalled components using different product information;

[0009] (3) The automated business operation and maintenance module performs operations and maintenance according to the product-customized operation and maintenance process.

[0010] Preferably, the step (1) specifically includes the following steps:

[0011] (1.1) The product configuration module uses database configuration tables to bind the relationship between products and components, and associates and binds products with instances through database tables to automatically upgrade and deploy instances;

[0012] (1.2) Bind the automated operation and maintenance process to the product relationship, build the operation and maintenance process definition table, configure exclusive operation and maintenance steps, and initialize the operation and maintenance status according to the operation and maintenance steps.

[0013] Preferably, the step (2) specifically includes the following steps:

[0014] (2.1) Clear redundant information before the upgrade deployment and the record data of the last upgrade deployment;

[0015] (2.2) Deployment pre-upgrade verification, verifying the upgrade version and component status by checking the heartbeat of the instance to be upgraded;

[0016] (2.3) Initialize server information, component information, instance information, and computer room information, and set parameters;

[0017] (2.4) Create a deployment upgrade task. Create a deployment task based on component information, set the task type and necessary parameters, insert the task into the deployment task table, and initialize the instance state.

[0018] (2.5) Execute deployment tasks.

[0019] Preferably, the step (2.2) specifically includes the following steps:

[0020] (2.2.1) Obtain information about the instances that need to be upgraded and filter out instances that are not on the exemption list;

[0021] (2.2.2) Determine whether the instance is alive based on the current time and the time it was added to the heartbeat table. If the time exceeds the threshold, no surviving instance is detected and the instance is stopped; otherwise, the instance is alive.

[0022] Preferably, the step (2.3) specifically includes the following steps:

[0023] (2.3.1) Based on the file upload record, determine whether the upgrade deployment file ID exists in the upload list;

[0024] (2.3.2) Check whether the product ID corresponding to the file exists, and set the product name of the current installation package according to the corresponding file name;

[0025] (2.3.3) Enter the root directory of the installation package, initialize the server information, component information, instance information, and computer room information, and set parameters.

[0026] Preferably, the step (2.4) specifically includes the following steps:

[0027] (2.4.1) Generate backup timestamp based on current system time;

[0028] (2.4.2) Generate the main task, set the processing status to processing, set the task type and necessary parameters, insert the task into the deployment task table, and obtain the task ID;

[0029] (2.4.3) Generate subtasks, execute upgrade deployment, insert group tasks into the subtask table, and obtain the task ID of the subtask;

[0030] (2.4.4) Initialize instance state.

[0031] Preferably, the step (2.5) specifically includes the following steps:

[0032] (2.5.1) Decompress the installation package, read the identity verification information of each file configured in the version and convert it into object information, obtain the instance content and version information file in the installation package, and verify it;

[0033] (2.5.2) Back up the database;

[0034] (2.5.3) Add all asynchronous tasks to the task queue, upload the file, find the corresponding server address according to the instance and replace it, and wait for all asynchronous tasks in the thread pool to complete;

[0035] (2.5.4) Generate a version file and upload it to the installation package directory of the specified node machine to confirm the upgrade version;

[0036] (2.5.5) Update the instance status and task status to deployment completed;

[0037] (2.5.6) If there are new deployment components, update the installation deployment checklist configuration, check the instance status, and start and stop the instance.

[0038] Preferably, the step (3) specifically includes the following steps:

[0039] (3.1) Before execution, initiate a step execution request through the page and substitute the step execution input parameters;

[0040] Verify step information and determine step status, lock the step with a distributed lock to prevent repeated execution, set the step status to executing, and insert the step execution log;

[0041] (3.2) Define the step execution method as the cut point and execute the execution logic of each step;

[0042] (3.3) End post-notification, obtain exceptions during step execution, capture exception status, insert exception status information, and release distributed locks at the same time;

[0043] (3.4) Configure automated operation and maintenance.

[0044] Preferably, the step (3.1) specifically includes the following steps:

[0045] (3.1.1) Verify step parameters, check whether the current process exists, and determine whether the step information exists. If so, continue with step (3.1.2); otherwise, end the step;

[0046] (3.1.2) If there is a sequence between processes, then the sequence of execution between processes is checked;

[0047] (3.1.3) Step status check: determine whether the current step status is executable, whether the previous step status is completed, or whether the step status information is normal. If so, continue with step (3.1.4); determine whether the step is locked. If the current step is locked, it indicates that the step is being executed; otherwise, end the step;

[0048] (3.1.4) Lock the current step;

[0049] (3.1.5) Set the current step status to executing.

[0050] (3.1.6) Insert step execution log.

[0051] Preferably, the step (3.1.4) is specifically as follows:

[0052] Build a step lock table and insert a record during execution. If the insertion is successful, the lock is acquired successfully. If the insertion fails or the current step lock already exists, the lock acquisition fails. When the step is completed, the lock and step are released by deleting the step lock record.

[0053] Preferably, the step (3.3) specifically includes the following steps:

[0054] (3.3.1) Determine whether the step execution is abnormal by capturing the abnormal content during the step execution. If the step execution is abnormal, continue with step (3.3.2); if the step execution does not capture the abnormality, continue with step (3.3.3);

[0055] (3.3.2) Change the current step status to execution failure, insert the abnormal status information into the log, display it on the visualization page, and simultaneously release the step distributed lock;

[0056] (3.3.3) Release the step lock and the step execution is completed.

[0057] Preferably, the step (3.4) specifically includes the following steps:

[0058] Configure the automated execution operation and maintenance switch, determine whether to enable the automated execution operation and maintenance step in the step execution aspect, obtain the current step sequence and determine the current step status, obtain the automated process step to be executed next, and perform automated operation and maintenance according to the configured time.

[0059] The system, which supports multiple securities business types and realizes automated operation and maintenance management of securities trading, has the following main features: the system includes a product configuration module, an automated upgrade deployment module and an automated business operation and maintenance module. The input ends of the automated upgrade deployment module and the automated business operation and maintenance module are both connected to the product configuration module. The product configuration module realizes automated deployment and automated operation and maintenance of different business systems by building product, process and component instance relationships; the automated upgrade deployment module manages multi-product distributed node components, performs independent version installation and deployment, version upgrades and upgrade records for different business systems, and realizes incremental or full installation and upgrade of components of different business systems; the automated business operation and maintenance module generates automated operation and maintenance templates by pre-configuring operation and maintenance processes to form daily operation and maintenance, and executes different operation and maintenance tasks according to the trading environment required by each business.

[0060] The device supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions has the following main features:

[0061] a processor configured to execute computer-executable instructions;

[0062] The memory stores one or more computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions are implemented.

[0063] The main feature of the processor that supports multiple securities business types and realizes automated operation and maintenance management of securities trading is that the processor is configured to execute computer-executable instructions. When the computer-executable instructions are executed by the processor, the various steps of the above-mentioned method of supporting multiple securities business types and realizing automated operation and maintenance management of securities trading are implemented.

[0064] The main feature of this computer-readable storage medium is that it stores a computer program, which can be executed by a processor to implement the various steps of the above-mentioned method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions.

[0065] The method, system, device, processor and computer-readable storage medium thereof of the present invention are used to support multiple securities business types and realize automated operation and maintenance management of securities transactions. Lightweight configuration realizes distributed node operation and maintenance management of single business online expansion, overcoming the shortcomings of traditional system expansion, such as a large increase in the number of system nodes, which leads to difficulty in timely expansion of business, poor stability, redundant software and hardware resources, and high development and operation and maintenance costs. In the same multi-business system scenario, through the design of business operation and maintenance and system management modules, all-round coverage of system operation and maintenance scenarios is achieved, supporting high customization and elastic expansion, realizing unified management of a system of multi-business distributed nodes, and intelligent operation and maintenance management with high flexibility, convenience and stability. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] Figure 1 This is a product deployment and operation flow chart of the method of the present invention that supports multiple securities business types and realizes automated operation and maintenance management of securities transactions.

[0067] Figure 2 This is a single-step operation and maintenance execution flow chart of the method of the present invention that supports multiple securities business types and realizes automated operation and maintenance management of securities transactions. DETAILED DESCRIPTION

[0068] In order to more clearly describe the technical content of the present invention, further description is given below in conjunction with specific embodiments.

[0069] The method of the present invention for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions includes the following steps:

[0070] (1) The product configuration module builds the relationship between products, processes, and component instances to achieve automated deployment and automated operation and maintenance of business systems;

[0071] (2) The automated upgrade deployment module deploys the uninstalled components using different product information;

[0072] (3) The automated business operation and maintenance module performs operations and maintenance according to the product-customized operation and maintenance process.

[0073] As a preferred embodiment of the present invention, the step (1) specifically includes the following steps:

[0074] (1.1) The product configuration module uses database configuration tables to bind the relationship between products and components, and associates and binds products with instances through database tables to automatically upgrade and deploy instances;

[0075] (1.2) Bind the automated operation and maintenance process to the product relationship, build the operation and maintenance process definition table, configure exclusive operation and maintenance steps, and initialize the operation and maintenance status according to the operation and maintenance steps.

[0076] As a preferred embodiment of the present invention, the step (2) specifically includes the following steps:

[0077] (2.1) Clear redundant information before the upgrade deployment and the record data of the last upgrade deployment;

[0078] (2.2) Deployment pre-upgrade verification, verifying the upgrade version and component status by checking the heartbeat of the instance to be upgraded;

[0079] (2.3) Initialize server information, component information, instance information, and computer room information, and set parameters;

[0080] (2.4) Create a deployment upgrade task. Create a deployment task based on component information, set the task type and necessary parameters, insert the task into the deployment task table, and initialize the instance state.

[0081] (2.5) Execute deployment tasks.

[0082] As a preferred embodiment of the present invention, the step (2.2) specifically includes the following steps:

[0083] (2.2.1) Obtain information about the instances that need to be upgraded and filter out instances that are not on the exemption list;

[0084] (2.2.2) Determine whether the instance is alive based on the current time and the time it was added to the heartbeat table. If the time exceeds the threshold, no surviving instance is detected and the instance is stopped; otherwise, the instance is alive.

[0085] As a preferred embodiment of the present invention, the step (2.3) specifically includes the following steps:

[0086] (2.3.1) Based on the file upload record, determine whether the upgrade deployment file ID exists in the upload list;

[0087] (2.3.2) Check whether the product ID corresponding to the file exists, and set the product name of the current installation package according to the corresponding file name;

[0088] (2.3.3) Enter the root directory of the installation package, initialize the server information, component information, instance information, and computer room information, and set parameters.

[0089] As a preferred embodiment of the present invention, the step (2.4) specifically includes the following steps:

[0090] (2.4.1) Generate backup timestamp based on current system time;

[0091] (2.4.2) Generate the main task, set the processing status to processing, set the task type and necessary parameters, insert the task into the deployment task table, and obtain the task ID;

[0092] (2.4.3) Generate subtasks, execute upgrade deployment, insert group tasks into the subtask table, and obtain the task ID of the subtask;

[0093] (2.4.4) Initialize instance state.

[0094] As a preferred embodiment of the present invention, the step (2.5) specifically includes the following steps:

[0095] (2.5.1) Decompress the installation package, read the identity verification information of each file configured in the version and convert it into object information, obtain the instance content and version information file in the installation package, and verify it;

[0096] (2.5.2) Back up the database;

[0097] (2.5.3) Add all asynchronous tasks to the task queue, upload the file, find the corresponding server address according to the instance and replace it, and wait for all asynchronous tasks in the thread pool to complete;

[0098] (2.5.4) Generate a version file and upload it to the installation package directory of the specified node machine to confirm the upgrade version;

[0099] (2.5.5) Update the instance status and task status to deployment completed;

[0100] (2.5.6) If there are new deployment components, update the installation deployment checklist configuration, check the instance status, and start and stop the instance.

[0101] As a preferred embodiment of the present invention, the step (3) specifically includes the following steps:

[0102] (3.1) Before execution, initiate a step execution request through the page and substitute the step execution input parameters;

[0103] Verify step information and determine step status, lock the step with a distributed lock to prevent repeated execution, set the step status to executing, and insert the step execution log;

[0104] (3.2) Define the step execution method as the cut point and execute the execution logic of each step;

[0105] (3.3) End post-notification, obtain exceptions during step execution, capture exception status, insert exception status information, and release distributed locks at the same time;

[0106] (3.4) Configure automated operation and maintenance.

[0107] As a preferred embodiment of the present invention, the step (3.1) specifically includes the following steps:

[0108] (3.1.1) Verify step parameters, check whether the current process exists, and determine whether the step information exists. If so, continue with step (3.1.2); otherwise, end the step;

[0109] (3.1.2) If there is a sequence between processes, then the sequence of execution between processes is checked;

[0110] (3.1.3) Step status check: determine whether the current step status is executable, whether the previous step status is completed, or whether the step status information is normal. If so, continue with step (3.1.4); determine whether the step is locked. If the current step is locked, it indicates that the step is being executed; otherwise, end the step;

[0111] (3.1.4) Lock the current step;

[0112] (3.1.5) Set the current step status to executing.

[0113] (3.1.6) Insert step execution log.

[0114] As a preferred embodiment of the present invention, the step (3.1.4) is specifically as follows:

[0115] Build a step lock table and insert a record during execution. If the insertion is successful, the lock is acquired successfully. If the insertion fails or the current step lock already exists, the lock acquisition fails. When the step is completed, the lock and step are released by deleting the step lock record.

[0116] As a preferred embodiment of the present invention, the step (3.3) specifically includes the following steps:

[0117] (3.3.1) Determine whether the step execution is abnormal by capturing the abnormal content during the step execution. If the step execution is abnormal, continue with step (3.3.2); if the step execution does not capture the abnormality, continue with step (3.3.3);

[0118] (3.3.2) Change the current step status to execution failure, insert the abnormal status information into the log, display it on the visualization page, and simultaneously release the step distributed lock;

[0119] (3.3.3) Release the step lock and the step execution is completed.

[0120] As a preferred embodiment of the present invention, the step (3.4) specifically includes the following steps:

[0121] Configure the automated execution operation and maintenance switch, determine whether to enable the automated execution operation and maintenance step in the step execution aspect, obtain the current step sequence and determine the current step status, obtain the automated process step to be executed next, and perform automated operation and maintenance according to the configured time.

[0122] The system of the present invention supports multiple securities business types and realizes automated operation and maintenance management of securities trading, wherein the system includes a product configuration module, an automated upgrade deployment module and an automated business operation and maintenance module, the input ends of the automated upgrade deployment module and the automated business operation and maintenance module are both connected to the product configuration module, and the product configuration module realizes automated deployment and automated operation and maintenance of different business systems by establishing product, process, and component instance relationships; the automated upgrade deployment module manages multi-product distributed node components, performs independent version installation and deployment, version upgrades and upgrade records for different business systems, and realizes incremental or full installation and upgrade of different business system components; the automated business operation and maintenance module generates automated operation and maintenance templates by pre-configuring operation and maintenance processes to form daily operation and maintenance, and executes different operation and maintenance tasks according to the trading environment required by each business.

[0123] The device of the present invention supports multiple securities business types and realizes automated operation and maintenance management of securities transactions, wherein the device comprises:

[0124] a processor configured to execute computer-executable instructions;

[0125] The memory stores one or more computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions are implemented.

[0126] The processor of the present invention supports multiple securities business types to realize automated operation and maintenance management of securities trading, wherein the processor is configured to execute computer-executable instructions. When the computer-executable instructions are executed by the processor, the various steps of the above-mentioned method of supporting multiple securities business types to realize automated operation and maintenance management of securities trading are implemented.

[0127] The computer-readable storage medium of the present invention stores a computer program thereon, and the computer program can be executed by a processor to implement the various steps of the above-mentioned method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions.

[0128] The present invention relates to the field of computer application technology, and in particular to the operation and maintenance management technology of securities trading systems. The complexity and diversity of securities business dictate that different core trading engines handle corresponding business operations, and a set of trading cores dictates a corresponding set of operation and maintenance management processes. The purpose of the present invention is to provide an automated operation and maintenance management method for securities trading that supports multiple securities business types. Through intelligent and automated technical means, this method addresses the problems of low operation and maintenance efficiency, poor system stability, insufficient scalability, and weak risk control faced by traditional securities trading systems in multi-product scenarios, thereby achieving efficient, stable, and scalable operation of the securities trading system.

[0129] The purpose of the present invention is to solve the shortcomings of the above-mentioned existing technology status and provide a securities trading automated operation and maintenance management method that supports multiple securities business types. It integrates the original multi-terminal management that requires one-to-one business with one-to-many unified management, and realizes the automated deployment and operation and maintenance management of different business systems through the free configuration plug-in implementation of the product, such as Figure 1 shown.

[0130] The securities trading automated operation and maintenance management module, which supports multiple securities business types, includes the following modules:

[0131] The automated upgrade deployment module is used to execute version upgrades of securities trading component instances and initial or overwriting deployments of component instances, while also generating log records of system deployment and upgrade operations.

[0132] The automated upgrade deployment module manages distributed node components across multiple products. It provides independent version installation, deployment, upgrades, and upgrade logging for different business systems, enabling incremental or full installation and upgrades of components across different business systems. Specifically, it dynamically selects the upgrade granularity based on scenario needs, allowing for flexible upgrades at the node level to minimize the risk of upgrade changes.

[0133] The automated business operations module is used to complete the daily operations of multiple business systems. It performs different operations and maintenance tasks based on the transaction environment required by each business, ensuring the normal startup and shutdown of each core transaction component and the smooth completion of transactions.

[0134] The automated business operation and maintenance module forms daily operation and maintenance by pre-configuring operation and maintenance processes and steps, generating automated operation and maintenance templates to ensure the daily operation and maintenance of various businesses, expand multi-product transaction operation and maintenance scenarios, and decouple various business scenarios to achieve unified management.

[0135] The product configuration module freely implements the automated deployment and automated operation and maintenance of different business systems by building relationships among products, processes, and component instances. Securities products correspond to multiple component instances, and a securities product also corresponds to its own independent operation and maintenance process.

[0136] First, identify the product information requiring O&M management, establish product domains, and associate the product's corresponding O&M processes with the product domains. Then, deploy components based on product configuration. Each component corresponds to multiple instances, which can include active and standby instances, ensuring high availability for the entire approach.

[0137] Preconfigure product information, upgrade and deploy component instances through the relationship between products and component instances. The installation, upgrade and deployment functions use pipeline operations to complete the incremental version upgrade of the current business system. The steps include uploading the installation package, instance selection, version deployment, and database script execution.

[0138] The system uses heartbeats to screen surviving components and determine whether the node components currently being upgraded meet the deployment upgrade requirements. It also creates a unique identifier for the upgrade deployment, obtains the uploaded upgrade file information, decompresses the deployment upgrade installation package, backs up the database and application information, verifies the file, and distributes it to each instance machine, updating file version information, instance status, and deployment records.

[0139] The method detects high-risk syntax, flexibly designs the boundaries of script upgrades, and asynchronously calls database connections with concurrent threads to execute database upgrade files, thereby ensuring high system availability.

[0140] This method adopts a layered technical architecture based on domain-driven design to build automated upgrade deployment and automated operation and maintenance modules. Data persistence is achieved by importing data into distributed databases according to multi-sharding processing. It supports multiple types of mainstream databases such as Oracle and MySQL, as well as domestic distributed databases such as GoldenDB and OceanBase.

[0141] The automated upgrade deployment module supports visual interface operations for all types of operation and maintenance services. It deploys uninstalled components using different product information. The specific steps are as follows:

[0142] 2-1 Clear redundant data: Clear redundant information before the upgrade deployment and the record data of the last upgrade deployment.

[0143] 2-2 Deployment instance verification: The automated upgrade deployment technology implementation includes pre-deployment upgrade verification, which verifies the survival of the upgraded version and component status by checking the heartbeat of the instance to be upgraded. The upgrade deployment should ensure that all instances are in a stopped state.

[0144] 2-3 Initialize data: Determine whether the uploaded file exists, initialize server information, component information, instance information and computer room information, and set parameters.

[0145] 2-4 Initialize Task: Create a deployment upgrade task. Based on the component information, create a globally uniquely labeled deployment task. Set the task type and required parameters, insert the task into the deployment task table, and initialize the instance status to Maintenance.

[0146] 2-5 Execute deployment tasks: Execute deployment tasks through multi-threading to improve deployment efficiency. Start executing the task upgrade deployment task based on the globally unique tag attribute. Verify the uploaded upgrade file information, automatically back up the pre-upgrade version, decompress the upgrade file, verify the actual file through the MD5 algorithm, and finally transfer the deployment file to the component machine that needs to be upgraded. Update the instance status and task status to deployment completed.

[0147] The automated business operation and maintenance module performs operation and maintenance according to the product-customized operation and maintenance process. The operation and maintenance steps can be executed through automated tasks or by clicking on a single step. The specific steps are as follows:

[0148] 3-1 Pre-step execution: All steps are executed uniformly before execution, step information is verified, and step status is determined. The steps are locked by distributed locks to prevent repeated execution of the steps. The step status is set to executing and the step execution log is inserted.

[0149] 3-2 Step point execution: Define the step execution method as a point in an aspect-oriented manner, and execute the unique execution logic of each step.

[0150] 3-3 Post-step execution: End the post-step notification of the step, obtain the exception in the step execution, capture the exception status, insert the exception status information, and release the distributed lock of the step execution at the same time. The step execution is completed.

[0151] 3-4 Automated Operation and Maintenance Configuration: Configure the automated execution operation and maintenance switch, determine whether to enable the automated execution operation and maintenance step in the step execution aspect, obtain the current step sequence when executing the step, determine the current step status, obtain the next automated process step to be executed, and perform automated operation and maintenance according to the configured time.

[0152] This method supports the dynamic configuration of multi-product securities business, ensures the daily operation and maintenance of core trading components, and supports multi-product trading operation and maintenance scenarios.

[0153] In a specific embodiment of the present invention, the specific steps are as follows:

[0154] 1. Product configuration

[0155] 1.1 Product Configuration: Configure the t_product table in the database to bind products and components. A single product can contain multiple components. For example, to set up a proprietary gold business for a securities product, add the proprietary gold product to the product table. Database tables are used to associate and bind products with instances, such as the proprietary gold related instances GTE (proprietary gold trading core component) and AGW (proprietary gold trading gateway component). Specific component instances correspond to corresponding physical data centers and servers. Once configured, you can use this to automatically upgrade and deploy instances.

[0156] 1.2 Automated operation and maintenance processes are bound to product relationships, and the operation and maintenance process definition table t_operation_process is constructed. A single product can correspond to multiple operation and maintenance processes. The operation and maintenance process includes process step definitions, step status definitions, and step log definitions. Process steps are used to display step information on the visual page, step status is used to indicate the flow between steps within the process, and step logs are used to record step execution information. Dedicated operation and maintenance steps are configured for specific products, and the operation and maintenance status is initialized based on the operation and maintenance steps.

[0157] 2. Automated deployment

[0158] Automated upgrade deployment involves uploading the required upgrade deployment package on the page and selecting the deployment upgrade instance to automatically replace the required runtime files and scripts for the instance program. Users can dynamically select the upgrade granularity based on scenario needs, flexibly upgrading at the node granularity to minimize the risk of upgrade changes. The specific steps are as follows:

[0159] 2.1 Clear Data

[0160] Clear redundant information before the upgrade deployment and the record data of the last upgrade deployment.

[0161] 2.2 Determine whether the instance is running. The upgrade deployment should ensure that all instances are in the stopped state.

[0162] (1) Obtain information about the instances that need to be upgraded and filter out instances that are not on the exemption list.

[0163] (2) Based on the value of currentTime-heartbeatTime>10s, whether the current time and the time of adding the heartbeat table exceed 10 seconds is used to determine whether the instance is alive.

[0164] (3) If the time exceeds 10 seconds, it means that no surviving instance can be detected and the instance is stopped.

[0165] 2.3 Initialization Data

[0166] (1) File upload record, determine whether the upgrade deployment file ID exists in the upload list;

[0167] (2) Check whether the product ID corresponding to the file exists, and set the name of the current installation package product according to the file name corresponding to the file;

[0168] (3) Enter the root directory of the installation package, initialize the server information, component information, instance information, computer room information, and set parameters.

[0169] 2.4 Initialize the generation task

[0170] (1) Generate a backup timestamp based on the current system time.

[0171] (2) Generate the main task, set the productId of the main task, set the processing status to processing, set the task type and necessary parameters, insert the task into the deployment task table, and obtain the task Id.

[0172] (3) Generate subtasks and create a corresponding subTask for each instance. For subsequent multi-threaded upgrade deployment, the subtask inserts the group task into the subtask table and obtains the subTaskId of the subtask.

[0173] (4) Initialize the instance status to maintenance.

[0174] 2.5 Thread pool execution deployment tasks

[0175] By executing deployment tasks through multi-threading, deployment efficiency is improved. First, the installation package is decompressed, then the database information and applications are backed up, and then the file is transferred to the machine to be deployed through file copying. Finally, the MD5 code is used to determine whether the file transfer is complete.

[0176] (1) Unzip the installation package. Obtain the service for different file decompression services based on the file format, obtain server information, unzip the installation package, read VersionConfig.json, which contains the identity verification information for each file configured in the version, and convert it into object information. Obtain the instance content and version information file in the installation package. Use the MD5 algorithm to verify the actual file and the source MD5 value in VersionConfig.json to determine whether the upgrade content meets expectations.

[0177] (2) Backup. Back up the database. Generate corresponding backup export statements for each product to back up all databases to be backed up and exported.

[0178] (3) Add file copy. Add all asynchronous tasks to the task queue based on taskId and subTaskId, upload the file to the instance machine where the upgrade is deployed, find the corresponding server address based on the instance and replace it, and wait for all asynchronous tasks in the thread pool to complete.

[0179] (4) Generate a version file and upload it to the installation package name directory of the machine of the specified node to determine the upgraded version.

[0180] (5) Update status. Update the instance status and task status to deployment completed.

[0181] (6) If there are new deployment components, update the install.list (installation deployment list configuration). You can also use manual shell scripts to check the instance status and start and stop the instance.

[0182] (7) Upgrade deployment completed.

[0183] 3. Automated Operation and Maintenance

[0184] The method supports visual interface operations for all types of operation and maintenance services under multiple industries, simplifies the complexity and difficulty of operations, reduces the operating costs of operation and maintenance personnel, and improves the overall operation and maintenance efficiency of the entire trading system. The execution of steps is carried out through the AOP aspect-oriented approach. For different steps, the operation and maintenance step process can be divided into three parts. Please refer to Figure 2 As shown:

[0185] 3.1 Step Pre-execution

[0186] All steps are executed uniformly before execution. A step execution request is initiated through the page, and step execution parameters are substituted, including product information, step information, execution item content, etc.

[0187] (1) Step parameter verification: check whether the current process exists and whether the step information exists.

[0188] (2) If there is a sequence between processes, the execution sequence between processes is checked.

[0189] (3) Step status check: determine whether the current step status is executable, whether the previous step status is completed, and whether the step status information is abnormal. By determining whether the step is in a locked state, if the current step is locked, it indicates that the step is being executed.

[0190] (4) Once the step verification is passed, the current step is locked. Step locking is implemented using a distributed lock in a database. First, a step lock table is constructed. When a step is executed, a record is inserted into the table. A successful insertion indicates a successful lock acquisition. A failed insertion or an existing step lock indicates a failed lock acquisition. When the step is completed, the lock and the step are released by deleting the step lock record.

[0191] (5) Locking is successful, and the current step status is set to executing.

[0192] (6) Insert the step execution log and complete the preparation before step execution.

[0193] 3.2 Execution steps

[0194] The execution of a step serves as the execution point for all other steps, implementing its own unique execution logic. Taking the system environment preparation step as an example, step execution, through the configured aspect annotations, enters the environment preparation method, begins to verify the current component instance status, validate the current trading day, and generate and distribute the necessary files for the instance.

[0195] 3.3 Ending Steps

[0196] The end step is a post-notification for all steps.

[0197] (1) By capturing the abnormal content during the execution of the step, determine whether the execution of the step is abnormal.

[0198] (2) If an exception occurs during step execution, the current step status is changed to execution failure, the exception status information is inserted into the log, and displayed on the visualization page. The distributed lock of the step is released synchronously.

[0199] (3) The step execution does not catch the exception, the current step is executed successfully, the step lock is released, and the step execution is completed.

[0200] 3.4 Operation and maintenance automation configuration

[0201] Configure the automated execution switch and determine whether to enable automated execution of the step in the step execution aspect. Configure the automated execution service ScheduleDomainService and read the automated execution configuration: execution time, execution steps, and other information. When executing a step, obtain the current step sequence and follow the aforementioned step execution logic. If the current step is executed successfully, obtain the next automated process step to be executed. If a next step exists, obtain the input parameters based on the configuration information and call the next step execution service to start execution. If no next step exists, the automated operation and maintenance execution ends.

[0202] The automated upgrade deployment function is used to perform system version installation and upgrades, as well as initial or overwrite deployments. It also generates log records of system deployment and upgrade operations. This method ensures high system availability by detecting high-risk syntax, flexibly designing script upgrade boundaries, and asynchronously calling database connections with concurrent threads to execute database upgrade files.

[0203] The automated operation and maintenance module optimizes operational functions by flexibly updating operational processes, ensuring stable trading system operation. The automated execution of operational processes includes scheduled tasks, which are executed based on the opening and closing times of the current product. This approach also supports the dynamic configuration of multi-product securities transactions, ensuring the daily operation and maintenance of core trading components, and supporting multi-product trading operations.

[0204] The beneficial effects of the present invention are as follows:

[0205] The present invention provides system operation and maintenance functions, provides personalized operation and maintenance function support for different products and different businesses, ensures the normal operation of the transaction system and improves the security performance of the transaction system.

[0206] The present invention can achieve centralized and unified management, decompose the complex products and business scenarios of securities trading, build a unified management system that integrates multiple business products to upgrade and deploy component instances managed by operation and maintenance, and optimize the transaction operation and maintenance process.

[0207] The present invention can realize automated operation and maintenance, simplify the operation and maintenance process of business systems, realize automated and intelligent operation and maintenance methods, improve the operation and maintenance efficiency of transaction systems, reduce the difficulty of manual operation and maintenance and deployment, and promote the formalization and process of transaction operation and maintenance.

[0208] The present invention is business-centric and product-oriented, and distributes components and nodes to achieve the decomposition and decoupling of complex transaction products and business scenarios, providing the system with the ability to adapt to the changing development of subsequent business.

[0209] The operation and maintenance module in this technical solution achieves automated operations and maintenance through the flow of its self-defined operation and maintenance state machine. By flexibly configuring operation and maintenance tasks and steps, the operation and maintenance process is realized through the operation and maintenance state during the implementation of steps and tasks. Using the process as the basic unit, the operation and maintenance of trading systems is adaptable to a variety of securities trading products and trading scenarios. This further emphasizes the flexible configuration of the operation and maintenance module, the convenience of automation, and the scalability of products and trading scenarios.

[0210] The upgrade deployment module in this technical solution executes upgrade deployment tasks through a visual interface, ensuring version maintenance of the automated securities trading operation and management method itself and enabling continuous upgrades and optimization of the method's functionality. By integrating a heartbeat component to determine the survival of trading components and whether upgrade components meet deployment requirements, the module executes component upgrade tasks through concurrent threads, ensuring high system availability.

[0211] The deployment and operation and maintenance modules in this invention's technical solution implement transaction component upgrades and basic operation and maintenance services through visual interfaces and flexible task configuration within each module. This automated operation and maintenance management method, based on the independent deployment and upgrade needs of multiple business systems, utilizes lightweight configuration to implement distributed node operation and maintenance management for single-business rollout and expansion. This overcomes the shortcomings of traditional system expansion, such as the difficulty in timely business expansion due to a large increase in the number of system nodes, poor stability, redundant software and hardware resources, and high development and operation and maintenance costs.

[0212] The database construction method in the technical solution of the present invention constructs database relationships based on operation and maintenance scenarios, creates basic database tables through database relationships, and provides basic data support for the operation and maintenance system.

[0213] The technical solution of the present invention defines an automated upgrade deployment module, which completes the automated upgrade deployment of the system by supporting and recording version upgrades and component instance deployment methods and records through a basic database.

[0214] The operation and maintenance execution in the technical solution of the present invention executes the operation and maintenance process through the flow of adaptive operation and maintenance status, flows the operation and maintenance status through its own automated workflow, and flexibly realizes operation and maintenance through configurable step information and tasks.

[0215] The specific implementation scheme of this embodiment can be found in the relevant descriptions in the above embodiments and will not be repeated here.

[0216] It can be understood that the same or similar parts of the above embodiments can be referenced to each other, and the contents not described in detail in some embodiments can refer to the same or similar contents in other embodiments.

[0217] It should be noted that, in the description of the present invention, the terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance. In addition, in the description of the present invention, unless otherwise specified, the meaning of "plurality" is at least two.

[0218] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention pertain.

[0219] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution device. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0220] Those skilled in the art will understand that all or part of the steps in the method for implementing the above-mentioned embodiment can be completed by instructing related hardware through a program, and the corresponding program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0221] Furthermore, the functional units in the various embodiments of the present invention may be integrated into a single processing module, each unit may exist physically separately, or two or more units may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or software functional modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

[0222] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0223] Throughout this specification, reference to terms such as "one embodiment," "some embodiments," "examples," "specific examples," or "some examples" means that a specific feature, structure, material, or characteristic described in conjunction with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0224] The method, system, device, processor and computer-readable storage medium thereof of the present invention are used to support multiple securities business types and realize automated operation and maintenance management of securities transactions. Lightweight configuration realizes distributed node operation and maintenance management of single business online expansion, overcoming the shortcomings of traditional system expansion, such as a large increase in the number of system nodes, which leads to difficulty in timely expansion of business, poor stability, redundant software and hardware resources, and high development and operation and maintenance costs. In the same multi-business system scenario, through the design of business operation and maintenance and system management modules, all-round coverage of system operation and maintenance scenarios is achieved, supporting high customization and elastic expansion, realizing unified management of a system of multi-business distributed nodes, and intelligent operation and maintenance management with high flexibility, convenience and stability.

[0225] In this specification, the present invention has been described with reference to specific embodiments thereof. However, it will be apparent that various modifications and variations may be made without departing from the spirit and scope of the present invention. Accordingly, the specification and drawings are to be regarded as illustrative rather than restrictive.

Claims

1. A method for supporting multiple securities business types to realize automated operation and maintenance management of securities transactions, characterized in that: The method comprises the following steps: (1) The product configuration module builds the relationship between products, processes, and component instances to achieve automated deployment and automated operation and maintenance of business systems; (2) The automated upgrade deployment module deploys the uninstalled components using different product information; (3) The automated business operation and maintenance module performs operations and maintenance according to the product-customized operation and maintenance process.

2. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 1, characterized in that: The step (1) specifically includes the following steps: (1.1) The product configuration module uses database configuration tables to bind the relationship between products and components, and associates and binds products with instances through database tables to automatically upgrade and deploy instances; (1.2) Bind the automated operation and maintenance process to the product relationship, build the operation and maintenance process definition table, configure exclusive operation and maintenance steps, and initialize the operation and maintenance status according to the operation and maintenance steps.

3. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 1, characterized in that: The step (2) specifically includes the following steps: (2.1) Clear redundant information before the upgrade deployment and the record data of the last upgrade deployment; (2.2) Deployment pre-upgrade verification, verifying the upgrade version and component status by checking the heartbeat of the instance to be upgraded; (2.3) Initialize server information, component information, instance information, and computer room information, and set parameters; (2.4) Create a deployment upgrade task. Create a deployment task based on component information, set the task type and necessary parameters, insert the task into the deployment task table, and initialize the instance state. (2.5) Execute deployment tasks.

4. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 3, characterized in that: The step (2.2) specifically includes the following steps: (2.2.1) Obtain information about the instances that need to be upgraded and filter out instances that are not on the exemption list; (2.2.2) Determine whether the instance is alive based on the current time and the time it was added to the heartbeat table. If the time exceeds the threshold, no surviving instance is detected and the instance is stopped; otherwise, the instance is alive.

5. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 3, characterized in that: The step (2.3) specifically includes the following steps: (2.3.1) Based on the file upload record, determine whether the upgrade deployment file ID exists in the upload list; (2.3.2) Check whether the product ID corresponding to the file exists, and set the product name of the current installation package according to the corresponding file name; (2.3.3) Enter the root directory of the installation package, initialize the server information, component information, instance information, and computer room information, and set parameters.

6. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 3, characterized in that: The step (2.4) specifically includes the following steps: (2.4.1) Generate backup timestamp based on current system time; (2.4.2) Generate the main task, set the processing status to processing, set the task type and necessary parameters, insert the task into the deployment task table, and obtain the task ID; (2.4.3) Generate subtasks, execute upgrade deployment, insert group tasks into the subtask table, and obtain the task ID of the subtask; (2.4.4) Initialize instance state.

7. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 3, characterized in that: The step (2.5) specifically includes the following steps: (2.5.1) Decompress the installation package, read the identity verification information of each file configured in the version and convert it into object information, obtain the instance content and version information file in the installation package, and verify it; (2.5.2) Back up the database; (2.5.3) Add all asynchronous tasks to the task queue, upload the file, find the corresponding server address according to the instance and replace it, and wait for all asynchronous tasks in the thread pool to complete; (2.5.4) Generate a version file and upload it to the installation package directory of the specified node machine to confirm the upgrade version; (2.5.5) Update the instance status and task status to deployment completed; (2.5.6) If there are new deployment components, update the installation deployment checklist configuration, check the instance status, and start and stop the instance.

8. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 1, characterized in that: The step (3) specifically includes the following steps: (3.1) Before execution, initiate a step execution request through the page and substitute the step execution input parameters; Verify step information and determine step status, lock the step with a distributed lock to prevent repeated execution, set the step status to executing, and insert the step execution log; (3.2) Define the step execution method as the cut point and execute the execution logic of each step; (3.3) End post-notification, obtain exceptions during step execution, capture exception status, insert exception status information, and release distributed locks at the same time; (3.4) Configure automated operation and maintenance.

9. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 8, characterized in that: The step (3.1) specifically includes the following steps: (3.1.1) Verify step parameters, check whether the current process exists, and determine whether the step information exists. If so, continue with step (3.1.2); otherwise, end the step; (3.1.2) If there is a sequence between processes, then the sequence of execution between processes is checked; (3.1.3) Step status check: determine whether the current step status is executable, whether the previous step status is completed, or whether the step status information is normal. If so, continue with step (3.1.4); determine whether the step is locked. If the current step is locked, it indicates that the step is being executed; otherwise, end the step; (3.1.4) Lock the current step; (3.1.5) Set the current step status to executing; (3.1.6) Insert step execution log.

10. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 9, characterized in that: The steps (3.1.4) are specifically: Build a step lock table and insert a record during execution. If the insertion is successful, the lock is acquired successfully. If the insertion fails or the current step lock already exists, the lock acquisition fails. When the step is completed, the lock and step are released by deleting the step lock record.

11. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 8, characterized in that: The step (3.3) specifically includes the following steps: (3.3.1) Determine whether the step execution is abnormal by capturing the abnormal content during the step execution. If the step execution is abnormal, continue with step (3.3.2); if the step execution does not capture the abnormality, continue with step (3.3.3); (3.3.2) Change the current step status to execution failure, insert the abnormal status information into the log, display it on the visualization page, and simultaneously release the step distributed lock; (3.3.3) Release the step lock and the step execution is completed.

12. The method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions according to claim 8, characterized in that: The step (3.4) specifically includes the following steps: Configure the automated execution operation and maintenance switch, determine whether to enable the automated execution operation and maintenance step in the step execution aspect, obtain the current step sequence and determine the current step status, obtain the automated process step to be executed next, and perform automated operation and maintenance according to the configured time.

13. A system for implementing the method according to any one of claims 1 to 12, supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions, characterized in that: The system includes a product configuration module, an automated upgrade deployment module and an automated business operation and maintenance module. The input ends of the automated upgrade deployment module and the automated business operation and maintenance module are both connected to the product configuration module. The product configuration module realizes the automated deployment and automated operation and maintenance of different business systems by building product, process and component instance relationships; the automated upgrade deployment module manages multi-product distributed node components, performs independent version installation and deployment, version upgrades and upgrade records for different business systems, and realizes incremental or full installation and upgrade of different business system components; the automated business operation and maintenance module generates automated operation and maintenance templates through pre-configured operation and maintenance processes to form daily operation and maintenance, and executes different operation and maintenance tasks according to the transaction environment required by each business.

14. A device that supports multiple securities business types and realizes automated operation and maintenance management of securities transactions, characterized in that: The device comprises: a processor configured to execute computer-executable instructions; A memory storing one or more computer-executable instructions, wherein when the computer-executable instructions are executed by the processor, the steps of the method for supporting multiple securities business types and realizing automated operation and maintenance management of securities trading as described in any one of claims 1 to 12 are implemented.

15. A processor that supports multiple securities business types and realizes automated operation and maintenance management of securities transactions, characterized in that: The processor is configured to execute computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the method for supporting multiple securities business types and realizing automated operation and maintenance management of securities trading as described in any one of claims 1 to 12 are implemented.

16. A computer-readable storage medium, characterized in that A computer program is stored thereon, and the computer program can be executed by a processor to implement the various steps of the method for supporting multiple securities business types and realizing automated operation and maintenance management of securities transactions as described in any one of claims 1 to 12.

Images