WO2019062132A1 - 业务规则管理方法、装置、存储介质和计算机设备 - Google Patents

业务规则管理方法、装置、存储介质和计算机设备 Download PDF

Info

Publication number
WO2019062132A1
WO2019062132A1 PCT/CN2018/086302 CN2018086302W WO2019062132A1 WO 2019062132 A1 WO2019062132 A1 WO 2019062132A1 CN 2018086302 W CN2018086302 W CN 2018086302W WO 2019062132 A1 WO2019062132 A1 WO 2019062132A1
Authority
WO
WIPO (PCT)
Prior art keywords
rule
business
business rule
service
belongs
Prior art date
Application number
PCT/CN2018/086302
Other languages
English (en)
French (fr)
Inventor
吴亮平
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019062132A1 publication Critical patent/WO2019062132A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database

Definitions

  • the present application relates to the field of computer technologies, and in particular, to a network security joint defense method, apparatus, server, and storage medium.
  • Business rules are descriptions of business definitions and constraints that are used to maintain business structure or to control and influence business behavior.
  • the basic idea of business rule technology is to extract the business logic processed by the business system from the program code, transform it into a simple business rule, represent the business behavior with structured business rule data, and describe it in a natural language. Centrally stored in the rule base.
  • Business rules are created by business people, updated and debugged in real time, and complex logical relationships between business rules are handled by the rules engine.
  • the traditional business rule management method is to import business rule data into collaborative tools such as SVN (version control system).
  • SVN version control system
  • the collaborative tool adds configuration data to the business rule data
  • the business system developer cannot directly use the collaborative tool.
  • the stored business rule data reduces the development efficiency of business rules.
  • a business rule management method, apparatus, storage medium, and computer device are provided.
  • a business rule management method including:
  • the business rule import request carries a series of business rules, a business system name to which the business rule belongs, a service system version number to which the business rule belongs, a business rule engine version number, a first business rule name, and a first business rule file. ;
  • the business rule belongs to the series, the business system name to which the business rule belongs, the business system version number to which the business rule belongs, the business rule engine version number, the first business rule name, and the first preset format
  • the first business rule data is saved to the business rule information table, and the version state of the first business rule data of the first preset format is set to a development state.
  • a business rule management device includes:
  • the business rule import request receiving module is configured to receive a business rule import request, where the business rule import request carries a series of service rules, a business system name to which the business rule belongs, a business system version number to which the business rule belongs, and a business rule engine version number, first Business rule name and first business rule file;
  • a business rule file parsing module configured to parse the first business rule file to obtain first business rule data
  • a business rule compiling module configured to compile a text format of the first business rule data into a first preset format
  • a business rule storage module configured to belong to the series of the business rule, the business system name to which the business rule belongs, the service system version number to which the business rule belongs, the business rule engine version number, the first business rule name, and
  • the first service rule data of the first preset format is saved to the service rule information table, and the version state of the first service rule data of the first preset format is set to a development state.
  • One or more non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the following steps:
  • the business rule import request carries a series of business rules, a business system name to which the business rule belongs, a service system version number to which the business rule belongs, a business rule engine version number, a first business rule name, and a first business rule file. ;
  • the business rule belongs to the series, the business system name to which the business rule belongs, the business system version number to which the business rule belongs, the business rule engine version number, the first business rule name, and the first preset format
  • the first business rule data is saved to the business rule information table, and the version state of the first business rule data of the first preset format is set to a development state.
  • a computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executable by the processor to cause the one or more processors to execute The following steps:
  • the business rule import request carries a series of business rules, a business system name to which the business rule belongs, a service system version number to which the business rule belongs, a business rule engine version number, a first business rule name, and a first business rule file. ;
  • the business rule belongs to the series, the business system name to which the business rule belongs, the business system version number to which the business rule belongs, the business rule engine version number, the first business rule name, and the first preset format
  • the first business rule data is saved to the business rule information table, and the version state of the first business rule data of the first preset format is set to a development state.
  • FIG. 1 is an application environment diagram of a business rule management method in accordance with one or more embodiments.
  • FIG. 2 is a flow chart of a method for managing a business rule in accordance with one or more embodiments
  • FIG. 3 is a flowchart of a business rule management configuration method in a business rule management method in another embodiment
  • FIG. 4 is a flowchart of a method for downloading a business rule in a business rule management method according to one or more embodiments
  • FIG. 5 is a flowchart of a business rule release management method in a business rule management method according to one or more embodiments
  • FIG. 6 is a structural block diagram of a business rule management apparatus according to one or more embodiments.
  • FIG. 7 is a diagram showing the internal structure of a computer device in accordance with one or more embodiments.
  • the business rule management method provided by the embodiment of the present application can be applied to the application environment as shown in FIG. 1 .
  • computer device 102 receives a receive service rule import request initiated by terminal 104.
  • the computer device 102 receives the receiving service rule import request initiated by the terminal 104, where the business rule import request carries the series of the business rule, the business system name to which the business rule belongs, the service system version number to which the business rule belongs, and the business rule engine version number.
  • a business rule name and a first business rule file parsing the first business rule file to obtain the first business rule data; compiling the text format of the first business rule data into the first preset format;
  • the business system name, the business system version number to which the business rule belongs, the business rule engine version number, the first business rule name, and the first business rule data of the first preset format are saved to the business rule information table, and the first preset format is set.
  • the version status of the first business rule data is the development status.
  • FIG. 2 is a schematic flowchart diagram of a data distribution method according to an embodiment of the present application. It should be understood that although the various steps in the flowchart of FIG. 2 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and may be performed in other sequences. Moreover, at least a portion of the steps in FIG. 2 may include a plurality of sub-steps or stages, which are not necessarily sequential, but may alternate or alternate with at least a portion of the other steps or other sub-steps or stages carried out.
  • the computer device may be a server, and the method includes:
  • Step 202 Receive a business rule import request, where the business rule import request carries a series of service rules, a business system name to which the business rule belongs, a business system version number to which the business rule belongs, a business rule engine version number, a first business rule name, and a first business rule. file.
  • the service rule belongs to the service type to which the business rule belongs, such as property insurance, life insurance, etc.;
  • the business system name to which the business rule belongs is the name of the business system corresponding to the business rule to be imported, such as the auto insurance automatic underwriting system;
  • the service system version number to which the business rule belongs is the version identifier of the business system corresponding to the business rule to be imported, such as EPCIS-AUTO2.2.0 (Auto insurance underwriting 2.2.0 version);
  • the business rule engine version number is the version identifier of the business rule engine , such as ENGINE 4.0.0 (Business Rule Engine version 4.0.0), where the business rules engine is a component embedded in the application that separates business decisions from the application code and uses predefined semantics.
  • the module writes the business decision;
  • the first business rule name is the name of the business rule to be imported into the rule management system, such as the batch policy audit;
  • the first business rule file is the rule file to be imported into the rule management system, and the rule file includes Three parts:
  • the first part is the dependency data of the business rules for the subsequent industry.
  • the second part is to provide a rule base for the description of business rules in Chinese. It is used for page display of business rules and editing of business rules.
  • the third part is business rule data.
  • the format of the rule file is not limited.
  • the compressed package format including the foregoing three parts such as a ZIP package, a RAR package, or a file compression package of other compressed formats, may also be three independent files corresponding to the foregoing three parts.
  • Step 204 Parse the first business rule file to obtain first business rule data.
  • the first service rule file includes business rule dependency data, business rule base data, and business rule data.
  • the business rule data needs to be parsed from the business rule file.
  • Step 206 Compile the text format of the first business rule data into a first preset format.
  • the first preset format is an executable format of the rule engine.
  • compiling the first business rule file includes the following two steps: formatting the text format of the first business rule data into an intermediate format, such as the intermediate format being a Java format; compiling the intermediate format of the first business rule data into the first format A preset format, wherein the first preset format may be a Java Class format.
  • step 208 the service rule belongs to the business rule information table, the business system to which the business rule belongs, the business system version number to which the business rule belongs, the business rule engine version number, the first business rule name, and the first preset format business rule data are saved to the business rule information table. And setting a version state of the first business rule data in the first preset format to a development state.
  • the first business rule file uploaded from the terminal parses the business rule data, compiles the text format of the business rule data into a first preset format, and then uses the first business rule data of the first preset format
  • Corresponding business rule information that is, the business system to which the business rule belongs, the service system version number to which the business rule belongs, the business rule engine version number, and the business rule file name
  • the version status of a business rule file is a development state, and the rule file exported from the rule file generator is implemented to be centrally stored in a format directly executable by the rule engine.
  • the business rule data is obtained by parsing the business rule file uploaded by the terminal, and the text format of the business rule data is compiled into the first preset format, and the first business rule data of the first preset format is Corresponding business rule information is correspondingly saved in the business rule information table, and the version state of the first business rule file in the first preset format is set to the development state, and the rule file exported from the rule file generator is implemented by the rule engine.
  • the format of the directly executed file is stored in a centralized manner, which facilitates the management of subsequent rule files, thereby improving the development efficiency of business rules.
  • the business rule management method shown in FIG. 2 further includes:
  • Step 302 Receive a business rule management configuration request, where the business rule management configuration request carries a series of business rule belongs, a business system to which the business rule belongs, a business system version number, a business rule engine version number, and a version status of the business rule data.
  • the version status of the service rule data refers to the version status of the service rule data stored in the first preset format of the service rule management system, where the first preset format is an executable format of the rule engine, Can be in Java Class format.
  • Step 304 Search, in the business rule information table, a second business rule file name corresponding to the series to which the business rule belongs, the business system to which the business rule belongs, the business system version number, the business rule engine version number, and the version status of the business rule file.
  • the business rule information carried in the configuration request is managed according to the received business rule, and the corresponding business rule name is searched in the pre-established business rule information table.
  • the number of the rule name is not limited, and may be one or more, which corresponds to the number of service rules imported by the entry personnel through the terminal and conforms to the business rule information carried by the business rule management configuration request.
  • Step 306 Send the second service rule name to the first terminal corresponding to the service rule management configuration request, so that the first terminal displays the business rule management configuration interface that includes the second service rule name.
  • the found second service rule name is sent to the first terminal that initiates the service rule management configuration request, and the first terminal displays the business rule management including the business rule name after receiving the business rule name.
  • Configuration interface
  • Step 308 Count the number of the second business rule name.
  • Step 310 If the number is greater than one, receive the third service rule name that is sent by the first terminal and is selected by the service rule management configuration interface.
  • the third business rule name is all the business rule files included in the system selected by the business system developer in the second business rule name displayed on the business rule management configuration interface. As business rules are continually updated, there are multiple versions of a rule file. At this point, the business system developer needs to ensure that the selected third business rule name is any set of required version names for different business rules.
  • Step 312 Search for the third service rule data corresponding to the third service rule name in the service rule information table.
  • the corresponding business rule data is obtained from the business rule information table according to the third business rule name selected by the terminal operator, and is used for subsequent business rule management configuration operations.
  • Step 314 Convert the first preset format of the third service rule data into the second preset format.
  • the second preset format is an identifiable compression format corresponding to the rule engine, such as an ear compression package.
  • the business rule management method shown in FIG. 2 further includes:
  • Step 402 Receive a business rule query request, and receive a service rule download request carrying a series of service rules, a business system to which the business rule belongs, and a service system version number to which the business rule belongs.
  • the business rule belongs to the business type to which the business rule belongs; the business system to which the business rule belongs is the business system corresponding to the business rule to be imported; the version number of the business system to which the business rule belongs is the version identifier of the business system corresponding to the business rule to be imported. .
  • Step 404 Search, in the business rule information table, a fourth business rule name corresponding to the series to which the business rule belongs, the business system to which the business rule belongs, and the version number of the business system to which the business rule belongs.
  • the business rule information carried in the service rule query request is searched for the corresponding business rule name in the business rule information table.
  • Step 406 Send the fourth service rule name to the second terminal corresponding to the service rule query request, so that the second terminal displays the service rule download interface that includes the fourth service rule name.
  • the searched fourth service rule name corresponding to the service rule query request is sent to the second terminal that initiates the service rule query request, and after receiving the fourth service rule name, the second terminal displays the The business rule download interface of the fourth business rule name, the business rule download interface is used by the business system developer to download the required business rules.
  • Step 408 Receive a business rule download request, where the business rule download request carries a fifth business rule name selected from the fourth business rule name by using the business rule download interface.
  • the fifth business rule file name is a business rule name selected from a fourth business rule name displayed by the business system developer from the business rule download interface.
  • Step 410 Search, in the business rule information table, the fifth business rule data corresponding to the fifth business rule name.
  • the server after receiving the fifth service rule file name sent by the terminal, the server searches for the fifth service rule data corresponding to the fifth service rule name in the service rule information table.
  • Step 412 Send the fifth service rule data to the service system development environment corresponding to the service system name to which the service rule belongs.
  • the business system development environment is a software and hardware environment that is set in advance and is suitable for the operation of the business system in the development state. After the fifth business rule data is found, the data is sent to the business system development environment corresponding to the business system to which the business rule belongs.
  • the business rule data required for the business system development is downloaded to the business system development environment, and can be used for the integrated development test of the subsequent business system.
  • the business rule management method shown in FIG. 2 further includes:
  • Step 502 Receive a business rule publishing request, where the business rule publishing request carries a service system version number to which the business rule belongs.
  • the version number of the service system to which the business rule belongs is the version identifier of the business system corresponding to the business rule to be imported.
  • Step 504 Obtain sixth service rule data corresponding to the service system version number to which the service rule belongs.
  • the business rule publishing request carries the business rule version number corresponding to the business system to which the business rule belongs.
  • Step 506 Search the service rule information table for the version status of the service system corresponding to the service system version number to which the service rule belongs.
  • the version status of the service system includes three types: development status, test status, and production status.
  • development status When the business system is in the development stage, including the requirements analysis, function design, function implementation method, overall structure design, module design, coding and debugging of the business system, the version status is the development status; when all the required functions of the business system have been implemented
  • the version status is the test status.
  • the service system is brought online, and the version status is the production status.
  • Step 508 If the version status is the development status, send the sixth service rule data to the service system test environment corresponding to the service system version number of the service rule, and set the version status of the sixth service rule data to the test status.
  • the service system test environment is a software and hardware environment in which the business system running in the test state is set in advance.
  • the initial state of the version of the business rule is the development state.
  • the version of the business rule is changed to the test state.
  • Step 510 If the version status is the test status, send the sixth service rule data to the service system production environment corresponding to the service system version number of the service rule, and set the version status of the sixth service rule file to the production status.
  • the business system production environment is a software and hardware environment that is set in advance and is suitable for the operation of the business system in the production state. After the business rule is successfully deployed to the corresponding business system production environment, the version of the business rule is changed to the production state.
  • the business rule is released and managed according to the version status of the service system, and the version status of the service system is associated with the version status of the business rule, which facilitates the development and handover of the business rules.
  • the business rule management method shown in FIG. 5 further includes: if the version status is the production status, sending the sixth service rule data to the business system version of the business rule that is closest to the service system version number to which the business rule belongs. No. corresponds to the business system production environment.
  • the production rollback of the business rules can be implemented, thereby further improving the convenience of business rule development.
  • a service rule management apparatus including:
  • the business rule import request receiving module 602 is configured to receive a business rule import request, where the business rule import request carries the series of the business rule, the business system name to which the business rule belongs, the service system version number to which the business rule belongs, the business rule engine version number, and the first service Rule name and first business rule file;
  • the business rule file parsing module 604 is configured to parse the first business rule file to obtain the first business rule data
  • the business rule compiling module 606 is configured to compile the text format of the first business rule data into a first preset format
  • the business rule storage module 608 is configured to: the business rule belongs to the series, the business system name to which the business rule belongs, the business system version number to which the business rule belongs, the business rule engine version number, the first business rule name, and the first service in the first preset format.
  • the rule data is saved to the business rule information table, and the version state of the first business rule data in the first preset format is set to the development state.
  • the device further includes: a service rule management configuration module, configured to receive a business rule management configuration request, where the business rule management configuration request carries a series of service rules, a business system to which the business rule belongs, and a service system version number to which the business rule belongs , the business rule engine version number and the version status of the business rule data; searching the business rule information table for the series to which the business rule belongs, the business system to which the business rule belongs, the business system version number to which the business rule belongs, the business rule engine version number, and the business rule data
  • the second service rule name corresponding to the version status is sent to the first terminal corresponding to the business rule management configuration request, so that the first terminal displays the business rule management configuration interface including the second business rule name And counting the number of the second business rule name; if the number is greater than one, receiving the third business rule name selected by the first terminal and selected by the business rule management configuration interface; and searching for the third business rule name in the business rule information table Corresponding third business rule Data; converting a first business rule third preset format
  • the device further includes: a service rule downloading module, configured to receive a service rule query request, and receive a business rule download request carrying a series of service rules, a business system to which the business rule belongs, and a service system version number to which the business rule belongs;
  • the service rule information table searches for the fourth business rule name corresponding to the series to which the business rule belongs, the business system to which the business rule belongs, and the version number of the business system to which the business rule belongs; and sends the fourth business rule name to the corresponding to the business rule query request.
  • the second terminal displays a business rule download interface that includes the fourth business rule name; and receives the business rule download request, and the business rule download request carries the fifth business rule selected from the fourth business rule name by using the business rule download interface.
  • the name is: the fifth business rule data corresponding to the name of the fifth business rule is searched; the fifth business rule data is sent to the business system development environment corresponding to the name of the business system to which the business rule belongs.
  • the device further includes: a service rule release management module, configured to receive a service rule issue request, where the service rule issue request carries a service system version number to which the service rule belongs; and obtain a sixth corresponding to the service system version number to which the service rule belongs The service rule data; the version status of the service system corresponding to the service system version number to which the service rule belongs; and the service system test environment corresponding to the service system version number to which the service rule belongs, if the version status is the development status, And setting the version status of the sixth service rule data to the test status; if the version status is the test status, sending the sixth service rule data to the service system production environment corresponding to the service system version number of the service rule, and setting the sixth service rule data
  • the version status is the production status.
  • the service rule issuance management module is further configured to: if the version status is the production status, send the sixth service rule data to the service system version number of the service rule that is closest to the service system version number to which the service rule belongs. Business system production environment.
  • Each of the above-described business rule management devices may be implemented in whole or in part by software, hardware, and combinations thereof.
  • Each of the above modules may be embedded in or independent of the processor in the computer device, or may be stored in a memory in the computer device in a software form, so that the processor invokes the operations corresponding to the above modules.
  • Each of the above-described devices may be implemented in whole or in part by software, hardware, and combinations thereof.
  • Each of the above modules may be embedded in or independent of the computer device in the server, or may be stored in a memory in the server in a software form, so that the computer device invokes the operations corresponding to the above modules.
  • the computer device can be a central processing unit (CPU), a microcomputer device, a single chip microcomputer, or the like.
  • One or more non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the following steps:
  • the business rule import request carries a series of business rules, a business system name to which the business rule belongs, a business system version number to which the business rule belongs, a business rule engine version number, a first business rule name, and a first business rule file;
  • the business rule belongs to the series, the business system name to which the business rule belongs, the business system version number to which the business rule belongs, the business rule engine version number, the first business rule name, and the first business rule data in the first preset format are saved to the business rule information table. And setting a version state of the first business rule data in the first preset format to a development state.
  • the computer readable instructions are further executed by the processor to: receive a business rule management configuration request, the business rule management configuration request carries a series of business rules, a business system to which the business rules belong, and a business system to which the business rules belong The version number, the business rule engine version number, and the version status of the business rule data; the service rule information table is searched for the series to which the business rule belongs, the business system to which the business rule belongs, the business system version number to which the business rule belongs, the business rule engine version number, and the service a second service rule name corresponding to the version status of the rule file; sending the second service rule name to the first terminal corresponding to the service rule management configuration request, so that the first terminal displays the business rule management including the second service rule name a configuration interface; the number of the second business rule name is counted; if the number is greater than one, the third business rule name selected by the first terminal and selected by the business rule management configuration interface is received; and the third business rule is selected in the business rule information table.
  • the following steps are further implemented: receiving a business rule query request, receiving a business rule download request carrying a series of business rules, a service system to which the business rule belongs, and a service system version to which the business rule belongs In the business rule information table, the fourth business rule name corresponding to the series to which the business rule belongs, the business system to which the business rule belongs, and the version number of the service system to which the business rule belongs is searched; the fourth business rule name is sent to the business rule query request.
  • Corresponding second terminal so that the second terminal displays the business rule download interface including the fourth business rule name; receiving the business rule download request, and the business rule download request carries the first selected from the fourth business rule name through the business rule download interface
  • the fifth business rule name is obtained in the business rule information table, and the fifth business rule data is sent to the business system development environment corresponding to the business system name to which the business rule belongs.
  • the following steps are further performed: receiving a business rule publishing request, the business rule publishing request carrying a service system version number to which the business rule belongs; and obtaining a service system version number corresponding to the business rule The sixth service rule data; the version status of the service system corresponding to the version number of the service system to which the service rule belongs; and the service system test corresponding to the version number of the service system to which the service rule belongs, if the version status is the development status Environment, and setting the version status of the sixth business rule data to the test status; if the version status is the test status, sending the sixth service rule data to the business system production environment corresponding to the service system version number to which the business rule belongs, and setting the sixth service The version status of the rule data is the production status.
  • the following steps are further implemented: if the version status is a production status, the sixth business rule data is sent to the business rule that is closest to the service system version number to which the business rule belongs.
  • the business system production environment corresponding to the business system version number.
  • a computer device comprising a memory and one or more processors having stored therein computer readable instructions that, when executed by a processor, cause one or more processors to execute a program The steps of implementing a business rule management method provided in each of the above embodiments.
  • the computer device can be a server.
  • FIG. 7 it is a schematic diagram of the internal structure of a computer device in one embodiment.
  • the computer device includes a processor, memory, and network interface coupled by a system bus.
  • the processor is used to provide computing and control capabilities to support the operation of the entire computer device.
  • the memory includes a nonvolatile storage medium and an internal memory.
  • the non-volatile storage medium can be a computer-readable non-volatile storage medium.
  • An operating system and computer readable instructions are stored in the non-volatile storage medium, the computer readable instructions being executed by the processor to implement a business rule management method.
  • the internal memory provides an environment for the operation of operating systems and computer readable instructions in a non-volatile storage medium.
  • the network interface is used to communicate with an external server or terminal over a network connection.
  • the server can be implemented with a stand-alone server or a server cluster consisting of multiple servers.
  • FIG. 7 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied.
  • the specific server may include a ratio. More or fewer components are shown in the figures, or some components are combined, or have different component arrangements.
  • the processor executes the computer readable instructions, the following steps are performed: receiving a business rule import request, the business rule import request carrying the series of the business rule, the business system name to which the business rule belongs, and the service system version number to which the business rule belongs. a business rule engine version number, a first business rule name and a first business rule file; parsing the first business rule file to obtain the first business rule data; compiling the text format of the first business rule data into the first preset format; The business rule belongs to the series, the business system name to which the business rule belongs, the business system version number to which the business rule belongs, the business rule engine version number, the business rule name, and the first business rule data of the first preset format are saved to the business rule information table, and are set.
  • the version status of the first business rule data of the first preset format is a development status.
  • the processor executes the computer readable instructions to: receive a business rule management configuration request, the business rule management configuration request carries a series of business rules, a service system to which the business rule belongs, and a service system version number to which the business rule belongs , the business rule engine version number and the version status of the business rule data; searching the business rule information table for the series to which the business rule belongs, the business system to which the business rule belongs, the business system version number to which the business rule belongs, the business rule engine version number, and the business rule data
  • the second service rule name corresponding to the version status is sent to the first terminal corresponding to the business rule management configuration request, so that the first terminal displays the business rule management configuration interface including the second business rule name And counting the number of the second business rule name; if the number is greater than one, receiving the third business rule name selected by the first terminal and selected by the business rule management configuration interface; and searching for the third business rule name in the business rule information table Corresponding third business rule Data; converting a first business rule third preset format data becomes a second
  • the method further includes the following steps: receiving a business rule query request, receiving the business rule download request carrying the series of the business rule, the business system to which the business rule belongs, and the service system version number to which the business rule belongs Searching the business rule information table for the fourth business rule name corresponding to the series to which the business rule belongs, the business system to which the business rule belongs, and the version number of the business system to which the business rule belongs; and sending the fourth business rule name to the business rule query request
  • the second terminal is configured to enable the second terminal to display a business rule download interface including the fourth business rule name; receive the business rule download request, and the business rule download request carries the fifth selected from the fourth business rule name by using the business rule download interface
  • the business rule name; the fifth business rule data corresponding to the fifth business rule name is searched in the business rule information table; and the fifth business rule data is sent to the business system development environment corresponding to the business system name to which the business rule belongs.
  • the method when the processor executes the computer readable instructions, the method further includes the following steps: receiving a business rule publishing request, the business rule publishing request carrying a service system version number to which the business rule belongs; and obtaining a corresponding version of the business system version number to which the business rule belongs Six business rule data; in the business rule information table, the version status of the business system corresponding to the service system version number to which the business rule belongs; and if the version status is the development status, the sixth business rule data is sent to the service system version number to which the business rule belongs.
  • Corresponding service system test environment and setting the version status of the sixth service rule file to the test status; if the version status is the test status, sending the sixth service rule data to the business system production environment corresponding to the service system version number to which the service rule belongs, And setting the version status of the sixth business rule data to the production status.
  • the processor executes the computer readable instructions, the following steps are further implemented: if the version status is the production status, the sixth service rule file is sent to the service rule belonging to the service system version number that belongs to the business rule.
  • the business system production environment corresponding to the system version number.
  • Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory can include random access memory (RAM) or external cache memory.
  • RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain.
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDRSDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • Synchlink DRAM SLDRAM
  • Memory Bus Radbus
  • RDRAM Direct RAM
  • DRAM Direct Memory Bus Dynamic RAM
  • RDRAM Memory Bus Dynamic RAM

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Mining & Analysis (AREA)
  • Stored Programmes (AREA)

Abstract

一种业务规则管理方法，包括：接收业务规则导入请求，所述业务规则导入请求携带所属系列，所属业务***名称，所属业务***版本号，引擎版本号，第一业务规则名称和第一业务规则文件；解析第一业务规则文件获取第一业务规则数据；将所述第一业务规则数据的文本格式编译为第一预设格式；将所述所属系列，所述所属业务***名称，所属业务***版本号，引擎版本号，所述业务规则文件名称和所述第一预设格式的第一业务规则数据保存至业务规则信息表，并设置所述第一预设格式的第一业务规则数据的版本状态为开发状态。

Description

业务规则管理方法、装置、存储介质和计算机设备
本申请要求于2017年09月27日提交中国专利局、申请号为201710888234.8、发明名称为“业务规则管理方法、装置、存储介质和计算机设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，特别是涉及一种网络安全联合防御方法、装置、服务器和存储介质。
背景技术
业务规则是指对业务定义和约束的描述，用于维持业务结构或控制和影响业务的行为。业务规则技术的基本思想是将业务***处理的业务逻辑从程序代码中抽取出来，将其转变为简单的业务规则，以结构化的业务规则数据来表示业务行为，采用类自然语言来描述，并集中存储在规则库中。业务规则由业务人员创建、实时更新和调试，业务规则之间的复杂逻辑关系由规则引擎处理。
传统的业务规则管理方法是将业务规则数据导入到SVN(版本控制***)等协同工具上，但由于协同工具会在业务规则数据中加入配置数据，使得业务***开发人员无法直接使用在协同工具上存储的业务规则数据，降低了业务规则的开发效率。
发明内容
根据本申请公开的各种实施例，提供了一种业务规则管理方法、装置、存储介质和计算机设备。
一种业务规则管理方法，包括：
接收业务规则导入请求，所述业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；
解析第一业务规则文件获取第一业务规则数据；
将所述第一业务规则数据的文本格式编译为第一预设格式；及
将所述业务规则所属系列，所述业务规则所属业务***名称，所述业务规则所属业务***版本号，所述业务规则引擎版本号，所述第一业务规则名称和所述第一预设格式的第一业务规则数据保存至业务规则信息表，并设置所述第一预设格式的第一业务规则数据的版本状态为开发状态。
一种业务规则管理装置，包括：
业务规则导入请求接收模块，用于接收业务规则导入请求，所述业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；
业务规则文件解析模块，用于解析第一业务规则文件获取第一业务规则数据；
业务规则编译模块，用于将所述第一业务规则数据的文本格式编译为第一预设格式；及
业务规则存储模块，用于将所述业务规则所属系列，所述业务规则所属业务***名称，所述业务规则所属业务***版本号，所述业务规则引擎版本号，所述第一业务规则名称和所述第一预设格式的第一业务规则数据保存至业务规则信息表，并设置所述第一预设格式的第一业务规则数据的版本状态为开发状态。
一个或多个存储有计算机可读指令的非易失性存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：
接收业务规则导入请求，所述业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；
解析第一业务规则文件获取第一业务规则数据；
将所述第一业务规则数据的文本格式编译为第一预设格式；及
将所述业务规则所属系列，所述业务规则所属业务***名称，所述业务规则所属业务***版本号，所述业务规则引擎版本号，所述第一业务规则名称和所述第一预设格式的第一业务规则数据保存至业务规则信息表，并设置所述第一预设格式的第一业务规则数据的版本状态为开发状态。
一种计算机设备，包括存储器和一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器执行以下步骤：
接收业务规则导入请求，所述业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；
解析第一业务规则文件获取第一业务规则数据；
将所述第一业务规则数据的文本格式编译为第一预设格式；及
将所述业务规则所属系列，所述业务规则所属业务***名称，所述业务规则所属业务***版本号，所述业务规则引擎版本号，所述第一业务规则名称和所述第一预设格式的第一业务规则数据保存至业务规则信息表，并设置所述第一预设格式的第一业务规则数据的版本状态为开发状态。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征、目的和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为根据一个或多个实施例中业务规则管理方法的应用环境图。
图2为根据一个或多个实施例中业务规则管理方法的流程图；
图3为另一个实施例中业务规则管理方法中的业务规则管理配置方法流程图；
图4为根据一个或多个实施例中的业务规则管理方法中的业务规则下载方法流程图；
图5为根据一个或多个实施例中的业务规则管理方法中的业务规则发布管理方法流程图；
图6为根据一个或多个实施例中业务规则管理装置的结构框图；
图7为根据一个或多个实施例中计算机设备的内部结构图。
具体实施方式
为了使本申请技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请实施例提供的业务规则管理方法可应用于如图1所示的应用环境中。参考图1所示，计算机设备102接收终端104发起的接收业务规则导入请求。具体的，计算机设备102接收终端104发起的接收业务规则导入请求，该业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；解析第一业务规则文件获取第一业务规则数据；将第一业务规则数据的文本格式编译为第一预设格式；将业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一预设格式的第一业务规则数据保存至业务规则信息表，并设置第一预设格式的第一业务规则数据的版本状态为开发状态。
图2为本申请一个实施例的数据发布方法的流程示意图。应当理解的是，虽然图2的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必须按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，其可以以其他的顺序执行。而且图2中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是依次进行，而是可以与其他步骤或者其他步骤的子步骤或者阶段的至少一部分轮流或者交替执行。
参考图2，提供的一种业务规则管理方法以应用于如图1所示的计算机设备中为例进行说明，该计算机设备可为服务器，该方法包括：
步骤202，接收业务规则导入请求，业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件。
本实施例中，业务规则所属系列即业务规则所属业务类型，如产险，人身保险等；业务规则所属业务***名称为即将导入的业务规则对应的业务***名称，如车险自动核保***等；业务规则所属业务***版本号为即将导入的业务规则对应的业务***的版本标识，如EPCIS-AUTO2.2.0(车险自动核保2.2.0版本)；业务规则引擎版本号为业务规则引擎的版本标识，如ENGINE4.0.0(业务规则引擎4.0.0版本)，其中，业务规则引擎是一种嵌入在应用程序中的组件，实现了将业务决策从应用程序代码中分离出来，并使用预定义的语义模块编写业务决策；第一业务规则名称是即将导入到规则管理***的业务规则的名称，如批量保单审核；第一业务规则文件是即将导入到规则管理***的规则文件，该规则文件中包括了三部分内容：第一个部分是业务规则的依赖数据，用于后续的业务规则编译，第二部分是提供业务规则中文描述的规则库，用于业务规则的页面显示和业务规则的编辑，第三部分是业务规则数据，此外，该规则文件格式不做限定，可以是包含前述三个部分的压缩包格式，如ZIP包、RAR包或其他压缩格式的文件压缩包，也可以是前述三个部分对应的三个独立文件。
步骤204，解析第一业务规则文件获取第一业务规则数据。
本实施例中，第一业务规则文件中包括业务规则依赖数据、业务规则库数据和业务规则数据，为了后续的进一步操作，需要从业务规则文件中解析出业务规则数据。
步骤206，将第一业务规则数据的文本格式编译为第一预设格式。
本实施例中，第一预设格式为规则引擎的可执行格式。
具体地，编译第一业务规则文件包括以下两个步骤：格式化第一业务规则数据的文本格式为中间格式，如该中间格式为Java格式；将第一业务规则数据的中间格式编译为第一预设格式，其中，第一预设格式可以为Java Class格式。
步骤208，将业务规则所属系列，业务规则所属业务***，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一预设格式的业务规则数据保存至业务规则信息表，并设置第一预设格式的第一业务规则数据的版本状态为开发状态。
本实施例中，从终端上传的第一业务规则文件解析出业务规则数据，将业务规则数据的文本格式编译成第一预设格式，再将该第一预设格式的第一业务规则数据与其对应的业务规则信息(即业务规则所属业务***，业务规则所属业务***版本号，业务规则引擎版本号和业务规则文件名称)对应保存至业务规则信息表中，并设置第一预设格式的第一业务规则文件的版本状态为开发状态，实现了将从规则文件生成器导出的规则文件以规则引擎可直接执行的格式进行集中存储。
本实施例中，通过解析终端上传的业务规则文件得到业务规则数据，并将该业务规则数据的文本格式编译成第一预设格式，再将该第一预设格式的第一业务规则数据与其对应的业 务规则信息对应保存至业务规则信息表中，并设置第一预设格式的第一业务规则文件的版本状态为开发状态，实现了将从规则文件生成器导出的规则文件以规则引擎可直接执行的格式集中存储，便于后续规则文件的管理，从而提高了业务规则的开发效率。
在一个实施例中，如图3所示，图2所示的业务规则管理方法还包括：
步骤302，接收业务规则管理配置请求，业务规则管理配置请求携带业务规则所属系列，业务规则所属业务***，业务***版本号，业务规则引擎版本号和业务规则数据的版本状态。
本实施例中，业务规则数据的版本状态指的是存储在业务规则管理***的第一预设格式的业务规则数据的版本状态，其中，第一预设格式为规则引擎的可执行格式，具体可为Java Class格式。
步骤304，在业务规则信息表中查找与业务规则所属系列，业务规则所属业务***，业务***版本号，业务规则引擎版本号和业务规则文件的版本状态均对应的第二业务规则文件名称。
本实施例中，根据接收到的业务规则管理配置请求携带的业务规则信息，在预先建立的业务规则信息表中查找对应的业务规则名称。该规则名称的个数没有限定，可以是一个或多个，具体对应于录入人员通过终端导入的符合业务规则管理配置请求携带的业务规则信息的业务规则个数。
步骤306，将第二业务规则名称发送给与业务规则管理配置请求对应的第一终端，以使第一终端显示包含第二业务规则名称的业务规则管理配置界面。
本实施例中，将查找到的第二业务规则名称发送给发起业务规则管理配置请求的第一终端，该第一终端在接收到这些业务规则名称后，显示包括这些业务规则名称的业务规则管理配置界面。
步骤308，统计第二业务规则名称的个数。
本实施例中，根据查找到的第二业务规则个数的不同做相应不同的处理，因此，首先统计第二业务规则名称的个数。
步骤310，若个数大于一，则接收第一终端发送的通过业务规则管理配置界面选择的第三业务规则名称。
本实例中，第三业务规则名称是业务***开发人员在业务规则管理配置界面显示的第二业务规则名称中选择的包含一个***中的所有业务规则文件。随着业务规则的不断更新，一个规则文件有多个版本，此时，业务***开发人员需要确保选择的第三业务规则名称中是不同业务规则的任一所需版本名称集合。
步骤312，在业务规则信息表中查找第三业务规则名称对应的第三业务规则数据。
本实施例中，根据终端操作人员选择的第三业务规则名称从业务规则信息表中获取对应的业务规则数据，用于后续的业务规则管理配置操作。
步骤314，将第三业务规则数据的第一预设格式转换成为第二预设格式。
本实施例中，第二预设格式是对应于规则引擎的可识别压缩格式，如ear压缩包。
本实施例中，在确定业务开发***对应多个业务规则数据时，将这些多个业务规则数据的第一预设格式转换为第二预设格式(如ear包)的业务规则数据，从而完成业务规则的管理配置，便于业务***的部署。
在一个实施例中，如图4所示，图2所示的业务规则管理方法还包括：
步骤402，接收业务规则查询请求，接收业务规则下载请求携带业务规则所属系列，业务规则所属业务***和业务规则所属业务***版本号。
同样地，业务规则所属系列即业务规则所属业务类型；业务规则所属业务***为即将导入的业务规则对应的业务***；业务规则所属业务***版本号为即将导入的业务规则对应的业务***的版本标识。
步骤404，在业务规则信息表中查找与业务规则所属系列，业务规则所属业务***和业务规则所属业务***版本号均对应的第四业务规则名称。
本实施例中，根据业务规则查询请求中携带的业务规则信息在业务规则信息表中查找出对应的业务规则名称。
步骤406，将第四业务规则名称发送给与业务规则查询请求对应的第二终端，以使第二终端显示包含第四业务规则名称的业务规则下载界面。
本实施例中，将查找到的对应于业务规则查询请求的第四业务规则名称发送给发起业务规则查询请求的第二终端，该第二终端在接收到第四业务规则名称后，显示包含该第四业务规则名称的业务规则下载界面，该业务规则下载界面用于业务***开发人员下载所需的业务规则。
步骤408，接收业务规则下载请求，业务规则下载请求携带通过业务规则下载界面从第四业务规则名称中选择的第五业务规则名称。
本实施例中，第五业务规则文件名称是从业务***开发人员从业务规则下载界面显示的第四业务规则名称中选择的业务规则名称。
步骤410,在业务规则信息表中查找与第五业务规则名称对应的第五业务规则数据。
本实施例中，服务器在接收到终端发送的第五业务规则文件名称后，在从业务规则信息表中查找与该第五业务规则名称对应的第五业务规则数据。
步骤412，将第五业务规则数据发送给业务规则所属业务***名称对应的业务***开发环境。
本实施例中，业务***开发环境是预先设置的适用于开发状态的业务***运行的软硬件环境。在查找到第五业务规则数据后，将该数据发送给业务规则所属业务***对应的业务***开发环境。
本实施例中，通过接收业务规则下载请求，将业务***开发所需的业务规则数据下载至该业务***开发环境，可用于后续业务***的集成开发测试。
在一个实施例中，如图5所示，图2所示的业务规则管理方法还包括：
步骤502，接收业务规则发布请求，业务规则发布请求携带业务规则所属业务***版本号。
同样地，业务规则所属业务***版本号为即将导入的业务规则对应的业务***的版本标识。
步骤504，获取业务规则所属业务***版本号对应的第六业务规则数据。
本实施例中，根据业务规则发布请求携带业务规则所属业务***版本号查找与之对应的业务规则数据。
步骤506，在业务规则信息表中查找与业务规则所属业务***版本号对应的业务***的版本状态。
本实施例中，业务***的版本状态包括开发状态，测试状态和生产状态三种。当业务***处于开发阶段，包括业务***的需求分析、功能设计、功能实现方法、总体结构设计、模块设计、编码和调试等，则版本状态为开发状态；当业务***的所有需求功能均已实现，***开发人员或测试人员对业务***进行测试，则版本状态为测试状态；当业务***中所有需求功能的测试工作完成，将该业务***进行上线，则版本状态为生产状态。
步骤508，若版本状态为开发状态，则发送第六业务规则数据至业务规则所属业务***版本号对应的业务***测试环境，并设置第六业务规则数据的版本状态为测试状态。
本实施例中，业务***测试环境是预先设置的适用于测试状态的业务***运行的软硬件环境。业务规则的版本状态初始值为开发状态，当该业务规则被成功部署到与之对应的业务***测试环境后，则该业务规则的版本状变更为测试状态。
步骤510，若版本状态为测试状态，则发送第六业务规则数据至业务规则所属业务***版本号对应的业务***生产环境，并设置第六业务规则文件的版本状态为生产状态。
本实施例中，业务***生产环境是预先设置的适用于生产状态的业务***运行的软硬件环境。当业务规则被成功部署到与之对应的业务***生产环境后，则该业务规则的版本状变更为生产状态。
本实施例中，根据业务***的版本状态实现业务规则的发布管理，同时将业务***的版本状态与业务规则的版本状态对应起来，便于业务规则的开发和移交。
在一个实施例中，图5所示的业务规则管理方法还包括：若版本状态为生产状态，则发送第六业务规则数据至与业务规则所属业务***版本号相差最近的业务规则所属业务***版本号对应的业务***生产环境。
本实施例中，当业务***的版本状态为生产状态时，可实现业务规则的生产回滚，进一步提高了业务规则开发的便利性。
在一个实施例中，如图6所示，提供了一种业务规则管理装置，包括：
业务规则导入请求接收模块602，用于接收业务规则导入请求，业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；
业务规则文件解析模块604，用于解析第一业务规则文件获取第一业务规则数据；
业务规则编译模块606，用于将第一业务规则数据的文本格式编译为第一预设格式；
业务规则存储模块608，用于将业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一预设格式的第一业务规则数据保存至业务规则信息表，并设置第一预设格式的第一业务规则数据的版本状态为开发状态。
在一个实施例中，上述装置还包括：业务规则管理配置模块，用于接收业务规则管理配置请求，业务规则管理配置请求携带业务规则所属系列，业务规则所属业务***，业务规则所属业务***版本号，业务规则引擎版本号和业务规则数据的版本状态；在业务规则信息表中查找与业务规则所属系列，业务规则所属业务***，业务规则所属业务***版本号，业务规则引擎版本号和业务规则数据的版本状态均对应的第二业务规则名称；将第二业务规则名称发送给与业务规则管理配置请求对应的第一终端，以使第一终端显示包含第二业务规则名称的业务规则管理配置界面；统计第二业务规则名称的个数；若个数大于一，则接收第一终端发送的通过业务规则管理配置界面选择的第三业务规则名称；在业务规则信息表中查找第三业务规则名称对应的第三业务规则数据；将第三业务规则数据的第一预设格式转换成为第二预设格式。
在一个实施例中，上述装置还包括：业务规则下载模块，用于接收业务规则查询请求，接收业务规则下载请求携带业务规则所属系列，业务规则所属业务***和业务规则所属业务***版本号；在业务规则信息表中查找与业务规则所属系列，业务规则所属业务***和业务规则所属业务***版本号均对应的第四业务规则名称；将第四业务规则名称发送给与业务规则查询请求对应的第二终端，以使第二终端显示包含第四业务规则名称的业务规则下载界面；接收业务规则下载请求，业务规则下载请求携带通过业务规则下载界面从第四业务规则名称中选择的第五业务规则名称；查找与第五业务规则名称对应的第五业务规则数据；将第五业务规则数据发送给业务规则所属业务***名称对应的业务***开发环境。
在一个实施例中，上述装置还包括：业务规则发布管理模块，用于接收业务规则发布请求，业务规则发布请求携带业务规则所属业务***版本号；获取业务规则所属业务***版本号对应的第六业务规则数据；查找与业务规则所属业务***版本号对应的业务***的版本状态；若版本状态为开发状态，则发送第六业务规则数据至业务规则所属业务***版本号对应的业务***测试环境，并设置第六业务规则数据的版本状态为测试状态；若版本状态为测试状态，则发送第六业务规则数据至业务规则所属业务***版本号对应的业务***生产环境，并设置第六业务规则数据的版本状态为生产状态。
在一个实施例中，上述业务规则发布管理模块还用于若版本状态为生产状态，则发送第六业务规则数据至与业务规则所属业务***版本号相差最近的业务规则所属业务***版本号对应的业务***生产环境。
关于业务规则管理装置的具体限定可以参见上文中对于业务规则管理方法的限定，在此不再赘述。上述业务规则管理装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中，也可以以软件形式存储于计算机设备中的存储器中，以便于处理器调用执行以上各个模块对应的操作。
上述装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于服务器中的计算机设备中，也可以以软件形式存储于服务器中的存储器中，以便于计算机设备调用执行以上各个模块对应的操作。该计算机设备可以为中央处理单元(CPU)、微计算机设备、单片机等。
一个或多个存储有计算机可读指令的非易失性存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：
接收业务规则导入请求，业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；
解析第一业务规则文件获取第一业务规则数据；
将第一业务规则数据的文本格式编译为第一预设格式；
将业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一预设格式的第一业务规则数据保存至业务规则信息表，并设置第一预设格式的第一业务规则数据的版本状态为开发状态。
在一个实施例中，该计算机可读指令被处理器执行时还实现以下步骤：接收业务规则管理配置请求，业务规则管理配置请求携带业务规则所属系列，业务规则所属业务***，业务规则所属业务***版本号，业务规则引擎版本号和业务规则数据的版本状态；在业务规则信息表中查找与业务规则所属系列，业务规则所属业务***，业务规则所属业务***版本号，业务规则引擎版本号和业务规则文件的版本状态均对应的第二业务规则名称；将第二业务规则名称发送给与业务规则管理配置请求对应的第一终端，以使第一终端显示包含第二业务规则名称的业务规则管理配置界面；统计第二业务规则名称的个数；若个数大于一，则接收第一终端发送的通过业务规则管理配置界面选择的第三业务规则名称；在业务规则信息表中第三业务规则名称对应的第三业务规则数据；第三业务规则数据的第一预设格式转换成为第二预设格式。
在一个实施例中，该计算机可读指令被处理器执行时还实现以下步骤：接收业务规则查询请求，接收业务规则下载请求携带业务规则所属系列，业务规则所属业务***和业务规则所属业务***版本号；在业务规则信息表中查找与业务规则所属系列，业务规则所属业务系 统和业务规则所属业务***版本号均对应的第四业务规则名称；将第四业务规则名称发送给与业务规则查询请求对应的第二终端，以使第二终端显示包含第四业务规则名称的业务规则下载界面；接收业务规则下载请求，业务规则下载请求携带通过业务规则下载界面从第四业务规则名称中选择的第五业务规则名称；在业务规则信息表中查找与第五业务规则名称对应的第五业务规则数据；将第五业务规则数据发送给业务规则所属业务***名称对应的业务***开发环境。
在一个实施例中，该计算机可读指令被处理器执行时还实现以下步骤：接收业务规则发布请求，业务规则发布请求携带业务规则所属业务***版本号；获取业务规则所属业务***版本号对应的第六业务规则数据；查找与业务规则所属业务***版本号对应的业务***的版本状态；若版本状态为开发状态，则发送第六业务规则数据至业务规则所属业务***版本号对应的业务***测试环境，并设置第六业务规则数据的版本状态为测试状态；若版本状态为测试状态，则发送第六业务规则数据至业务规则所属业务***版本号对应的业务***生产环境，并设置第六业务规则数据的版本状态为生产状态。
在一个实施例中，该计算机可读指令被处理器执行时还实现以下步骤：若版本状态为生产状态，则发送第六业务规则数据至与业务规则所属业务***版本号相差最近的业务规则所属业务***版本号对应的业务***生产环境。
在一个实施例中，提供了计算机设备，包括存储器和一个或多个处理器，存储器中储存有计算机可读指令，计算机可读指令被处理器执行时，使得一个或多个处理器执行程序时实现上述各实施例中提供的一种业务规则管理方法的步骤。
具体地，该计算机设备可为服务器。如图7所示，为一个实施例中计算机设备的内部结构示意图。该计算机设备包括通过***总线连接的处理器、存储器和网络接口。其中，处理器用于提供计算和控制能力，支撑整个计算机设备的运行。存储器包括非易失性存储介质和内存储器。非易失性存储介质可以是计算机可读非易失性存储介质。非易失性存储介质中存储有操作***和计算机可读指令，该计算机可读指令被处理器执行时以实现一种业务规则管理方法。内存储器为非易失性存储介质中的操作***和计算机可读指令的运行提供环境。网络接口用于与外部的服务器或终端通过网络连接通信。服务器可以用独立的服务器或者是多个服务器组成的服务器集群来实现。
本领域技术人员可以理解，图7中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的服务器的限定，具体的服务器可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
在一个实施例中，该处理器执行计算机可读指令时实现如下步骤：接收业务规则导入请求，业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；解析第一 业务规则文件获取第一业务规则数据；将第一业务规则数据的文本格式编译为第一预设格式；；将业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，业务规则名称和第一预设格式的第一业务规则数据保存至业务规则信息表，并设置第一预设格式的第一业务规则数据的版本状态为开发状态。
在一个实施例中，该处理器执行计算机可读指令时实现如下步骤：接收业务规则管理配置请求，业务规则管理配置请求携带业务规则所属系列，业务规则所属业务***，业务规则所属业务***版本号，业务规则引擎版本号和业务规则数据的版本状态；在业务规则信息表中查找与业务规则所属系列，业务规则所属业务***，业务规则所属业务***版本号，业务规则引擎版本号和业务规则数据的版本状态均对应的第二业务规则名称；将第二业务规则名称发送给与业务规则管理配置请求对应的第一终端，以使第一终端显示包含第二业务规则名称的业务规则管理配置界面；统计第二业务规则名称的个数；若个数大于一，则接收第一终端发送的通过业务规则管理配置界面选择的第三业务规则名称；在业务规则信息表中查找第三业务规则名称对应的第三业务规则数据；将第三业务规则数据的第一预设格式转换成为第二预设格式。
在一个实施例中，该处理器执行计算机可读指令时还实现如下步骤：接收业务规则查询请求，接收业务规则下载请求携带业务规则所属系列，业务规则所属业务***和业务规则所属业务***版本号；在业务规则信息表中查找与业务规则所属系列，业务规则所属业务***和业务规则所属业务***版本号均对应的第四业务规则名称；将第四业务规则名称发送给与业务规则查询请求对应的第二终端，以使第二终端显示包含第四业务规则名称的业务规则下载界面；接收业务规则下载请求，业务规则下载请求携带通过业务规则下载界面从第四业务规则名称中选择的第五业务规则名称；在业务规则信息表中查找与第五业务规则名称对应的第五业务规则数据；将第五业务规则数据发送给业务规则所属业务***名称对应的业务***开发环境。
在一个实施例中，该处理器执行计算机可读指令时还实现如下步骤：接收业务规则发布请求，业务规则发布请求携带业务规则所属业务***版本号；获取业务规则所属业务***版本号对应的第六业务规则数据；在业务规则信息表中查找与业务规则所属业务***版本号对应的业务***的版本状态；若版本状态为开发状态，则发送第六业务规则数据至业务规则所属业务***版本号对应的业务***测试环境，并设置第六业务规则文件的版本状态为测试状态；若版本状态为测试状态，则发送第六业务规则数据至业务规则所属业务***版本号对应的业务***生产环境，并设置第六业务规则数据的版本状态为生产状态。
在一个实施例中，该处理器执行计算机可读指令时还实现如下步骤：若版本状态为生产状态，则发送第六业务规则文件至与业务规则所属业务***版本号相差最近的业务规则所属业务***版本号对应的业务***生产环境，。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计 算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一非易失性计算机可读取存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

  1. 一种业务规则管理方法，包括：
    接收业务规则导入请求，所述业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；
    解析第一业务规则文件获取第一业务规则数据；
    将所述第一业务规则数据的文本格式编译为第一预设格式；及
    将所述业务规则所属系列，所述业务规则所属业务***名称，所述业务规则所属业务***版本号，所述业务规则引擎版本号，所述第一业务规则名称和所述第一预设格式的第一业务规则数据保存至业务规则信息表，并设置所述第一预设格式的第一业务规则数据的版本状态为开发状态。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收业务规则管理配置请求，所述业务规则管理配置请求携带所述业务规则所属系列，所述业务规则所属业务***，所述业务规则所属业务***版本号，所述业务规则引擎版本号和业务规则数据的版本状态；
    在所述业务规则信息表中查找与所述业务规则所属系列，所述业务规则所属业务***，所述业务规则所属业务***版本号，所述业务规则引擎版本号和所述业务规则数据的版本状态均对应的第二业务规则名称；
    将所述第二业务规则名称发送给与所述业务规则管理配置请求对应的第一终端，以使所述第一终端显示包含所述第二业务规则名称的业务规则管理配置界面；
    统计所述第二业务规则名称的个数；
    若所述个数大于一，则接收所述第一终端发送的通过所述业务规则管理配置界面选择的第三业务规则名称；
    在所述业务规则信息表中查找所述第三业务规则名称对应的第三业务规则数据；
    将所述第三业务规则数据的第一预设格式转换成为第二预设格式。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收业务规则查询请求，所述接收业务规则下载请求携带所述业务规则所属系列，所述业务规则所属业务***和所述业务规则所属业务***版本号；
    在所述业务规则信息表中查找与所述业务规则所属系列，所述业务规则所属业务***和所述业务规则所属业务***版本号均对应的第四业务规则名称；
    将所述第四业务规则名称发送给与所述业务规则查询请求对应的第二终端，以使所述第二终端显示包含所述第四业务规则名称的业务规则下载界面；
    接收业务规则下载请求，所述业务规则下载请求携带通过所述业务规则下载界面从所述第四业务规则名称中选择的第五业务规则名称；
    在所述业务规则信息表中查找与所述第五业务规则名称对应的第五业务规则数据；
    将所述第五业务规则数据发送给所述业务规则所属业务***名称对应的业务***开发环境。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收业务规则发布请求，所述业务规则发布请求携带所述业务规则所属业务***版本号；
    获取所述业务规则所属业务***版本号对应的第六业务规则数据；
    在所述业务规则信息表中查找与所述业务规则所属业务***版本号对应的业务***的版本状态；
    若所述版本状态为开发状态，则发送所述第六业务规则数据至所述业务规则所属业务***版本号对应的业务***测试环境，并设置所述第六业务规则数据的版本状态为测试状态；
    若所述版本状态为测试状态，则发送所述第六业务规则数据至所述业务规则所属业务***版本号对应的业务***生产环境，并设置所述第六业务规则数据的版本状态为生产状态。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    当所述版本状态为生产状态时，则发送所述第六业务规则数据至与所述业务规则所属业务***版本号相差最近的业务规则所属业务***版本号对应的业务***生产环境。
  6. 一种业务规则管理装置，包括：
    业务规则导入请求接收模块，用于接收业务规则导入请求，所述业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；
    业务规则文件解析模块，用于解析第一业务规则文件获取第一业务规则数据；
    业务规则编译模块，用于将所述第一业务规则数据的文本格式编译为第一预设格式；及
    业务规则存储模块，用于将所述业务规则所属系列，所述业务规则所属业务***名称，所述业务规则所属业务***版本号，所述业务规则引擎版本号，所述第一业务规则名称和所述第一预设格式的第一业务规则数据保存至业务规则信息表，并设置所述第一预设格式的第一业务规则数据的版本状态为开发状态。
  7. 根据权利要求6所述的装置，其特征在于，所述装置还包括：
    业务规则管理配置模块，用于接收业务规则管理配置请求，所述业务规则管理配置请求携带所述业务规则所属系列，所述业务规则所属业务***，所述业务规则所属业务***版本号，所述业务规则引擎版本号和业务规则数据的版本状态；在所述业务规则信息表中查找与所述业务规则所属系列，所述业务规则所属业务***，所述业务规则所属业务***版本号，所述业务规则引擎版本号和所述业务规则数据的版本状态均对应的第二业务规则名称；将所述第二业务规则名称发送给与所述业务规则管理配置请求对应的第一终端，以使所述第一终端显示包含所述第二业务规则名称的业务规则管理配置界面；统计所述第二业务规则名称的个数；当所述个数大于一时，则接收所述第一终端发送的通过所述业务规则管理配置界面选 择的第三业务规则名称；在所述业务规则信息表中查找所述第三业务规则名称对应的第三业务规则数据；将所述第三业务规则数据的第一预设格式转换成为第二预设格式。
  8. 根据权利要求6所述的装置，其特征在于，所述装置还包括：
    业务规则下载模块，用于接收业务规则查询请求，所述接收业务规则下载请求携带所述业务规则所属系列，所述业务规则所属业务***和所述业务规则所属业务***版本号；在所述业务规则信息表中查找与所述业务规则所属系列，所述业务规则所属业务***和所述业务规则所属业务***版本号均对应的第四业务规则名称；将所述第四业务规则名称发送给与所述业务规则查询请求对应的第二终端，以使所述第二终端显示包含所述第四业务规则名称的业务规则下载界面；接收业务规则下载请求，所述业务规则下载请求携带通过所述业务规则下载界面从所述第四业务规则名称中选择的第五业务规则名称；查找与所述第五业务规则名称对应的第五业务规则数据；将所述第五业务规则数据发送给所述业务规则所属业务***名称对应的业务***开发环境。
  9. 根据权利要求6所述的装置，其特征在于，所述装置还包括：
    业务规则发布管理模块，用于接收业务规则发布请求，所述业务规则发布请求携带所述业务规则所属业务***版本号；获取所述业务规则所属业务***版本号对应的第六业务规则数据；在所述业务规则信息表中查找与所述业务规则所属业务***版本号对应的业务***的版本状态；当所述版本状态为开发状态时，则发送所述第六业务规则数据至所述业务规则所属业务***版本号对应的业务***测试环境，并设置所述第六业务规则数据的版本状态为测试状态；当所述版本状态为测试状态，则发送所述第六业务规则数据至所述业务规则所属业务***版本号对应的业务***生产环境，并设置所述第六业务规则数据的版本状态为生产状态。
  10. 根据权利要求9所述的装置，其特征在于，所述业务规则发布管理模块，还用于当所述版本状态为生产状态时，则发送所述第六业务规则数据至与所述业务规则所属业务***版本号相差最近的业务规则所属业务***版本号对应的业务***生产环境。
  11. 一种计算机设备，包括存储器和处理器，所述存储器中存储有计算机计算机可执行指令，所述指令被所述处理器执行时，使得所述处理器执行以下步骤：
    接收业务规则导入请求，所述业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；
    解析第一业务规则文件获取第一业务规则数据；
    将所述第一业务规则数据的文本格式编译为第一预设格式；及
    将所述业务规则所属系列，所述业务规则所属业务***名称，所述业务规则所属业务***版本号，所述业务规则引擎版本号，所述第一业务规则名称和所述第一预设格式的第一业务规则数据保存至业务规则信息表，并设置所述第一预设格式的第一业务规则数据的版本状 态为开发状态。
  12. 根据权利要求11所述的计算机设备，其特征在于，所述处理器还执行以下步骤：
    接收业务规则管理配置请求，所述业务规则管理配置请求携带所述业务规则所属系列，所述业务规则所属业务***，所述业务规则所属业务***版本号，所述业务规则引擎版本号和业务规则数据的版本状态；
    在所述业务规则信息表中查找与所述业务规则所属系列，所述业务规则所属业务***，所述业务规则所属业务***版本号，所述业务规则引擎版本号和所述业务规则数据的版本状态均对应的第二业务规则名称；
    将所述第二业务规则名称发送给与所述业务规则管理配置请求对应的第一终端，以使所述第一终端显示包含所述第二业务规则名称的业务规则管理配置界面；
    统计所述第二业务规则名称的个数；
    当所述个数大于一时，则接收所述第一终端发送的通过所述业务规则管理配置界面选择的第三业务规则名称；
    在所述业务规则信息表中查找所述第三业务规则名称对应的第三业务规则数据；
    将所述第三业务规则数据的第一预设格式转换成为第二预设格式。
  13. 根据权利要求11所述的计算机设备，其特征在于，所述处理器还执行以下步骤：
    接收业务规则查询请求，所述接收业务规则下载请求携带所述业务规则所属系列，所述业务规则所属业务***和所述业务规则所属业务***版本号；
    在所述业务规则信息表中查找与所述业务规则所属系列，所述业务规则所属业务***和所述业务规则所属业务***版本号均对应的第四业务规则名称；
    将所述第四业务规则名称发送给与所述业务规则查询请求对应的第二终端，以使所述第二终端显示包含所述第四业务规则名称的业务规则下载界面；
    接收业务规则下载请求，所述业务规则下载请求携带通过所述业务规则下载界面从所述第四业务规则名称中选择的第五业务规则名称；
    在所述业务规则信息表中查找与所述第五业务规则名称对应的第五业务规则数据；
    将所述第五业务规则数据发送给所述业务规则所属业务***名称对应的业务***开发环境。
  14. 根据权利要求11所述的计算机设备，其特征在于，所述处理器还执行以下步骤：
    接收业务规则发布请求，所述业务规则发布请求携带所述业务规则所属业务***版本号；
    获取所述业务规则所属业务***版本号对应的第六业务规则数据；
    在所述业务规则信息表中查找与所述业务规则所属业务***版本号对应的业务***的版本状态；
    当所述版本状态为开发状态时，则发送所述第六业务规则数据至所述业务规则所属业务***版本号对应的业务***测试环境，并设置所述第六业务规则数据的版本状态为测试状态；
    当所述版本状态为测试状态时，则发送所述第六业务规则数据至所述业务规则所属业务***版本号对应的业务***生产环境，并设置所述第六业务规则数据的版本状态为生产状态。
  15. 根据权利要求14所述的计算机设备，其特征在于，所述处理器还执行以下步骤：
    当所述版本状态为生产状态时，则发送所述第六业务规则数据至与所述业务规则所属业务***版本号相差最近的业务规则所属业务***版本号对应的业务***生产环境。
  16. 一个或多个存储有计算机可执行指令的非易失性可读存储介质，所述指令被一个或多个处理器执行，使得所述一个或多个处理器执行以下步骤：
    接收业务规则导入请求，所述业务规则导入请求携带业务规则所属系列，业务规则所属业务***名称，业务规则所属业务***版本号，业务规则引擎版本号，第一业务规则名称和第一业务规则文件；
    解析第一业务规则文件获取第一业务规则数据；
    将所述第一业务规则数据的文本格式编译为第一预设格式；
    将所述业务规则所属系列，所述业务规则所属业务***名称，所述业务规则所属业务***版本号，所述业务规则引擎版本号，所述第一业务规则名称和所述第一预设格式的第一业务规则数据保存至业务规则信息表，并设置所述第一预设格式的第一业务规则数据的版本状态为开发状态。
  17. 根据权利要求16所述的非易失性可读存储介质，其特征在于，所述处理器还执行以下步骤：
    接收业务规则管理配置请求，所述业务规则管理配置请求携带所述业务规则所属系列，所述业务规则所属业务***，所述业务规则所属业务***版本号，所述业务规则引擎版本号和业务规则数据的版本状态；
    在所述业务规则信息表中查找与所述业务规则所属系列，所述业务规则所属业务***，所述业务规则所属业务***版本号，所述业务规则引擎版本号和所述业务规则数据的版本状态均对应的第二业务规则名称；
    将所述第二业务规则名称发送给与所述业务规则管理配置请求对应的第一终端，以使所述第一终端显示包含所述第二业务规则名称的业务规则管理配置界面；
    统计所述第二业务规则名称的个数；
    当所述个数大于一时，则接收所述第一终端发送的通过所述业务规则管理配置界面选择的第三业务规则名称；
    在所述业务规则信息表中查找所述第三业务规则名称对应的第三业务规则数据；
    将所述第三业务规则数据的第一预设格式转换成为第二预设格式。
  18. 根据权利要求16所述的非易失性可读存储介质，其特征在于，所述处理器还执行以下步骤：
    接收业务规则查询请求，所述接收业务规则下载请求携带所述业务规则所属系列，所述 业务规则所属业务***和所述业务规则所属业务***版本号；
    在所述业务规则信息表中查找与所述业务规则所属系列，所述业务规则所属业务***和所述业务规则所属业务***版本号均对应的第四业务规则名称；
    将所述第四业务规则名称发送给与所述业务规则查询请求对应的第二终端，以使所述第二终端显示包含所述第四业务规则名称的业务规则下载界面；
    接收业务规则下载请求，所述业务规则下载请求携带通过所述业务规则下载界面从所述第四业务规则名称中选择的第五业务规则名称；
    在所述业务规则信息表中查找与所述第五业务规则名称对应的第五业务规则数据；
    将所述第五业务规则数据发送给所述业务规则所属业务***名称对应的业务***开发环境。
  19. 根据权利要求16所述的非易失性可读存储介质，其特征在于，所述处理器还执行以下步骤：
    接收业务规则发布请求，所述业务规则发布请求携带所述业务规则所属业务***版本号；
    获取所述业务规则所属业务***版本号对应的第六业务规则数据；
    在所述业务规则信息表中查找与所述业务规则所属业务***版本号对应的业务***的版本状态；
    当所述版本状态为开发状态时，则发送所述第六业务规则数据至所述业务规则所属业务***版本号对应的业务***测试环境，并设置所述第六业务规则数据的版本状态为测试状态；
    当所述版本状态为测试状态时，则发送所述第六业务规则数据至所述业务规则所属业务***版本号对应的业务***生产环境，并设置所述第六业务规则数据的版本状态为生产状态。
  20. 根据权利要求19所述的非易失性可读存储介质，其特征在于，所述处理器还执行以下步骤：
    当所述版本状态为生产状态时，则发送所述第六业务规则数据至与所述业务规则所属业务***版本号相差最近的业务规则所属业务***版本号对应的业务***生产环境。
PCT/CN2018/086302 2017-09-27 2018-05-10 业务规则管理方法、装置、存储介质和计算机设备 WO2019062132A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710888234.8A CN107797823B (zh) 2017-09-27 2017-09-27 业务规则管理方法、装置、存储介质和计算机设备
CN201710888234.8 2017-09-27

Publications (1)

Publication Number Publication Date
WO2019062132A1 true WO2019062132A1 (zh) 2019-04-04

Family

ID=61532100

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/086302 WO2019062132A1 (zh) 2017-09-27 2018-05-10 业务规则管理方法、装置、存储介质和计算机设备

Country Status (2)

Country Link
CN (1) CN107797823B (zh)
WO (1) WO2019062132A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107797823B (zh) * 2017-09-27 2020-01-17 平安科技（深圳）有限公司 业务规则管理方法、装置、存储介质和计算机设备
CN109284106A (zh) * 2018-07-18 2019-01-29 平安科技（深圳）有限公司 业务规则的发布管理方法、电子装置及可读存储介质
CN109783802A (zh) * 2018-12-13 2019-05-21 平安医疗健康管理股份有限公司 一种业务规则处理方法、服务器及计算机可读存储介质
CN111198863B (zh) * 2019-12-27 2023-06-20 天阳宏业科技股份有限公司 一种规则引擎及其实现方法
CN113065801A (zh) * 2021-04-26 2021-07-02 平安普惠企业管理有限公司 组织架构管理方法、装置、设备及存储介质
US11954458B2 (en) * 2022-04-26 2024-04-09 Accenture Global Solutions Limited Decision logic translation system and method

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102065066A (zh) * 2009-11-17 2011-05-18 ***通信集团广东有限公司 一种数据业务门户的数据业务内容访问装置及访问方法
CN102426579A (zh) * 2011-08-25 2012-04-25 中兴通讯股份有限公司 一种基于网络方式导入导出文件的方法
CN105426164A (zh) * 2014-09-04 2016-03-23 北大方正集团有限公司 一种数据的校验方法及浏览器、服务器
US20170039175A1 (en) * 2015-08-05 2017-02-09 Sap Se Method and system for an electronic document framework
CN107797823A (zh) * 2017-09-27 2018-03-13 平安科技（深圳）有限公司 业务规则管理方法、装置、存储介质和计算机设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8966442B2 (en) * 2011-01-13 2015-02-24 Sap Se Custom code innovation management
CN103019726B (zh) * 2012-12-19 2016-08-10 中国电子科技集团公司第十五研究所 软件***业务规则的管理方法和装置
CN103793223A (zh) * 2013-12-27 2014-05-14 远光软件股份有限公司 一种规则创建方法及***
CN107122220A (zh) * 2017-04-12 2017-09-01 上海前隆金融信息服务有限公司 规则引擎的组建方法/***、业务管理方法/***及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102065066A (zh) * 2009-11-17 2011-05-18 ***通信集团广东有限公司 一种数据业务门户的数据业务内容访问装置及访问方法
CN102426579A (zh) * 2011-08-25 2012-04-25 中兴通讯股份有限公司 一种基于网络方式导入导出文件的方法
CN105426164A (zh) * 2014-09-04 2016-03-23 北大方正集团有限公司 一种数据的校验方法及浏览器、服务器
US20170039175A1 (en) * 2015-08-05 2017-02-09 Sap Se Method and system for an electronic document framework
CN107797823A (zh) * 2017-09-27 2018-03-13 平安科技（深圳）有限公司 业务规则管理方法、装置、存储介质和计算机设备

Also Published As

Publication number Publication date
CN107797823B (zh) 2020-01-17
CN107797823A (zh) 2018-03-13

Similar Documents

Publication Publication Date Title
WO2019062132A1 (zh) 业务规则管理方法、装置、存储介质和计算机设备
US9983924B2 (en) Analytics platform for automated diagnosis, remediation, and proactive supportability
CN111158674B (zh) 组件管理方法、***、设备及存储介质
CN107368503B (zh) 基于Kettle的数据同步方法和***
US9356966B2 (en) System and method to provide management of test data at various lifecycle stages
CN114327678B (zh) 一种支持多引擎的实时数据处理***及方法
US8782609B2 (en) Test failure bucketing
US10324710B2 (en) Indicating a trait of a continuous delivery pipeline
CN108763091B (zh) 用于回归测试的方法、装置及***
US20140006459A1 (en) Rule-based automated test data generation
CN109032631B (zh) 应用程序补丁包获取方法、装置、计算机设备及存储介质
CN109445837B (zh) 一种应用程序的发布方法及设备
CN103514223A (zh) 一种数据仓库数据同步方法和***
CN112835924A (zh) 实时计算任务处理方法、装置、设备及存储介质
CN111737140A (zh) 接口自动化测试方法、装置、设备及计算机可读存储介质
CN111124872A (zh) 基于差异代码分析的分支检测方法、装置及存储介质
US20230259358A1 (en) Documentation enforcement during compilation
US9411618B2 (en) Metadata-based class loading using a content repository
CN110543427B (zh) 测试用例存储方法、装置、电子设备及存储介质
US20070245313A1 (en) Failure tagging
CN110502242B (zh) 代码自动生成方法、装置、计算机设备及存储介质
CN113495723B (zh) 一种调用功能组件的方法、装置及存储介质
US20150033213A1 (en) Compiling method, storage medium and compiling apparatus
US11256602B2 (en) Source code file retrieval
CN111400243B (zh) 基于流水线服务的研发管理***以及文件存储方法、装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18863562

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 28.09.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18863562

Country of ref document: EP

Kind code of ref document: A1