Core business system access queue system and method

Abstract

The present invention provides a core business system access queue system and method, including: CTIN function module, encryption machine proxy module and Tuxedo proxy module; the CTIN function module is responsible for caching concurrent requests and calling Tuxedo proxy module and encryption machine proxy module; the Tuxedo proxy module is responsible for using Tuxedo client to call backend CTSP / OTIP service; the encryption machine proxy module is responsible for calling the encryption machine to perform encryption and decryption and calculate the message MAC. The present invention further improves the transaction service capability of the core business system; copes with Internet application surges, core daily cuts and suspension services; and shortens the time consumption of the core start and stop process.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a method and system for accessing a core business system queue. Background Art

[0002] CTIN has no queue mechanism and will send all received requests to the core application layer, resulting in high CTSP application concurrency, serious database internal lock competition, and increased average transaction response time. Directly rejecting transaction requests after exceeding the maximum number of connections is not friendly to the front-end system.

[0003] Patent document CN104219235B (application number: 201410430832.7) discloses a distributed transaction request method, including: the access node reads the message to be processed from the message queue and selects the computing node of the message; generates the session information of the message, sends the message to the computing node, and stores the session information in the session storage node; after receiving the message, the computing node processes the message, updates the session information, and sends the response information to the access node; the access node determines whether the waiting for the response information has timed out, if so, sends a query request to the computing node; if not, continues to wait; after receiving the query request, the computing node returns the session processing result; the access node chooses to continue waiting or resend the message to a new computing node for processing according to the received session processing result. The present invention also discloses a distributed transaction request device. Summary of the invention

[0004] In view of the defects in the prior art, the object of the present invention is to provide a core business system access queue system and method.

[0005] A core business system access queue system provided according to the present invention includes: a CTIN function module, an encryption machine proxy module and a Tuxedo proxy module;

[0006] The CTIN function module is responsible for caching concurrent requests and calling the Tuxedo proxy module and the encryption machine proxy module;

[0007] The Tuxedo proxy module is responsible for using the Tuxedo client to call the backend CTSP / OTIP service;

[0008] The encryption machine proxy module is responsible for calling the encryption machine to perform encryption and decryption and calculate the message MAC.

[0009] Preferably, the CTIN functional module, the encryption machine proxy module and the Tuxedo proxy module are all multi-threaded asynchronous communication models, and asynchronous communication is used between the CTIN functional module, the encryption machine proxy module and the Tuxedo proxy module.

[0010] Preferably, synchronous communication is used between the Tuxedo proxy module and the backend CTSP / OTIP service.

[0011] Preferably, synchronous communication is used between the encryption machine proxy module and the encryption machine.

[0012] Preferably, the CTIN functional module, the encryption machine proxy module and the Tuxedo proxy module all have a queue scheduling mechanism.

[0013] Preferably, the CTIN module includes: a resource restriction acquisition module, a queue scheduling module, an IO thread module, a management command thread module, an accept thread module, an internal IPC communication module, a communication module, a management command module, a client IO module, an encryption machine proxy module, and a Tuxedo proxy module.

[0014] The resource limit acquisition module is used to obtain the limited usage of various system resources that each process can create;

[0015] The queue scheduling module implements queue insertion data, queue retrieval data, transaction grouping, transaction service, number, host address queue scheduling, client sleep and queue scheduling status;

[0016] The IO thread module implementation includes adding a new client, calling online command processing and IO thread event loop;

[0017] The management command thread module implementation includes setting whether the management command is executable, whether it is acceptable, management command execution, reception, timeout processing and management command thread event loop;

[0018] The accept thread module implementation includes thread mutex, client call, socket connection acceptance, accept thread event loop and wake-up event;

[0019] The internal IPC communication module implements the sending of scheduling commands, receiving of scheduling commands, sending of online commands, and receiving of online commands;

[0020] The communication module implementation includes synchronous communication, asynchronous communication and connection check;

[0021] The management command module implementation includes direct exit, safe exit, safe restart, version acquisition, status acquisition, normal service status, transaction access but no command processing, management command execution and response;

[0022] The client IO module implementation includes the client sending a request and receiving a response;

[0023] The encryption machine proxy module includes encryption and decryption of the encryption machine, setting MAC, checking MAC, sending requests to the encryption machine proxy, receiving responses, encryption machine connection checking, and encryption machine reconnection;

[0024] The Tuxedo proxy module call implementation includes sending a request to the Tuxedo proxy, receiving a response, Tuxedo connection checking, and Tuxedo reconnection.

[0025] Preferably, the encryption machine proxy module includes a resource restriction acquisition module, an IO thread module, an encryption machine thread module, an accept thread module, a queue module, an internal IPC communication module and a client IO module;

[0026] The resource limit acquisition module is used to obtain the limited usage of various system resources that each process can create;

[0027] The IO thread module implementation includes IO thread increase and decrease, call, wake-up, retry command processing and IO thread event loop;

[0028] The encryption machine thread module implementation includes setting the encryption machine return, socket connection and encryption machine thread event loop;

[0029] The accept thread module implementation includes thread mutex, client call, socket connection acceptance and accept thread event loop;

[0030] The queue module implementation includes queue insertion, queue retrieval, request generation, request retry, request deletion, request destruction, request clearing, response wake-up, response retry and response waiting;

[0031] The internal IPC communication module includes sending a scheduling command, receiving a scheduling command, sending a wake-up command, receiving a wake-up command, sending a retry command, and receiving a retry command;

[0032] The client IO module implementation includes creating a client, deleting a client, creating an encryption machine message, deleting an encryption machine message, checking whether the message has been deleted, the client sending a request, and the client receiving a return.

[0033] Preferably, the Tuxedo proxy module includes: a resource restriction acquisition module, an IO thread module, a Tuxedo thread module, an accept thread module, a queue module, an internal IPC communication module and a client IO module;

[0034] The resource limit acquisition module is used to obtain the limited usage of various system resources that each process can create;

[0035] The IO thread module implementation includes IO thread addition and subtraction, calling, wake-up command processing and IO thread event loop;

[0036] The Tuxedo thread module implementation includes request consumption, client synchronous call to server service and response generation;

[0037] The accept thread module implementation includes calling the client, socket accepting connection and accept thread event loop;

[0038] The queue module implementation includes queue insertion, queue retrieval, request generation, request destruction, request clearing, response generation, response clearing and response waiting;

[0039] The internal IPC communication module includes sending a scheduling command, receiving a scheduling command, sending a wake-up command, and receiving a wake-up command;

[0040] The client IO module implementation includes creating a client, deleting a client, creating a Tuxedo message, deleting a Tuxedo message, checking whether the message has been deleted, the client sending a request, and the client receiving a response.

[0041] A core business system access queue method provided by the present invention includes: a CTIN function module, an encryption machine proxy module and a Tuxedo proxy module;

[0042] The CTIN function module is responsible for caching concurrent requests and calling the Tuxedo proxy module and the encryption machine proxy module;

[0043] The Tuxedo proxy module is responsible for using the Tuxedo client to call the backend CTSP / OTIP service;

[0044] The encryption machine proxy module is responsible for calling the encryption machine to perform encryption and decryption and calculate the message MAC.

[0045] Preferably, the CTIN function module, the encryption machine proxy module and the Tuxedo proxy module are all multi-threaded asynchronous communication models, and asynchronous communication is used between the CTIN function module, the encryption machine proxy module and the Tuxedo proxy module;

[0046] Synchronous communication is used between the Tuxedo proxy module and the backend CTSP / OTIP service;

[0047] The encryption machine proxy module and the encryption machine use synchronous communication;

[0048] The CTIN function module, the encryption machine proxy module and the Tuxedo proxy module all have a queue scheduling mechanism.

[0049] Compared with the prior art, the present invention has the following beneficial effects: the present invention further improves the transaction service capability of the core business system; copes with Internet application surges and core daily service suspensions; and shortens the time consumption of the core startup and shutdown process. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0051] Figure 1 This is a schematic diagram of the core business system access queue system. DETAILED DESCRIPTION

[0052] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0053] Example 1

[0054] In order to solve the problem in the prior art that transaction requests exceeding the maximum number of connections are queued for processing instead of being directly rejected, the present invention provides a core business system access queue system and method.

[0055] According to a core business system access queue system provided by the present invention, Figure 1 As shown, it includes: CTIN function module, encryption machine proxy module and Tuxedo proxy module;

[0056] The CTIN function module is responsible for caching concurrent requests and calling the Tuxedo proxy module and the encryption machine proxy module;

[0057] The Tuxedo proxy module is responsible for using the Tuxedo client to call the backend CTSP / OTIP service;

[0058] The encryption machine proxy module is responsible for calling the encryption machine to perform encryption and decryption and calculate the message MAC.

[0059] Specifically, the CTIN functional module, the encryption machine proxy module and the Tuxedo proxy module are all multi-threaded asynchronous communication models, and asynchronous communication is used between the CTIN functional module, the encryption machine proxy module and the Tuxedo proxy module to further decouple Tuxedo services.

[0060] Specifically, synchronous communication is used between the Tuxedo proxy module and the backend CTSP / OTIP service.

[0061] Specifically, synchronous communication is used between the encryption machine proxy module and the encryption machine.

[0062] Specifically, the CTIN functional module, the encryption machine proxy module and the Tuxedo proxy module all have a queue scheduling mechanism.

[0063] The present invention implements a queue scheduling and management mechanism for access modules. Through the queue mechanism, concurrent requests are cached to buffer system pressure instead of directly rejecting requests. Asynchronous communication is used between modules to alleviate the online real-time service pressure caused by transactions with long processing times, further improve the transaction service capabilities of the core business system, and meet the transaction service needs with Internet surge characteristics caused by factors such as the bank's group strategy adjustment and changing application needs.

[0064] Specifically, the CTIN module includes: a resource restriction acquisition module, a queue scheduling module, an IO thread module, a management command thread module, an accept thread module, an internal IPC communication module, a communication module, a management command module, a client IO module, an encryption machine proxy module, and a Tuxedo proxy module;

[0065] The resource limit acquisition module is used to obtain the limited usage of various system resources that each process can create;

[0066] The queue scheduling module implements queue insertion data, queue retrieval data, transaction grouping, transaction service, number, host address queue scheduling, client sleep and queue scheduling status;

[0067] It includes the following processing: blocking in pause state, waking up after online, waking up after parallel release, waking up and blocking again, etc.

[0068] The IO thread module implementation includes adding a new client, calling online command processing and IO thread event loop (including encryption machine events and Tuxedo events);

[0069] Including various exception handling: memory exhaustion, encryption machine reconnection, Tuxedo reconnection, etc.

[0070] The management command thread module implementation includes setting whether the management command is executable, whether it is acceptable, management command execution, reception, timeout processing and management command thread event loop;

[0071] Including various exception handling: IO timeout, serial, etc.

[0072] The accept thread module implementation includes thread mutex, client call, socket connection acceptance, accept thread event loop and wake-up event;

[0073] Includes exception handling: fd exhausted.

[0074] The internal IPC communication module implements the sending of scheduling commands, receiving of scheduling commands, sending of online commands, and receiving of online commands;

[0075] The communication module implementation includes synchronous communication, asynchronous communication and connection check;

[0076] The management command module implements commands including direct exit, safe exit, safe restart, obtain version, obtain status, online (normal service status), pause (transactions can be accessed but not processed), management command execution and response;

[0077] The client IO module implementation includes the client sending a request and receiving a response;

[0078] Including various exception handling: timeout handling, automatic reconnection in case of exception, cli recycling of recv queue in case of exception, cli reset of send queue in case of exception, priority of write-back message, etc.

[0079] The encryption machine proxy module includes encryption and decryption of the encryption machine, setting MAC, checking MAC, sending requests to the encryption machine proxy, receiving responses, encryption machine connection checking, and encryption machine reconnection;

[0080] Including various exception handling: the link with the encryption machine proxy crashes after sending a request, the transaction timeouts during the request sending, the timeout while waiting for the encryption machine proxy response message, the encryption machine proxy response is received after the transaction has timed out, various IO errors, etc.

[0081] The Tuxedo proxy module call implementation includes sending a request to the Tuxedo proxy, receiving a response, Tuxedo connection checking, and Tuxedo reconnection.

[0082] Including various exception handling: link collapse with Tuxedo proxy after sending request, transaction timeout during request sending, timeout while waiting for Tuxedo proxy response message, receiving Tuxedo proxy response after transaction has timed out, various IO errors, etc.

[0083] Specifically, the encryption machine proxy module includes a resource restriction acquisition module, an IO thread module, an encryption machine thread module, an accept thread module, a queue module, an internal IPC communication module, and a client IO module;

[0084] The resource limit acquisition module is used to obtain the limited usage of various system resources that each process can create;

[0085] The IO thread module implementation includes IO thread increase and decrease, call, wake-up, retry command processing and IO thread event loop;

[0086] Including various exception handling: memory exhaustion, response timeout, request retry, etc.

[0087] The encryption machine thread module implementation includes setting the encryption machine return, socket connection and encryption machine thread event loop;

[0088] Including various exception handling: fd exhaustion, response retry, response wakeup, etc.

[0089] The accept thread module implementation includes thread mutex, client call, socket connection acceptance and accept thread event loop;

[0090] Includes exception handling: fd exhausted.

[0091] The queue module implementation includes queue insertion, queue retrieval, request generation, request retry, request deletion, request destruction, request clearing, response wake-up, response retry and response waiting;

[0092] The internal IPC communication module includes sending a scheduling command, receiving a scheduling command, sending a wake-up command, receiving a wake-up command, sending a retry command, and receiving a retry command;

[0093] The client IO module implementation includes creating a client, deleting a client, creating an encryption machine message, deleting an encryption machine message, checking whether the message has been deleted, the client sending a request, and the client receiving a return.

[0094] Including various exception handling: memory exhaustion, transaction timeout, various IO errors, etc.

[0095] Specifically, the Tuxedo proxy module includes: a resource restriction acquisition module, an IO thread module, a Tuxedo thread module, an accept thread module, a queue module, an internal IPC communication module and a client IO module;

[0096] The resource limit acquisition module is used to obtain the limited usage of various system resources that each process can create;

[0097] The IO thread module implementation includes IO thread addition and subtraction, calling, wake-up command processing and IO thread event loop;

[0098] Including various exception handling: memory exhaustion, transaction timeout, etc.

[0099] The Tuxedo thread module implementation includes request consumption, client synchronous call to server service and response generation;

[0100] Includes exception handling: retry when response generation fails.

[0101] The accept thread module implementation includes calling the client, socket accepting connection and accept thread event loop;

[0102] Includes exception handling: fd exhausted.

[0103] The queue module implementation includes queue insertion, queue retrieval, request generation, request destruction, request clearing, response generation, response clearing and response waiting;

[0104] The internal IPC communication module includes sending a scheduling command, receiving a scheduling command, sending a wake-up command, and receiving a wake-up command;

[0105] The client IO module implementation includes creating a client, deleting a client, creating a Tuxedo message, deleting a Tuxedo message, checking whether the message has been deleted, the client sending a request, and the client receiving a response.

[0106] Including various exception handling: memory exhaustion, IO timeout, various IO errors, etc.

[0107] A core business system access queue method provided by the present invention includes: a CTIN function module, an encryption machine proxy module and a Tuxedo proxy module;

[0108] The CTIN function module is responsible for caching concurrent requests and calling the Tuxedo proxy module and the encryption machine proxy module;

[0109] The Tuxedo proxy module is responsible for using the Tuxedo client to call the backend CTSP / OTIP service;

[0110] The encryption machine proxy module is responsible for calling the encryption machine to perform encryption and decryption and calculate the message MAC.

[0111] Specifically, the CTIN functional module, the encryption machine proxy module and the Tuxedo proxy module are all multi-threaded asynchronous communication models, and asynchronous communication is used between the CTIN functional module, the encryption machine proxy module and the Tuxedo proxy module to further decouple Tuxedo services.

[0112] Specifically, synchronous communication is used between the Tuxedo proxy module and the backend CTSP / OTIP service.

[0113] Specifically, synchronous communication is used between the encryption machine proxy module and the encryption machine.

[0114] Specifically, the CTIN functional module, the encryption machine proxy module and the Tuxedo proxy module all have a queue scheduling mechanism.

[0115] The present invention implements a queue scheduling and management mechanism for access modules. Through the queue mechanism, concurrent requests are cached to buffer system pressure instead of directly rejecting requests. Asynchronous communication is used between modules to alleviate the online real-time service pressure caused by transactions with long processing times, further improve the transaction service capabilities of the core business system, and meet the transaction service needs with Internet surge characteristics caused by factors such as the bank's group strategy adjustment and changing application needs.

[0116] Specifically, the CTIN module includes: a resource restriction acquisition module, a queue scheduling module, an IO thread module, a management command thread module, an accept thread module, an internal IPC communication module, a communication module, a management command module, a client IO module, an encryption machine proxy module, and a Tuxedo proxy module;

[0117] The resource limit acquisition module is used to obtain the limited usage of various system resources that each process can create;

[0118] The queue scheduling module implements queue insertion data, queue retrieval data, transaction grouping, transaction service, number, host address queue scheduling, client sleep and queue scheduling status;

[0119] It includes the following processing: blocking in pause state, waking up after online, waking up after parallel release, waking up and blocking again, etc.

[0120] The IO thread module implementation includes adding a new client, calling online command processing and IO thread event loop (including encryption machine events and Tuxedo events);

[0121] Including various exception handling: memory exhaustion, encryption machine reconnection, Tuxedo reconnection, etc.

[0122] The management command thread module implementation includes setting whether the management command is executable, whether it is acceptable, management command execution, reception, timeout processing and management command thread event loop;

[0123] Including various exception handling: IO timeout, serial, etc.

[0124] The accept thread module implementation includes thread mutex, client call, socket connection acceptance, accept thread event loop and wake-up event;

[0125] Includes exception handling: fd exhausted.

[0126] The internal IPC communication module implements the sending of scheduling commands, receiving of scheduling commands, sending of online commands, and receiving of online commands;

[0127] The communication module implementation includes synchronous communication, asynchronous communication and connection check;

[0128] The management command module implements commands including direct exit, safe exit, safe restart, obtain version, obtain status, online (normal service status), pause (transactions can be accessed but not processed), management command execution and response;

[0129] The client IO module implementation includes the client sending a request and receiving a response;

[0130] Including various exception handling: timeout handling, automatic reconnection in case of exception, cli recycling of recv queue in case of exception, cli reset of send queue in case of exception, priority of write-back message, etc.

[0131] The encryption machine proxy module includes encryption and decryption of the encryption machine, setting MAC, checking MAC, sending requests to the encryption machine proxy, receiving responses, encryption machine connection checking, and encryption machine reconnection;

[0132] Including various exception handling: the link with the encryption machine proxy crashes after sending a request, the transaction timeouts during the request sending, the timeout while waiting for the encryption machine proxy response message, the encryption machine proxy response is received after the transaction has timed out, various IO errors, etc.

[0133] The Tuxedo proxy module call implementation includes sending a request to the Tuxedo proxy, receiving a response, Tuxedo connection checking, and Tuxedo reconnection.

[0134] Including various exception handling: link collapse with Tuxedo proxy after sending request, transaction timeout during request sending, timeout while waiting for Tuxedo proxy response message, receiving Tuxedo proxy response after transaction has timed out, various IO errors, etc.

[0135] Specifically, the encryption machine proxy module includes a resource restriction acquisition module, an IO thread module, an encryption machine thread module, an accept thread module, a queue module, an internal IPC communication module, and a client IO module;

[0136] The resource limit acquisition module is used to obtain the limited usage of various system resources that each process can create;

[0137] The IO thread module implementation includes IO thread increase and decrease, call, wake-up, retry command processing and IO thread event loop;

[0138] Including various exception handling: memory exhaustion, response timeout, request retry, etc.

[0139] The encryption machine thread module implementation includes setting the encryption machine return, socket connection and encryption machine thread event loop;

[0140] Including various exception handling: fd exhaustion, response retry, response wakeup, etc.

[0141] The accept thread module implementation includes thread mutex, client call, socket connection acceptance and accept thread event loop;

[0142] Includes exception handling: fd exhausted.

[0143] The queue module implementation includes queue insertion, queue retrieval, request generation, request retry, request deletion, request destruction, request clearing, response wake-up, response retry and response waiting;

[0144] The internal IPC communication module includes sending a scheduling command, receiving a scheduling command, sending a wake-up command, receiving a wake-up command, sending a retry command, and receiving a retry command;

[0145] The client IO module implementation includes creating a client, deleting a client, creating an encryption machine message, deleting an encryption machine message, checking whether the message has been deleted, the client sending a request, and the client receiving a return.

[0146] Including various exception handling: memory exhaustion, transaction timeout, various IO errors, etc.

[0147] Specifically, the Tuxedo proxy module includes: a resource restriction acquisition module, an IO thread module, a Tuxedo thread module, an accept thread module, a queue module, an internal IPC communication module and a client IO module;

[0148] The resource limit acquisition module is used to obtain the limited usage of various system resources that each process can create;

[0149] The IO thread module implementation includes IO thread addition and subtraction, calling, wake-up command processing and IO thread event loop;

[0150] Including various exception handling: memory exhaustion, transaction timeout, etc.

[0151] The Tuxedo thread module implementation includes request consumption, client synchronous call to server service and response generation;

[0152] Includes exception handling: retry when response generation fails.

[0153] The accept thread module implementation includes calling the client, socket accepting connection and accept thread event loop;

[0154] Includes exception handling: fd exhausted.

[0155] The queue module implementation includes queue insertion, queue retrieval, request generation, request destruction, request clearing, response generation, response clearing and response waiting;

[0156] The internal IPC communication module includes sending a scheduling command, receiving a scheduling command, sending a wake-up command, and receiving a wake-up command;

[0157] The client IO module implementation includes creating a client, deleting a client, creating a Tuxedo message, deleting a Tuxedo message, checking whether the message has been deleted, the client sending a request, and the client receiving a response.

[0158] Including various exception handling: memory exhaustion, IO timeout, various IO errors, etc.

[0159] Those skilled in the art know that, in addition to implementing the system, device and its various modules provided by the present invention in a purely computer-readable program code, it is entirely possible to implement the same program in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded microcontrollers by logically programming the method steps. Therefore, the system, device and its various modules provided by the present invention can be considered as a hardware component, and the modules included therein for implementing various programs can also be considered as structures within the hardware component; the modules for implementing various functions can also be considered as both software programs for implementing the method and structures within the hardware component.

[0160] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. A core business system access queue system, characterized in that: include: CTIN functional module, encryption machine proxy module and Tuxedo proxy module; The CTIN function module is responsible for caching concurrent requests and calling the Tuxedo proxy module and the encryption machine proxy module; The Tuxedo proxy module is responsible for using the Tuxedo client to call the backend CTSP / OTIP service; The encryption machine proxy module is responsible for calling the encryption machine to perform encryption and decryption and calculate the message MAC; The CTIN function module, the encryption machine proxy module and the Tuxedo proxy module are all multi-threaded asynchronous communication models, and asynchronous communication is used between the CTIN function module, the encryption machine proxy module and the Tuxedo proxy module; Synchronous communication is used between the Tuxedo proxy module and the backend CTSP / OTIP service; The encryption machine proxy module and the encryption machine use synchronous communication; The CTIN function module, the encryption machine proxy module and the Tuxedo proxy module all have a queue scheduling mechanism; The CTIN function module includes: an acquisition resource restriction module in the CTIN function module, a queue scheduling module in the CTIN function module, an IO thread module in the CTIN function module, a management command thread module in the CTIN function module, an accept thread module in the CTIN function module, an internal IPC communication module in the CTIN function module, a communication module in the CTIN function module, a management command module in the CTIN function module, a client IO module in the CTIN function module, an encryption machine proxy module in the CTIN function module, and a Tuxedo proxy module in the CTIN function module; The resource limit acquisition module in the CTIN function module is used to obtain the limited usage of various system resources that each process can create; The queue scheduling module in the CTIN functional module includes queue insertion data, queue retrieval data, transaction grouping, transaction service, numbering, host address queue scheduling, client sleep and queue scheduling status; The IO thread module implementation in the CTIN functional module includes adding a new client, calling online command processing and IO thread event loop; The management command thread module in the CTIN function module includes setting whether the management command is executable, whether it is acceptable, management command execution, reception, timeout processing and management command thread event loop; The accept thread module in the CTIN function module includes thread mutex, calling client, socket accepting connection, accept thread event loop and wake-up event; The internal IPC communication module in the CTIN functional module implements the dispatch command sending, dispatch command receiving, online command sending and online command receiving; The communication module implementation in the CTIN functional module includes synchronous communication, asynchronous communication and connection check; The management command module in the CTIN function module includes direct exit, safe exit, safe restart, version acquisition, status acquisition, normal service status, transaction access but no command processing, management command execution and response; The client IO module implementation in the CTIN functional module includes the client sending a request and receiving a response; The encryption machine proxy module in the CTIN function module implements the following steps: encrypting and decrypting the encryption machine, setting MAC, checking MAC, sending requests to the encryption machine proxy, receiving responses, checking the encryption machine connection, and reconnecting the encryption machine; The Tuxedo proxy module in the CTIN function module includes sending a request to the Tuxedo proxy, receiving a response, Tuxedo connection check, and Tuxedo reconnection; The encryption machine proxy module includes an acquisition resource restriction module in the encryption machine proxy module, an IO thread module in the encryption machine proxy module, an encryption machine thread module in the encryption machine proxy module, an accept thread module in the encryption machine proxy module, a queue module in the encryption machine proxy module, an internal IPC communication module in the encryption machine proxy module, and a client IO module in the encryption machine proxy module; The resource limit acquisition module in the encryption machine proxy module is used to obtain the limited usage of various system resources that each process can create; The IO thread module in the encryption machine proxy module includes IO thread increase and decrease, call, wake up, retry command processing and IO thread event loop; The implementation of the encryption machine thread module in the encryption machine proxy module includes setting the encryption machine return, socket connection and encryption machine thread event loop; The accept thread module in the encryption machine proxy module includes thread mutex lock, client call, socket connection acceptance and accept thread event loop; The queue module in the encryption machine proxy module implements the following: queue insertion, queue retrieval, request generation, request retry, request deletion, request destruction, request clearing, response wake-up, response retry, and response waiting; The internal IPC communication module in the encryption machine proxy module implements the sending of scheduling commands, receiving scheduling commands, sending of wake-up commands, receiving of wake-up commands, sending of retry commands, and receiving of retry commands; The client IO module in the encryption machine proxy module implements the following functions: creating a client, deleting a client, creating an encryption machine message, deleting an encryption machine message, checking whether the message has been deleted, the client sending a request, and the client receiving a response; The Tuxedo proxy module includes: an acquisition resource restriction module in the Tuxedo proxy module, an IO thread module in the Tuxedo proxy module, a Tuxedo thread module in the Tuxedo proxy module, an accept thread module in the Tuxedo proxy module, a queue module in the Tuxedo proxy module, an internal IPC communication module in the Tuxedo proxy module, and a client IO module in the Tuxedo proxy module; The resource limit acquisition module in the Tuxedo agent module is used to obtain the limited usage of various system resources that each process can create; The IO thread module implementation in the Tuxedo proxy module includes IO thread increase and decrease, call, wake-up command processing and IO thread event loop; The Tuxedo thread module implementation in the Tuxedo proxy module includes request consumption, client synchronous call to server service and response generation; The accept thread module in the Tuxedo proxy module includes calling the client, socket accepting connection and accept thread event loop; The queue module implementation in the Tuxedo proxy module includes queue insertion data, queue retrieval data, request generation, request destruction, request clearing, response generation, response clearing and response waiting; The internal IPC communication module in the Tuxedo proxy module implements the sending of scheduling commands, receiving of scheduling commands, sending of wake-up commands, and receiving of wake-up commands; The client IO module implementation in the Tuxedo proxy module includes creating a client, deleting a client, creating a Tuxedo message, deleting a Tuxedo message, checking whether the message has been deleted, the client sending a request, and the client receiving a response.

2. A method for core business system access queue, characterized in that: include: CTIN functional module, encryption machine proxy module and Tuxedo proxy module; The CTIN function module is responsible for caching concurrent requests and calling the Tuxedo proxy module and the encryption machine proxy module; The Tuxedo proxy module is responsible for using the Tuxedo client to call the backend CTSP / OTIP service; The encryption machine proxy module is responsible for calling the encryption machine to perform encryption and decryption and calculate the message MAC; The CTIN function module, the encryption machine proxy module and the Tuxedo proxy module are all multi-threaded asynchronous communication models, and asynchronous communication is used between the CTIN function module, the encryption machine proxy module and the Tuxedo proxy module; Synchronous communication is used between the Tuxedo proxy module and the backend CTSP / OTIP service; The encryption machine proxy module and the encryption machine use synchronous communication; The CTIN function module, the encryption machine proxy module and the Tuxedo proxy module all have a queue scheduling mechanism; The CTIN function module includes: an acquisition resource restriction module in the CTIN function module, a queue scheduling module in the CTIN function module, an IO thread module in the CTIN function module, a management command thread module in the CTIN function module, an accept thread module in the CTIN function module, an internal IPC communication module in the CTIN function module, a communication module in the CTIN function module, a management command module in the CTIN function module, a client IO module in the CTIN function module, an encryption machine proxy module in the CTIN function module, and a Tuxedo proxy module in the CTIN function module; The resource limit acquisition module in the CTIN function module is used to obtain the limited usage of various system resources that each process can create; The queue scheduling module in the CTIN functional module includes queue insertion data, queue retrieval data, transaction grouping, transaction service, numbering, host address queue scheduling, client sleep and queue scheduling status; The IO thread module implementation in the CTIN functional module includes adding a new client, calling online command processing and IO thread event loop; The management command thread module in the CTIN function module includes setting whether the management command is executable, whether it is acceptable, management command execution, reception, timeout processing and management command thread event loop; The accept thread module in the CTIN function module includes thread mutex, calling client, socket accepting connection, accept thread event loop and wake-up event; The internal IPC communication module in the CTIN functional module implements the dispatch command sending, dispatch command receiving, online command sending and online command receiving; The communication module implementation in the CTIN functional module includes synchronous communication, asynchronous communication and connection check; The management command module in the CTIN function module includes direct exit, safe exit, safe restart, version acquisition, status acquisition, normal service status, transaction access but no command processing, management command execution and response; The client IO module implementation in the CTIN functional module includes the client sending a request and receiving a response; The encryption machine proxy module in the CTIN function module implements the following steps: encrypting and decrypting the encryption machine, setting MAC, checking MAC, sending requests to the encryption machine proxy, receiving responses, checking the encryption machine connection, and reconnecting the encryption machine; The Tuxedo proxy module in the CTIN function module includes sending a request to the Tuxedo proxy, receiving a response, Tuxedo connection check, and Tuxedo reconnection; The encryption machine proxy module includes an acquisition resource restriction module in the encryption machine proxy module, an IO thread module in the encryption machine proxy module, an encryption machine thread module in the encryption machine proxy module, an accept thread module in the encryption machine proxy module, a queue module in the encryption machine proxy module, an internal IPC communication module in the encryption machine proxy module, and a client IO module in the encryption machine proxy module; The resource limit acquisition module in the encryption machine proxy module is used to obtain the limited usage of various system resources that each process can create; The IO thread module in the encryption machine proxy module includes IO thread increase and decrease, call, wake up, retry command processing and IO thread event loop; The implementation of the encryption machine thread module in the encryption machine proxy module includes setting the encryption machine return, socket connection and encryption machine thread event loop; The accept thread module in the encryption machine proxy module includes thread mutex lock, client call, socket connection acceptance and accept thread event loop; The queue module in the encryption machine proxy module implements the following: queue insertion, queue retrieval, request generation, request retry, request deletion, request destruction, request clearing, response wake-up, response retry, and response waiting; The internal IPC communication module in the encryption machine proxy module implements the sending of scheduling commands, receiving scheduling commands, sending of wake-up commands, receiving of wake-up commands, sending of retry commands, and receiving of retry commands; The client IO module in the encryption machine proxy module implements the following functions: creating a client, deleting a client, creating an encryption machine message, deleting an encryption machine message, checking whether the message has been deleted, the client sending a request, and the client receiving a response; The Tuxedo proxy module includes: an acquisition resource restriction module in the Tuxedo proxy module, an IO thread module in the Tuxedo proxy module, a Tuxedo thread module in the Tuxedo proxy module, an accept thread module in the Tuxedo proxy module, a queue module in the Tuxedo proxy module, an internal IPC communication module in the Tuxedo proxy module, and a client IO module in the Tuxedo proxy module; The resource limit acquisition module in the Tuxedo agent module is used to obtain the limited usage of various system resources that each process can create; The IO thread module implementation in the Tuxedo proxy module includes IO thread increase and decrease, call, wake-up command processing and IO thread event loop; The Tuxedo thread module implementation in the Tuxedo proxy module includes request consumption, client synchronous call to server service and response generation; The accept thread module in the Tuxedo proxy module includes calling the client, socket accepting connection and accept thread event loop; The queue module implementation in the Tuxedo proxy module includes queue insertion data, queue retrieval data, request generation, request destruction, request clearing, response generation, response clearing and response waiting; The internal IPC communication module in the Tuxedo proxy module implements the sending of scheduling commands, receiving of scheduling commands, sending of wake-up commands, and receiving of wake-up commands; The client IO module implementation in the Tuxedo proxy module includes creating a client, deleting a client, creating a Tuxedo message, deleting a Tuxedo message, checking whether the message has been deleted, the client sending a request, and the client receiving a response.

Images