A financial institution operation and maintenance service automation management method and system

Abstract

The application provides a financial institution operation and maintenance service automation management method, which comprises the following steps: based on a relational database, establishing operation and maintenance service management business process form data; configuring a form table engine and a form table component, realizing parameter data caching and query management through a cache database and a relational database; based on a form table listener, realizing form table action monitoring; classifying operation and maintenance objects based on operation and maintenance object attributes, and binding the classified operation and maintenance objects with operation and maintenance operations; when an operation and maintenance process is driven to a process node, a process listener automatically transmits business process forms and data in the form table to a preset operation and maintenance tool script, and drives the corresponding preset operation and maintenance tool script to operate on an operation and maintenance object corresponding to an operation and maintenance operation, so as to automatically execute the operation and maintenance operation. The application further provides a financial institution operation and maintenance service automation management system, and the efficiency of financial institution operation and maintenance service management is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of operation and maintenance service management, in particular to a financial institution operation and maintenance service automation management method and system. BACKGROUND

[0002] The ITSM platform (operation and maintenance service management platform) of a financial institution is mainly used for managing the operation and maintenance service work of the financial institution.

[0003] The traditional ITSM platform only manages the operation and maintenance service work in a process manner, and builds the operation and maintenance service management process through a process engine and a self-defined form. Although the operation and maintenance work can be effectively managed in a process manner, a large amount of operation and maintenance work still needs to be executed offline, resulting in high construction and maintenance costs of the process. In addition, the operation and maintenance service management process lacks monitoring and management of the form in the operation and maintenance process, and the operation and maintenance object cannot be matched with the operation and maintenance operation, resulting in chaotic execution of the operation and maintenance operation and low operation and maintenance management efficiency. SUMMARY

[0004] In order to solve the problems in the prior art, the present application provides a financial institution operation and maintenance service automation management method and system, which effectively solves the problem of low operation and maintenance management efficiency caused by the prior art and effectively improves the operation and maintenance service management efficiency of the financial institution.

[0005] The first aspect of the present application provides a financial institution operation and maintenance service automation management method, comprising:

[0006] Based on a relational database, a business process form data of operation and maintenance service management is established, and the business process form data at least includes a Json type field and a virtual column field. The Json type field is used for storing form item data in the business process form data, which has a change frequency greater than a first preset frequency threshold. The virtual column field is used for storing the Json type field, which has a query frequency greater than a second preset frequency threshold.

[0007] A form form engine and a form form component supporting dynamic data source configuration are configured, and the parameter data is cached and queried through a cache database and a relational database. Based on a pre-set form form listener, form form action monitoring is realized.

[0008] Based on different operation and maintenance object attributes, the operation and maintenance objects are classified, and the classified operation and maintenance objects are correspondingly bound with the operation and maintenance operations, so as to realize the management of the operation and maintenance operations.

[0009] A flow listener is set, when the operation and maintenance flow is driven to the flow node, the flow listener automatically transmits the business flow form and the data in the form to the preset operation and maintenance tool script, and drives the corresponding preset operation and maintenance tool script to operate on the operation and maintenance object corresponding to the operation and maintenance operation, and automatically executes the operation and maintenance operation.

[0010] Optionally, the business flow form data further includes a varchar type field for storing form item data in the business flow form data that does not change.

[0011] Optionally, the configuration of the form form engine and the form form component supporting the dynamic data source configuration is achieved by a cache database and a relational database to realize the cache and query management of parameter data, specifically:

[0012] The parameter data in the business flow form data is managed by a relational database, wherein the parameter data supports a tree structure, and each parameter data can be configured with a parent parameter.

[0013] The cache database is used to realize the cache of the parameter data in the business flow form data, and when the parameter data in the relational database changes, the changed parameter data is automatically synchronized to the cache database.

[0014] When the front-end parameter data query request is obtained, the cache database is first searched, and if the search is not found, the relational database is searched.

[0015] Further, the parameter data in the business flow form data also supports the configuration of an extended attribute, and multiple extended attribute parameters are configured for a parameter data.

[0016] Optionally, the form form component is bound with the parameter data type in the business flow form data, and the bound parameter data type is stored in the Json description field defined by the form form engine for the form form, and the Json description field is used to describe the data format information of the Json type field.

[0017] Further, when the form form is rendered, the form form component obtains the parameter data in the business flow form data through the cache interface of the cache database, and renders the parameter data in the business flow form data to the form form.

[0018] Optionally, the form listener comprises a listening component, a listening condition, a triggering component, and a triggering action, the listening component is used to define which component in the form triggers the form listener after a change; the listening condition is used to define what kind of change condition the component to be listened to in the form meets, so as to trigger the form listener to monitor; the triggering component is used to define what kind of linkage change of which component in the form is caused after the change of the component to be listened to; and the triggering action is used to define what kind of change of the linked component in the form occurs.

[0019] Optionally, the classified operation and maintenance objects comprise an application system, an infrastructure, a storage device, a security device, a network device, a host, a database, and middleware.

[0020] Further, the classified operation and maintenance objects support multi-level classification.

[0021] The second aspect of the application provides a financial institution operation and maintenance service automation management system, comprising:

[0022] A building module is configured to build business process form data of operation and maintenance service management based on a relational database, wherein the business process form data at least comprises a Json type field and a virtual column field, the Json type field is used to store form item data in the business process form data, and the number of changes of the form item data is greater than a first preset number threshold, and the virtual column field is used to store the Json type field, and the number of queries of the Json type field is greater than a second preset number threshold;

[0023] A configuration module is configured to configure a form form engine and a form form component supporting dynamic data source configuration, to realize parameter data caching and query management through a cache database and a relational database, and to realize form form action monitoring based on a pre-set form form listener;

[0024] A classification module is configured to classify operation and maintenance objects based on different operation and maintenance object attributes, to correspondingly bind the classified operation and maintenance objects and operation and maintenance operations, and to realize operation and maintenance operation management;

[0025] A setting module is configured to automatically transmit data in a business process form and a form form to a preset operation tool script when an operation process drives to a process node, and to drive the corresponding preset operation tool script to automatically execute operation and maintenance operations on operation and maintenance objects corresponding to the operation and maintenance operations.

[0026] The technical solution adopted by the application has the following technical effects:

[0027] 1. The application is based on a pre-set form listener, which realizes form action monitoring; classifies operation and maintenance objects, and binds the classified operation and maintenance objects with operation and maintenance operations to realize operation and maintenance operation management; when the operation and maintenance process drives to a process node, the process listener automatically transmits the business process form and the data in the form to the preset operation and maintenance tool script, and drives the corresponding preset operation and maintenance tool script to operate on the operation and maintenance object corresponding to the operation and maintenance operation, and automatically executes the operation and maintenance operation, effectively solving the problem of low operation and maintenance management efficiency caused by the prior art, and effectively improving the efficiency of financial institution operation and maintenance service management.

[0028] 2. In the technical solution of the application, the business process form data includes not only Json type fields and virtual column fields, but also varchar type fields, the virtual column fields are used to store Json type fields with query times greater than a second preset number threshold, and through the Json type fields, the virtual column fields and the varchar type fields, the flexibility and scalability of operation and maintenance service management are ensured, and the performance requirements and statistical analysis requirements are met to the greatest extent.

[0029] 3. In the technical solution of the application, the form component is bound with the parameter data type in the business process form data, the bound parameter data type is stored in the Json description field defined by the form form engine for the form form, and the Json description field is used to describe the data format information of the Json type field; and when the form form is rendered, the form component obtains the parameter data in the business process form data through the cache interface of the cache database, and renders the parameter data in the business process form data into the form form, which not only effectively reduces the system resource consumption, but also greatly improves the flexibility and scalability of the form.

[0030] 4. The form listener in the technical solution of the application includes a listening component, a listening condition, a triggering component and a triggering action, the listening component is used to define which component in the form form triggers the form listener after a change; the listening condition is used to define what change condition the component to be listened to in the form form meets to trigger the form listener to monitor; the triggering component is used to define what linkage change of which components in the form form will be caused after the change of the component to be listened to; and the triggering action is used to define what change of the linked component in the form form, by dividing the form listener, the linkage between the form components in the form form can be realized, and the user can complete the setting of the complex change of the form by defining the listening rule for each form.

[0031] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the application. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 This is a flowchart illustrating the method of Embodiment 1 in the present invention;

[0034] Figure 2 This is a schematic diagram of the operation and maintenance service management process in Embodiment 1 of the present invention;

[0035] Figure 3 This is a schematic diagram of the overall architecture of the ITSM platform constructed based on Embodiment 1 of the present invention.

[0036] Figure 4 This is a diagram illustrating how traditional ITSM platforms store form data using relational databases.

[0037] Figure 5 This is a diagram illustrating how traditional ITSM platforms store form data using a non-relational database.

[0038] Figure 6 This is a schematic diagram illustrating how the ITSM platform, built based on this embodiment, stores form data using a relational database in the method of embodiment one of the present invention.

[0039] Figure 7 This is a flowchart illustrating step S2 in the method of Embodiment 1 of the present invention;

[0040] Figure 8 This is a schematic diagram illustrating the process of caching and querying parameter data through a cached database and relational data in the method of Embodiment 1 of the present invention.

[0041] Figure 9 This is a schematic diagram of the JSON description field defined in the form by the form engine in the method of Embodiment 1 of the present invention;

[0042] Figure 10 This is a diagram illustrating how a form listener monitors changes to a form in a traditional ITSM platform.

[0043] Figure 11 This is a schematic diagram illustrating the monitoring of form changes by the form listener in the ITSM platform constructed based on this embodiment of the present invention.

[0044] Figure 12 Figure 1 is a schematic diagram of the classification of operation and maintenance objects in the method of embodiment one of the present application;

[0045] Figure 13 Figure 2 is a schematic diagram of the monitoring of a flow listener in the method of embodiment one of the present application;

[0046] Figure 14 Figure 3 is a schematic diagram of the overall operation and maintenance service flow in the ITSM platform constructed based on embodiment one of the present application;

[0047] Figure 15 Figure 4 is a schematic diagram of the basic configuration of a flow node in the method of embodiment one of the present application;

[0048] Figure 16 Figure 5 is a schematic diagram of the configuration of a flow listener in the method of embodiment one of the present application;

[0049] Figure 17 Figure 6 is a schematic diagram of the binding of a flow listener to a preset operation and maintenance tool in the method of embodiment one of the present application;

[0050] Figure 18 Figure 7 is a schematic diagram of the configuration of a form listener in the method of embodiment one of the present application;

[0051] Figure 19 Figure 8 is a schematic diagram of the structure of the system of embodiment two of the present application. DETAILED DESCRIPTION

[0052] In order to clearly illustrate the technical features of the present application, the present application will be described in detail below with reference to specific embodiments and the accompanying drawings. The following disclosure provides many different embodiments or examples for implementing the different structures of the present application. In order to simplify the disclosure of the present application, the components and settings of specific examples are described below. In addition, the present application can repeatedly refer to numerals and / or letters in different examples. Such repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings being discussed. It should be noted that the components illustrated in the drawings are not necessarily drawn to scale. The present application omits the description of well-known components and processing techniques and processes to avoid unnecessary limitation of the present application.

[0053] Embodiment one

[0054] As shown in Figure 1 , the present application provides a financial institution operation and maintenance service automation management method, comprising:

[0055] S1. Based on a relational database, establish business process form data for operation and maintenance service management. The business process form data includes at least a JSON type field and a virtual column field. The JSON type field is used to store form item data in the business process form data whose number of changes is greater than a first preset threshold. The virtual column field is used to store JSON type fields whose number of queries is greater than a second preset threshold.

[0056] S2 configures the form engine and supports form components with dynamic data source configuration. It caches and manages parameter data by caching databases and relational data. Based on pre-set form listeners, it monitors form actions.

[0057] S3 categorizes operation and maintenance objects based on their different attributes, and then binds the categorized operation and maintenance objects to corresponding operation and maintenance operations to achieve the management of operation and maintenance operations.

[0058] S4. Set up a process listener. When the operation and maintenance process drives to a process node, the process listener automatically passes the business process form and the data in the form to the preset operation and maintenance tool script, and drives the corresponding preset operation and maintenance tool script to automatically execute the operation and maintenance operation on the operation and maintenance object corresponding to the operation and maintenance operation.

[0059] In step S1, the business process form data also includes a varchar type field, which is used to store form item data that does not change in the business process form data. The technical solution of this invention creates a fully automated and self-service operation and maintenance service management process by building a new generation of operation and maintenance service management platform.

[0060] like Figure 2 As shown, the process side quickly builds easy-to-maintain and easily expandable operation and maintenance service processes through "zero-code" and "low-code" methods; the business side takes CMDB (IT Configuration Management Database) and automated operation and maintenance as the core to realize the automated execution of operation and maintenance actions and the automated update of IT asset changes, creating an operation and maintenance service management platform that runs through the entire life cycle of operation and maintenance services / operation and maintenance delivery, with the aim of improving user satisfaction, reducing operation and maintenance service costs, and improving operation and maintenance service efficiency.

[0061] like Figure 3As shown, in the technical scheme embodiment of the present application, the overall scheduling of the operation and maintenance service process is realized by the flow engine (flowable) in the ITSM platform, the IT asset data is managed by taking the CMDB (Configuration Management Database) as the core data source, and the operation automation is realized by customizing a series of operation scripts (easyops script library) / processes (easyosp process library) in the automatic operation and maintenance platform.

[0062] The core capability of the operation service process platform is to drive the process execution according to the pre-set rules based on the flow engine capability. By introducing the flowable flow engine (an open source lightweight business process engine written in Java, based on the BPMN2.0 protocol, realizing the management of operations such as creation, query, flow, and report of the process), and a large number of secondary development is carried out for the flowable, it is more suitable for the requirements of the operation and maintenance management process of the financial IT enterprise.

[0063] The process form data is stored and managed in the Json field in the Mysql (relational database), which meets the flexibility of data query statistics and the scalability requirements of the system under the premise of ensuring the system performance requirements.

[0064] As shown in Figures 4-5 The traditional ITSM platform stores form data mainly in two ways: one is to store it in a relational database: each item in the business process form corresponds to a database table field, which is the way most ITSM platforms adopt. Although this way can clearly store and manage data, it loses the ability of flexible expansion, and the problems are as shown in Table 1:

[0065]

[0066] The other is to store it in a non-relational database, that is, to store the form data in a non-relational database (such as mongodb), and to store the non-variable part of the business process form data in a relational database and the frequently changing part in a non-relational database. Although this scheme can solve the problem of flexible data storage, it affects the system performance and is not convenient for data statistics and query, and the problems are as shown in Table 2:

[0067]

[0068] Based on the advantages and disadvantages of the above two schemes, as shown in Figure 6 , the embodiment selects to manage the business process form data by the "regular type field (varchar field) + Json type field + virtual column field" of the mysql database:

[0069] The "unchanging type" is stored through a Mysql normal field (varchar field), the "frequently changing type" is stored through a Json type field, and the frequently queried fields in Json are mapped to the business table through a virtual column (supporting adding an index to the virtual column), that is, the Json type field is used to store the form item data in the business process form data which changes more than a first preset number of times, and the virtual column field is used to store the Json type field which is queried more than a second preset number of times; the varchar type field is used to store the form item data in the business process form data which does not change; both ensure the flexibility and scalability of operation and maintenance service management, and meet the performance requirements and statistical analysis requirements to the greatest extent.

[0070] As shown in Figure 7 S21, managing parameter data in the business process form data through a relational database, wherein the parameter data supports a tree structure, and each parameter data can be configured with a parent parameter;

[0071] S21, managing parameter data in the business process form data through a relational database, wherein the parameter data supports a tree structure, and each parameter data can be configured with a parent parameter;

[0072] S22, caching parameter data in the business process form data through a cache database, and automatically synchronizing the changed parameter data in the relational database to the cache database when the parameter data in the relational database changes;

[0073] S23, when a front-end parameter data query request is obtained, first searching in the cache database, and if not found, searching in the relational database.

[0074] In steps S21-S23, the form is the main interactive form of users using the ITSM operation and maintenance service platform, mainly including data / transaction input, viewing, modification, and the like. Quickly defining the form in a flexible manner is one of the core functional points of the platform.

[0075] The form engine can adopt form-render (a form rendering engine of an open source cross-component system proposed by Alibaba), and a large number of modifications are made on the basis of the existing functions to ensure that the capabilities are more suitable for the functional requirements of the operation and maintenance service process platform in the financial industry.

[0076] The data source management (such as the enumeration value of the drop-down selection) of the form component is a necessary function for customizing a complete form, and the traditional ITSM platform mainly adopts two ways of fixing the enumeration value in the form and storing the enumeration value in the database. However, there are a series of problems, as shown in Table 3:

[0077]

[0078] To this end, the embodiment configures a form form engine and a form form component supporting dynamic data source configuration, and realizes parameter data caching capability through Redis (a cache database).

[0079] Preferably, the parameter data in the business process form data supports extension attribute configuration at the same time, and multiple extension attribute parameters are configured for a parameter data. The parameter data management capability is realized through a Mysql relational database, wherein the parameter data supports a tree structure, i.e., each parameter data can be configured with a parent (PARENT) parameter. The parameter data also supports extension attribute configuration, i.e., multiple extension attribute parameters can be configured for a parameter. As shown in Figure 8 , the cache management capability is realized through Redis. When the parameter data in Mysql changes, the modified data is automatically synchronized to Reids, wherein the cache data supports effective period setting. When the parameter data needs to be queried on the front end, the back end queries the data in Reids by default, and queries the data in Mysql if the data does not exist.

[0080] As shown in Figure 9 , the form form component is bound to the parameter data type in the business process form data, and the bound parameter data type is stored in the Json description field (JSON schema) defined by the form form engine for the form form, which is used to describe the data format information of the Json type field.

[0081] When the form form is rendered, the form form component obtains the parameter data in the business process form data through the cache interface of the cache database, and renders the parameter data in the business process form data into the Form form. In this way, not only the system resource consumption is effectively reduced, but also the flexibility and scalability of the form are greatly improved.

[0082] Further, the form listener in step S2 includes a listening component, a listening condition, a triggering component, and a triggering action. The listening component is used to define which component in the form form triggers the form listener after a change; the listening condition is used to define what change condition the component to be listened to in the form form meets to trigger the form listener to monitor; the triggering component is used to define which components are changed after the component to be listened to in the form form is changed; and the triggering action is used to define what change of the component to be changed.

[0083] The change of the Form form (such as controlling a component to be displayed or hidden, or dynamically assigning a value to a component) is a capability that a complete process form cannot obtain. As shown in Figure 10As shown, when implementing form changes, the traditional ITSM platform usually uses javascript functions written in code to achieve this. Although this approach is flexible, it can lead to bloated code, difficulty in expansion, and a series of problems such as high development cost and long delivery cycle in the context of excessive personalized needs.

[0084] The new ITSM platform in this embodiment deeply extends the native "listener" function provided by the form engine. Through simple configuration, it can achieve high-level cascading between forms, for example Figure 11 As shown. Further, when the above scenarios (listening components, listening conditions, triggering components, and triggering actions) cannot meet the needs, custom javascript scripts can be written to define high-level changes of the form. Through the above methods, the form static and dynamic code is effectively decoupled, and the user can complete the setting of the form complex change by defining the listening rules for each form.

[0085] In step S3, the fault, change, and problem in the operation and maintenance service activity are all directed to one or a certain type of operation and maintenance object, which is usually composed of IT assets. As shown, Figures 11-18 In this embodiment, the management of operation and maintenance objects is realized based on CMDB. According to different operation and maintenance object attributes, the operation and maintenance objects are mainly divided into eight categories: application system, infrastructure, storage device, security device, network device, host, database, and middleware. Preferably, the classified operation and maintenance objects can be further subdivided into two levels, ensuring that each operation and maintenance service application can be directed to a specific IT resource.

[0086] Through the classification of operation and maintenance objects and the corresponding binding of the classified operation and maintenance objects and operation and maintenance operations, the management of operation and maintenance operations is realized. That is, through the CMDB resource perspective, it can be clearly traced back to which changes have occurred to the IT resources. In this way, the operation and maintenance fault can be quickly diagnosed. Changes to IT resources (such as the on and off of the host and the scalability of the storage resource) can be updated back to the CMDB in a timely manner, ensuring the accuracy of the configuration management database. Moreover, because each operation and maintenance service process indicates the corresponding operation and maintenance object (IT resource) of the operation and maintenance operation, various automated operation and maintenance means (preset operation and maintenance tool scripts) can be used to realize the automation of operation and maintenance work.

[0087] In step S4, each operation and maintenance service activity needs to be performed by specific operation and maintenance personnel. Such work has high repeatability and frequency, which leads to a great pressure on operation and maintenance professionals who are busy handling various change requests and operation and maintenance service requests every day. As shown, Figure 12As shown, in the embodiment, the automation operation and maintenance platform is linked to realize the automatic execution of operation and maintenance service work by setting the process listener. When the process is configured, the automation operation and maintenance tool box type listener and the preset operation and maintenance tool script are added, when the process is driven to the corresponding process node, the process listener automatically presets the operation and maintenance tool script with the data in the business process form and the form, and drives the corresponding operation and maintenance tool script to the operation and maintenance object corresponding to the operation and maintenance operation, and automatically executes the operation and maintenance operation.

[0088] As shown, Figure 13 Based on the new generation ITSM platform constructed in the embodiment, the three core operation and maintenance processes of problem, change and event are constructed based on ITIL and ISO20000 international standards. The new generation ITSM platform externally carries the main work of customer fault reporting and member service demand response. Internally, a professional operation model of change, event, problem, data use management and report is established, and the process is guided, the customer service is centered, the process, personnel and technology are integrated, the effective scientific management is carried out, and the standardization of IT service is realized.

[0089] The application realizes the form form action monitoring based on the preset form form listener, classifies the operation and maintenance objects, and correspondingly binds the classified operation and maintenance objects and the operation and maintenance operation to realize the management of the operation and maintenance operation, when the operation and maintenance process is driven to the process node, the process listener automatically transmits the data in the business process form and the form to the preset operation and maintenance tool script, and drives the corresponding preset operation and maintenance tool script to the operation and maintenance object corresponding to the operation and maintenance operation, and automatically executes the operation and maintenance operation, effectively solves the problem of low operation and maintenance management efficiency caused by the prior art, and effectively improves the efficiency of the operation and maintenance service management of the financial institution.

[0090] In the technical scheme of the application, the business process form data includes not only the Json type field and the virtual column field, but also the varchar type field, the virtual column field is used for storing the Json type field with the query frequency greater than the second preset frequency threshold, and through the Json type field, the virtual column field and the varchar type field, the flexibility and scalability of the operation and maintenance service management are guaranteed, and the performance requirement and the statistical analysis requirement are met to the greatest extent.

[0091] In the technical scheme of the present application, the form form component is bound with the parameter data type in the business process form data, the bound parameter data type is stored in the Json description field defined by the form form engine for the form form, the Json description field is used for describing the data format information of the Json type field, and when the form form is rendered, the form form component obtains the parameter data in the business process form data through the cache interface of the cache database, and renders the parameter data in the business process form data into the form form, thereby effectively reducing the system resource consumption and greatly improving the flexibility and scalability of the form.

[0092] In the technical scheme of the present application, the form listener includes a listening component, a listening condition, a triggering component and a triggering action, the listening component is used for defining which component in the form form triggers the form listener after a change, the listening condition is used for defining what change condition the component to be listened to in the form form meets, so as to trigger the form listener to monitor, the triggering component is used for defining what linkage change of which component in the form form will be caused after the change of the component to be listened to, and the triggering action is used for defining what change of the linked component in the form form occurs, so that the linkage between the form components in the form form can be realized by dividing the form listener, and the user can complete the setting of the complex change of the form by defining the listening rule for each form.

[0093] Embodiment two

[0094] As shown in Figure 19 The present application also provides a financial institution operation and maintenance service automation management system, which comprises:

[0095] The establishing module 101 establishes the business process form data of the operation and maintenance service management based on a relational database, and the business process form data at least includes a Json type field and a virtual column field, the Json type field is used for storing the form item data in the business process form data which has a change frequency greater than a first preset frequency threshold, and the virtual column field is used for storing the Json type field which has a query frequency greater than a second preset frequency threshold;

[0096] The configuration module 102 configures the form form engine and the form form component supporting dynamic data source configuration, realizes the cache and query management of the parameter data through the cache database and the relational data, and realizes the form form action monitoring based on the pre-set form form listener.

[0097] The classification module 103 classifies the operation and maintenance objects based on different operation and maintenance object attributes, and binds the classified operation and maintenance objects with operation and maintenance operations, thereby realizing management of the operation and maintenance operations.

[0098] The setting module 104 automatically transmits the business process form and data in the form to a preset operation and maintenance tool script when the operation and maintenance process drives to a process node, and drives the corresponding preset operation and maintenance tool script to automatically execute operation and maintenance operations on operation and maintenance objects corresponding to the operation and maintenance operations.

[0099] The application realizes form action monitoring based on a preset form listener, classifies operation and maintenance objects, and binds the classified operation and maintenance objects with operation and maintenance operations, thereby realizing management of the operation and maintenance operations; when the operation and maintenance process drives to a process node, the process listener automatically transmits the business process form and data in the form to a preset operation and maintenance tool script, and drives the corresponding preset operation and maintenance tool script to automatically execute operation and maintenance operations on operation and maintenance objects corresponding to the operation and maintenance operations, thereby effectively solving the problem of low operation and maintenance management efficiency caused by the prior art and effectively improving the efficiency of operation and maintenance service management of financial institutions.

[0100] In the technical scheme of the application, the business process form data includes not only Json type fields and virtual column fields, but also varchar type fields; the virtual column fields are used to store Json type fields with a query frequency greater than a second preset frequency threshold; through the Json type fields, the virtual column fields and the varchar type fields, the flexibility and scalability of operation and maintenance service management are ensured, and the performance requirements and statistical analysis requirements are met to the greatest extent.

[0101] In the technical scheme of the application, form components are bound with parameter data types in business process form data, the bound parameter data types are stored in a Json description field defined by a form engine for a form, the Json description field is used to describe data format information of the Json type field, and when the form is rendered, the form components acquire parameter data in the business process form data through a cache interface of a cache database and render the parameter data in the business process form data into the form, thereby effectively reducing system resource consumption and greatly improving the flexibility and scalability of the form.

[0102] The form listener in the technical scheme of the present application comprises a listening component, a listening condition, a triggering component and a triggering action, the listening component is used to define which component in the form is triggered after the change to trigger the form listener, the listening condition is used to define what kind of change condition of the component to be listened to in the form is met to trigger the form listener to monitor, the triggering component is used to define what kind of linkage change of some components is caused after the change of the component to be listened to in the form, and the triggering action is used to define what kind of change of the linked component occurs, by dividing the form listener, linkage between the form components in the form can be realized, and the user can complete the setting of the complex change of the form by defining the listening rule for each form.

[0103] Although the specific embodiments of the present application are described above in combination with the drawings, the description is not a limitation on the protection scope of the present application, and those skilled in the art should understand that various modifications or changes made by those skilled in the art on the basis of the technical scheme of the present application without creative labor are still within the protection scope of the present application.

Claims

1. A financial institution operation and maintenance service automation management method, characterized by, The application comprises the following steps: Based on a relational database, a business process form data of operation and maintenance service management is established, which at least includes a Json type field, a virtual column field and a varchar type field. The Json type field is used to store form item data in the business process form data which has a change frequency greater than a first preset frequency threshold. The virtual column field is used to store the Json type field which has a query frequency greater than a second preset frequency threshold. The varchar type field is used to store form item data in the business process form data which does not change. A form engine and a form component supporting dynamic data source configuration are configured, and the parameter data is cached and queried by a cache database and a relational database. Specifically, the parameter data in the business process form data is managed by the relational database, and the parameter data supports a tree structure, and each parameter data can be configured with a parent parameter. The parameter data in the business process form data is cached by the cache database, and when the parameter data in the relational database changes, the changed parameter data is automatically synchronized to the cache database. When a front-end parameter data query request is obtained, the cache database is first searched, and if the parameter data is not found, the relational database is searched. Based on a pre-set form listener, form action monitoring is realized. The form listener includes a listening component, a listening condition, a triggering component and a triggering action. The listening component is used to define which component in the form is changed to trigger the form listener. The listening condition is used to define what change condition the component to be listened to in the form meets to trigger the form listener for monitoring. The triggering component is used to define which components are changed after the component to be listened to in the form is changed. The triggering action is used to define what change of the component to be linked occurs. Based on different attributes of operation and maintenance objects, the operation and maintenance objects are classified, and the classified operation and maintenance objects are correspondingly bound with operation and maintenance operations to realize the management of operation and maintenance operations. A process listener is set, and when the operation and maintenance process is driven to a process node, the process listener automatically transmits the data in the business process form and the form to a preset operation and maintenance tool script, and drives the corresponding preset operation and maintenance tool script to automatically execute the operation and maintenance operation on the operation and maintenance object corresponding to the operation and maintenance operation.

2. The financial institution operation service automation management method of claim 1, wherein, The parameter data in the business process form data supports extension attribute configuration, and multiple extension attribute parameters are configured for a parameter data.

3. The financial institution operation service automation management method of claim 1, wherein, The form component is bound with the parameter data type in the business process form data, and the bound parameter data type is stored in a Json description field defined by the form engine for the form. The Json description field is used to describe the data format information of the Json type field.

4. The financial institution operation service automation management method of claim 3, wherein the step of automatically generating the operation service automation management plan is performed by the operation service automation management system. When rendering the form form, the form form component obtains the parameter data in the business process form data through the cache interface of the cache database, and renders the parameter data in the business process form data into the Form form.

5. The financial institution operation service automation management method of claim 1, wherein, The classified operation and maintenance objects include application systems, infrastructures, storage devices, security devices, network devices, hosts, databases, and middleware.

6. The financial institution operation service automation management method of claim 5, wherein, The classified operation and maintenance objects support multi-level classification.

7. A financial institution operation and maintenance service automation management system, characterized by, Comprise: The establishment module establishes the business process form data of the operation and maintenance service management based on a relational database, and the business process form data at least includes a Json type field, a virtual column field, and a varchar type field. The Json type field is used to store form item data in the business process form data that has a change frequency greater than a first preset frequency threshold. The virtual column field is used to store the Json type field that has a query frequency greater than a second preset frequency threshold. The varchar type field is used to store form item data in the business process form data that does not change. The configuration module configures a form form engine and a form form component supporting dynamic data source configuration, and realizes parameter data caching and query management through a cache database and a relational database. Specifically, the parameter data in the business process form data is managed through the relational database, and the parameter data supports a tree structure, and each parameter data can be configured with a parent parameter. The cache database is used to realize caching of the parameter data in the business process form data, and when the parameter data in the relational database changes, the changed parameter data is automatically synchronized to the cache database. When a front-end parameter data query request is obtained, the cache database is first queried, and if the parameter data is not found, the relational database is queried. Based on a pre-set form form listener, form form action monitoring is realized. The form listener includes a listening component, a listening condition, a triggering component, and a triggering action. The listening component is used to define which component in the form form triggers the form listener after a change. The listening condition is used to define what change condition the component to be listened to in the form form meets to trigger the form listener for monitoring. The triggering component is used to define which components are linked and changed after the component to be listened to in the form form changes. The triggering action is used to define what change of the linked component. The classification module classifies the operation and maintenance objects based on different operation and maintenance object attributes, and binds the classified operation and maintenance objects with operation and maintenance operations to realize operation and maintenance operation management. The setting module automatically transmits data in the business process form and the form form to a preset operation and maintenance tool script through a process listener when the operation and maintenance process drives to a process node, and drives the corresponding preset operation and maintenance tool script to automatically execute operation and maintenance operations on the operation and maintenance objects corresponding to the operation and maintenance operations.

Images