WO2018107812A1 - 交易系统错误检测方法、装置、存储介质和计算机设备 - Google Patents

交易系统错误检测方法、装置、存储介质和计算机设备 Download PDF

Info

Publication number
WO2018107812A1
WO2018107812A1 PCT/CN2017/099728 CN2017099728W WO2018107812A1 WO 2018107812 A1 WO2018107812 A1 WO 2018107812A1 CN 2017099728 W CN2017099728 W CN 2017099728W WO 2018107812 A1 WO2018107812 A1 WO 2018107812A1
Authority
WO
WIPO (PCT)
Prior art keywords
transaction
server
transaction data
centralized
detection
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/099728
Other languages
English (en)
French (fr)
Inventor
杜一森
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
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 Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Priority to US16/070,549 priority Critical patent/US20190026707A1/en
Priority to KR1020187018395A priority patent/KR102274561B1/ko
Priority to EP17872887.9A priority patent/EP3570170A4/en
Priority to JP2018517562A priority patent/JP6614756B2/ja
Priority to AU2017370317A priority patent/AU2017370317A1/en
Priority to SG11201805501VA priority patent/SG11201805501VA/en
Publication of WO2018107812A1 publication Critical patent/WO2018107812A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G06Q20/027—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] involving a payment switch or gateway
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/50—Testing arrangements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/178—Techniques for file synchronisation in file systems
    • G06F16/1794—Details of file format conversion
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108—Remote banking, e.g. home banking
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors

Definitions

  • the present application relates to the field of computer technology, and in particular, to a transaction system error detection method, apparatus, storage medium, and computer equipment.
  • the inspector needs to perform multiple interactions with the multi-party system involved in the cooperative transaction system to detect the error items in the cooperative transaction system, the process is cumbersome, and the detection efficiency is low.
  • a trading system error detection method comprising:
  • the detection sequence table including the check items arranged in order, the arrangement order of the check items conforming to the transaction data corresponding to the transaction data flow category in the cooperative transaction system Flow direction
  • the transaction data transmission link is detected in turn according to the check item in the detection sequence table.
  • a trading system error detecting device comprising:
  • An obtaining module configured to acquire a transaction identifier; and determine a transaction data flow direction category corresponding to the transaction identifier;
  • a search module configured to search a detection sequence table that matches the transaction data flow to the category, the detection sequence table includes an in-order check item, and the check item is arranged in an order consistent with the transaction data flow in the cooperative transaction system a transaction data flow corresponding to the category; determining a transaction data transmission link corresponding to the transaction identifier in the cooperative transaction system; and
  • a detecting module configured to sequentially detect the transaction data transmission link according to the check item in the detection sequence table.
  • One or more computer readable non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause the one or more processors to perform the steps of:
  • the detection sequence table including the check items arranged in order, the arrangement order of the check items conforming to the transaction data corresponding to the transaction data flow category in the cooperative transaction system Flow direction
  • the transaction data transmission link is detected in turn according to the check item in the detection sequence table.
  • a computer device includes a memory and a processor, wherein the memory stores a computer Reading instructions that, when executed by the processor, cause the processor to perform the following steps:
  • the detection sequence table including the check items arranged in order, the arrangement order of the check items conforming to the transaction data corresponding to the transaction data flow category in the cooperative transaction system Flow direction
  • the transaction data transmission link is detected in turn according to the check item in the detection sequence table.
  • 1 is an application environment diagram of a transaction system error detection method in an embodiment
  • FIG. 2 is a system architecture diagram of a cooperative transaction system in an embodiment
  • FIG. 3 is a schematic flow chart of a method for detecting a transaction system error in an embodiment
  • FIG. 4 is a schematic flow chart showing the steps of detecting a transaction data transmission link according to an inspection item in a detection sequence table in an embodiment
  • FIG. 5 is a flow chart showing the steps of detecting a transaction data format conversion file in a centralized transaction server in one embodiment
  • FIG. 6 is a flow chart showing the steps of detecting a transaction data transmission link in accordance with an inspection item in a detection order table in another embodiment
  • FIG. 7 is a logic processing diagram of a transaction system error detection method in an embodiment
  • Figure 8 is a block diagram showing the structure of a transaction system error detecting apparatus in an embodiment
  • FIG. 9 is a schematic structural diagram of a computer device in an embodiment.
  • FIG. 1 is an application environment diagram of a transaction system error detection method in an embodiment.
  • the application environment includes a terminal 110 and a cooperative transaction system 120.
  • the user operates the terminal 110 and inputs a transaction identifier.
  • the terminal After acquiring the transaction identifier, the terminal automatically determines a transaction data flow category corresponding to the transaction identifier, and searches for The transaction data flows to the category matching detection sequence table, and determines the transaction data transmission link corresponding to the transaction identifier in the cooperation transaction system 120, and then detects the transaction data transmission link according to the check items arranged in order in the detection order table.
  • the terminal 110 can be a personal computer or a mobile terminal, such as a mobile phone or a tablet computer.
  • the cooperative transaction system includes a service server 210, a centralized transaction server 220, an internal front server 230, and a cooperation partner front server 240.
  • the service server 210 is connected to the centralized transaction server 220 via the network
  • the centralized transaction server 220 is connected to the internal front server 230 via the network
  • the internal front server 230 is connected to the cooperation partner front server 240 via the network.
  • the service server 210 may initiate a transaction in which the cooperation object pre-server 240 is invoked.
  • the transaction data is output from the service server 210, and flows through the centralized transaction server 220, the internal pre-server 230, and the cooperation partner pre-server 240 to form a transaction data transmission chain. road.
  • the cooperation partner front server 240 may also initiate a transaction to invoke the service server 210.
  • the transaction data is output from the cooperation partner front server 240, flows through the internal front server 230, flows through the centralized transaction server 220, and the service server 210 forms a transaction. Data transmission link.
  • FIG. 3 is a schematic flow chart of a method for detecting a transaction system error in an embodiment. This embodiment takes The method is applied to the terminal 110 in FIG. 1 described above for illustration.
  • the transaction system error detection method specifically includes the following steps:
  • the transaction identifier is used to uniquely identify a transaction made in the cooperative transaction system.
  • a cooperative trading system is a system in which a multi-party system cooperates to conduct transactions.
  • the insurance business system cooperates with a cooperative trading system composed of a banking system to realize a transaction in which a user purchases insurance.
  • the transaction identifier can be a transaction code or a transaction code and a partner code.
  • the transaction identifier may include any character supported by the computer, and the transaction related data for the transaction is stored in the database or the cache corresponding to the transaction identifier.
  • the transaction related data includes the transaction data flow direction category and the transaction data transmission link.
  • the terminal can receive the transaction identifier input by the user on the interface, and obtain the transaction identifier.
  • the transaction data flow to the category indicates the direction of the transaction data when it passes through the cooperative transaction system, specifically the caller from the caller of the transaction to the transaction.
  • the cooperative transaction system involves cooperation between multi-party systems. When the cooperative transaction system conducts cooperative transactions, the party that initiates the transaction is the caller, and the party that is called to conduct the cooperative transaction is the called party. Among them, any one of the cooperative trading systems can be used as the caller of the transaction or as the callee of the transaction.
  • the category of transaction data flow can be internal flow to cooperative object type or cooperative object flow to internal type.
  • the terminal searches for a transaction-related data corresponding to the transaction identifier in a database or a cache, and extracts a transaction data flow from the transaction-related data to the category.
  • the transaction category can be an internal flow to a collaborative object type or a collaborative object flow to an internal type.
  • the detection sequence table includes the check items arranged in order, and the arrangement order of the check items conforms to the transaction data flow direction corresponding to the transaction data flow category in the cooperative transaction system.
  • the detection sequence table is a data table for setting inspection items arranged in a certain order.
  • the check item refers to a preset check item that needs to be detected, and indicates the specific items that the terminal performs detection, such as the network connection status between servers.
  • the terminal establishes an inspection order table including each inspection item in the cooperative transaction system in the database or the cache according to the transaction caller to the transaction callee. That is, the order of the check items is in accordance with the flow of the transaction data corresponding to the transaction data flow category in the cooperative transaction system.
  • the terminal After acquiring the transaction data flow to the category, the terminal searches the database or the cache for a check order table matching the transaction data flow to the category, and determines the check order and the check items to be checked according to the check order table.
  • the transaction data transmission link refers to a link formed by a specific server through which transaction data flows when a transaction is specifically performed in the cooperative transaction system.
  • the transaction data transmission link includes a service server for processing transaction data corresponding to the transaction identifier, a centralized transaction server, an internal front server, and a cooperative object front server; the centralized transaction server connects the service server and the internal front server, and the cooperation object Set the server to connect to the internal front server.
  • the terminal searches for a transaction data transmission link corresponding to the transaction identifier in a database or a cache, and determines a service server, a centralized transaction server, an internal front server, and a cooperation corresponding to the acquired transaction identifier.
  • Object front server Object front server.
  • the transaction data transmission link is detected according to the check item in the detection sequence table.
  • the terminal determines the order of the check and the check item to be checked, and sequentially, according to the check item in the check order table, the determined service server corresponding to the acquired transaction identifier, the centralized transaction server, The transaction data transmission link formed by the internal front server and the partner front server is detected.
  • the above transaction system error detection method automatically determines a transaction data flow direction category corresponding to the transaction identifier by acquiring the transaction identifier, and searches for a detection sequence table matching the transaction data flow category, and determines a transaction corresponding to the transaction identifier in the cooperative transaction system.
  • the data transmission link detects the transaction data transmission link according to the check items arranged in order in the detection sequence table, and displays the detection result corresponding to the inspection item when the detection fails.
  • the order of the check items is preset and conforms to the transaction data flow corresponding to the transaction data flow category in the cooperative transaction system. This test The method automatically detects after obtaining the transaction identifier, which avoids the cumbersome detection process of multiple interaction operations when the tester manually detects, and greatly improves the error detection efficiency of the transaction system.
  • S310 is a flow chart showing the steps of detecting the transaction data transmission link according to the check items in the detection order table in step S310 when the transaction data flows to the internal flow to the cooperation object type in one embodiment. As shown in FIG. 4, S310 specifically includes the following steps:
  • the transaction data format conversion file is a file for format conversion of transaction data.
  • the transaction data format conversion file may be an XSL (eXtensible Stylesheet Language) file or a CSS (Cascading Style Sheets) file.
  • XSL eXtensible Stylesheet Language
  • CSS CSS
  • a transaction data format conversion file corresponding to each cooperation object that needs to perform data conversion is stored in the centralized server, and a file directory is established.
  • the terminal can access the centralized transaction server to obtain a transaction data format conversion file directory stored in the centralized transaction server.
  • the terminal traverses the directory entry of the file directory, and compares the correspondence between the directory item and the transaction identifier during the traversal, and when the traversed directory item matches the acquired transaction identifier, obtains The transaction data format conversion file corresponding to the directory entry.
  • the correspondence between the directory item and the transaction identifier is also stored in the centralized transaction server.
  • transaction data format conversion file corresponding to the transaction identifier is found, it is checked whether the format of the found transaction data format conversion file is correct.
  • the format check of the transaction data format conversion file it can be whether the field structure in the file is With the detection. For example, for an XSL file, it can be checked whether the forward slash "/" is used correctly. When the XSL file is used for format conversion, the forward slash "/" indicates that the root node is selected. For example, it is determined that the XSL file structure matches when ⁇ xsl:otherwise>L2 ⁇ /xsl:otherwise> is detected, and the XSL file structure is determined to be mismatched when detecting: ⁇ xsl:otherwise>L2 ⁇ xsl:otherwise>.
  • Step S404 if the transaction data format conversion file corresponding to the transaction identifier is not found in the centralized transaction server, it indicates that the transaction caller is consistent with the data format supported by the transaction callee, and does not need to perform transaction data format conversion, and can be directly executed. Step S404.
  • the detection result may be displayed in the detection result display area, or the detection result may be recorded in a file or a cache, so that when the inspection result needs to be viewed Get the test result.
  • the network connection status between the centralized transaction server and the internal front server is detected.
  • the transaction data flow direction corresponding to the acquired transaction identifier is an internal flow to the cooperation object type, that is, the transaction data flows from the centralized transaction server to the internal front server, that is, the network that detects the centralized transaction server to the internal front server Whether it is connected.
  • the centralized transaction server is the network detection initiator, and the internal front server is the network connection party to be detected.
  • the method for checking the network connection status is to send a network detection start command to the network detection initiator by the terminal, and the network detection initiator sends a network detection command to the network connection party to be detected after receiving the network detection start instruction. And obtaining the return content of the network detection command, detecting that the returned content includes a preset keyword, and if yes, determining that the network connection between the network detection initiator and the network connection to be detected is normal.
  • the network detection initiator can detect the network connection status with the network port of the network to be detected by sending a "telnet (remote terminal protocol)" command.
  • telnet remote terminal protocol
  • the network connection is determined to be normal. If the string is not included, it is determined that the network connection is abnormal.
  • the detection result may be displayed in the test result display area, or the detection result may be recorded in a file or a cache, so that the inspection is required to be checked.
  • the result of the test is obtained at the time of the result.
  • the transaction data record file is used to record transaction related information flowing through the internal pre-server.
  • Each internal pre-server stores a transaction data record file for recording transactions through the internal pre-server, and each time a transaction passes through the internal pre-server, the transaction data of the internal pre-server is The transaction identifier, transaction data source, and transaction data trend of the transaction are written in the log file.
  • the transaction data record file may be an XML (Extensible Markup Language) file or an HTML (HyperText Markup Language) file or the like.
  • the transaction data record file in the internal front server is detected.
  • the transaction record field corresponding to the transaction identifier in the transaction data record file is searched according to the obtained transaction identifier, and the format of the field is detected to be correct.
  • the format check of the transaction data record file may be to detect whether the transaction record field structure corresponding to the transaction identifier in the file matches. For example, for an XML file, you can check it out. The slash "/" is used correctly. When the XSL file is used for format conversion, the forward slash "/" indicates that the slash is selected from the root node. For example, when it is detected that: ⁇ transmitIP>192.168.29.98 ⁇ /transmitIP>, the judgment field is in the correct format. When it detects: ⁇ transmitIP>192.168.29.98 ⁇ transmitIP>, the format of the determination field is incorrect.
  • the detection result may be displayed in the test result display area, or the detection result may be recorded in a file or a cache. In order to obtain the test result when it is necessary to view the inspection result.
  • the network connection status between the internal pre-server and the cooperation partner pre-server is detected.
  • the terminal sends a network detection start command to the internal front server, and after receiving the network detection start command, the internal front server sends a network detection command to the partner front server.
  • the returned content of the network detection command is obtained, and the returned content includes a preset keyword, and if yes, it is determined that the network connection between the internal front server and the partner front server is normal.
  • the detection result may be displayed in the test result display area, or the detection result may be recorded in a file or a cache, so as needed Obtain the test result when viewing the check result.
  • the specific detection method for the transaction data transmission link corresponding to the transaction identifier is specifically followed by the detection item in the check order table, and the user only An interaction with the terminal is required to enable the terminal to detect the transaction data transmission link, thereby avoiding the cumbersome detection process of multiple interactions by the tester during manual detection, and greatly improving the error detection efficiency of the transaction system.
  • FIG. 6 is a flow chart showing the steps of detecting the transaction data transmission link according to the check items in the detection order table in step S310 when the transaction data flows to the category as the cooperation object to the internal type in one embodiment.
  • S310 specifically includes the following steps:
  • the transaction data record file in the internal front server is detected.
  • the transaction record field corresponding to the transaction identifier in the transaction data record file is searched according to the obtained transaction identifier, and the format of the field is detected to be correct.
  • the transaction record field structure corresponding to the transaction identifier in the file is matched, or may be detected whether the transaction record field corresponding to the transaction identifier in the file contains extra spaces; It is to detect whether the structure of the transaction record field attribute value corresponding to the transaction identifier in the file is normal.
  • the detection result may be displayed in the test result display area, or the detection result may be recorded in a file or a cache. In order to obtain the test result when it is necessary to view the inspection result.
  • the acquired transaction is completed.
  • the network connection status between the internal front server and the centralized transaction server is detected.
  • the terminal sends a network detection start command to the internal front server, and after receiving the network detection start command, the internal front server sends a network detection command to the centralized transaction server.
  • obtaining the return service server content for the network detection command detecting that the returned content includes a preset keyword, and if yes, determining that the network connection between the internal front server and the centralized transaction server is normal.
  • the detection result may be displayed in the test result display area, or the detection result may be recorded in a file or a cache, so that the inspection is needed.
  • the result of the test is obtained at the time of the result.
  • the network connection status between the internal front server and the centralized transaction server is detected.
  • the terminal sends a network detection start command to the centralized transaction server, and after receiving the network detection start command, the centralized transaction server sends a network detection command to the service server. Then, the returned content of the network detection command is obtained, and the returned content includes a preset keyword, and if yes, it is determined that the network connection between the centralized transaction server and the service server is normal.
  • the detection result may be displayed in the test result display area, or the detection result may be recorded in a file or a cache, so that the inspection result needs to be viewed. Get the test results at the time.
  • the transaction data format conversion file in the transaction server is detected.
  • the terminal can access the centralized transaction server, obtain the transaction data format conversion file directory stored in the centralized transaction server, traverse the directory entry of the file directory, and compare the correspondence between the directory item and the transaction identifier during the traversal, when traversing the directory entry and obtaining When the transaction identifier matches, the transaction data format conversion file corresponding to the directory entry is obtained. If the transaction data format conversion file corresponding to the transaction identifier is found, the found correspondence is checked. The format of the easy data format conversion file is correct. If the transaction data format conversion file corresponding to the transaction identifier is not found in the centralized transaction server, it indicates that the transaction caller is consistent with the data format supported by the transaction callee, and no transaction data format conversion is required.
  • the detection result may be displayed in the detection result display area, or the detection result may be recorded in a file or a cache, so that when the inspection result needs to be viewed Get the test result.
  • the specific detection method for the transaction data transmission link corresponding to the transaction identifier is specifically followed by the detection item in the inspection order table, and the user only It is necessary to perform an interaction with the terminal, so that the terminal can detect the transaction data transmission link, thereby avoiding the cumbersome detection process of multiple interaction operations by the tester during manual detection, and greatly improving the error detection efficiency of the transaction system.
  • Figure 7 is a logic diagram showing the transaction system error detection method in one embodiment. As shown in FIG. 7, after acquiring the input transaction identifier, the terminal determines the transaction data flow corresponding to the transaction identifier to the category and transaction data transmission link, and searches for a detection sequence table that matches the transaction data flow to the category.
  • the transaction data transmission link is detected in turn according to the check items in the detection order table. First, detecting the transaction data format conversion file in the centralized transaction server, searching the transaction data format conversion file directory, and detecting whether there is a transaction data format conversion file corresponding to the acquired transaction identifier. If yes, it detects whether the format of the transaction data format conversion file is correct. If the file format is correct, the network connection status between the centralized transaction server and the internal front server is detected; if the file format is incorrect, the display result is displayed in the detection result display area. The transaction server transaction data format conversion file format error information; if the corresponding transaction data format conversion file is not detected, the network connection status between the centralized transaction server and the internal front server is detected.
  • the network connection abnormality between the centralized transaction server and the internal front-end server is displayed in the detection result display area; if between the centralized transaction server and the internal front-end server Network connection is normal, then detection and transaction identification Whether the format of the transaction data record file in the corresponding internal pre-server is correct. If the file format is incorrect, the format of the transaction data record file in the internal front server is displayed in the test result display area; if the file format is correct, the network connection status between the internal front server and the partner front server is detected.
  • the network connection abnormality between the internal front server and the partner front server is displayed in the detection result display area; if the internal front server is If the network connection between the front-end servers of the partner is normal, the information of the transaction cooperation system is displayed in the test result display area.
  • the transaction data transmission link is detected in turn according to the check items in the detection order table. First, detecting whether the format of the transaction data record file in the pre-server corresponding to the transaction identifier is correct; if the file format is incorrect, displaying the format information of the internal pre-server transaction data record file in the detection result display area; if the file format is correct, Then the status of the network connection between the internal front server and the centralized transaction server is detected.
  • the network connection abnormality between the internal front server and the centralized transaction server is displayed in the detection result display area; if the internal front server and the centralized transaction server are If the network connection is normal, the network connection status between the centralized transaction server and the service server is detected.
  • the network connection abnormality between the centralized transaction server and the service server is displayed in the detection result display area; if the network connection between the centralized transaction server and the service server is centralized Normally, the transaction data format conversion file in the centralized transaction server corresponding to the transaction identifier is detected.
  • the transaction data format conversion file directory in the centralized transaction server is searched to detect whether there is a transaction data format conversion file corresponding to the acquired transaction identifier. If it exists, it detects whether the format of the transaction data format conversion file is correct. If the file format is correct, the normal information of the transaction cooperation system is displayed in the detection result display area; if the file format is wrong, the centralized transaction server transaction data is displayed in the detection result display area. The format conversion file format error information; if the corresponding transaction data format conversion file is not detected, the normal information of the transaction cooperation system is displayed in the detection result display area.
  • FIG. 8 is a structural block diagram of a transaction system error detecting apparatus in an embodiment.
  • the transaction system error detecting apparatus 800 includes an obtaining module 801, a searching module 802, and a detecting module 803.
  • the obtaining module 801 is configured to obtain a transaction identifier, and determine a transaction data flow direction category corresponding to the transaction identifier.
  • the searching module 802 is configured to search for a detection sequence table that matches the transaction data flow to the category; the detection sequence table includes the check items arranged in order, and the arrangement order of the check items is consistent with the transaction data flow corresponding to the transaction data flow category in the cooperative transaction system; A transaction data transmission link corresponding to the transaction identifier in the cooperative transaction system is determined.
  • the detecting module 803 is configured to sequentially detect the transaction data transmission link according to the check item in the detection sequence table.
  • the transaction system error detecting apparatus 800 automatically determines a transaction data flow direction category corresponding to the transaction identifier by acquiring the transaction identifier, and searches for a detection sequence table matching the transaction data flow category, and determines a transaction processing system corresponding to the transaction identifier. Transaction data transmission link, and then detecting the transaction data transmission link according to the check items arranged in order in the detection sequence table, and displaying the detection result corresponding to the inspection item when the detection fails.
  • the order of the check items is preset and conforms to the transaction data flow corresponding to the transaction data flow category in the cooperative transaction system. This detection method automatically detects after obtaining the transaction identifier, which avoids the cumbersome detection process of multiple interactions when the tester manually detects, and greatly improves the error detection efficiency of the transaction system.
  • the transaction data transmission link includes a service server, a centralized transaction server, an internal pre-server, and a cooperative object pre-server for processing transaction data corresponding to the transaction identifier; wherein the centralized transaction server is connected to the service server and The internal front-end server and the partner front-end server are connected to the internal front-end server.
  • the detecting module 803 is further configured to detect the transaction data format conversion file in the centralized transaction server; if the detection passes, the centralized transaction server and the internal front The network connection status between the servers is detected; if the detection is passed, the network connection status between the internal front server and the partner front server is detected; if the detection is passed, the transaction data record file in the internal front server is performed. Detection.
  • the detection module 803 is further configured to detect the transaction data record file in the internal pre-server; if the detection passes, the internal pre-server and the centralized The network connection status between the transaction servers is detected; if the detection is passed, the transaction data format conversion file in the centralized transaction server is detected; if the detection is passed, the network connection status between the centralized transaction server and the service server is detected.
  • the detecting module 803 is further configured to obtain a transaction data format conversion file directory in the centralized transaction server; and convert the file directory according to the transaction data format to search for a transaction data format conversion file corresponding to the transaction identifier; if the corresponding transaction data is found
  • the format conversion file detects whether the transaction data format conversion file format is correct.
  • FIG. 9 is a schematic diagram showing the internal structure of a computer device in an embodiment.
  • the computer device may specifically be the terminal 110 in FIG.
  • the computer device includes a processor coupled through a system bus, a non-volatile storage medium, an internal memory, a network interface, a display screen, and an input device.
  • the non-volatile storage medium of the computer device stores an operating system, a database and computer executable instructions for implementing a transaction system error detection method suitable for the computer device.
  • the processor of the computer device is used to provide computing and control capabilities to support the operation of the entire computer device.
  • Computer-executable instructions may be stored in the internal memory of the computer device, and when executed by the processor, the computer-executable instructions may cause the processor to perform a transaction system error detection method.
  • the network interface is used for network communication with the server, such as obtaining a transaction data format conversion file directory in the server, and the input device may be a touch layer covered on the display screen, or may be an external keyboard, a touchpad or a mouse.
  • the structure shown in FIG. 9 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 of the computer device to which the solution of the present application is applied.
  • the specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.
  • the transaction system error detection apparatus of the various embodiments described above may be implemented in the form of a computer program, and the computer executable instructions corresponding to the computer program may be executed on a computer device as shown in FIG.
  • Each of the above-described transaction system error detection devices may be implemented in whole or in part by software, hardware, and combinations thereof.
  • the network interface may be an Ethernet card or a wireless network card.
  • Each of the above modules may be embedded in or independent of the memory of the computer device in hardware, or may be stored in the memory of the computer device in software form, so that the processor invokes the operations corresponding to the above modules.
  • the processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like.
  • one or more computer readable non-volatile storage media having computer readable instructions stored by one or more processors are provided for causing one or more processes
  • the device performs the following steps: obtaining a transaction identifier; determining a transaction data flow direction category corresponding to the transaction identifier; finding a detection sequence table matching the transaction data flow to the category, the detection sequence table includes the check items arranged in order, and the arrangement order of the check items conforms to the cooperation Transaction data flow direction corresponding to the transaction data flow direction category in the transaction system; determining a transaction data transmission link corresponding to the transaction identifier in the cooperative transaction system; and sequentially detecting the transaction data transmission link according to the check item in the detection order table.
  • the transaction data transmission link includes a service server, a centralized transaction server, an internal pre-server, and a cooperative object pre-server for processing transaction data corresponding to the transaction identifier; wherein the centralized transaction server is connected to the service server and The internal front-end server and the partner front-end server are connected to the internal front-end server.
  • detecting the transaction data transmission link according to the check items in the detection order table includes: detecting the transaction data format conversion file in the centralized transaction server. If the detection is passed, the network connection status between the centralized transaction server and the internal front server is detected. If the detection is passed, the transaction data record file in the internal front server is detected, and if the detection passes, the internal front is detected. The status of the network connection between the server and the partner front server is detected.
  • the transaction data transmission link is detected according to the check item in the detection order table in turn: detecting the transaction data record file in the internal pre-server If the test passes, the network connection status between the internal front server and the centralized transaction server is detected, and if the test passes, the centralized transaction is performed. The network connection status between the server and the service server is detected, and if the detection passes, the transaction data format conversion file in the centralized transaction server is detected.
  • detecting the transaction data format conversion file in the centralized transaction server comprises: obtaining a transaction data format conversion file directory in the centralized transaction server; and converting the file directory according to the transaction data format to find a transaction data format conversion file corresponding to the transaction identifier. And if the corresponding transaction data format conversion file is found, it is detected whether the transaction data format conversion file format is correct.
  • the storage medium automatically determines a transaction data flow direction category corresponding to the transaction identifier by acquiring the transaction identifier, and searches a detection sequence table matching the transaction data flow category, and determines a transaction data transmission chain corresponding to the transaction identifier in the cooperative transaction system.
  • the road detects the transaction data transmission link according to the check items arranged in order in the detection sequence table, and displays the detection result corresponding to the inspection item when the detection fails.
  • the order of the check items is preset and conforms to the transaction data flow corresponding to the transaction data flow category in the cooperative transaction system.
  • This detection method automatically detects after obtaining the transaction identifier, which avoids the cumbersome detection process of multiple interactions when the tester manually detects, and greatly improves the error detection efficiency of the transaction system.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Environmental & Geological Engineering (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Debugging And Monitoring (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种交易系统错误检测方法，包括：获取交易标识；确定与所述交易标识对应的交易数据流向类别；查找与所述交易数据流向类别匹配的检测顺序表，所述检测顺序表包括按序排列的检查项，所述检查项的排列顺序符合合作交易系统中与所述交易数据流向类别对应的交易数据流向；确定所述合作交易系统中与所述交易标识对应的交易数据传输链路；依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测。

Description

交易系统错误检测方法、装置、存储介质和计算机设备
相关申请的交叉引用
本申请要求于2016年12月14日提交中国专利局，申请号为201611154475.1，发明名称为“交易系统错误检测方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，特别是涉及一种交易系统错误检测方法、装置、存储介质和计算机设备。
背景技术
随着计算机技术的发展，通过基于计算机的合作交易系统来完成交易过程越来越普遍。但是由于合作交易系统涉及多方系统之间的合作，每进行一次合作交易，实现该合作交易过程所涉及的任意一个系统或者系统之间的连接状态都会影响交易的成败，因此在涉及多方系统合作的交易过程中容易出现错误而导致交易失败。
传统的交易错误检测，检测人员需要与合作交易系统中涉及的多方系统进行多次交互操作才可以检测出合作交易系统中的错误项，过程繁琐，而且检测效率低下。
发明内容
根据本申请的各种实施例，提供一种交易系统错误检测方法、装置、存储介质和计算机设备。
一种交易系统错误检测方法，包括：
获取交易标识；
确定与所述交易标识对应的交易数据流向类别；
查找与所述交易数据流向类别匹配的检测顺序表，所述检测顺序表包括按序排列的检查项，所述检查项的排列顺序符合合作交易系统中与所述交易数据流向类别对应的交易数据流向；
确定所述合作交易系统中与所述交易标识对应的交易数据传输链路；及
依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测。
一种交易系统错误检测装置，包括：
获取模块，用于获取交易标识；确定与所述交易标识对应的交易数据流向类别；
查找模块，用于查找与所述交易数据流向类别匹配的检测顺序表，所述检测顺序表包括按序排列的检查项，所述检查项的排列顺序符合合作交易系统中与所述交易数据流向类别对应的交易数据流向；确定所述合作交易系统中与所述交易标识对应的交易数据传输链路；及
检测模块，用于依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测。
一个或多个存储有计算机可读指令的计算机可读非易失性存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行以下步骤：
获取交易标识；
确定与所述交易标识对应的交易数据流向类别；
查找与所述交易数据流向类别匹配的检测顺序表，所述检测顺序表包括按序排列的检查项，所述检查项的排列顺序符合合作交易系统中与所述交易数据流向类别对应的交易数据流向；
确定所述合作交易系统中与所述交易标识对应的交易数据传输链路；及
依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测。
一种计算机设备，包括存储器和处理器，所述存储器中储存有计算机可 读指令，所述计算机可读指令被所述处理器执行时，使得所述处理器执行以下步骤：
获取交易标识；
确定与所述交易标识对应的交易数据流向类别；
查找与所述交易数据流向类别匹配的检测顺序表，所述检测顺序表包括按序排列的检查项，所述检查项的排列顺序符合合作交易系统中与所述交易数据流向类别对应的交易数据流向；
确定所述合作交易系统中与所述交易标识对应的交易数据传输链路；及
依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征、目的和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为一个实施例中交易系统错误检测方法的应用环境图；
图2为一个实施例中合作交易系统的系统架构图；
图3为一个实施例中交易系统错误检测方法的流程示意图；
图4为一个实施例中依次按照检测顺序表中的检查项对交易数据传输链路进行检测的步骤的流程示意图；
图5为一个实施例中对集中交易服务器中交易数据格式转换文件进行检测的步骤的流程示意图；
图6为另一个实施例中依次按照检测顺序表中的检查项对交易数据传输链路进行检测的步骤的流程示意图；
图7为一个实施例中交易系统错误检测方法的逻辑处理图；
图8为一个实施例中交易系统错误检测装置的结构框图；
图9为一个实施例中计算机设备的结构示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
图1为一个实施例中交易系统错误检测方法的应用环境图。如图1所示，该应用环境包括终端110和合作交易系统120，用户操作终端110，输入交易标识，终端在获取到交易标识后自动确定与该交易标识对应的交易数据流向类别，并查找与交易数据流向类别匹配的检测顺序表，且确定合作交易系统120中与交易标识对应的交易数据传输链路，再根据检测顺序表中按序排列的检查项对交易数据传输链路进行检测。该终端110可以是个人电脑或移动终端，移动终端如手机或平板电脑等。
图2为一个实施例中合作交易系统的系统架构图。如图2所示，该合作交易系统包括业务服务器210、集中交易服务器220、内部前置服务器230和合作对象前置服务器240。其中，业务服务器210通过网络与集中交易服务器220连接，集中交易服务器220通过网络与内部前置服务器230连接，内部前置服务器230通过网络与合作对象前置服务器240连接。业务服务器210可以发起调用合作对象前置服务器240的交易，此时，交易数据从业务服务器210输出，流经集中交易服务器220、内部前置服务器230和合作对象前置服务器240形成交易数据传输链路。合作对象前置服务器240也可以发起调用业务服务器210的交易，此时，交易数据从合作对象前置服务器240输出，流经内部前置服务器230、流经集中交易服务器220和业务服务器210形成交易数据传输链路。
图3为一个实施例中交易系统错误检测方法的流程示意图。本实施例以 该方法应用于上述图1中的终端110来举例说明。参照图3，该交易系统错误检测方法具体包括如下步骤：
S302，获取交易标识。
其中，交易标识用于唯一标识在合作交易系统中进行的一次交易。合作交易系统是指多方系统之间合作进行交易的系统。例如，保险业务系统与银行系统组成的合作交易系统合作实现用户购买保险的交易。交易标识可以是交易代码，也可以是交易代码和合作对象代码。
具体地，每发起一次交易都会生成对应的交易标识，该交易标识可包括计算机支持的任意字符，并将进行交易的交易相关数据对应于交易标识存储在数据库或者缓存中。其中，交易相关数据包括交易数据流向类别以及交易数据传输链路等。终端可接收用户在界面输入的交易标识，获取该交易标识。
S304，确定与交易标识对应的交易数据流向类别。
其中，交易数据流向类别表示的是交易数据经过合作交易系统时的走向，具体是指从交易的调用方流向交易的被调用方。合作交易系统中涉及多方系统之间的合作，合作交易系统在进行合作交易时，发起交易的一方为调用方，被调用进行合作交易的一方是被调用方。其中，合作交易系统中的任一方系统既可以作为交易的调用方，也可以作为交易的被调用方。交易数据流向的类别可以是内部流向合作对象类型或者合作对象流向内部类型。
具体地，终端在获取到交易标识后，在数据库或者缓存中查找与该交易标识对应的交易相关数据，从该交易相关数据中提取交易数据流向类别。该交易类别可以是内部流向合作对象类型或者合作对象流向内部类型。
S306，查找与交易数据流向类别匹配的检测顺序表；检测顺序表包括按序排列的检查项，检查项的排列顺序符合合作交易系统中与交易数据流向类别对应的交易数据流向。
其中，检测顺序表是用来设定按照一定顺序排列的检查项的数据表。检查项是指预先设定的需要进行检测的检查项，表示终端进行检测的具体事项，比如服务器间网络连接状态等。
终端事先根据交易数据在合作交易系统中的流向，按照交易调用方到交易被调用方，在数据库或者缓存中建立了包括合作交易系统中各个检查项的检查顺序表。也就是检查项的排列顺序符合合作交易系统中与交易数据流向类别对应的交易数据流向。
具体地，终端在获取到交易数据流向类别后，在数据库或者缓存中查找与该交易数据流向类别匹配的检查顺序表，根据该检查顺序表确定检查的顺序与需要检查的检查项。
S308，确定合作交易系统中与交易标识对应的交易数据传输链路。
其中，交易数据传输链路是指在合作交易系统中具体进行一次交易时，交易数据流经的具体的服务器构成的链路。交易数据传输链路包括用于处理与交易标识对应的交易数据的业务服务器、集中交易服务器、内部前置服务器和合作对象前置服务器；集中交易服务器连接业务服务器和内部前置服务器，合作对象前置服务器连接内部前置服务器。
具体地，终端在获取到交易标识后，在数据库或者缓存中查找与该交易标识对应的交易数据传输链路，确定与获取的交易标识对应的业务服务器、集中交易服务器、内部前置服务器和合作对象前置服务器。
S310，依次按照检测顺序表中的检查项对交易数据传输链路进行检测。
具体地，终端在根据查找到的检查顺序表确定检查的顺序与需要检查的检查项后，依次按照检测顺序表中的检查项对确定的与获取的交易标识对应的业务服务器、集中交易服务器、内部前置服务器和合作对象前置服务器构成的交易数据传输链路进行检测。
上述交易系统错误检测方法，通过获取的交易标识自动确定与该交易标识对应的交易数据流向类别，并查找与交易数据流向类别匹配的检测顺序表，且确定合作交易系统中与交易标识对应的交易数据传输链路，再根据检测顺序表中按序排列的检查项对交易数据传输链路进行检测，在检测未通过时，展示与检查项对应的检测结果。其中，检查项的排列顺序是预先设置好的，且符合合作交易系统中与交易数据流向类别对应的交易数据流向。这种检测 方式在获取到交易标识后自动进行检测，避免了测试人员手工检测时多次交互操作繁琐的检测过程，极大地提高了交易系统错误检测效率。
图4为一个实施例中当交易数据流向类别为内部流向合作对象类型时步骤S310依次按照检测顺序表中的检查项对交易数据传输链路进行检测的步骤的流程示意图。如图4所示，S310具体包括以下步骤：
S402，对集中交易服务器中交易数据格式转换文件进行检测。
其中，交易数据格式转换文件是用于对交易数据进行格式转换的文件。当交易涉及到多方系统之间的合作时，存在不同的系统支持的数据格式不同的情况，因此在支持不同数据格式的系统之间进行合作交易时，需要对交易数据的格式进行转换。交易数据格式转换文件可以是XSL(eXtensible Stylesheet Language可扩展样式表语言)文件或者CSS(Cascading Style Sheets层叠样式表)文件等。具体地，如图5所示，步骤S402具体包括以下步骤：
S502，获取集中交易服务器中交易数据格式转换文件目录。
具体地，在集中服务器中存储了与需要进行数据转换的各个合作对象对应的交易数据格式转换文件，并建立了文件目录。终端可以访问集中交易服务器，获取在集中交易服务器中存储的交易数据格式转换文件目录。
S504，根据交易数据格式转换文件目录查找与交易标识对应的交易数据格式转换文件。
具体地，终端在获取到交易数据格式转换文件目录后，遍历该文件目录的目录项，在遍历时对照目录项与交易标识的对应关系，当遍历的目录项与获取的交易标识匹配时，获取该目录项对应的交易数据格式转换文件。其中，目录项与交易标识对应关系也存储在集中交易服务器中。
S506，若查找到对应的交易数据格式转换文件，则检测交易数据格式转换文件格式是否正确。
具体地，如果查找到与交易标识对应的交易数据格式转换文件，则检查该查找到的交易数据格式转换文件的格式是否正确。
对于交易数据格式转换文件的格式检查可以是对文件中字段结构是否匹 配进行检测。比如，对于XSL文件，可以是检查正斜杠“/”是否使用正确，在XSL文件用来进行格式转换时，正斜杠“/”表示从根节点进行选取。例如，在检测到：＜xsl：otherwise＞L2＜/xsl：otherwise＞时判定XSL文件结构匹配，而在检测到：＜xsl：otherwise＞L2＜xsl：otherwise＞时判定XSL文件结构不匹配。
对于交易数据格式转换文件的格式检查也可以是对文件中字段是否包含多余空格进行检测。比如，对于XSL文件，在检测到：＜xsl：value-of select＝″java：XSLString.strFillAll($a4，′15′，′′，′R′)″/＞时判定XSL文件不包含多余空格，在检测到：＜xsl：value-of select＝″java：XSLString.strFillAll($a4，′15′，′′，′R′)″/＞时判定XSL文件包含多余空格。
对于交易数据格式转换文件的格式检查还可以是对文件中字段属性值结构是否正常进行检测。比如，对于XSL文件，在检测到＜xsl：variable name＝″v_md5key″＞时判定XSL文件中字段属性值结构正常，在检测到：＜xsl：variable name＝″v_md5key＞时判定XSL文件中字段属性值结构异常。
另一方面，如果在集中交易服务器中没有查找到与交易标识对应的交易数据格式转换文件，表明交易调用方与交易被调用方支持的数据格式一致，不需要进行交易数据格式转换，可直接执行步骤S404。
进一步地，在对集中交易服务器中的交易数据格式转换文件检测完成后，可以在检测结果展示区展示检测结果，也可以将该检测结果记录在文件或者缓存中，以便在需要查看检查结果的时候获取该检测结果。
S404，若对集中交易服务器中交易数据格式转换文件检测通过，则对集中交易服务器与内部前置服务器之间网络连接状态进行检测。
具体地，在对集中交易服务器检查通过后，检测集中交易服务器与内部前置服务器之间网络连接状态。本实施例中，与获取的交易标识对应的交易数据流向类别为内部流向合作对象类型，也就是交易数据从集中交易服务器流向内部前置服务器，那么即检测集中交易服务器到内部前置服务器的网络是否连通。其中，集中交易服务器为网络检测发起方，内部前置服务器为待检测网络连接方。
检查网络连接状态的方法是通过终端向网络检测发起方发送网络检测启动指令，网络检测发起方在接收到该网络检测启动指令后，向待检测网络连接方发送网络检测命令。再获取针对该网络检测命令的返回内容，检测该返回内容中是包含预设关键字，若包含，则判定网络检测发起方与待检测网络连接方之间的网络连接正常。
具体地，网络检测发起方可通过发送“telnet(远程终端协议)”命令检测与待检测网络连接方网络端口的网络连接状态。比如“telnet 10.36.192.1871600”即检测与IP地址为“10.36.192.187”的1600端口网络连接状态，若在针对该命令的返回内容中包括“Escape character is‘^]”’则判定网络连接正常，若不包含该字符串则判定网络连接异常。
进一步地，在对集中交易服务器与内部前置服务器之间网络连接状态检测完成后，可以在测试结果展示区展示检测结果，也可以将该检测结果记录在文件或者缓存中，以便在需要查看检查结果的时候获取该检测结果。
S406，若对集中交易服务器与内部前置服务器之间网络连接状态检测通过，则对内部前置服务器中交易数据记录文件进行检测。
其中，交易数据记录文件用于记录流经该内部前置服务器的交易相关信息。每台内部前置服务器中都存储了交易数据记录文件，用来对经过该内部前置服务器的交易进行记录，每有一次交易经过该内部前置服务器，便在该内部前置服务器的交易数据记录文件中写入该交易的交易标识、交易数据来源和交易数据走向等。交易数据记录文件可以是XML(Extensible Markup Language可扩展标记语言)文件或者HTML(HyperText Markup Language超级文本标记语言)文件等。
在检测得到集中交易服务器与内部前置服务器交易正常之后，检测内部前置服务器中交易数据记录文件。根据获取到的交易标识查找交易数据记录文件中与该交易标识对应的交易记录字段，检测该字段格式是否正确。
对于交易数据记录文件的格式检查可以是对文件中与交易标识对应的交易记录字段结构是否匹配进行检测。比如，对于XML文件，可以是检查正 斜杠“/”是否使用正确，在XSL文件用来进行格式转换时，正斜杠“/”表示从根节点进行选取。例如，比如在检测到：＜transmitIP＞192.168.29.98＜/transmitIP＞时，判定字段格式正确，在检测到：＜transmitIP＞192.168.29.98＜transmitIP＞时，判定字段格式不正确。
对于交易数据记录文件的格式检查也可以是对文件中与交易标识对应的交易记录字段是否包含多余空格进行检测。比如，对于XML文件，在检测到：＜xsl：value-of select＝″java：XSLString.strFillAll($a4，′15′，′′，′R′)″/＞时判定XML文件不包含多余空格，在检测到：＜xsl：value-of select＝″java：XSLString.strFillAll($a4，′15′，′′，′R′)″/＞时判定XML文件包含多余空格。
对于交易数据记录文件的格式检查还可以是对文件中与交易标识对应的交易记录字段属性值结构是否正常进行检测。比如，在检测到＜item ip＝″211.151.112.5″＞时判定XML文件中字段属性值结构正常，在检测到：＜item ip＝″211.151.112.5＞时判定XML文件中字段属性值结构异常。
进一步地，在对内部前置服务器的交易数据记录文件中与获取的交易标识对应的字段格式检测完成后，可以在测试结果展示区展示检测结果，也可以将该检测结果记录在文件或者缓存中，以便在需要查看检查结果的时候获取该检测结果。
S408，若对内部前置服务器中交易数据记录文件检测通过，则对内部前置服务器与合作对象前置服务器之间网络连接状态进行检测。
具体地，在完成对内部前置服务器的交易数据记录文件中与获取的交易标识对应的字段格式检测后，检测内部前置服务器与合作对象前置服务器之间网络连接状态。终端向内部前置服务器发送网络检测启动指令，内部前置服务器在接收到该网络检测启动指令后，向合作对象前置服务器发送网络检测命令。再获取针对该网络检测命令的返回内容，检测该返回内容中是包含预设关键字，若包含，则判定内部前置服务器与合作对象前置服务器之间网络连接正常。
进一步地，在对内部前置服务器与合作对象前置服务器之间网络连接状态检测完成后，可以在测试结果展示区展示检测结果，也可以将该检测结果记录在文件或者缓存中，以便在需要查看检查结果的时候获取该检测结果。
在本实施例中，提供了在数据流向类别为内部流向合作对象类型时，依次按照检查顺序表中的检测项，针对具体地与交易标识对应的交易数据传输链路的具体检测方法，用户只需要和终端进行一次交互，即可使得终端检测交易数据传输链路，避免了测试人员手工检测时多次交互操作繁琐的检测过程，极大地提高了交易系统错误检测效率。
图6为一个实施例中当交易数据流向类别为合作对象流向内部类型时步骤S310依次按照检测顺序表中的检查项对交易数据传输链路进行检测的步骤的流程示意图。如图6所示，S310具体包括以下步骤：
S602，对内部前置服务器中交易数据记录文件进行检测。
具体地，在检测得到集中交易服务器与内部前置服务器交易正常之后，检测内部前置服务器中交易数据记录文件。根据获取到的交易标识查找交易数据记录文件中与该交易标识对应的交易记录字段，检测该字段格式是否正确。
对于交易数据记录文件的格式检查可以是对文件中与交易标识对应的交易记录字段结构是否匹配进行检测；也可以是对文件中与交易标识对应的交易记录字段是否包含多余空格进行检测；还可以是对文件中与交易标识对应的交易记录字段属性值结构是否正常进行检测。
进一步地，在对内部前置服务器的交易数据记录文件中与获取的交易标识对应的字段格式检测完成后，可以在测试结果展示区展示检测结果，也可以将该检测结果记录在文件或者缓存中，以便在需要查看检查结果的时候获取该检测结果。
S604，若对交易数据记录文件检测通过，则对内部前置服务器与集中交易服务器之间网络连接状态进行检测。
具体地，在完成对内部前置服务器的交易数据记录文件中与获取的交易 标识对应的字段格式检测后，检测内部前置服务器与集中交易服务器之间网络连接状态。终端向内部前置服务器发送网络检测启动指令，内部前置服务器在接收到该网络检测启动指令后，向集中交易服务器发送网络检测命令。再获取针对该网络检测命令的返回业务服务器内容，检测该返回内容中是包含预设关键字，若包含，则判定内部前置服务器与集中交易服务器之间网络连接正常。进一步地，在对内部前置服务器与集中交易服务器之间网络连接状态检测完成后，可以在测试结果展示区展示检测结果，也可以将该检测结果记录在文件或者缓存中，以便在需要查看检查结果的时候获取该检测结果。
S606，若对内部前置服务器与集中交易服务器之间网络连接状态检测通过，则对集中交易服务器与业务服务器之间网络连接状态进行检测。
具体地，在完成对内部前置服务器与集中交易服务器之间网络连接状态检测后，检测集中交易服务器与业务服务之间网络连接状态。终端向集中交易服务器发送网络检测启动指令，集中交易服务器在接收到该网络检测启动指令后，向业务服务器发送网络检测命令。再获取针对该网络检测命令的返回内容，检测该返回内容中是包含预设关键字，若包含，则判定集中交易服务器与业务服务器之间网络连接正常。
进一步地，在对集中交易服务器与业务服务器之间网络连接状态检测完成后，可以在测试结果展示区展示检测结果，也可以将该检测结果记录在文件或者缓存中，以便在需要查看检查结果的时候获取该检测结果。
S608，若对集中交易服务器与业务服务器之间网络连接状态通过，则对集中交易服务器中交易数据格式转换文件进行检测。
具体地，在完成对集中交易服务器与业务服务器之间网络连接状态检测后，检测交易服务器中交易数据格式转换文件。终端可以访问集中交易服务器，获取在集中交易服务器中存储的交易数据格式转换文件目录，遍历该文件目录的目录项，在遍历时对照目录项与交易标识的对应关系，当遍历的目录项与获取的交易标识匹配时，获取该目录项对应的交易数据格式转换文件。如果查找到与交易标识对应的交易数据格式转换文件，则检查该查找到的交 易数据格式转换文件的格式是否正确。如果在集中交易服务器中没有查找到与交易标识对应的交易数据格式转换文件，表明交易调用方与交易被调用方支持的数据格式一致，不需要进行交易数据格式转换。
进一步地，在对集中交易服务器中的交易数据格式转换文件检测完成后，可以在检测结果展示区展示检测结果，也可以将该检测结果记录在文件或者缓存中，以便在需要查看检查结果的时候获取该检测结果。
在本实施例中，提供了在数据流向类别为合作对象流向内部类型时，依次按照检查顺序表中的检测项，针对具体地与交易标识对应的交易数据传输链路的具体检测方法，用户只需要和终端进行一次交互，即可使得终端对交易数据传输链路进行检测，避免了测试人员手工检测时多次交互操作繁琐的检测过程，极大地提高了交易系统错误检测效率。
图7示出了一个实施例中交易系统错误检测方法的逻辑处理图。如图7所示，终端在获取到输入的交易标识后，确定与该交易标识对应的交易数据流向类别和交易数据传输链路，查找与该交易数据流向类别匹配的检测顺序表。
当交易数据流向类别为内部流向合作对象类型时，依次按照检测顺序表中的检查项对交易数据传输链路进行检测。首先，检测集中交易服务器中交易数据格式转换文件，查找交易数据格式转换文件目录，检测是否存在与获取的交易标识对应的交易数据格式转换文件。若存在，则检测该交易数据格式转换文件格式是否正确，若文件格式正确，则检测集中交易服务器与内部前置服务器之间的网络连接状态；若文件格式错误，则在检测结果展示区展示集中交易服务器交易数据格式转换文件格式错误的信息；若没有检测到对应的交易数据格式转换文件，则检测集中交易服务器与内部前置服务器的网络连接状态。
若集中交易服务器与内部前置服务器之间的网络连接异常，则在检测结果展示区展示集中交易服务器与内部前置服务器的网络连接异常的信息；若集中交易服务器与内部前置服务器之间的网络连接正常，则检测与交易标识 对应的内部前置服务器中交易数据记录文件格式是否正确。若文件格式错误，则在检测结果展示区展示内部前置服务器中交易数据记录文件格式错误的信息；若文件格式正确，则检测内部前置服务器与合作对象前置服务器之间的网络连接状态。
若内部前置服务器与合作对象前置服务器之间的网络连接异常，则在检测结果展示区展示内部前置服务器与合作对象前置服务器之间的网络连接异常的信息；若内部前置服务器与合作对象前置服务器之间的网络连接正常，则在检测结果展示区展示交易合作系统正常的信息。
当交易数据流向类别为合作对象流向内部类型时，依次按照检测顺序表中的检查项对交易数据传输链路进行检测。首先，检测与交易标识对应的前置服务器中交易数据记录文件格式是否正确；若文件格式错误，则在检测结果展示区展示内部前置服务器交易数据记录文件格式错误的信息；若文件格式正确，则检测内部前置服务器与集中交易服务器之间的网络连接状态。
若内部前置服务器与集中交易服务器之间的网络连接异常，则在检测结果展示区展示内部前置服务器与集中交易服务器之间的网络连接异常的信息；若内部前置服务器与集中交易服务器之间的网络连接正常，则检测集中交易服务器与业务服务器之间的网络连接状态。
若集中交易服务器与内部前置服务器之间的网络连接异常，则在检测结果展示区展示集中交易服务器与业务服务器之间的网络连接异常的信息；若集中交易服务器与业务服务器之间的网络连接正常，则检测与交易标识对应的集中交易服务器中交易数据格式转换文件。
查找集中交易服务器中的交易数据格式转换文件目录，检测是否存在与获取的交易标识对应的交易数据格式转换文件。若存在，则检测交易数据格式转换文件格式是否正确，若文件格式正确，则在检测结果展示区展示交易合作系统正常的信息；若文件格式错误，则在检测结果展示区展示集中交易服务器交易数据格式转换文件格式错误的信息；若没有检测到对应的交易数据格式转换文件，则在检测结果展示区展示交易合作系统正常的信息。
图8为一个实施例中交易系统错误检测装置的结构框图，参照图8，交易系统错误检测装置800包括获取模块801、查找模块802和检测模块803。
获取模块801，用于获取交易标识；确定与交易标识对应的交易数据流向类别。
查找模块802，用于查找与交易数据流向类别匹配的检测顺序表；检测顺序表包括按序排列的检查项，检查项的排列顺序符合合作交易系统中与交易数据流向类别对应的交易数据流向；确定合作交易系统中与交易标识对应的交易数据传输链路。
检测模块803，用于依次按照检测顺序表中的检查项对交易数据传输链路进行检测。
上述交易系统错误检测装置800，通过获取的交易标识自动确定与该交易标识对应的交易数据流向类别，并查找与交易数据流向类别匹配的检测顺序表，且确定合作交易系统中与交易标识对应的交易数据传输链路，再根据检测顺序表中按序排列的检查项对交易数据传输链路进行检测，在检测未通过时，展示与检查项对应的检测结果。其中，检查项的排列顺序是预先设置好的，且符合合作交易系统中与交易数据流向类别对应的交易数据流向。这种检测方式在获取到交易标识后自动进行检测，避免了测试人员手工检测时多次交互操作繁琐的检测过程，极大地提高了交易系统错误检测效率。
在一个实施例中，交易数据传输链路包括用于处理与交易标识对应的交易数据的业务服务器、集中交易服务器、内部前置服务器和合作对象前置服务器；其中，集中交易服务器连接业务服务器和内部前置服务器，合作对象前置服务器连接内部前置服务器。
在一个实施例中，当交易数据流向类别为内部流向合作对象类型时，检测模块803还用于对集中交易服务器中交易数据格式转换文件进行检测；若检测通过，则对集中交易服务器与内部前置服务器之间网络连接状态进行检测；若检测通过，则对内部前置服务器与合作对象前置服务器之间网络连接状态进行检测；若检测通过，则对内部前置服务器中交易数据记录文件进行 检测。
在一个实施例中，当交易数据流向类别为合作对象流向内部类型时，检测模块803还用于对内部前置服务器中交易数据记录文件进行检测；若检测通过，则对内部前置服务器与集中交易服务器之间网络连接状态进行检测；若检测通过，则对集中交易服务器中交易数据格式转换文件进行检测；若检测通过，则对集中交易服务器与业务服务器之间网络连接状态进行检测。
在一个实施例中，检测模块803还用于获取集中交易服务器中交易数据格式转换文件目录；根据交易数据格式转换文件目录查找与交易标识对应的交易数据格式转换文件；若查找到对应的交易数据格式转换文件，则检测交易数据格式转换文件格式是否正确。
图9为一个实施例中计算机设备的内部结构示意图。该计算机设备具体可以是图1中的终端110。如图9所示，该计算机设备包括通过系统总线连接的处理器、非易失性存储介质、内存储器、网络接口、显示屏和输入装置。其中，计算机设备的非易失性存储介质存储有操作系统、数据库和计算机可执行指令，该计算机可执行指令用于实现适用于计算机设备的一种交易系统错误检测方法。计算机设备的处理器用于提供计算和控制能力，支撑整个计算机设备的运行。计算机设备的内存储器中可储存有计算机可执行指令，该计算机可执行指令被处理器执行时，可使得处理器执行一种交易系统错误检测方法。网络接口用于与服务器进行网络通信，如获取服务器中的交易数据格式转换文件目录等，输入装置可以是显示屏上覆盖的触摸层，也可以是外接的键盘、触控板或鼠标等。本领域技术人员可以理解，图9中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定，具体的计算机设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
在一个实施例中，上述各个实施例中的交易系统错误检测装置可以实现为一种计算机程序的形式，计算机程序对应的计算机可执行指令可在如图9所示的计算机设备上运行。
上述交易系统错误检测装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。其中，网络接口可以是以太网卡或无线网卡等。上述各模块可以硬件形式内嵌于或独立于计算机设备的存储器中，也可以以软件形式存储于计算机设备的存储器中，以便于处理器调用执行以上各个模块对应的操作。该处理器可以为中央处理单元(CPU)、微处理器、单片机等。
在一个实施例中，提供了一个或多个存储有计算机可读指令的计算机可读非易失性存储介质，该计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：获取交易标识；确定与交易标识对应的交易数据流向类别；查找与交易数据流向类别匹配的检测顺序表，检测顺序表包括按序排列的检查项，检查项的排列顺序符合合作交易系统中与交易数据流向类别对应的交易数据流向；确定合作交易系统中与交易标识对应的交易数据传输链路；及依次按照检测顺序表中的检查项对交易数据传输链路进行检测。
在一个实施例中，交易数据传输链路包括用于处理与交易标识对应的交易数据的业务服务器、集中交易服务器、内部前置服务器和合作对象前置服务器；其中，集中交易服务器连接业务服务器和内部前置服务器，合作对象前置服务器连接内部前置服务器。
在一个实施例中，当交易数据流向类别为内部流向合作对象类型时，依次按照检测顺序表中的检查项对交易数据传输链路进行检测包括：对集中交易服务器中交易数据格式转换文件进行检测，若检测通过，则对集中交易服务器与内部前置服务器之间网络连接状态进行检测，若检测通过，则对内部前置服务器中交易数据记录文件进行检测，若检测通过，则对内部前置服务器与合作对象前置服务器之间网络连接状态进行检测。
在一个实施例中，当交易数据流向类别为合作对象流向内部类型时，依次按照检测顺序表中的检查项对交易数据传输链路进行检测包括：对内部前置服务器中交易数据记录文件进行检测，若检测通过，则对内部前置服务器与集中交易服务器之间网络连接状态进行检测，若检测通过，则对集中交易 服务器与业务服务器之间网络连接状态进行检测，若检测通过，则对集中交易服务器中交易数据格式转换文件进行检测。
在一个实施例中，对集中交易服务器中交易数据格式转换文件进行检测包括：获取集中交易服务器中交易数据格式转换文件目录；根据交易数据格式转换文件目录查找与交易标识对应的交易数据格式转换文件；及若查找到对应的交易数据格式转换文件，则检测交易数据格式转换文件格式是否正确。
上述存储介质，通过获取的交易标识自动确定与该交易标识对应的交易数据流向类别，并查找与交易数据流向类别匹配的检测顺序表，且确定合作交易系统中与交易标识对应的交易数据传输链路，再根据检测顺序表中按序排列的检查项对交易数据传输链路进行检测，在检测未通过时，展示与检查项对应的检测结果。其中，检查项的排列顺序是预先设置好的，且符合合作交易系统中与交易数据流向类别对应的交易数据流向。这种检测方式在获取到交易标识后自动进行检测，避免了测试人员手工检测时多次交互操作繁琐的检测过程，极大地提高了交易系统错误检测效率。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一非易失性计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对本申请专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

  1. 一种交易系统错误检测方法，包括：
    获取交易标识；
    确定与所述交易标识对应的交易数据流向类别；
    查找与所述交易数据流向类别匹配的检测顺序表，所述检测顺序表包括按序排列的检查项，所述检查项的排列顺序符合合作交易系统中与所述交易数据流向类别对应的交易数据流向；
    确定所述合作交易系统中与所述交易标识对应的交易数据传输链路；及
    依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测。
  2. 根据权利要求1所述的方法，其特征在于，所述交易数据传输链路包括用于处理与所述交易标识对应的交易数据的业务服务器、集中交易服务器、内部前置服务器和合作对象前置服务器；
    其中，所述集中交易服务器连接所述业务服务器和所述内部前置服务器，所述合作对象前置服务器连接所述内部前置服务器。
  3. 根据权利要求2所述的方法，其特征在于，当所述交易数据流向类别为内部流向合作对象类型时，所述依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测包括：
    对所述集中交易服务器中交易数据格式转换文件进行检测，若检测通过，则
    对所述集中交易服务器与所述内部前置服务器之间网络连接状态进行检测，若检测通过，则
    对所述内部前置服务器中交易数据记录文件进行检测，若检测通过，则
    对所述内部前置服务器与所述合作对象前置服务器之间网络连接状态进行检测。
  4. 根据权利要求2所述的方法，其特征在于，当所述交易数据流向类别为合作对象流向内部类型时，所述依次按照所述检测顺序表中的所述检查项 对所述交易数据传输链路进行检测包括：
    对所述内部前置服务器中交易数据记录文件进行检测，若检测通过，则
    对所述内部前置服务器与所述集中交易服务器之间网络连接状态进行检测，若检测通过，则
    对所述集中交易服务器与所述业务服务器之间网络连接状态进行检测，若检测通过，则
    对所述集中交易服务器中交易数据格式转换文件进行检测。
  5. 根据权利要求3或4所述的方法，其特征在于，所述对所述集中交易服务器中交易数据格式转换文件进行检测包括：
    获取所述集中交易服务器中交易数据格式转换文件目录；
    根据所述交易数据格式转换文件目录查找与所述交易标识对应的交易数据格式转换文件；及
    若查找到所述对应的交易数据格式转换文件，则检测所述交易数据格式转换文件格式是否正确。
  6. 一种交易系统错误检测装置，包括：
    获取模块，用于获取交易标识；确定与所述交易标识对应的交易数据流向类别；
    查找模块，用于查找与所述交易数据流向类别匹配的检测顺序表，所述检测顺序表包括按序排列的检查项，所述检查项的排列顺序符合合作交易系统中与所述交易数据流向类别对应的交易数据流向；确定所述合作交易系统中与所述交易标识对应的交易数据传输链路；及
    检测模块，用于依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测。
  7. 根据权利要求6所述的装置，其特征在于，所述交易数据传输链路包括用于处理与所述交易标识对应的交易数据的业务服务器、集中交易服务器、内部前置服务器和合作对象前置服务器；其中，所述集中交易服务器连接所述业务服务器和所述内部前置服务器，所述合作对象前置服务器连接所述内 部前置服务器。
  8. 根据权利要求7所述的装置，其特征在于，当所述交易数据流向类别为内部流向合作对象类型时，所述检测模块还用于对所述集中交易服务器中交易数据格式转换文件进行检测；若对所述集中交易服务器中交易数据格式转换文件检测通过，则对所述集中交易服务器与所述内部前置服务器之间网络连接状态进行检测；若对所述集中交易服务器与所述内部前置服务器之间网络连接状态检测通过，则对所述内部前置服务器与所述合作对象前置服务器之间网络连接状态进行检测；及若对所述内部前置服务器与所述合作对象前置服务器之间网络连接状态检测通过，则对所述内部前置服务器中交易数据记录文件进行检测。
  9. 根据权利要求7所述的装置，其特征在于，当所述交易数据流向类别为合作对象流向内部类型时，所述检测模块还用于对所述内部前置服务器中交易数据记录文件进行检测；若对所述内部前置服务器中交易数据记录文件检测通过，则对所述内部前置服务器与所述集中交易服务器之间网络连接状态进行检测；若对所述内部前置服务器与所述集中交易服务器之间网络连接状态检测通过，则对所述集中交易服务器中交易数据格式转换文件进行检测；及若对所述集中交易服务器中交易数据格式转换文件检测通过，则对所述集中交易服务器与所述业务服务器之间网络连接状态进行检测。
  10. 根据权利要求8或9所述的装置，其特征在于，所述检测模块还用于获取所述集中交易服务器中交易数据格式转换文件目录；根据所述交易数据格式转换文件目录查找与所述交易标识对应的交易数据格式转换文件；及若查找到所述对应的交易数据格式转换文件，则检测所述交易数据格式转换文件格式是否正确。
  11. 一个或多个存储有计算机可读指令的计算机可读非易失性存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行以下步骤：
    获取交易标识；
    确定与所述交易标识对应的交易数据流向类别；
    查找与所述交易数据流向类别匹配的检测顺序表，所述检测顺序表包括按序排列的检查项，所述检查项的排列顺序符合合作交易系统中与所述交易数据流向类别对应的交易数据流向；
    确定所述合作交易系统中与所述交易标识对应的交易数据传输链路；及
    依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测。
  12. 根据权利要求11所述的存储介质，其特征在于，所述交易数据传输链路包括用于处理与所述交易标识对应的交易数据的业务服务器、集中交易服务器、内部前置服务器和合作对象前置服务器；
    其中，所述集中交易服务器连接所述业务服务器和所述内部前置服务器，所述合作对象前置服务器连接所述内部前置服务器。
  13. 根据权利要求12所述的存储介质，其特征在于，当所述交易数据流向类别为内部流向合作对象类型时，所述依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测包括：
    对所述集中交易服务器中交易数据格式转换文件进行检测，若检测通过，则
    对所述集中交易服务器与所述内部前置服务器之间网络连接状态进行检测，若检测通过，则
    对所述内部前置服务器中交易数据记录文件进行检测，若检测通过，则
    对所述内部前置服务器与所述合作对象前置服务器之间网络连接状态进行检测。
  14. 根据权利要求12所述的存储介质，其特征在于，当所述交易数据流向类别为合作对象流向内部类型时，所述依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测包括：
    对所述内部前置服务器中交易数据记录文件进行检测，若检测通过，则
    对所述内部前置服务器与所述集中交易服务器之间网络连接状态进行检 测，若检测通过，则
    对所述集中交易服务器与所述业务服务器之间网络连接状态进行检测，若检测通过，则
    对所述集中交易服务器中交易数据格式转换文件进行检测。
  15. 根据权利要求13或14所述的存储介质，其特征在于，所述对所述集中交易服务器中交易数据格式转换文件进行检测包括：
    获取所述集中交易服务器中交易数据格式转换文件目录；
    根据所述交易数据格式转换文件目录查找与所述交易标识对应的交易数据格式转换文件；及
    若查找到所述对应的交易数据格式转换文件，则检测所述交易数据格式转换文件格式是否正确。
  16. 一种计算机设备，包括存储器和处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述处理器执行以下步骤：获取交易标识；
    确定与所述交易标识对应的交易数据流向类别；
    查找与所述交易数据流向类别匹配的检测顺序表，所述检测顺序表包括按序排列的检查项，所述检查项的排列顺序符合合作交易系统中与所述交易数据流向类别对应的交易数据流向；
    确定所述合作交易系统中与所述交易标识对应的交易数据传输链路；及
    依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测。
  17. 根据权利要求16所述的计算机设备，其特征在于，所述交易数据传输链路包括用于处理与所述交易标识对应的交易数据的业务服务器、集中交易服务器、内部前置服务器和合作对象前置服务器；
    其中，所述集中交易服务器连接所述业务服务器和所述内部前置服务器，所述合作对象前置服务器连接所述内部前置服务器。
  18. 根据权利要求17所述的计算机设备，其特征在于，当所述交易数据 流向类别为内部流向合作对象类型时，所述依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测包括：
    对所述集中交易服务器中交易数据格式转换文件进行检测，若检测通过，则
    对所述集中交易服务器与所述内部前置服务器之间网络连接状态进行检测，若检测通过，则
    对所述内部前置服务器中交易数据记录文件进行检测，若检测通过，则
    对所述内部前置服务器与所述合作对象前置服务器之间网络连接状态进行检测。
  19. 根据权利要求17所述的计算机设备，其特征在于，当所述交易数据流向类别为合作对象流向内部类型时，所述依次按照所述检测顺序表中的所述检查项对所述交易数据传输链路进行检测包括：
    对所述内部前置服务器中交易数据记录文件进行检测，若检测通过，则
    对所述内部前置服务器与所述集中交易服务器之间网络连接状态进行检测，若检测通过，则
    对所述集中交易服务器与所述业务服务器之间网络连接状态进行检测，若检测通过，则
    对所述集中交易服务器中交易数据格式转换文件进行检测。
  20. 根据权利要求18或19所述的计算机设备，其特征在于，所述对所述集中交易服务器中交易数据格式转换文件进行检测包括：
    获取所述集中交易服务器中交易数据格式转换文件目录；
    根据所述交易数据格式转换文件目录查找与所述交易标识对应的交易数据格式转换文件；及
    若查找到所述对应的交易数据格式转换文件，则检测所述交易数据格式转换文件格式是否正确。
PCT/CN2017/099728 2016-12-14 2017-08-30 交易系统错误检测方法、装置、存储介质和计算机设备 Ceased WO2018107812A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
US16/070,549 US20190026707A1 (en) 2016-12-14 2017-08-30 Method of detecting transaction system error, device, storage medium, and computer equipment
KR1020187018395A KR102274561B1 (ko) 2016-12-14 2017-08-30 거래 시스템 에러 검출 방법, 장치, 저장 매체 및 컴퓨터 장치
EP17872887.9A EP3570170A4 (en) 2016-12-14 2017-08-30 ERROR DETECTION METHOD AND APPARATUS FOR TRANSACTION SYSTEMS, STORAGE MEDIA AND COMPUTER DEVICES
JP2018517562A JP6614756B2 (ja) 2016-12-14 2017-08-30 取引システムエラー検出方法、装置、記憶媒体及びコンピュータデバイス
AU2017370317A AU2017370317A1 (en) 2016-12-14 2017-08-30 Method of detecting transaction system error, device, storage medium, and computer equipment
SG11201805501VA SG11201805501VA (en) 2016-12-14 2017-08-30 Method of detecting transaction system error, device, storage medium, and computer equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611154475.1A CN107679051B (zh) 2016-12-14 2016-12-14 交易系统错误检测方法和装置
CN201611154475.1 2016-12-14

Publications (1)

Publication Number Publication Date
WO2018107812A1 true WO2018107812A1 (zh) 2018-06-21

Family

ID=61133481

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/099728 Ceased WO2018107812A1 (zh) 2016-12-14 2017-08-30 交易系统错误检测方法、装置、存储介质和计算机设备

Country Status (8)

Country Link
US (1) US20190026707A1 (zh)
EP (1) EP3570170A4 (zh)
JP (1) JP6614756B2 (zh)
KR (1) KR102274561B1 (zh)
CN (1) CN107679051B (zh)
AU (1) AU2017370317A1 (zh)
SG (1) SG11201805501VA (zh)
WO (1) WO2018107812A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112613967A (zh) * 2020-12-29 2021-04-06 南方电网数字电网研究院有限公司 业务交易数据处理方法、装置、计算机设备和存储介质
CN115250245A (zh) * 2022-06-24 2022-10-28 中信百信银行股份有限公司 一种多机房支付系统前置与应用多活的方法及装置

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109726048A (zh) * 2018-12-13 2019-05-07 中国银联股份有限公司 一种交易系统中数据恢复方法及装置
CN110415115A (zh) * 2019-06-18 2019-11-05 平安证券股份有限公司 交易系统的运维方法、装置及计算机可读存储介质
CN110674184B (zh) * 2019-09-06 2023-10-17 创新先进技术有限公司 一种构造异动检测模型库的方法、系统及设备
CN112465505B (zh) * 2020-12-17 2024-03-22 泸州银行股份有限公司 一种基于交易链组装的交易风险监控方法
CN113959483A (zh) * 2021-08-31 2022-01-21 格力电器（武汉）有限公司 空调质量检测方法以及检测系统
CN114584490B (zh) * 2022-03-25 2024-04-09 阿里巴巴（中国）有限公司 数据传输检测方法以及装置
CN118214681A (zh) * 2022-12-16 2024-06-18 脸萌有限公司 数据分析方法、装置、设备和存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103678085A (zh) * 2013-12-16 2014-03-26 上海证券交易所 一种流量动态可控的系统监控数据采集方法
CN105869033A (zh) * 2016-04-05 2016-08-17 王升 一种检测网络交易系统内部错误的方法及对应的设备系统

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5557780A (en) * 1992-04-30 1996-09-17 Micron Technology, Inc. Electronic data interchange system for managing non-standard data
JP3374925B2 (ja) * 1992-11-17 2003-02-10 日本電信電話株式会社 資源予約管理装置
JP3165765B2 (ja) * 1993-09-20 2001-05-14 富士通株式会社 Ｃａｄ設計支援装置
JP2000330808A (ja) * 1999-05-19 2000-11-30 Mitsubishi Electric Corp トランザクション処理システム
US6624817B1 (en) * 1999-12-31 2003-09-23 Intel Corporation Symmetrical accelerated graphics port (AGP)
AUPQ696500A0 (en) * 2000-04-17 2000-05-11 Qsi Payment Technologies Pty Ltd Electronic commerce payment system
US20020116205A1 (en) * 2000-05-19 2002-08-22 Ankireddipally Lakshmi Narasimha Distributed transaction processing system
GB2369973B (en) * 2000-12-06 2002-12-04 Open Business Exchange Ltd Communication Router
US7103597B2 (en) * 2002-10-03 2006-09-05 Mcgoveran David O Adaptive transaction manager for complex transactions and business process
JP4291060B2 (ja) * 2003-07-01 2009-07-08 富士通株式会社 トランザクション処理方法，トランザクション制御装置およびトランザクション制御プログラム
KR20060083275A (ko) * 2005-01-14 2006-07-20 삼성전자주식회사 Ｎｏ.7 망에서 신호 링크 부하 분담 방법 및 장치
US7840456B2 (en) * 2007-05-30 2010-11-23 Intuit Inc. System and method for categorizing credit card transaction data
JP2010176300A (ja) * 2009-01-28 2010-08-12 Fuji Xerox Co Ltd 情報処理システム、情報処理装置、要求処理装置、情報処理プログラム、要求処理プログラム
CN101895435A (zh) * 2009-11-30 2010-11-24 英业达股份有限公司 检测服务器的安装模块的方法
JP5869513B2 (ja) * 2013-04-05 2016-02-24 株式会社日立製作所 障害対応システムおよび障害対応方法
US11797689B2 (en) * 2013-06-18 2023-10-24 Cloud Broker Ip Innovation, Llc Enabling reliable communications between computing instances
CN105931028A (zh) * 2016-05-13 2016-09-07 中国建设银行股份有限公司 一种银企直联系统的管理方法及系统
CN106155906B (zh) * 2016-07-05 2019-01-15 中国银行股份有限公司 一种银行主机内部测试系统及方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103678085A (zh) * 2013-12-16 2014-03-26 上海证券交易所 一种流量动态可控的系统监控数据采集方法
CN105869033A (zh) * 2016-04-05 2016-08-17 王升 一种检测网络交易系统内部错误的方法及对应的设备系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3570170A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112613967A (zh) * 2020-12-29 2021-04-06 南方电网数字电网研究院有限公司 业务交易数据处理方法、装置、计算机设备和存储介质
CN112613967B (zh) * 2020-12-29 2023-01-20 南方电网数字电网研究院有限公司 业务交易数据处理方法、装置、计算机设备和存储介质
CN115250245A (zh) * 2022-06-24 2022-10-28 中信百信银行股份有限公司 一种多机房支付系统前置与应用多活的方法及装置

Also Published As

Publication number Publication date
KR20190095099A (ko) 2019-08-14
KR102274561B1 (ko) 2021-07-08
CN107679051B (zh) 2019-02-01
US20190026707A1 (en) 2019-01-24
EP3570170A1 (en) 2019-11-20
AU2017370317A1 (en) 2018-07-05
JP2019505028A (ja) 2019-02-21
JP6614756B2 (ja) 2019-12-04
EP3570170A4 (en) 2020-11-11
CN107679051A (zh) 2018-02-09
SG11201805501VA (en) 2018-07-30

Similar Documents

Publication Publication Date Title
WO2018107812A1 (zh) 交易系统错误检测方法、装置、存储介质和计算机设备
CN108683562B (zh) 异常检测定位方法、装置、计算机设备及存储介质
CN113238940B (zh) 一种接口测试结果的比对方法、装置、设备和存储介质
US9483386B2 (en) Information interaction test device and method based on automatic generation of associated test cases
CN108763076A (zh) 一种软件自动测试方法、装置、设备及介质
US12079298B2 (en) Methods and systems for browser extension used to generate relative XPath, absolute XPath and/or CSS selectors
US20240338306A1 (en) Automatic generation of test scenarios from specification files
CN113392024B (zh) 存储过程的测试方法、装置、设备及介质
CN106502895A (zh) 一种自动化测试信息生成装置及方法
CN113032244A (zh) 接口测试方法、装置、计算机系统和计算机可读存储介质
CN106775937A (zh) 一种命令行校验方法及装置
CN113590172B (zh) 一种代码文件发布方法、装置、设备及存储介质
CN111881054A (zh) 用户界面自动化测试方法、系统、设备及存储介质
CN112199277B (zh) 一种基于浏览器的缺陷复现方法、装置、设备及存储介质
CN108255654A (zh) 自动检测方法及装置
CN108073429A (zh) 一种支付方式配置方法、装置、设备及存储介质
US20170351730A1 (en) Automatically correcting invalid scripts in web applications
WO2020232900A1 (zh) 系统测试方法及装置、计算机设备、存储介质
US20260064244A1 (en) Merge menu directed inspections from multiple borescope inspections into a single inspection and report
CN110716843B (zh) 系统故障分析处理方法、装置、存储介质及电子设备
CN113986381B (zh) 数据解析方法、装置、设备及存储介质
CN112528577A (zh) 时钟复位电路的管理方法、装置和计算机存储介质
CN114048123A (zh) 一种终端认证报告的审核方法及设备
CN114461724A (zh) 一种基于随机抽样的数据同步比对方法、装置及系统
CN114297055A (zh) 一种基于智能学习的WebUI自动化测试方法

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018517562

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 11201805501V

Country of ref document: SG

ENP Entry into the national phase

Ref document number: 20187018395

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017370317

Country of ref document: AU

Date of ref document: 20170830

Kind code of ref document: A

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

Ref document number: 17872887

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE