WO2019000963A1 - 业务系统预先稽查方法、服务器及计算机可读存储介质 - Google Patents

业务系统预先稽查方法、服务器及计算机可读存储介质 Download PDF

Info

Publication number
WO2019000963A1
WO2019000963A1 PCT/CN2018/076187 CN2018076187W WO2019000963A1 WO 2019000963 A1 WO2019000963 A1 WO 2019000963A1 CN 2018076187 W CN2018076187 W CN 2018076187W WO 2019000963 A1 WO2019000963 A1 WO 2019000963A1
Authority
WO
WIPO (PCT)
Prior art keywords
code
released
rolled back
needs
previous version
Prior art date
Application number
PCT/CN2018/076187
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 WO2019000963A1 publication Critical patent/WO2019000963A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/362—Software debugging
    • G06F11/3628—Software debugging of optimised code
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • 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

Definitions

  • the present application relates to the field of system troubleshooting, and in particular, to a business system pre-inspection method, a server, and a computer readable storage medium.
  • the business system of the enterprise internal application will continuously introduce new business functions. When the coverage of new functions is insufficient, it is difficult to find faults and performance problems. Once a large-scale application is promoted, such as an exception, it takes a lot of time to troubleshoot the problem. Even if the rollback version restarts the service, due to the influence of the associated system and database, the system may not be restarted in time, which may lead to internal normal work. paralysis. Therefore, there is a need for a system and method for performing fault auditing and testing operations before a new version of an enterprise business system is released, so as to reduce the risk of system anomalies after the new version is launched, or to complete the failure if the new version is online. Roll back the version to reduce the impact of the failure.
  • the present application provides a business system pre-inspection method, a server, and a computer-readable storage medium, which can roll back the service system to be released to the previous version, and pre-inspect the abnormal risk caused by the system, and reduce the to-be-released
  • the fault occurs, or if the fault occurs after the new version is online, the rollback version can be quickly completed to reduce the impact of the fault.
  • a first aspect of the present application provides a business system pre-inspection method, the method comprising the following steps:
  • the service system to be released determines whether the service system to be released has an associated system; if there is an associated system, the service system to be released is determined when the service system to be released needs to be rolled back to the previous version according to the pre-stored record file. Whether the associated system needs to be rolled back to the previous version, and/or, according to the pre-stored record file, whether the business system to be released needs to be rolled back to the related system when the related system of the business system to be released needs to be rolled back to the previous version. Previous version;
  • the first alert is issued to prompt the user to remind the business system to be released and/or its associated system to be rolled back to the rollback to Previous version.
  • a second aspect of the present application further provides a server, where the server includes a memory, a processor, and a service system pre-inspection system stored on the processor and operable on the processor, the service system pre-inspecting the system
  • the server includes a memory, a processor, and a service system pre-inspection system stored on the processor and operable on the processor, the service system pre-inspecting the system
  • the first alert is sent to the user to remind the business system to be released and/or its associated system to be rolled back. Scroll to the previous version.
  • a third aspect of the present application further provides a computer readable storage medium storing a business system pre-audit program, the business system pre-audit program being executable by at least one processor So that at least one processor performs the following steps:
  • the first alert is sent to the user to remind the business system to be released and/or its associated system to be rolled back. Scroll to the previous version.
  • the business system pre-inspection method, the server, and the computer-readable storage medium proposed by the present application may be rolled back after the upgrade version is released through a unified specification before the upgrade version of the service system is released.
  • the existing problems are tested one by one, and the warnings are sent to remind the user to make corresponding modifications.
  • the risk of system anomalies after the new version is released in the prior art can be reduced, and the rollback version can be quickly completed if the failure occurs after the new version is put on the line, thereby reducing the impact of the failure.
  • FIG. 1 is a hardware architecture diagram of a preferred embodiment of a server of the present application
  • FIG. 2 is a functional block diagram of a preferred embodiment of the business system pre-inspection system of the present application
  • FIG. 3 is a functional block diagram of another preferred embodiment of the pre-inspection system of the business system of the present application.
  • FIG. 4 is a sub-function block diagram of the code inspection module of FIG. 3;
  • FIG. 5 is a flow chart of a preferred embodiment of a pre-inspection method of the business system of the present application.
  • FIG. 6 is a flow chart of another preferred embodiment of the pre-inspection method of the service system of the present application.
  • first, second and the like in the present application are for the purpose of description only, and are not to be construed as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. .
  • features defining “first” and “second” may include at least one of the features, either explicitly or implicitly.
  • the technical solutions between the various embodiments may be combined with each other, but must be based on the realization of those skilled in the art, and when the combination of the technical solutions is contradictory or impossible to implement, it should be considered that the combination of the technical solutions does not exist. Nor is it within the scope of protection required by this application.
  • the server 1 may include, but is not limited to, a memory 11, a processor 12, a network interface 13, and a display 14 that are communicably coupled to each other through a system bus. It is to be noted that Figure 1 shows only server 1 with components 11-14, but it should be understood that not all illustrated components may be implemented and that more or fewer components may be implemented instead.
  • the memory 11 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (for example, SD or DX memory, etc.), a random access memory (RAM), and a static random access.
  • Memory SRAM
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • PROM programmable read only memory
  • magnetic memory magnetic disk, optical disk, and the like.
  • the memory 11 may be an internal storage unit of the server 1, such as the hard disk or memory of the server 1.
  • the memory 11 may also be an external storage device of the server 1, such as a plug-in hard disk equipped on the server 1, a smart memory card (SMC), and a Secure Digital (SD) card. , Flash Card, etc.
  • the memory 11 can also include both the internal storage unit of the server 1 and its external storage device.
  • the memory 11 is generally used to store an operating system installed on the server 1 and various types of application software, such as a program code of a business system (APP) to be released, and a business system pre-inspection system 200 (APP) of the present application. Program code, program code of the associated system (APP), and various audit rules, specifications, templates, etc. Further, the memory 11 can also be used to temporarily store various types of data that have been output or are to be output.
  • Processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments.
  • the processor 12 is typically used to control the overall operation of the server 1.
  • the processor 12 is configured to run program code or process data stored in the memory 11, such as a code of a running business system pre-audit program.
  • the network interface 13 may include a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the server 2 and other electronic devices.
  • the display 14 can be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch sensor, or the like.
  • the display 14 is for displaying information processed in the server 1 and a user interface for displaying visualizations and the like. In this embodiment, the display 14 is used to display the audit result information of the business system pre-audit system 200, and display the operation that prompts the user to perform next.
  • the server 1 may not include the display 14, but display the audit result information of the business system pre-audit system 200 through the display device communicatively connected with the server 1, and display the prompt user. The next step should be performed, etc.
  • the present application proposes a business system pre-audit system 200.
  • FIG. 2 it is a functional block diagram of an embodiment of the business system pre-inspection system 200 of the present application.
  • the business system pre-audit system 200 can be partitioned into one or more modules, one or more modules being stored in the memory 11 and by one or more processors (the processor in this embodiment) 12) Executed to complete the application.
  • the business system pre-inspection system 200 can be divided into a first judging module 201, a first alerting module 202, a second judging module 203, and a second alerting module 204.
  • the functional modules referred to in the present application refer to a series of computer program instruction segments capable of performing a specific function, and are more suitable than the program to describe the execution process of the business system pre-audit system 200 in the server 1.
  • the functions of the function modules 201-204 will be described in detail below.
  • the first judging module 201 is configured to determine, according to the pre-stored record file, whether the service system to be published has an associated system; if there is an associated system, determine, according to the pre-stored record file, that the service system to be released needs to be rolled back to the previous version. Whether the associated system of the service system to be released needs to be rolled back to the previous version, and/or, according to the pre-stored record file, the service to be released when the associated system of the service system to be released needs to be rolled back to the previous version. Whether the system needs to roll back to the previous version.
  • the developer evaluates and determines the associated system of the business system to be released according to the needs of the business, and in the process of developing and meeting the business requirements, according to the actual The development needs to evaluate whether the corresponding associated system needs to be modified, and records the associated system of the business system to be released and the associated system that needs to be modified, and pre-existing in the log file of the business system to be released.
  • the business system pre-inspection method of the present application before the installation and use of the business system to be released (the new version of the installed business system), it is necessary to determine whether there is an associated system through the first judgment module, and if it is determined that it is associated The system then tests whether the associated system is rolled back to the previous version, whether the service system to be released is faulty, and whether the service system to be released is rolled back to the previous version, and the associated system of the service system to be released is faulty. .
  • the service system to be advertised is rolled back to the previous version, the associated system is faulty, indicating that the associated system needs to roll back to the previous version when the service system to be advertised is rolled back to the previous version. If the associated system is rolled back to the previous version, the service system to be advertised is faulty. The service system to be released needs to be rolled back to the previous version when the associated system is rolled back to the previous version.
  • the first warning module 202 is configured to roll back to the previous version in the service system to be released and/or its associated system, and issue a first alert to prompt the user to remind the business system to be released that needs to be rolled back and/or The associated system rolls back to the previous version.
  • the user of the business system to be released and its associated system development and testing personnel will test the published business system and its associated system, and propose modifications.
  • the service system to be released is rolled back to the previous version.
  • the associated system of the service system to be released is not rolled back to the previous version, or the associated system of the service system to be released is rolled back to the previous version.
  • the modification is proposed until the test system that is to be released and any of its associated systems are rolled back to the previous version, and the other one is rolled back to the previous version.
  • the test passes.
  • the second judging module 203 is configured to determine, according to the pre-stored record file, whether the service system to be released is rolled back to the previous version, and whether the database script corresponding to the service system to be released needs to be rolled back to the previous version.
  • the database script includes DDL, DML, package, and the like.
  • the database script is also adaptively modified, for example, the DML and the package statement are modified, and the modified DML and package statements may be modified.
  • the old version has an impact, so you need to determine whether the database script needs to be rolled back to the previous version if the business system to be released is rolled back to the previous version, that is, the old version.
  • the second alert module 204 is configured to: when the service system to be released is rolled back to the previous version, the database script needs to roll back to the previous version, and issue a second alert to prompt the user.
  • the user needs to write the script that needs to be rolled back in advance and save it in the service system to be released. If an abnormality occurs in the online operation of the service system to be released, it needs to be rolled back. At that time, you can directly provide a stored script that needs to be rolled back in advance to operate. This program requires the tester to pass the test and pass it before it can be used.
  • the above is a functional block diagram of a preferred embodiment of the pre-inspection system of the business system of the present application. It should be noted that in other embodiments of the present application, more or fewer components may be implemented instead. For example, only the first determining module 201 and the first alerting module 202 can be selectively implemented.
  • the pre-audit method of the service system of the present application first determines whether the service system to be released has an associated system according to the pre-stored record file; if there is an associated system, judges the service system to be released according to the pre-stored record file.
  • FIG. 3 it is a functional block diagram of another embodiment of the business system pre-inspection system 200 of the present application.
  • the business system pre-inspection system 200 of the present application can be further divided into a code inspection module 301, a third alert module 302, and a fourth alert on the basis of the functional modules shown in FIG.
  • the business system pre-inspection system 200 shown in FIG. 3 includes the various functional modules shown in FIG. 2, but the various functional modules shown in FIG. 2 are not shown in FIG. 3 for convenience of display.
  • the code auditing module 301 can be divided into a code auditing unit 401 and a code security detecting unit 402 as shown in FIG.
  • the code checking unit 401 is configured to check whether the code of the business system to be released conforms to a preset code specification, or to automatically adjust the code in the business system that does not meet the preset code specification to be consistent according to the preset code specification.
  • the format of the code specification is configured to check whether the code of the business system to be released conforms to a preset code specification, or to automatically adjust the code in the business system that does not meet the preset code specification to be consistent according to the preset code specification.
  • the code security detecting unit 502 is configured to check whether a code of a business system to be released has a security vulnerability.
  • the third alert module 302 is configured to issue a third alert to the user when the code auditing module 301 finds a code that does not conform to the preset code specification.
  • the fourth alert module 303 is configured to issue a fourth alert to the user when the code security detecting unit 502 checks that a security vulnerability is found.
  • the database auditing module 304 is configured to check whether the new function added by the business system to be released has an impact on the existing data of the database.
  • the fifth alert module 305 is configured to issue a fifth alert to the user when the database auditing module 304 checks that the new function added by the service system to be released has an impact on the database.
  • the analysis module 306 is configured to analyze the impact of the business system to be released on the database and the SQL statement. Specifically, it includes evaluating the performance impact of newly added tables, newly added and/or changed indexes on the database, checking whether the newly added SQL statements conform to the syntax specification of the SQL statement, and whether the newly added SQL statement causes the database to be full. Whether the table scan statement, the newly added SQL statement has a statement that causes an implicit conversion.
  • the way to evaluate the performance impact of newly added tables, new and/or changed indexes on the database in the database is to pass the DDL scripts through the system parsing the new version.
  • the sixth alert module 307 is configured to: when the analysis module 306 finds that there is an index added change and a new table, and sends a sixth alert to prompt the user.
  • a further assessment is made.
  • the change of the index automatically submits the signing process to notify the DBA to perform the index impact evaluation.
  • the newly added SQL statement conforms to the syntax specification of the SQL statement, whether there is a statement in the newly added SQL statement that causes a full table scan of the database, and whether there is an implicit conversion in the newly added SQL statement.
  • the method adopted by the statement is that the system scans the script in the database of the test environment, and finds that the test phase has implicit conversion and full table scan through email reminder processing, and then manually modified.
  • the first warning to the sixth warning are both displaying the inspection result information through the display interface, prompting the user to perform the next operation; and/or sending the mail or information to the preset user notification inspection result information.
  • the third alert and the fourth alert further include a specific location of the code indicating the problem.
  • the fifth alert and the sixth alert also include a newly added table that affects data performance, an index of new and/or changed, and a statement that causes a full table scan or implicit conversion of the database.
  • the business system pre-inspection system of the present application runs on the basis of the embodiment described in FIG. 2, further examines the code and database of the publishing service system 200, and analyzes the business system pair to be released.
  • the business system pre-inspection method of the present application includes step S501 and step S504.
  • Step S501 determining, according to the pre-stored record file, whether the service system to be published has an associated system; if there is an associated system, determining, according to the pre-stored record file, the service to be released when the service system to be released needs to be rolled back to the previous version. Whether the system's associated system needs to be rolled back to the previous version, and/or, based on the pre-stored record file, whether the service system to be released needs to be rolled back when the associated system of the service system to be released needs to be rolled back to the previous version. To the previous version.
  • the developer evaluates and determines the associated system of the business system to be released according to the needs of the business, and in the process of developing and meeting the business requirements, according to the actual The development needs to evaluate whether the corresponding associated system needs to be modified, and records the associated system of the business system to be released and the associated system that needs to be modified, and pre-existing in the business system to be released.
  • the service system to be released (the new version of the installed service system) needs to be tested before the installation of the service system to be rolled back to the previous version.
  • the service system to be released will be faulty and tested.
  • the published service system is rolled back to the previous version, and the associated system of the business system to be released will fail.
  • the service system to be advertised is rolled back to the previous version, the associated system is faulty, indicating that the associated system needs to roll back to the previous version when the service system to be advertised is rolled back to the previous version. If the associated system is rolled back to the previous version, the service system to be advertised is faulty. The service system to be released needs to be rolled back to the previous version when the associated system is rolled back to the previous version.
  • step S502 if the service system to be released and/or its associated system needs to roll back to the previous version, the first alert is sent to prompt the user to remind the service system to be released and/or its associated system to be rolled back. To the previous version.
  • the user of the business system to be released and its associated system development and testing personnel will test the published business system and its associated system, and propose modifications.
  • the service system to be released is rolled back to the previous version.
  • the associated system of the service system to be released is not rolled back to the previous version, or the associated system of the service system to be released is rolled back to the previous version.
  • the modification is proposed until the test system that is to be released and any of its associated systems are rolled back to the previous version, and the other one is rolled back to the previous version.
  • the test passes.
  • Step S503 According to the pre-stored record file, it is determined whether the database system to be released is rolled back to the previous version, and whether the database script needs to be rolled back to the previous version.
  • the database script includes DDL, DML, package, and the like.
  • the database script is also adaptively modified, for example, the DML and the package statement are modified, and the modified DML and package statements may be modified.
  • the old version has an impact. Therefore, it is necessary to determine whether the database system to be released is rolled back to the previous version, that is, the old version, whether the database script needs to be rolled back to the previous version.
  • Step S504 if it is determined that the database system to be released is rolled back to the previous version, and the database script needs to roll back to the previous version, a second alert is issued to prompt the user.
  • the user needs to write the script that needs to be rolled back in advance and save it in the service system to be released. If an abnormality occurs in the online operation of the service system to be released, it needs to be rolled back. At that time, you can directly provide a stored script that needs to be rolled back in advance to operate. This program requires the tester to pass the test and pass it before it can be used.
  • FIG. 6 is a schematic flowchart showing an implementation process of another embodiment of the pre-inspection method of the business system of the present application. As shown in FIG. 6, in the embodiment, the business system pre-inspection method includes steps S601 to S606.
  • Step S601 Determine, according to the pre-stored record file, that the service system to be released is rolled back to the previous system, whether the associated system needs to be rolled back to the previous system, and/or its associated system is rolled back to the previous version, and the service to be released is to be released. Whether the system needs to roll back to the previous version; if the business system to be released and/or its associated system needs to roll back to the previous version, the first warning is issued to prompt the user.
  • the user of the business system to be released and its associated system development and testing personnel will test the published business system and its associated system, and propose modifications.
  • the service system to be released is rolled back to the previous version.
  • the associated system of the service system to be released is not rolled back to the previous version, or the associated system of the service system to be released is rolled back to the previous version.
  • the modification is proposed until the test system that is to be released and any of its associated systems are rolled back to the previous version, and the other one is rolled back to the previous version.
  • the test passes.
  • step S602 it is determined that the service system to be released is rolled back to the previous version, and whether the database script needs to be rolled back to the previous version; if the database script needs to be rolled back to the previous version, a second alert is issued to prompt the user.
  • the user needs to write the script that needs to be rolled back in advance and save it in the service system to be released. If an abnormality occurs in the online operation of the service system to be released, it needs to be rolled back. At that time, you can directly provide a stored script that needs to be rolled back in advance to operate. This program requires the tester to pass the test and pass it before it can be used.
  • Step S603 checking whether the code of the business system conforms to the preset code specification, and if the check finds that there is a code that does not conform to the code specification, issuing a third alert to prompt the user.
  • the code in the business system that does not meet the preset code specification may be automatically adjusted to a format conforming to the code specification according to a preset code specification.
  • step S604 it is checked whether there is a security vulnerability in the code of the service system to be issued. If the security breach is found, a fourth alert is issued to prompt the user.
  • Step S605 Check whether the new function added by the service system to be released has an impact on the existing data of the database, and if there is any impact, issue a fifth alert to prompt the user.
  • Step S606 analyzing whether the business system to be released has an impact on the database and the SQL statement; if there is an impact, issuing a sixth alert to prompt the user.
  • it includes evaluating the performance impact of newly added tables, newly added and/or changed indexes on the database, checking whether the newly added SQL statements conform to the syntax specification of the SQL statement, and whether the newly added SQL statement causes the database to be full. Whether the table scan statement, the newly added SQL statement has a statement that causes an implicit conversion.
  • the method of evaluating the performance of the newly added table, new and/or changed indexes in the database on the performance of the database is to transfer the DDL script through the system parsing the new version, if it is found that there are new changes to the index and new tables, A fifth alert is required to alert the user to the user for further evaluation after receiving the sixth alert.
  • the index change automatically submits the signing process to notify the DBA to perform the index impact evaluation. If there is an index impact, a bug modification is required.
  • steps S701 to S706 may be implemented simultaneously or in different orders, and the application does not stipulate the implementation sequence of each step.
  • the pre-inspection method of the service system of the present application pre-examines the faults that may be caused by the rollback of the service system to be issued, and finds out that the business system to be released may have a rollback. And automatically repair these problems or prompt the user to solve these problems through the display device; and check whether the program code of the business system itself to be issued is abnormal, and automatically adjust or mark the program code with abnormality. The user is prompted to make the modification through the display device; and the impact of the business system to be published on the database is checked, and the information that may cause the database to be faulty is prompted to be modified by the display device.
  • the risk of system anomalies after the new version is released in the prior art is reduced, or the rollback version can be quickly completed if the failure occurs after the new version is put on the line, thereby reducing the impact of the failure.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Abstract

一种业务系统预先稽查方法，该方法可以在业务系统的升级版本发布之前，通过统一的规范预先稽查升级版本发布后，需要回滚时可能会存在的问题，对存在的问题进行一一测试、排查、发出警示信息提醒用户进行相应的修改，降低了现有技术中新版本上线后系统异常的风险，或是在新版本上线后如发生故障可以快速完成回滚版本，降低故障导致的影响。

Description

业务系统预先稽查方法、服务器及计算机可读存储介质
本申请要求于2017年6月25日提交中国专利局、申请号为201710490423.X，发明名称为“业务系统预先稽查方法、服务器及计算机可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及系统故障排查领域，尤其涉及一种业务系统预先稽查方法、服务器及计算机可读存储介质。
背景技术
企业内部应用的业务系统会不断推出新的业务功能，当新功能的使用量覆盖度不够时，较难发现故障及性能问题。而一旦大范围推广应用，如出现异常，排除故障需要花费大量时间，即使回滚版本重启服务，但由于关联系统、数据库等的影响，可能导致无法及时重启系统，从而会导致企业内部正常工作陷入瘫痪。因此，需要一种系统及方法，可以在企业业务系统发布新版本前，进行故障稽查及测试运行，以降低新版本上线后系统异常的风险，或是在新版本上线后如果发生故障可以快速完成回滚版本，降低故障导致的影响。
发明内容
有鉴于此，本申请提出一种业务系统预先稽查方法、服务器及计算机可读存储介质，能够对待发布的业务系统回滚至前一版本，对系统引起的异常风险进行预先稽查，降低待发布的业务系统的新版本上线后，导致的故障发生，或是在新版本上线后如果发生故障可以快速完成回滚版本，降低故障导致的影响。
首先，为实现上述目的，本申请第一方面提出一种业务系统预先稽查方 法，该方法包括如下步骤：
A、根据预存的记录文件判断待发布的业务系统是否有关联系统；若有关联系统，则根据预存的记录文件判断在待发布的业务系统需要回滚至前一版本时，待发布的业务系统的关联系统是否需要回滚至前一版本，及/或，根据预存的记录文件判断在待发布的业务系统的关联系统需要回滚至前一版本时，待发布的业务系统是否需要回滚至前一版本；
B、若待发布的业务系统及/或其关联系统需要回滚至前一版本，则发出第一警示提示用户，提醒将需要回滚的待发布的业务系统及/或其关联系统回滚至前一版本。
此外，为实现上述目的，本申请第二方面还提供一种服务器，该服务器包括存储器、处理器及存储在存储器上并可在处理器上运行的业务系统预先稽查系统，该业务系统预先稽查系统被处理器执行时实现如下步骤：
根据预存的记录文件判断待发布的业务系统是否有关联系统；若有关联系统，则根据所述预存的记录文件判断在所述待发布的业务系统需要回滚至前一版本时，所述待发布的业务系统的关联系统是否需要回滚至前一版本，及/或，根据所述预存的记录文件判断在所述待发布的业务系统的关联系统需要回滚至前一版本时，所述待发布的业务系统是否需要回滚至前一版本；
若所述待发布的业务系统及/或其关联系统需要回滚至前一版本，则发出第一警示提示用户，提醒将需要回滚的所述待发布的业务系统及/或其关联系统回滚至前一版本。
进一步地，为实现上述目的，本申请第三方面还提供一种计算机可读存储介质，该计算机可读存储介质存储有业务系统预先稽查程序，该业务系统预先稽查程序可被至少一个处理器执行，以使至少一个处理器执行如下步骤：
根据预存的记录文件判断待发布的业务系统是否有关联系统；若有关联系统，则根据所述预存的记录文件判断在所述待发布的业务系统需要回滚至前一版本时，所述待发布的业务系统的关联系统是否需要回滚至前一版本， 及/或，根据所述预存的记录文件判断在所述待发布的业务系统的关联系统需要回滚至前一版本时，所述待发布的业务系统是否需要回滚至前一版本；
若所述待发布的业务系统及/或其关联系统需要回滚至前一版本，则发出第一警示提示用户，提醒将需要回滚的所述待发布的业务系统及/或其关联系统回滚至前一版本。
相较于现有技术，本申请所提出的业务系统预先稽查方法、服务器及计算机可读存储介质，可以在业务系统的升级版本发布之前，通过统一的规范预先稽查升级版本发布后，需要回滚时可能会存在的问题，对存在的问题进行一一测试，排查，发出警示信息提醒用户进行相应的修改。这样，既可以降低现有技术中新版本上线后系统异常的风险，也可以在新版本上线后如果发生故障可以快速完成回滚版本，降低故障导致的影响。
附图说明
图1是本申请的服务器一较佳实施例的硬件架构图；
图2是本申请业务系统预先稽查系统一较佳实施例的功能模块图；
图3是本申请业务系统预先稽查系统另一较佳实施例的功能模块图；
图4是图3中代码稽查模块的子功能模块图；
图5是本申请业务系统预先稽查方法的一较佳实施例的流程图；
图6是本申请业务系统预先稽查方法另一较佳实施例的流程图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。基于本申请中的实施例，本领 域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
需要说明的是，在本申请中涉及“第一”、“第二”等的描述仅用于描述目的，而不能理解为指示或暗示其相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。另外，各个实施例之间的技术方案可以相互结合，但是必须是以本领域普通技术人员能够实现为基础，当技术方案的结合出现相互矛盾或无法实现时应当认为这种技术方案的结合不存在，也不在本申请要求的保护范围之内。
参阅图1所示，是本申请的服务器一可选的硬件架构示意图。在本实施例中，服务器1可包括，但不仅限于，可通过系统总线相互通信连接的存储器11、处理器12、网络接口13及显示器14。需要指出的是，图1仅示出了具有组件11-14的服务器1，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
其中，存储器11至少包括一种类型的可读存储介质，可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如，SD或DX存储器等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁性存储器、磁盘、光盘等。在一些实施例中，存储器11可以是服务器1的内部存储单元，例如服务器1的硬盘或内存。在另一些实施例中，存储器11也可以是服务器1的外部存储设备，例如服务器1上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。当然，存储器11还可以既包括服务器1的内部存储单元也包括其外部存储设备。本实施例中，存储器11通常用于存储安装于服务器1的操作系统和各类应用软件，例如待发布的业务系统(APP)的程序代码、本申请的业务系统预先稽查系统200(APP)的程序代码、关联系统(APP)的程序代 码，以及各种稽查规则、规范、模板等资料。此外，存储器11还可以用于暂时地存储已经输出或者将要输出的各类数据。
处理器12在一些实施例中可以是中央处理器(Central Processing Unit，CPU)、控制器、微控制器、微处理器、或其他数据处理芯片。处理器12通常用于控制服务器1的总体操作。本实施例中，处理器12用于运行存储器11中存储的程序代码或者处理数据，例如运行的业务系统预先稽查程序的代码等。
网络接口13可包括无线网络接口或有线网络接口，网络接口13通常用于在服务器2与其他电子设备之间建立通信连接。
显示器14可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED(Organic Light-Emitting Diode，有机发光二极管)触摸器等。显示器14用于显示在服务器1中处理的信息以及用于显示可视化的用户界面等。在本实施例中，显示器14用于显示业务系统预先稽查系统200的稽查结果信息，及显示提示用户下一步应该执行的操作等。
需要说明的是，在本申请的另一些实施例中，服务器1可以不包括显示器14，而是通过与服务器1通信连接的显示装置显示业务系统预先稽查系统200的稽查结果信息，及显示提示用户下一步应该执行的操作等。
首先，本申请提出一种业务系统预先稽查系统200。
如图2所示，是本申请业务系统预先稽查系统200一实施例的功能模块图。在本实施例中，业务系统预先稽查系统200可以被分割成一个或多个模块，一个或者多个模块被存储于存储器11中，并由一个或多个处理器(本实施例中为处理器12)所执行，以完成本申请。例如，在图2中，业务系统预先稽查系统200可以被分割成第一判断模块201、第一警示模块202、第二判断模块203、及第二警示模块204。本申请所称的功能模块是指能够完成特定功能的一系列计算机程序指令段，比程序更适合于描述业务系统预先稽查系统200在服务器1中的执行过程。以下将就功能模块201-204的功能进行详细 描述。
第一判断模块201，用于根据预存的记录文件判断待发布的业务系统是否有关联系统；若有关联系统，则根据预存的记录文件判断在待发布的业务系统需要回滚至前一版本时，待发布的业务系统的关联系统是否需要回滚至前一版本，及/或，根据预存的记录文件判断在待发布的业务系统的关联系统需要回滚至前一版本时，待发布的业务系统是否需要回滚至前一版本。
通常，待发布的业务系统在业务方提出开发需求的时候，开发人员根据业务的需求会评估并确定出该待发布的业务系统的关联系统，且在开发满足业务需求的过程中，根据实际的开发需要会评估出相应的关联系统是否需要改造，并会将待发布的业务系统的关联系统及其需要改造的关联系统记录下来，并预存在待发布的业务系统的记录文件中。
本申请的业务系统预先稽查方法，在待发布的业务系统(已安装的业务系统的新版本)在安装使用前，需要通过第一判断模块，判断其是否有关联系统，若判断出其有关联系统，则测试其关联系统回滚至前一版本，待发布的业务系统是否会出现故障，及测试待发布的业务系统回滚至前一版本，待发布的业务系统的关联系统是否会出现故障。
若待发布的业务系统回滚至前一版本，其关联系统出现故障，说明其关联系统在待发布的业务系统回滚至前一版本时，需要回滚至前一版本。若其关联系统回滚至前一版本时，待发布的业务系统出现故障，说明在其关联系统回滚至前一版本时，待发布的业务系统需要回滚至前一版本。
第一警示模块202，用于在待发布的业务系统及/或其关联系统需要回滚至前一版本，发出第一警示提示用户，提醒将需要回滚的待发布的业务系统及/或其关联系统回滚至前一版本。
通常，用户在收到第一警示之后，待发布的业务系统及其关联系统的开发及测试人员，会对待发布的业务系统及其关联系统进行测试，及提出修改。并在测试到待发布的业务系统回滚至前一版本，待发布的业务系统的关联系 统没有回滚至前一版本，或待发布的业务系统的关联系统回滚至前一版本，待发布的业务系统没有回滚至前一版本时，提出修改意见，直到测试出待发布的业务系统及其关联系统中任意一个回滚至前一版本，另外一个也回滚至前一版本，并没有障碍时，测试通过。
第二判断模块203，用于根据预存的记录文件判断当待发布的业务系统回滚至前一版本，待发布业务系统对应的数据库脚本是否需要回滚至前一版本。
在本实施例中，数据库脚本包括DDL、DML、package等。
需要说明的是，由于待发布的业务系统中新增加了字段，相应地，数据库脚本也进行了适应性地修改，例如修改了DML、package语句等，而修改的DML、package语句有可能会对旧版本产生影响，因此需要判断若待发布的业务系统回滚至前一版本，也即旧版本时，数据库脚本是否需要回滚至前一版本。
第二警示模块204，用于当待发布的业务系统回滚至前一个版本，数据库脚本需要回滚至前一版本，发出第二警示提示用户。
通常，用户在收到第二警示之后，需要开发人员提前把需要回滚的脚本写好，并存入待发布的业务系统中，如果在待发布的业务系统上线运行中出现异常，需要回滚时，可以直接提供存储的提前写好的需要回滚的脚本进行运营。此方案需要测试人员测试验证通过之后，才可使用。
以上是本申请业务系统预先稽查系统一较佳实施例的功能模块图。需要说明的是，在本申请的另一些实施例中，可以替代的实施更多或更少的组件。例如，可以选择性地只实施第一判断模块201及第一警示模块202。
通过上述实施例可知，本申请的业务系统预先稽查方法，首先，根据预存的记录文件判断待发布的业务系统是否有关联系统；若有关联系统，根据预存的记录文件判断当待发布的业务系统、或其关联系统二者任意一个回滚至前一版本，另外一个系统是否也需要回滚至前一版本；然后，当待发布的业务系统、或其关联系统二者任意一个回滚至前一版本，另外一个系统也需 要回滚至前一版本，发出第一警示提示用户；再次，根据预存的记录文件判断当待发布的业务系统回滚至前一版本，数据库脚本是否需要回滚至前一版本；最后，当待发布的业务系统回滚至前一个版本，数据库脚本需要回滚至前一版本，发出第二警示提示用户。这样，既可以降低现有技术中新版本上线后系统异常的风险，也可以在新版本上线后如果发生故障可以快速完成回滚版本，降低故障导致的影响。
如图3所示，为本申请的业务系统预先稽查系统200的另一实施例的功能模块图。由图3可知，在本实施例中，本申请的业务系统预先稽查系统200在图2所示的功能模块的基础上还可被分割为代码稽查模块301、第三警示模块302、第四警示模块303、数据库稽查模块304、第五警示模块305、分析模块306、及第六警示模块307。需要说明的是，图3所示的业务系统预先稽查系统200包含了图2所示的各个功能模块，但是为了显示方便，将图2所示的各个功能模块在图3中未示出。
代码稽查模块301，可被分为如图4所示的代码稽查单元401及代码安全性检测单元402。代码稽查单元401,用于检查待发布的业务系统的代码是否符合预先设置的代码规范、或用于根据预先设置的代码规范，将业务系统中不符合预先设置的代码规范的代码自动调整成符合代码规范的格式。
代码安全性检测单元502，用于检查待发布的业务系统的代码是否存在安全性漏洞。
第三警示模块302，用于在代码稽查模块301发现有不符合预先设置的代码规范的代码时，发出第三警示提示用户。
第四警示模块303，用于在代码安全性检测单元502检查发现存在安全性漏洞时，发出第四警示提示用户。
数据库稽查模块304，用于检查待发布的业务系统增加的新功能对数据库已有的数据是否有影响。
第五警示模块305，用于在数据库稽查模块304检查出待发布的业务系统 增加的新功能对数据库有影响时，则发出第五警示提示用户。
分析模块306，用于分析待发布的业务系统对数据库及SQL语句的影响。具体包括评估数据库中新增加的表、新增及/或变更的索引对数据库的性能影响，检查新增加的SQL语句是否符合SQL语句的语法规范、新增加的SQL语句中是否有会引起数据库全表扫描的语句、新增加的SQL语句中是否有会引起隐式转换的语句。
通常，评估数据库中新增加的表、新增及/或变更的索引对数据库的性能影响采用的方法是，通过系统解析新版本移交DDL脚本。
第六警示模块307，用于在分析模块306发现有索引新增变更和新增表的，发出第六警示提示用户。
通常，用户收到第六警示之后，进行进一步的评估。索引的变更自动提交签报流程通知DBA进行索引影响度评估，评估出有索引影响时则需要提出bug修改。
需要说明的是，检查新增加的SQL语句是否符合SQL语句的语法规范、新增加的SQL语句中是否有会引起数据库全表扫描的语句、新增加的SQL语句中是否有会引起隐式转换的语句采用的方法是，通过系统在测试环境的数据库中进行脚本扫描，发现测试阶段有隐式转换的和全表扫描的通过邮件提醒处理，然后人工进行修改。
在本实施例中，第一警示至第六警示均是通过显示界面显示稽查结果信息，提示用户下一步应该执行的操作；及/或发送邮件或信息至预先设定的用户通知稽查结果信息。其中，第三警示和第四警示还包括，标示有问题的代码的具体位置。第五警示和第六警示还包括，标示会影响数据性能的新增加的表、新增及/或变更的索引，以及会引起数据库全表扫描或隐式转换的语句。
通过上述事实例可知，运行本申请的业务系统预先稽查系统，在图2所述实施例的基础上，进一步对待发布业务系统200的代码及数据库进行了稽查，并分析了待发布的业务系统对数据库就SQL语句的影响。从而，进一步地降低 了新版本上线后系统异常的风险，或是在新版本上线后如果发生故障可以快速完成回滚版本，降低故障导致的影响。
如图5所示，是本申请业务系统预先稽查方法的一实施例的实施流程示意图。由图5可知，在本实施例中，本申请的业务系统预先稽查方法包括步骤S501和步骤S504。
步骤S501，根据预存的记录文件判断待发布的业务系统是否有关联系统；若有关联系统，则根据预存的记录文件判断在待发布的业务系统需要回滚至前一版本时，待发布的业务系统的关联系统是否需要回滚至前一版本，及/或，根据预存的记录文件判断在待发布的业务系统的关联系统需要回滚至前一版本时，待发布的业务系统是否需要回滚至前一版本。
通常，待发布的业务系统在业务方提出开发需求的时候，开发人员根据业务的需求会评估并确定出该待发布的业务系统的关联系统，且在开发满足业务需求的过程中，根据实际的开发需要会评估出相应的关联系统是否需要改造，并会将待发布的业务系统的关联系统及其需要改造的关联系统记录下来，并预存在待发布的业务系统中。
待发布的业务系统(已安装的业务系统的新版本)在安装使用前，需要测试待发布的业务系统的关联系统回滚至前一版本，待发布的业务系统是否会出现故障，及测试待发布的业务系统回滚至前一版本，待发布的业务系统的关联系统是否会出现故障。
若待发布的业务系统回滚至前一版本，其关联系统出现故障，说明其关联系统在待发布的业务系统回滚至前一版本时，需要回滚至前一版本。若其关联系统回滚至前一版本时，待发布的业务系统出现故障，说明在其关联系统回滚至前一版本时，待发布的业务系统需要回滚至前一版本。
步骤S502，若待发布的业务系统及/或其关联系统需要回滚至前一版本，则发出第一警示提示用户，提醒将需要回滚的待发布的业务系统及/或其关联系统回滚至前一版本。
通常，用户在收到第一警示之后，待发布的业务系统及其关联系统的开发及测试人员，会对待发布的业务系统及其关联系统进行测试，及提出修改。并在测试到待发布的业务系统回滚至前一版本，待发布的业务系统的关联系统没有回滚至前一版本，或待发布的业务系统的关联系统回滚至前一版本，待发布的业务系统没有回滚至前一版本时，提出修改意见，直到测试出待发布的业务系统及其关联系统中任意一个回滚至前一版本，另外一个也回滚至前一版本，并没有障碍时，测试通过。
步骤S503，根据预存的记录文件判断当待发布的业务系统回滚至前一版本，数据库脚本是否需要回滚至前一版本。
在本实施例中，数据库脚本包括DDL、DML、package等。
需要说明的是，由于待发布的业务系统中新增加了字段，相应地，数据库脚本也进行了适应性地修改，例如修改了DML、package语句等，而修改的DML、package语句有可能会对旧版本产生影响，因此需要判断待发布的业务系统回滚至前一版本，也即旧版本时，数据库脚本是否需要回滚至前一版本。
步骤S504，若判断当所述待发布的业务系统回滚至前一个版本，数据库脚本需要回滚至前一版本，则发出第二警示提示用户。
通常，用户在收到第二警示之后，需要开发人员提前把需要回滚的脚本写好，并存入待发布的业务系统中，如果在待发布的业务系统上线运行中出现异常，需要回滚时，可以直接提供存储的提前写好的需要回滚的脚本进行运营。此方案需要测试人员测试验证通过之后，才可使用。
如图6所示，是本申请业务系统预先稽查方法另一实施例的实施流程示意图。如图6所示，在本实施例中，业务系统预先稽查方法包括步骤S601至步骤S606。
步骤S601，根据预存的记录文件判断待发布的业务系统回滚至前一系统，其关联系统是否需要回滚至前一系统、及/或其关联系统回滚至前一版本，待发布的业务系统是否需要回滚至前一版本；若待发布的业务系统及/或其关联 系统需要回滚至前一版本，则发出第一警示提示用户。
通常，用户在收到第一警示之后，待发布的业务系统及其关联系统的开发及测试人员，会对待发布的业务系统及其关联系统进行测试，及提出修改。并在测试到待发布的业务系统回滚至前一版本，待发布的业务系统的关联系统没有回滚至前一版本，或待发布的业务系统的关联系统回滚至前一版本，待发布的业务系统没有回滚至前一版本时，提出修改意见，直到测试出待发布的业务系统及其关联系统中任意一个回滚至前一版本，另外一个也回滚至前一版本，并没有障碍时，测试通过。
步骤S602，判断待发布的业务系统回滚至前一版本，是否有数据库脚本需要回滚至前一版本；若有数据库脚本需要回滚至前一版本，则发出第二警示提示用户。
通常，用户在收到第二警示之后，需要开发人员提前把需要回滚的脚本写好，并存入待发布的业务系统中，如果在待发布的业务系统上线运行中出现异常，需要回滚时，可以直接提供存储的提前写好的需要回滚的脚本进行运营。此方案需要测试人员测试验证通过之后，才可使用。
步骤S603，检查业务系统的代码是否符合预先设置的代码规范，若检查发现有不符合代码规范的代码，则发出第三警示提示用户。
需要说明的是，在其他一些实施例中，可根据预先设置的代码规范，将业务系统中不符合预先设置的代码规范的代码自动调整成符合代码规范的格式。
步骤S604，检查待发布的业务系统的代码是否存在安全性漏洞，若检查发现存在安全性漏洞，则发出第四警示提示用户。
步骤S605，检查待发布的业务系统增加的新功能对数据库已有的数据是否有影响，若有影响，则发出第五警示提示用户。
步骤S606，分析待发布的业务系统对数据库及SQL语句是否有影响；若有影响，则发出第六警示提示用户。
具体包括评估数据库中新增加的表、新增及/或变更的索引对数据库的性能影响，检查新增加的SQL语句是否符合SQL语句的语法规范、新增加的SQL语句中是否有会引起数据库全表扫描的语句、新增加的SQL语句中是否有会引起隐式转换的语句。
通常，评估数据库中新增加的表、新增及/或变更的索引对数据库的性能影响采用的方法是，通过系统解析新版本移交DDL脚本，如发现有索引新增变更和新增表的，需要发出第五警示提醒用户，用户收到第六警示之后，进行进一步的评估。索引的变更自动提交签报流程通知DBA进行索引影响度评估，有索引影响则需要提出bug修改。
检查新增加的SQL语句是否符合SQL语句的语法规范、新增加的SQL语句中是否有会引起数据库全表扫描的语句、新增加的SQL语句中是否有会引起隐式转换的语句采用的方法是，通过系统在测试环境的数据库中进行脚本扫描，发现测试阶段有隐式转换的和全表扫描的通过邮件提醒处理，然后人工进行修改。
需要说明的是，上述步骤S701至步骤S706可以同时实施，也可以按不同的顺序实施，本申请并没有规定各步骤的实施顺序。
通过实施上述的实施例可知，本申请的业务系统预先稽查方法，通过对待发布的业务系统的回滚可能引起的故障进行预先稽查，找出待发布的业务系统若发生回滚可能会存在的问题，并对这些问题进行自动修复或是通过显示装置提示用户对这些问题进行解决；及通过对待发布的业务系统自身的程序代码是否有异常进行稽查，并对有异常的程序代码进行自动调整或者标示出来通过显示装置提示用户进行修改；及通过对待发布的业务系统对数据库的影响进行稽查，并把可能导致数据库出现故障的信息通过显示装置提示用户进行修改。降低了现有技术中新版本上线后系统异常的风险，或是在新版本上线后如发生故障可以快速完成回滚版本，降低故障导致的影响。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围。

Claims (20)

  1. 一种业务系统预先稽查方法，其特征在于，所述方法包括如下步骤：
    A、根据预存的记录文件判断待发布的业务系统是否有关联系统；若有关联系统，则根据所述预存的记录文件判断在所述待发布的业务系统需要回滚至前一版本时，所述待发布的业务系统的关联系统是否需要回滚至前一版本，及/或，根据所述预存的记录文件判断在所述待发布的业务系统的关联系统需要回滚至前一版本时，所述待发布的业务系统是否需要回滚至前一版本；
    B、若所述待发布的业务系统及/或其关联系统需要回滚至前一版本，则发出第一警示提示用户，提醒将需要回滚的所述待发布的业务系统及/或其关联系统回滚至前一版本。
  2. 如权利要求1所述的业务系统预先稽查方法，其特征在于，所述方法还包括：
    若所述待发布的业务系统需要回滚至前一版本，则根据所述预存的记录文件判断所述待发布的业务系统对应的数据库脚本是否需要回滚至前一版本；
    若所述待发布的业务系统对应的数据库脚本需要回滚至前一版本，则发出第二警示提示用户，提醒将需要回滚的所述待发布的业务系统对应的数据库脚本回滚至前一版本。
  3. 如权利要求1所述的业务系统预先稽查方法，其特征在于，所述方法还包括业务系统代码稽查步骤，所述业务系统代码稽查步骤包括：
    检查所述待发布的业务系统的代码是否符合预先设置的代码规范，若检查发现有不符合所述预先设置的代码规范的代码，则发出第三警示提示用户，提醒将不符合所述预先设置的代码规范的代码进行修改；
    检查所述待发布的业务系统的代码是否存在安全性漏洞，若检查发现所述待发布的业务系统的代码存在安全性漏洞，则发出第四警示提示用户，提醒将存在安全性漏洞的代码进行修复。
  4. 如权利要求3所述的业务系统预先稽查方法，其特征在于，所述业务系统代码稽查步骤包括：
    根据所述预先设置的代码规范，将所述待发布的业务系统中代码的格式不符合所述预先设置的代码规范的代码格式的代码自动调整成符合所述预先设置的代码规范的代码格式。
  5. 如权利要求3所述的业务系统预先稽查方法，其特征在于，所述方法还包括如下步骤：
    检查所述待发布的业务系统增加的新功能对数据库已有的已安装使用的业务系统的数据是否有影响，若有影响，则发出第五警示提示用户，提醒对有影响的数据进行相应的修改。
  6. 如权利要求5所述的业务系统预先稽查方法，其特征在于，所述第一警示至所述第五警示还包括：
    在显示界面上显示稽查结果信息，提示用户下一步应该执行的操作；及/或发送邮件或信息至预先设定的用户通知稽查结果信息。
  7. 如权利要求6所述的业务系统预先稽查方法，其特征在于，所述第三警示、所述第四警示还包括：标示有问题的代码的具体位置。
  8. 如权利要求6所述的业务系统预先稽查方法，其特征在于，所述第五警示还包括：标示会影响已安装使用的业务系统性能的数据库中新增加的表、新增及/或变更的索引，以及会引起数据库全表扫描或隐式转换的语句。
  9. 一种服务器，其特征在于，所述服务器包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的业务系统预先稽查系统，所述业务系统预先稽查系统被所述处理器执行时实现如下步骤：
    根据预存的记录文件判断待发布的业务系统是否有关联系统；若有关联系统，则根据所述预存的记录文件判断在所述待发布的业务系统需要回滚至前一版本时，所述待发布的业务系统的关联系统是否需要回滚至前一版本，及/或，根据所述预存的记录文件判断在所述待发布的业务系统的关联系统需 要回滚至前一版本时，所述待发布的业务系统是否需要回滚至前一版本；
    若所述待发布的业务系统及/或其关联系统需要回滚至前一版本，则发出第一警示提示用户，提醒将需要回滚的所述待发布的业务系统及/或其关联系统回滚至前一版本。
  10. 如权利要求9所述的服务器，其特征在于，所述业务系统预先稽查系统被所述处理器执行时还实现如下步骤：
    若所述待发布的业务系统需要回滚至前一版本，则根据所述预存的记录文件判断所述待发布的业务系统对应的数据库脚本是否需要回滚至前一版本；
    若所述待发布的业务系统对应的数据库脚本需要回滚至前一版本，则发出第二警示提示用户，提醒将需要回滚的所述待发布的业务系统对应的数据库脚本回滚至前一版本。
  11. 如权利要求9所述的服务器，其特征在于，所述业务系统预先稽查系统被所述处理器执行时还实现业务系统代码稽查步骤，所述业务系统代码稽查步骤包括：
    检查所述待发布的业务系统的代码是否符合预先设置的代码规范，若检查发现有不符合所述预先设置的代码规范的代码，则发出第三警示提示用户，提醒将不符合所述预先设置的代码规范的代码进行修改；
    检查所述待发布的业务系统的代码是否存在安全性漏洞，若检查发现所述待发布的业务系统的代码存在安全性漏洞，则发出第四警示提示用户，提醒将存在安全性漏洞的代码进行修复。
  12. 如权利要求11所述的服务器，其特征在于，所述业务系统代码稽查步骤包括：
    根据所述预先设置的代码规范，将所述待发布的业务系统中代码的格式不符合所述预先设置的代码规范的代码格式的代码自动调整成符合所述预先设置的代码规范的代码格式。
  13. 如权利要求11所述的服务器，其特征在于，所述业务系统预先稽查系统被所述处理器执行时还实现如下步骤：
    检查所述待发布的业务系统增加的新功能对数据库已有的已安装使用的业务系统的数据是否有影响，若有影响，则发出第五警示提示用户，提醒对有影响的数据进行相应的修改。
  14. 一种计算机可读存储介质，所述计算机可读存储介质存储有业务系统预先稽查程序，所述业务系统预先稽查程序可被至少一个处理器执行，以使所述至少一个处理器执行如下步骤：
    根据预存的记录文件判断待发布的业务系统是否有关联系统；若有关联系统，则根据所述预存的记录文件判断在所述待发布的业务系统需要回滚至前一版本时，所述待发布的业务系统的关联系统是否需要回滚至前一版本，及/或，根据所述预存的记录文件判断在所述待发布的业务系统的关联系统需要回滚至前一版本时，所述待发布的业务系统是否需要回滚至前一版本；
    若所述待发布的业务系统及/或其关联系统需要回滚至前一版本，则发出第一警示提示用户，提醒将需要回滚的所述待发布的业务系统及/或其关联系统回滚至前一版本。
  15. 如权利要求14所述的存储介质，其特征在于，所述业务系统预先稽查程序被至少一个处理器执行，还实现如下步骤：
    若所述待发布的业务系统需要回滚至前一版本，则根据所述预存的记录文件判断所述待发布的业务系统对应的数据库脚本是否需要回滚至前一版本；
    若所述待发布的业务系统对应的数据库脚本需要回滚至前一版本，则发出第二警示提示用户，提醒将需要回滚的所述待发布的业务系统对应的数据库脚本回滚至前一版本。
  16. 如权利要求14所述的存储介质，其特征在于，所述业务系统预先稽查程序被至少一个处理器执行时，还执行业务系统代码稽查步骤，所述业务 系统代码稽查步骤包括：
    检查所述待发布的业务系统的代码是否符合预先设置的代码规范，若检查发现有不符合所述预先设置的代码规范的代码，则发出第三警示提示用户，提醒将不符合所述预先设置的代码规范的代码进行修改；
    检查所述待发布的业务系统的代码是否存在安全性漏洞，若检查发现所述待发布的业务系统的代码存在安全性漏洞，则发出第四警示提示用户，提醒将存在安全性漏洞的代码进行修复。
  17. 如权利要求16所述的存储介质，其特征在于，所述业务系统代码稽查步骤包括：
    根据所述预先设置的代码规范，将所述待发布的业务系统中代码的格式不符合所述预先设置的代码规范的代码格式的代码自动调整成符合所述预先设置的代码规范的代码格式。
  18. 如权利要求14所述的存储介质，其特征在于，所述业务系统预先稽查程序被所述处理器执行时还实现如下步骤：
    检查所述待发布的业务系统增加的新功能对数据库已有的已安装使用的业务系统的数据是否有影响，若有影响，则发出第五警示提示用户，提醒对有影响的数据进行相应的修改。
  19. 如权利要求18所述的存储介质，其特征在于，所述第一警示至所述第五警示还包括：
    在显示界面上显示稽查结果信息，提示用户下一步应该执行的操作；及/或发送邮件或信息至预先设定的用户通知稽查结果信息。
  20. 如权利要求19所述的存储介质，其特征在于，所述第三警示、所述第四警示还包括：标示有问题的代码的具体位置。
PCT/CN2018/076187 2017-06-25 2018-02-10 业务系统预先稽查方法、服务器及计算机可读存储介质 WO2019000963A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710490423.X 2017-06-25
CN201710490423.XA CN107678936B (zh) 2017-06-25 2017-06-25 业务系统预先稽查方法、服务器及计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2019000963A1 true WO2019000963A1 (zh) 2019-01-03

Family

ID=61133563

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076187 WO2019000963A1 (zh) 2017-06-25 2018-02-10 业务系统预先稽查方法、服务器及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN107678936B (zh)
WO (1) WO2019000963A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022189853A1 (en) 2021-03-09 2022-09-15 OneProjects Design and Innovation Ltd. Disposable catheter with rotatable image array
WO2023223091A1 (en) 2022-05-19 2023-11-23 OneProjects Design and Innovation Ltd. Systems and methods for tissue evaluation and classification
WO2023223095A1 (en) 2022-05-19 2023-11-23 OneProjects Design and Innovation Ltd. Systems and methods for reconstruction and visualization of anatomical data

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107678936B (zh) * 2017-06-25 2021-02-09 平安科技（深圳）有限公司 业务系统预先稽查方法、服务器及计算机可读存储介质
CN107861969B (zh) * 2017-09-14 2020-10-02 平安普惠企业管理有限公司 语句修改方法、扫描平台和计算机可读存储介质
CN109032930A (zh) * 2018-07-03 2018-12-18 泰康保险集团股份有限公司 系统测试方法及装置
CN110069400A (zh) * 2019-03-16 2019-07-30 平安普惠企业管理有限公司 漏洞测试报告生成方法、装置、计算机设备和存储介质
CN111352840B (zh) * 2020-02-28 2023-08-15 抖音视界有限公司 上线行为风险评估方法、装置、设备和可读存储介质
CN117827684A (zh) * 2024-03-05 2024-04-05 数翊科技(北京)有限公司武汉分公司 数据计算作业的预警方法、装置、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2749848A1 (en) * 2012-12-27 2014-07-02 General Electric Company Firmware upgrade error detection and automatic rollback
CN104572357A (zh) * 2014-12-30 2015-04-29 清华大学 一种用于hdfs系统的备份和恢复方法
CN105049486A (zh) * 2015-06-16 2015-11-11 腾讯科技（北京）有限公司 静态文件的版本管理、文件拉取控制方法、装置及系统
CN105528373A (zh) * 2014-10-21 2016-04-27 阿里巴巴集团控股有限公司 数据库故障处理方法、装置、系统及服务器
CN107678936A (zh) * 2017-06-25 2018-02-09 平安科技（深圳）有限公司 业务系统预先稽查方法、服务器及计算机可读存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080201705A1 (en) * 2007-02-15 2008-08-21 Sun Microsystems, Inc. Apparatus and method for generating a software dependency map
CN103294563B (zh) * 2012-02-28 2016-03-09 国际商业机器公司 一种对安装单元进行版本冲突检查的方法和系统
CN103226485B (zh) * 2013-05-21 2016-09-28 北京奇虎科技有限公司 代码发布方法、代码发布机和代码发布系统
US9841970B2 (en) * 2015-01-13 2017-12-12 Ford Global Technologies, Llc Vehicle control update methods and systems
CN104537309A (zh) * 2015-01-23 2015-04-22 北京奇虎科技有限公司 应用程序漏洞检测方法、装置及服务器
CN105204909A (zh) * 2015-10-12 2015-12-30 Tcl集团股份有限公司 一种基于移动终端的强相关apk升级方法及系统
CN106126204B (zh) * 2016-06-15 2019-03-19 中邮建技术有限公司 一种基于模块化设计的信息系统迭代式扩展开发方法
CN106201614A (zh) * 2016-07-11 2016-12-07 天津中兴智联科技有限公司 一种可对多种同类软件进行链式升级的通用方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2749848A1 (en) * 2012-12-27 2014-07-02 General Electric Company Firmware upgrade error detection and automatic rollback
CN105528373A (zh) * 2014-10-21 2016-04-27 阿里巴巴集团控股有限公司 数据库故障处理方法、装置、系统及服务器
CN104572357A (zh) * 2014-12-30 2015-04-29 清华大学 一种用于hdfs系统的备份和恢复方法
CN105049486A (zh) * 2015-06-16 2015-11-11 腾讯科技（北京）有限公司 静态文件的版本管理、文件拉取控制方法、装置及系统
CN107678936A (zh) * 2017-06-25 2018-02-09 平安科技（深圳）有限公司 业务系统预先稽查方法、服务器及计算机可读存储介质

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022189853A1 (en) 2021-03-09 2022-09-15 OneProjects Design and Innovation Ltd. Disposable catheter with rotatable image array
WO2023223091A1 (en) 2022-05-19 2023-11-23 OneProjects Design and Innovation Ltd. Systems and methods for tissue evaluation and classification
WO2023223095A1 (en) 2022-05-19 2023-11-23 OneProjects Design and Innovation Ltd. Systems and methods for reconstruction and visualization of anatomical data

Also Published As

Publication number Publication date
CN107678936A (zh) 2018-02-09
CN107678936B (zh) 2021-02-09

Similar Documents

Publication Publication Date Title
WO2019000963A1 (zh) 业务系统预先稽查方法、服务器及计算机可读存储介质
US9547702B2 (en) Validating code of an extract, transform and load (ETL) tool
US9824002B2 (en) Tracking of code base and defect diagnostic coupling with automated triage
US10437703B2 (en) Correlation of source code with system dump information
US20160004517A1 (en) SOFTWARE DEVELOPMENT IMPROVEMENT TOOL - iREVIEW
US8918885B2 (en) Automatic discovery of system integrity exposures in system code
US10223185B2 (en) Automated defect diagnosis from machine diagnostic data
US9256512B1 (en) Quality analysis for embedded software code
CN111814203B (zh) 一种环境数据的处理方法、装置、设备及存储介质
US11349712B1 (en) Configuration drift management tool
CN103440460A (zh) 一种应用系统变更验证方法及验证系统
US9720685B2 (en) Software development activity
WO2019169771A1 (zh) 电子装置、访问指令信息获取方法及存储介质
CN111884858B (zh) 设备资产信息的校验方法、装置、系统和介质
CN111694684A (zh) 存储设备的异常构造方法、装置、电子设备及存储介质
US11790249B1 (en) Automatically evaluating application architecture through architecture-as-code
US10489137B1 (en) Software verification system and methods
CN116401230A (zh) 一种关系型数据库的变更方法、系统、设备及存储介质
CN115757099A (zh) 平台固件保护恢复功能自动测试方法和装置
CN110807037B (zh) 一种数据修改方法、装置、电子设备及存储介质
CN114327588A (zh) 一种代码提交日志的处理方法及装置
US20180204127A1 (en) Management of building energy systems through quantification of reliability
JP6410705B2 (ja) 障害予兆検出システムおよび障害予兆検出方法
CN115827359A (zh) 告警验证方法及测试机
CN116680106A (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: 18823645

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 19.05.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18823645

Country of ref document: EP

Kind code of ref document: A1