CN114418554A - Method, system, computer device and medium for managing rules in various business systems - Google Patents

Method, system, computer device and medium for managing rules in various business systems Download PDF

Info

Publication number
CN114418554A
CN114418554A CN202210249995.XA CN202210249995A CN114418554A CN 114418554 A CN114418554 A CN 114418554A CN 202210249995 A CN202210249995 A CN 202210249995A CN 114418554 A CN114418554 A CN 114418554A
Authority
CN
China
Prior art keywords
rule
execution
management platform
rule management
state
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210249995.XA
Other languages
Chinese (zh)
Inventor
闫峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Taiping Financial Technology Services Shanghai Co Ltd Shenzhen Branch
Original Assignee
Taiping Financial Technology Services Shanghai Co Ltd Shenzhen Branch
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Taiping Financial Technology Services Shanghai Co Ltd Shenzhen Branch filed Critical Taiping Financial Technology Services Shanghai Co Ltd Shenzhen Branch
Priority to CN202210249995.XA priority Critical patent/CN114418554A/en
Publication of CN114418554A publication Critical patent/CN114418554A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/103Workflow collaboration or project management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2455Query execution
    • G06F16/24564Applying rules; Deductive queries
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25Integrating or interfacing systems involving database management systems
    • G06F16/252Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Computational Linguistics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The present application relates to a method, system, computer device and medium for rule management in various business systems. The method comprises the following steps: the rule management platform receives a rule management instruction, and the rule management instruction carries a rule identifier; the rule management platform inquires the rule state of a corresponding rule in each service system according to the rule identification, and the rule, the execution flow of the rule and the execution result of the rule are stored in the service systems; and the rule management platform manages the rule state according to the rule management instruction. By adopting the method, the repeated workload of each business system is reduced by uniformly managing the rules scattered in each business system, the rules in each business system, the execution flow of the rules and the execution results of the rules are still stored in each business system, the repeated workload of each business system is reduced, the rule management platform cannot become the bottleneck of rule execution, and the execution pressure of the rule management platform is reduced.

Description

Method, system, computer device and medium for managing rules in various business systems
Technical Field
The present application relates to the field of research and development technologies, and in particular, to a method, a system, a computer device, and a medium for rule management in various business systems.
Background
With the rapid development of services, the number of systems and the distribution frequency are increasing. In order to prevent the possible risks of each system, each application system develops various bibliographic rules aiming at how to prevent the data risks so as to prevent the occurrence of the business risks.
However, the rules are scattered in each business system, and each business system needs to manage, control, and the like the same rule, so that the user needs to repeat the above management and control process, and the rule management efficiency is reduced.
Disclosure of Invention
In view of the above, it is desirable to provide a rule management method, system, computer device, and medium in each business system, which can reduce the workload of repetition of each business system and improve the efficiency of rule management.
A method of rule management in business systems, the method comprising:
a rule management platform receives a rule management instruction, wherein the rule management instruction carries a rule identifier;
the rule management platform inquires the rule state of a corresponding rule in each service system according to the rule identification, and the rule, the execution flow of the rule and the execution result of the rule are stored in the service systems;
and the rule management platform manages the rule state according to the rule management instruction.
In one embodiment, before the rule management platform queries the rule state of the corresponding rule in each service system according to the rule identifier, the method further includes:
the rule management platform acquires a standard interface;
the rule management platform carries out interface standardization on the rules in each business system according to the standard interface so as to enable the execution results of the rules in each business system to be stored to a target position according to the target format of the standard interface;
the rule management platform manages the rule state according to the rule management instruction, and the method comprises the following steps:
and the rule management platform acquires the rule execution result in each service system according to the rule management instruction.
In one embodiment, the rule management platform manages the rule state according to the rule management instruction, including:
the rule management platform sets at least one of the type, the execution state and the notification rule of the rule in each business system, wherein the type of the rule comprises blocking and non-blocking, and the execution state comprises a valid state and an invalid state.
In one embodiment, the rule state is used for instructing each business system to execute a rule; the rule execution includes:
the business system judges whether the rule is valid;
and when the rule is valid, the business system executes the rule to obtain a rule execution result, converts the execution result into a target format and stores the target format to a target position.
In one embodiment, the method further comprises:
when the execution result is that the execution fails, the service system judges whether the type of the rule is a blocking type;
and when the type of the rule is a blocking type, the service system outputs an abnormal result, converts the abnormal result into a target format and stores the target format to a target position.
In one embodiment, the method further comprises:
when the execution result is execution failure, the service system acquires a notification rule of a preset rule state;
and the service system sends the execution result to a corresponding terminal according to the notification rule.
A rule management system in each service system comprises a rule management platform and each service system;
the rule management platform is used for receiving a rule management instruction, and the rule management instruction carries a rule identifier; inquiring the rule state of a corresponding rule in each business system according to the rule identification, wherein the rule, the execution flow of the rule and the execution result of the rule are stored in the business systems; and managing the rule state according to the rule management instruction.
In one embodiment, the rule management platform is further configured to obtain a standard interface before querying a rule state of a corresponding rule in each service system according to the rule identifier; interface standardization is carried out on the rules in each business system according to the standard interface, so that the execution result of the rules in each business system is stored to a target position according to the target format of the standard interface;
and the rule management platform is used for acquiring a rule execution result in each service system according to the rule management instruction.
A computer device comprising a memory storing a computer program and a processor implementing the steps of the method described above when executing the computer program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method.
According to the rule management method, the rule management system, the computer equipment and the medium in each business system, the repeated workload of each business system is reduced by uniformly managing the rules scattered in each business system, the rules in each business system, the execution flows of the rules and the execution results of the rules are still stored in each business system, the repeated workload of each business system is reduced, the rule management platform cannot become a bottleneck of rule execution, and the execution pressure of the rule management platform is reduced.
Drawings
FIG. 1 is a block diagram that illustrates a rule management system in the business systems, according to an embodiment;
FIG. 2 is a flow diagram that illustrates a method for rule management in various business systems, according to an embodiment;
FIG. 3 is a flow diagram that illustrates the processing performed in the business systems, according to one embodiment;
FIG. 4 is an interface diagram of rule state management in one embodiment;
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The rule management method in each business system provided by the application can be applied to the rule management system in each business system shown in fig. 1. The rule management platform 102 communicates with the service systems 104 through a network, wherein the rule management platform 102 receives a rule management instruction, the rule management instruction carries a rule identifier, the rule management platform 102 queries a rule state of a corresponding rule in each service system 104 according to the rule identifier, the rule, an execution flow of the rule and an execution result of the rule are stored in the service systems 104, and the rule management platform manages the rule state according to the rule management instruction. Therefore, the rules scattered in each business system are managed in a unified manner, repeated workload of each business system is reduced, the rules in each business system, the execution flow of the rules and the execution results of the rules are still stored in each business system, the repeated workload of each business system is reduced, the rule management platform cannot become a bottleneck of rule execution, and the execution pressure of the rule management platform is reduced. The rule management platform 102 and the business system 104 may be implemented by separate servers or a server cluster composed of a plurality of servers.
In an embodiment, as shown in fig. 2, a method for managing rules in business systems is provided, which is described by taking the method as an example of being applied to the rule management system in the business systems shown in fig. 1, and includes the following steps:
s202: and the rule management platform receives a rule management instruction, and the rule management instruction carries a rule identifier.
In particular, the rule management instructions are triggered by a user according to a rule management platform, which may include at least one of rule definition, query of rule execution results, rule suspension, rule enablement, and rule subscription. And uniformly managing the rules scattered in each business system through a rule management platform. In order to reduce the complexity of system change, in this embodiment, only a uniform rule interface is issued to each business system, so that each business system standardizes the output of the rule in each system, that is, the output is stored in a predetermined format at a corresponding position of the business system. The storage, execution and output of the execution result of the rule are all performed in each business system, but not in the rule management platform, that is, the storage, execution and output of the execution result of the original rules of each business system are not changed, and only at least one of rule definition, rule execution result query, rule pause, rule start and rule subscription is performed in the unified rule management platform, so that the data processing bottleneck of the rule management platform is avoided, and the reconstruction of each business system is reduced.
A rule identification is an identification that can uniquely determine a rule, for example it may be a rule name. The rule name can be a standard name, and the rule name scattered in each service system can be a non-standard name, so that the rule management platform can also store the corresponding relation between the standard name and the non-standard name, and when receiving a rule management instruction, the rule management platform determines the rule identifier in the corresponding service system according to the corresponding relation, and then sends the rule identifier to the corresponding service system, so that each service system can inquire the corresponding rule according to the processed rule identifier sent by the rule management platform.
Optionally, in other embodiments, one rule management instruction may carry multiple rule identifiers, and the query of multiple rule identifiers may be a parallel query.
S204: and the rule management platform inquires the rule state of the corresponding rule in each service system according to the rule identifier, and the rule, the execution flow of the rule and the execution result of the rule are stored in the service systems.
Specifically, the rule management platform sends the rule identifier to a corresponding service system, the service system inquires whether a corresponding rule exists locally, if so, the rule state is acquired, and the acquired rule state is returned to the rule management platform.
The rule state includes, but is not limited to, an execution result of the rule, a start of the rule, a pause of the rule, a subscription state of the rule, and the like. The specific content of the rule is stored in the business system, and the execution flow of the rule is namely the starting of the rule, the pausing of the rule, the subscription state of the rule and the like.
If the rule management platform needs to inquire the information, the rule management platform acquires the corresponding rule state from each service system and then checks and manages the rule state.
That is, the rules are displayed and managed through an independent rule management platform, but the rules are not stored in the rule management platform, database connection information of each business system is managed in the rule management platform, and execution records of the rules in the associated business systems are directly accessed through configured database connection in a multi-data-source mode.
S206: and the rule management platform manages the rule state according to the rule management instruction.
Specifically, the management of the rule includes, but is not limited to, redefinition of the rule, query of an execution result of the rule, suspension of the rule, enablement of the rule, subscription of the rule, and the like.
The rule management platform can acquire the rule states fed back by each service system and classify the rule states according to the rule identifications, namely when a plurality of rule identifications exist, the rule states are classified according to the rule identifications. After the classification is completed, the rule management platform may further perform classification management on the rule states in each rule according to the rule management instruction, for example, perform classification according to a service system, or perform classification according to the rule states, where the further classification is performed with the convenience of subsequent rule management as a target, and a user may set a classification mode of the rule states as needed to obtain statistical data required by the user.
According to the rule management method in each business system, the rules scattered in each business system are managed in a unified mode, repeated workload of each business system is reduced, the rules in each business system, the execution flow of the rules and the execution results of the rules are still stored in each business system, repeated workload of each business system is reduced, the rule management platform cannot become a bottleneck of rule execution, and execution pressure of the rule management platform is reduced.
In one embodiment, before the rule management platform queries the rule state of the corresponding rule in each service system according to the rule identifier, the method further includes: the rule management platform acquires a standard interface; the rule management platform carries out interface standardization on the rules in each business system according to the standard interface so as to enable the execution results of the rules in each business system to be stored to a target position according to the target format of the standard interface; the rule management platform manages the rule state according to the rule management instruction, and the rule management platform comprises the following steps: and the rule management platform acquires the rule execution result in each service system according to the rule management instruction.
Specifically, in this embodiment, a process of modifying a rule interface of each service system by the rule management platform is provided, where in order to implement unified management of rules in each service system by the rule management platform, the rule management platform formulates a unified standard interface, and after each service system is docked to the rule management platform, the rule management platform issues the standard interface to each service system, and each service system converts the rule interface of the rule stored in the rule management platform according to the standard interface, so as to quickly access the rule management platform.
In practical applications, the rules in each business system include a database rule and a java rule, and in order to fully understand the transformation of the rule interface of each business system in the present application, the following description will be made with the database rule and the java rule, respectively. Firstly, a uniform processing mode is explained, when a rule management platform receives an access request of a new service system, a standard interface is sent to the service system, when the service system receives the standard interface, after each rule is executed, the execution result of the rule is input to the standard interface, and therefore the format and the storage position of the rule execution result are unified by the standard interface.
The standardized implementation of the database rule needs to be uniformly written according to a procedure _ name (p _ IN anydata, p _ OUT IN OUT dfr _ rule _ o _ t) format, wherein p _ IN is an oracle arbitrary format type, a developer can input an arbitrary type of parameter, the rule execution result is converted into a corresponding format when the rule is implemented, the p _ OUT is provided with an agreed type by a rule management platform, the developer writes the rule execution result into a p _ OUT variable when the rule is implemented, and specifically:
Figure 178573DEST_PATH_IMAGE002
take java rule as an example: writing a rule, and realizing an interface DfrRulout iFdrrule (in Object, conn), wherein in is any java format type, a developer can transmit any type of parameters, and an execution result of the rule is converted into a corresponding format when the rule is realized; the returned value DfrRuleout is provided with an agreed type by the rule management platform, and a developer writes a rule execution result into an out variable when executing the rule, specifically:
Figure 445738DEST_PATH_IMAGE004
in the above embodiment, a standardized manner of the regular interfaces of each service platform is given.
Therefore, when the rule management platform acquires the rule execution result in each service system according to the rule management instruction, the execution result in the corresponding format can be directly read from the corresponding position according to the standard interface.
In one embodiment, the rule management platform manages the rule state according to the rule management instruction, including: the rule management platform sets at least one of the type, the execution state and the notification rule of the rule in each business system, wherein the type of the rule comprises blocking and non-blocking, and the execution state comprises a valid state and an invalid state.
Specifically, in this embodiment, the rule management platform may provide a uniform interface for each service system, so that the functions of rule execution check, log recording, notification alarm, and the like may be implemented.
The rule management platform provides a client package realized by API, the client package is deployed in each business system, the business systems call the bottom-of-pocket rule through the client package, and the client executes the flow execution rule according to the rule, thereby reducing the repeated workload of each business system and unifying the rule execution, the log record and the alarm notification. The client package supports conventional versions such as a database, java and the like, reads a regular real implementation program through mechanisms such as database dynamic sql, java reflection and the like, and dynamically executes the program.
It should be noted that the client program performs the following operations: controlling the rule execution flow, recording the rule execution log and triggering the alarm notification. Therefore, each business system only needs to realize the specific business logic of the rule, and does not need to realize the functions of rule management, rule execution control, rule execution failure notification, personnel configuration notification and the like. The part of work is a common part of each business system and is realized by the rule management platform, so that the repeated work of each business system can be reduced.
Because the rule management platform can be accessed to a plurality of service systems, in order to avoid the rule management platform becoming the bottleneck of rule execution, the rule management platform does not record data, but records the data by each service system; the rule management platform does not execute the rules itself, but executes the rules in the respective business systems. To achieve this goal, the following is required: and deploying a client program for controlling rule execution in each business system by using database scripts of rule definition, rule log execution, rule subscription configuration and the like related to each business system deployment platform.
The deployment mode of the client may include: the method comprises three steps of creating a data user, initializing a client script and deploying a main user program.
The data creating user mainly aims to protect the main application, namely the rule management platform only manages relevant information such as rules, notification groups, rule execution logs and the like, and cannot access other information except the main application.
The initialization client side script is mainly used for logging in a default _ rule and comprises the following steps: modify the household name in the authorization script and execute the corresponding statement, e.g.,/client/default _ rule/create _ schema _ default _ rule.
The deployment of the main user program is to log in the main user: executing CLIENT/EXEC _ CLIENT _ aql.sql, creating synonyms for tables and sequences authorized by the depender _ rule user, executing EXEC _ CLIENT _ frame _ plsql.sql, installing a scheduling rules program. And finally deploying the java jar package, and introducing the java jar package into the dfr.
In one embodiment, referring to fig. 3, fig. 3 is a flowchart illustrating a process performed by a client of a business system in one embodiment, where a rule status is used to instruct each business system to perform rule execution; the rule execution includes: the business system judges whether the rule is valid; and when the rule is effective, the business system executes the rule to obtain a rule execution result, converts the execution result into a target format and stores the target format to a target position.
In one embodiment, the method for rule management in each service system further includes: when the execution result is that the execution fails, the service system judges whether the type of the rule is a blocking type; and when the type of the rule is a blocking type, the service system outputs an abnormal result, converts the abnormal result into a target format and stores the target format to a target position.
Specifically, the rule management platform sets types of rules such as blocking, non-blocking, notification and the like and sets valid and invalid rule states for each bottom-of-pocket rule. Through the rule management platform, the types and the states of the rules can be dynamically adjusted, and the rules can be applied to each business system in real time, so that the bottom-pocket rules can be started and stopped, blocking and non-blocking types are set, and the abnormal functions of the business systems caused by abnormal rule execution are avoided. As shown in particular in connection with fig. 4.
In one embodiment, the method for rule management in each service system further includes: when the execution result is execution failure, the service system acquires a notification rule of a preset rule state; and the service system sends the execution result to the corresponding terminal according to the notification rule.
Specifically, the rule management platform provides a notification group management function, the notification group is used for carrying out classification management on rules, personnel who join the notification group can receive notifications such as mails, short messages and WeChat in real time according to configuration when the bottom-of-pocket rule is executed, and timely intervention processing is carried out aiming at abnormal bottom-of-pocket.
Specifically, the processing of the service system is described in detail with reference to fig. 3, where the service system first determines whether the rule is valid, if not, the process is directly ended, and if so, determines whether the rule uses the current product, if so, performs rule verification, and determines whether the rule passes the verification, if so, determines whether only the failure log is recorded, if so, the process is ended, otherwise, the verification log is recorded, that is, the rule execution result.
If the verification fails, three types of processing can be performed in parallel, the first is to perform log recording, namely recording the rule execution result, the second is to acquire a notification personnel list and send a mail or other modes to notify corresponding personnel, and the third is to judge whether the rule is of a blocking type, if so, output an exception, otherwise, directly ending.
According to the rule management method in each business system, the rules scattered in each business system are managed in a unified mode, repeated workload of each business system is reduced, the rules in each business system, the execution flow of the rules and the execution results of the rules are still stored in each business system, repeated workload of each business system is reduced, the rule management platform cannot become a bottleneck of rule execution, and execution pressure of the rule management platform is reduced.
For the convenience of fully understanding the technical scheme by those skilled in the art, the following two examples are used for illustration:
in one embodiment, the system development and operation and maintenance personnel conduct the act of fund stealing. For example, the operation and maintenance personnel change the payment account information and steal illegal funds. Aiming at the fund loss caused by the falsification of the key data, in the application, the business system can develop a bankbook rule and detect whether the payment account and the payment amount are modified or not. The bankbook rule can be set as a blocking rule in the bankbook configuration platform, and when an operation and maintenance person or a program tries to modify a payment account and a payment amount, the bankbook rule throws an exception to prevent data from being modified. And the person who subscribes the rule is informed by mails and short messages, and the risk is dealt with in time. If the data modification is finally confirmed by the service and is normal modification, the rule manager can temporarily set the rule as non-blocking on the bottom-of-pocket configuration management platform to allow the data to be modified. The program or operation and maintenance personnel can normally modify the data, but the bottom-pocketed rule platform still sends mails, short message notification mails and short message notification to the personnel subscribing the rule. Therefore, the bottom-pocket rule can be dynamically configured, so that serious risks can be prevented, and the influence on the business is minimized.
In another embodiment, a large company, which typically includes many business systems related to the exchange of funds, often has difficulty in the overall view of the managers in controlling the risk of critical funds and whether to control them effectively. Thus, companies can develop specialized risk control schemes and require systems to implement agreed upon rules of the underlying, e.g., control payment accounts, payment amounts. And each system respectively realizes the bottom-pocket rule and is configured on a bottom-pocket configuration platform. Company managers can check which systems realize the bottom-finding rule on line and which systems do not practice the bottom-finding rule; which systems touched the rule, whether the actual impact was produced. Therefore, the business risk of the company can be visually managed, and an effective management means is provided for managers.
It should be understood that although the steps in the flowcharts of fig. 2 and 3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2 and 3 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 1, there is provided a rule management system in business systems, including: a rule management platform and a business system.
The rule management platform receives a rule management instruction, and the rule management instruction carries a rule identifier;
the rule management platform inquires the rule state of the corresponding rule in each service system according to the rule identifier, and the rule, the execution flow of the rule and the execution result of the rule are stored in the service systems;
and the rule management platform manages the rule state according to the rule management instruction.
In one embodiment, before the rule management platform queries the rule state of the corresponding rule in each service system according to the rule identifier, the method further includes:
the rule management platform acquires a standard interface;
the rule management platform carries out interface standardization on the rules in each business system according to the standard interface so as to enable the execution results of the rules in each business system to be stored to a target position according to the target format of the standard interface;
the rule management platform manages the rule state according to the rule management instruction, and the rule management platform comprises the following steps:
and the rule management platform acquires the rule execution result in each service system according to the rule management instruction.
In one embodiment, the rule management platform manages the rule state according to the rule management instruction, including:
the rule management platform sets at least one of the type, the execution state and the notification rule of the rule in each business system, wherein the type of the rule comprises blocking and non-blocking, and the execution state comprises a valid state and an invalid state.
In one embodiment, the rule state is used to instruct each business system to perform rule execution; the rule execution includes:
the business system judges whether the rule is valid;
and when the rule is effective, the business system executes the rule to obtain a rule execution result, converts the execution result into a target format and stores the target format to a target position.
In one embodiment, the method further comprises:
when the execution result is that the execution fails, the service system judges whether the type of the rule is a blocking type;
and when the type of the rule is a blocking type, the service system outputs an abnormal result, converts the abnormal result into a target format and stores the target format to a target position.
In one embodiment, the method further comprises:
when the execution result is execution failure, the service system acquires a notification rule of a preset rule state;
and the service system sends the execution result to the corresponding terminal according to the notification rule.
For specific limitations of the rule management system in each business system, reference may be made to the above limitations of the rule management method in each business system, which are not described herein again. All or part of each module in the rule management system in each business system can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing rules, rule execution results and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of rule management in business systems.
Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program: the rule management platform receives a rule management instruction, and the rule management instruction carries a rule identifier; the rule management platform inquires the rule state of the corresponding rule in each service system according to the rule identifier, and the rule, the execution flow of the rule and the execution result of the rule are stored in the service systems; and the rule management platform manages the rule state according to the rule management instruction.
In one embodiment, before the rule management platform implemented when the processor executes the computer program queries the rule state of the corresponding rule in each business system according to the rule identifier, the method further includes: the rule management platform acquires a standard interface; the rule management platform carries out interface standardization on the rules in each business system according to the standard interface so as to enable the execution results of the rules in each business system to be stored to a target position according to the target format of the standard interface; the rule management platform implemented when the processor executes the computer program manages the rule state according to the rule management instruction, and comprises: and the rule management platform acquires the rule execution result in each service system according to the rule management instruction.
In one embodiment, a rule management platform implemented by a processor executing a computer program manages rule states according to rule management instructions, comprising: the rule management platform sets at least one of the type, the execution state and the notification rule of the rule in each business system, wherein the type of the rule comprises blocking and non-blocking, and the execution state comprises a valid state and an invalid state.
In one embodiment, the rule states implemented by the processor when executing the computer program are used to instruct the respective business system to perform the rule execution; the rule execution includes: the business system judges whether the rule is valid; and when the rule is effective, the business system executes the rule to obtain a rule execution result, converts the execution result into a target format and stores the target format to a target position.
In one embodiment, the processor, when executing the computer program, further performs the steps of: when the execution result is that the execution fails, the service system judges whether the type of the rule is a blocking type; and when the type of the rule is a blocking type, the service system outputs an abnormal result, converts the abnormal result into a target format and stores the target format to a target position.
In one embodiment, the processor, when executing the computer program, further performs the steps of: when the execution result is execution failure, the service system acquires a notification rule of a preset rule state; and the service system sends the execution result to the corresponding terminal according to the notification rule.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: the rule management platform receives a rule management instruction, and the rule management instruction carries a rule identifier; the rule management platform inquires the rule state of the corresponding rule in each service system according to the rule identifier, and the rule, the execution flow of the rule and the execution result of the rule are stored in the service systems; and the rule management platform manages the rule state according to the rule management instruction.
In one embodiment, before the rule management platform implemented when the processor executes the computer program queries the rule state of the corresponding rule in each business system according to the rule identifier, the method further includes: the rule management platform acquires a standard interface; the rule management platform carries out interface standardization on the rules in each business system according to the standard interface so as to enable the execution results of the rules in each business system to be stored to a target position according to the target format of the standard interface; the rule management platform implemented when the processor executes the computer program manages the rule state according to the rule management instruction, and comprises: and the rule management platform acquires the rule execution result in each service system according to the rule management instruction.
In one embodiment, a rule management platform implemented by a computer program when executed by a processor manages rule states according to rule management instructions, comprising: the rule management platform sets at least one of the type, the execution state and the notification rule of the rule in each business system, wherein the type of the rule comprises blocking and non-blocking, and the execution state comprises a valid state and an invalid state.
In one embodiment, the rule states implemented by the computer program when executed by the processor are used to instruct the respective business system to perform the rule execution; the rule execution includes: the business system judges whether the rule is valid; and when the rule is effective, the business system executes the rule to obtain a rule execution result, converts the execution result into a target format and stores the target format to a target position.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the execution result is that the execution fails, the service system judges whether the type of the rule is a blocking type; and when the type of the rule is a blocking type, the service system outputs an abnormal result, converts the abnormal result into a target format and stores the target format to a target position.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the execution result is execution failure, the service system acquires a notification rule of a preset rule state; and the service system sends the execution result to the corresponding terminal according to the notification rule.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A method for rule management in business systems, the method comprising:
a rule management platform receives a rule management instruction, wherein the rule management instruction carries a rule identifier;
the rule management platform inquires the rule state of a corresponding rule in each service system according to the rule identification, and the rule, the execution flow of the rule and the execution result of the rule are stored in the service systems;
and the rule management platform manages the rule state according to the rule management instruction.
2. The method according to claim 1, wherein before the rule management platform queries the rule state of the corresponding rule in each service system according to the rule identifier, the method further comprises:
the rule management platform acquires a standard interface;
the rule management platform carries out interface standardization on the rules in each business system according to the standard interface so as to enable the execution results of the rules in each business system to be stored to a target position according to the target format of the standard interface;
the rule management platform manages the rule state according to the rule management instruction, and the method comprises the following steps:
and the rule management platform acquires the rule execution result in each service system according to the rule management instruction.
3. The method of claim 1, wherein the rule management platform manages the rule states according to the rule management instructions, comprising:
the rule management platform sets at least one of the type, the execution state and the notification rule of the rule in each business system, wherein the type of the rule comprises blocking and non-blocking, and the execution state comprises a valid state and an invalid state.
4. The method according to claim 2 or 3, wherein the rule status is used to instruct each business system to perform rule execution; the rule execution includes:
the business system judges whether the rule is valid;
and when the rule is valid, the business system executes the rule to obtain a rule execution result, converts the execution result into a target format and stores the target format to a target position.
5. The method of claim 4, further comprising:
when the execution result is that the execution fails, the service system judges whether the type of the rule is a blocking type;
and when the type of the rule is a blocking type, the service system outputs an abnormal result, converts the abnormal result into a target format and stores the target format to a target position.
6. The method of claim 4, further comprising:
when the execution result is execution failure, the service system acquires a notification rule of a preset rule state;
and the service system sends the execution result to a corresponding terminal according to the notification rule.
7. A rule management system in each service system is characterized in that the rule management system in each service system comprises a rule management platform and each service system;
the rule management platform is used for receiving a rule management instruction, and the rule management instruction carries a rule identifier; inquiring the rule state of a corresponding rule in each business system according to the rule identification, wherein the rule, the execution flow of the rule and the execution result of the rule are stored in the business systems; and managing the rule state according to the rule management instruction.
8. The system of claim 7, wherein the rule management platform is further configured to obtain a standard interface before querying the rule status of the corresponding rule in each service system according to the rule identifier; interface standardization is carried out on the rules in each business system according to the standard interface, so that the execution result of the rules in each business system is stored to a target position according to the target format of the standard interface;
and the rule management platform is used for acquiring a rule execution result in each service system according to the rule management instruction.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 6.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
CN202210249995.XA 2022-03-15 2022-03-15 Method, system, computer device and medium for managing rules in various business systems Pending CN114418554A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210249995.XA CN114418554A (en) 2022-03-15 2022-03-15 Method, system, computer device and medium for managing rules in various business systems

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210249995.XA CN114418554A (en) 2022-03-15 2022-03-15 Method, system, computer device and medium for managing rules in various business systems

Publications (1)

Publication Number Publication Date
CN114418554A true CN114418554A (en) 2022-04-29

Family

ID=81264534

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210249995.XA Pending CN114418554A (en) 2022-03-15 2022-03-15 Method, system, computer device and medium for managing rules in various business systems

Country Status (1)

Country Link
CN (1) CN114418554A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116522030A (en) * 2023-04-28 2023-08-01 上海任意门科技有限公司 Information processing method, apparatus and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070094199A1 (en) * 2005-08-30 2007-04-26 International Business Machines Corporation System and method for automatically processing dynamic business rules in a content management system
CN109783802A (en) * 2018-12-13 2019-05-21 平安医疗健康管理股份有限公司 A kind of business rule processing method, server and computer readable storage medium
CN111737270A (en) * 2019-11-12 2020-10-02 北京京东尚科信息技术有限公司 Data processing method and system, computer system and computer readable medium
CN112948396A (en) * 2021-03-31 2021-06-11 中国建设银行股份有限公司 Data storage method and device, electronic equipment and storage medium

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070094199A1 (en) * 2005-08-30 2007-04-26 International Business Machines Corporation System and method for automatically processing dynamic business rules in a content management system
CN109783802A (en) * 2018-12-13 2019-05-21 平安医疗健康管理股份有限公司 A kind of business rule processing method, server and computer readable storage medium
CN111737270A (en) * 2019-11-12 2020-10-02 北京京东尚科信息技术有限公司 Data processing method and system, computer system and computer readable medium
CN112948396A (en) * 2021-03-31 2021-06-11 中国建设银行股份有限公司 Data storage method and device, electronic equipment and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116522030A (en) * 2023-04-28 2023-08-01 上海任意门科技有限公司 Information processing method, apparatus and storage medium
CN116522030B (en) * 2023-04-28 2024-05-24 上海任意门科技有限公司 Information processing method, apparatus and storage medium

Similar Documents

Publication Publication Date Title
CN110647580B (en) Distributed container cluster mirror image management main node, slave node, system and method
US7653913B2 (en) Method and apparatus for creating templates
CN103559118B (en) A kind of method for auditing safely based on AOP and annotating information system
US7039948B2 (en) Service control manager security manager lookup
US20050278191A1 (en) Change audit method, apparatus and system
CN110351366B (en) Service scheduling system and method for internet application and storage medium
KR20060079078A (en) Server queuing system and method
US20170289236A1 (en) Cloud Operating System and Method
WO2019148727A1 (en) Electronic device, redis-based exception warning method and storage medium
US8819155B2 (en) System and method for performing centralized common tasks for a set of functions
US20090300760A1 (en) Grid Security Intrusion Detection Configuration Mechanism
CN113726566B (en) Service gateway device
US20200175177A1 (en) Auto-injection of security protocols
WO2020224100A1 (en) Blockchain configuration file processing apparatus, system, and method, and storage medium
US20120254416A1 (en) Mainframe Event Correlation
CN109245962A (en) Server monitoring method, system, computer equipment and storage medium
US7275250B1 (en) Method and apparatus for correlating events
CN114418554A (en) Method, system, computer device and medium for managing rules in various business systems
US20020178297A1 (en) Service control manager tool execution
CN114422197A (en) Permission access control method and system based on policy management
Chandersekaran et al. An agent based monitoring system for web services
US8161014B1 (en) System and method for user file access and tracking
CN111782481B (en) Universal data interface monitoring system and monitoring method
US10129072B1 (en) Distributed security information and event management system with application-injected remote components
US20230061701A1 (en) Cloud service framework

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20220429

RJ01 Rejection of invention patent application after publication