Middleware control method, device, storage medium and equipment

Abstract

The present application discloses a middleware control method, device, storage medium and equipment, the method comprising: controlling the target AOR process instance to be in a static state, and no longer receiving transaction tasks sent by the TOR process instance; performing a downtime operation on the target AOR process instance, so that the target AOR process instance no longer runs; controlling the target TOR process instance to be in a state where new registration is not allowed; controlling the open gateway cluster to close the SNA session connection of the target TOR process instance; performing a downtime operation on the target TOR process instance, so that the target TOR process instance no longer runs. The method can control the target AOR process instance to no longer process new transaction tasks during the downtime of the middleware, and control the target TOR process instance to no longer create a new SNA session connection, so that the transaction tasks no longer fail due to the downtime of the middleware, thereby effectively avoiding the problem of a large number of business failures on the host platform during the downtime of the middleware.

Description

Technical Field

[0001] The present application relates to the field of information operation and maintenance, and in particular to a middleware control method, device, storage medium and equipment. Background Art

[0002] In the maintenance work of the Customer Information Control System (CICS) of the host platform, such as coordinating the implementation of projects such as software version upgrades, software patch implementation, and hardware upgrades, it is necessary to stop and start the routing controller (Terminal Owning Region, TOR) process instance and the application controller (Application Owning Region, AOR) process instance in the middleware cluster. In order to reduce the impact of the middleware maintenance process on system startup and online transactions, maintenance personnel usually select the change window during the low business peak period, such as early morning.

[0003] However, in the existing maintenance operation plan, before the TOR process instance of the middleware cluster is shut down, first, the open gateway cluster actively disconnects the host platform network (System Network Architecture, SNA) session connection with the TOR process instance. Although the direct disconnection of the SNA session connection operation will not cause inconsistency in business data, it will cause the failure of in-transit transactions that have not been completed between the gateway cluster and the middleware cluster. The greater the system business volume (such as transaction volume) during the downtime of the middleware, the more failed businesses (such as transaction businesses) will be caused.

[0004] Therefore, how to avoid a large number of business failures on a host platform (eg, a trading system) during a middleware downtime period has become an urgent problem to be solved in the art. Summary of the invention

[0005] The present application provides a middleware control method, apparatus, storage medium and device for avoiding the problem of a large number of business failures occurring on a host platform during a middleware downtime.

[0006] In order to achieve the above objectives, this application provides the following technical solutions:

[0007] A middleware control method, comprising:

[0008] The target AOR process instance is controlled to be in a static state and no longer receives transaction tasks sent by the TOR process instance;

[0009] Performing a shutdown operation on the target AOR process instance so that the target AOR process instance is no longer running;

[0010] Control the target TOR process instance to a state where new registration is not allowed;

[0011] Controlling the open gateway cluster to close the SNA session connection of the target TOR process instance;

[0012] The target TOR process instance is shut down so that the target TOR process instance is no longer running.

[0013] Optionally, the control target AOR process instance is in a static state and no longer receives transaction tasks sent by the TOR process instance, including:

[0014] After receiving the middleware downlink command input by the user, the AOR process instance that needs to be downlinked in the host platform is identified as the target AOR process instance, and the TOR process instance that needs to be downlinked is identified as the target TOR process instance;

[0015] The state of the target AOR process instance is changed so that the target AOR process instance is in a static state and no longer receives transaction tasks sent by the TOR process instance.

[0016] Optionally, the control target TOR process instance is in a state where new registration is not allowed, including:

[0017] From the various routing policies displayed by the host platform, select the routing policy corresponding to the target TOR process instance as the target routing policy;

[0018] The state of the target routing policy is changed so that the target TOR process instance is in a state where new registration is not allowed.

[0019] Optionally, controlling the open gateway cluster to close the SNA session connection of the target TOR process instance includes:

[0020] Collecting one or more SNA session connections of the target TOR process instance from the host platform, and constructing a session detail table of the target TOR process instance based on the collected one or more SNA session connections;

[0021] The session details list is sent to an open gateway cluster, so that the open gateway cluster closes each SNA session connection in the session details list one by one.

[0022] Optionally, also include:

[0023] After receiving the middleware startup command input by the user, turning off the preset switch of the target AOR process instance; the preset switch is used to control the target AOR process instance to directly join the middleware cluster after startup;

[0024] Adjusting the memory loading parameters of the target AOR process instance so that the target AOR process instance does not perform a memory loading operation after startup;

[0025] Starting the target AOR process instance;

[0026] Obtaining log information of the target AOR process instance from a host platform;

[0027] In the case where the log information contains a preset keyword, determining that the target AOR process instance is in a startup state, and turning on the preset switch;

[0028] Start the target TOR process instance.

[0029] Optionally, after starting the target TOR process instance, the step further includes:

[0030] The open gateway cluster and the target TOR process instance are controlled to establish each SNA session connection in the session detail table; the session detail table includes one or more SNA session connections of the target TOR process instance collected in advance from the host platform.

[0031] A middleware control device, comprising:

[0032] A first control unit is used to control the target AOR process instance to be in a static state and no longer receive transaction tasks sent by the TOR process instance;

[0033] A first shutdown unit, configured to perform a shutdown operation on the target AOR process instance so that the target AOR process instance is no longer running;

[0034] The second control unit is used to control the target TOR process instance to be in a state where new registration is not allowed;

[0035] A third control unit is used to control the open gateway cluster to close the SNA session connection of the target TOR process instance;

[0036] The second shutdown unit is used to perform a shutdown operation on the target TOR process instance so that the target TOR process instance is no longer running.

[0037] Optionally, the first control unit is specifically configured to:

[0038] After receiving the middleware downlink command input by the user, the AOR process instance that needs to be downlinked in the host platform is identified as the target AOR process instance, and the TOR process instance that needs to be downlinked is identified as the target TOR process instance;

[0039] The state of the target AOR process instance is changed so that the target AOR process instance is in a static state and no longer receives transaction tasks sent by the TOR process instance.

[0040] A computer-readable storage medium includes a stored program, wherein the program executes the middleware control method when started by a processor.

[0041] A middleware control device comprises: a processor, a memory and a bus; the processor and the memory are connected via the bus;

[0042] The memory is used to store a program, and the processor is used to start the program, wherein the middleware control method is executed when the program is started by the processor.

[0043] The technical solution provided by the present application controls the target AOR process instance to be in a dormant state and no longer receives transaction tasks sent by the TOR process instance. Perform a shutdown operation on the target AOR process instance so that the target AOR process instance no longer runs. Control the target TOR process instance to be in a state where new registrations are not allowed. Control the open gateway cluster to close the SNA session connection of the target TOR process instance. Perform a shutdown operation on the target TOR process instance so that the target TOR process instance no longer runs. The present application can control the target AOR process instance to no longer process new transaction tasks during the downtime of the middleware, and control the target TOR process instance to no longer create a new SNA session connection, so that transaction tasks no longer fail due to the downtime of the middleware, thereby effectively avoiding the problem of a large number of business failures on the host platform during the downtime of the middleware. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0045] Figure 1 A schematic diagram of the architecture of a host platform provided in an embodiment of the present application;

[0046] Figure 2a A flowchart of a middleware control method provided in an embodiment of the present application;

[0047] Figure 2b A flowchart of a middleware control method provided in an embodiment of the present application;

[0048] Figure 3A flowchart of another middleware control method provided in an embodiment of the present application;

[0049] Figure 4 A schematic diagram of the architecture of a middleware control device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0051] It should be noted that the host platform managed by CICS is usually deployed in a cluster architecture to achieve high concurrency and high availability business continuity construction requirements. In actual use, the core business system of the bank will deploy multiple business virtual machines at the same time, build multiple business virtual machines into a parallel coupling system (cluster), and deploy multiple transaction middleware process instances (such as TOR process instances and AOR process instances) on each business virtual machine.

[0052] On physical hardware, multiple business virtual machines will be distributed on multiple physical hardware hosts to achieve high availability of hardware equipment. Multiple physical hosts will establish physical full connections with at least two physical parallel coupler hosts, and multiple business virtual machines will use this physical connection to achieve communication and data sharing and collaboration. The realization of communication between physical hosts relies on the physical memory of the parallel coupler. The parallel coupler host divides its memory into parallel coupling structural units, which are used as the minimum management unit to provide implementation support for communication between physical hosts. A parallel coupling system (cluster) provides cross-system expansion function services and provides efficient access services for users such as database instances and middleware instances started on virtual machines, including cache processing, list data, lock management and other types of services. Correspondingly, the parallel coupling units inside the parallel coupler are also divided into cache type structural units, list type structural units and lock type structural units according to the above usage requirements. The database uses the lock type structural unit and the cache type structural unit global buffer pool.

[0053] On the existing host platform, operating systems, databases, middleware and other processes are called subsystems. Multiple subsystems deployed on virtual machines in the cluster interact and collaborate to support the implementation of business. To implement transaction execution, a transaction middleware cluster will be deployed on the host platform according to the requirements of high availability and high concurrency, such as Figure 1 As shown, the specific deployment method is:

[0054] On the host platform, multiple TOR process instances are usually deployed. The TOR process instance receives the transaction request from the open platform gateway cluster, and then routes the transaction request to the AOR process instance according to the load balancing principle. The AOR process instance interacts with the database in the host cluster to complete the transaction execution operation. Multiple TOR process instances constitute the transaction routing control layer, and multiple AOR process instances constitute the application controller layer.

[0055] A gateway cluster is deployed on an open platform, which is usually composed of multiple AIX servers. Each AIX server receives a transaction request sent from a peripheral channel system to the gateway cluster. The open gateway cluster converts the message into a message that can be recognized by the host platform network (i.e., the transaction task mentioned in the embodiment), and sends the message to the TOR process instance. The TOR process instance then routes the message to the AOR process instance and completes the transaction processing of the message based on the AOR process instance.

[0056] The open platform gateway cluster and the host middleware cluster are connected through the SNA network protocol. The SNA connection between the two is usually called an SNA session connection. The open platform gateway cluster and the TOR process instance create an SNA session connection, which is used to implement the following: the transaction upload process from the open platform gateway cluster to the host transaction middleware cluster, and the result delivery process from the host to the open gateway.

[0057] Based on the architectural principles of the above-mentioned existing host platform, the applicant also found that: in the existing middleware maintenance operation plan, when the AOR process instance is started, the AOR process instance will start executing transaction tasks by default after startup. If an exception occurs during the startup of the AOR process instance, the transaction task running on the AOR process instance will fail; at the same time, since the memory loading operation will be forced when the AOR process instance is started, this memory loading operation will cause the instantaneous transaction response time of the initial startup of the AOR process instance to be longer.

[0058] To this end, an embodiment of the present application provides a middleware control method for avoiding the problem of a large number of business (such as transaction business) failures on the host platform during the middleware downtime, and at the same time, avoiding the failure of transaction tasks and the problem of long transactions in the initial startup period during the startup of the middleware.

[0059] like Figure 2a and Figure 2b As shown, it is a flow chart of a middleware control method provided in an embodiment of the present application, which is applied to a host platform and includes the following steps.

[0060] S201: After receiving the middleware downlink command input by the user, the AOR process instance that needs to be downlinked in the host platform is identified as the target AOR process instance, and the TOR process instance that needs to be downlinked is identified as the target TOR process instance.

[0061] The down operation is used to shut down the middleware process instance (such as the AOR process instance and the TOR process instance).

[0062] It should be noted that the middleware downlink command includes the name of the AOR process instance that needs to be downlinked, and the name of the TOR process instance that needs to be downlinked.

[0063] In the embodiment of the present application, the middleware cluster is a basic environment built with CICS software running on a host platform, and the middleware cluster includes multiple AOR process instances and multiple TOR process instances.

[0064] Generally speaking, the TOR process instance is used to receive the transaction tasks sent by the open gateway cluster and forward the transaction tasks to the AOR process instance. Correspondingly, the AOR process instance is used to execute the transaction tasks sent by the TOR process instance.

[0065] The so-called open gateway cluster consists of multiple AIX servers, which are mainly responsible for receiving transaction tasks (i.e., transaction requests) sent from external channels and sending the transaction tasks to the TOR process instance through the SNA session connection. Specifically, the communication connection between the TOR process instance and the open gateway cluster is realized based on the SNA session connection.

[0066] S202: Changing the state of the target AOR process instance so that the target AOR process instance is in a static state and no longer receives transaction tasks sent by the TOR process instance.

[0067] Among them, if the target AOR process instance is in a dormant state, it will no longer receive the transaction tasks sent by the TOR process instance, that is, the target AOR process instance in a dormant state will not execute the transaction tasks sent by the TOR process instance.

[0068] Under normal circumstances, when the AOR process instance is in an active state, it can process transaction processing requests (i.e., transaction tasks sent by the TOR process instance). When the AOR process instance is in a dormant state, it will no longer process new transaction tasks.

[0069] It should be emphasized that when the AOR process instance just enters the quiescent state, the unfinished transaction tasks started on the AOR process instance will continue to be processed to ensure the consistency of the transaction.

[0070] Specifically, the specific implementation logic of changing the state of the target AOR process instance to make the target AOR process instance in a quiescent state includes but is not limited to: EYUAPI ('PERFORM SET ACTION (QUIESCE)').

[0071] S203: Perform a shutdown operation on the target AOR process instance so that the target AOR process instance is no longer running.

[0072] The specific implementation logic of performing the shutdown operation on the target AOR process instance includes but is not limited to: FAORx, CEMT P SHUT, and specifically, AORx is the name of the target AOR process instance.

[0073] S204: Filter the routing policy corresponding to the target TOR process instance from the various routing policies displayed by the host platform as the target routing policy.

[0074] The host platform includes routing policies corresponding to each TOR process instance.

[0075] S205: Change the state of the target routing policy so that the target TOR process instance is in a state where new registration is not allowed.

[0076] Among them, if the target TOR process instance is in a state where new registration is not allowed, it means that the open gateway cluster will no longer use the target TOR process instance as the object of a new SNA session connection, thereby ensuring that no new SNA session connection of the target TOR process instance will be added.

[0077] It should be noted that, as long as the target TOR process instance is restarted, the open gateway cluster will again use the target TOR process instance as the object of the newly created SNA session connection.

[0078] Specifically, the state of the target routing policy is changed to make the target TOR process instance in a state where new registration is not allowed. The specific implementation logic includes but is not limited to: F TORx, CEMT S VTAM DEREGISTERED, where TORx represents the name of the target TOR process instance.

[0079] S206: Collect one or more SNA session connections of the target TOR process instance from the host platform, and construct a session detail table of the target TOR process instance based on the collected one or more SNA session connections.

[0080] The specific implementation logic of collecting one or more SNA session connections of the target TOR process instance from the host platform includes but is not limited to: D NET, TORx, E.

[0081] S207: Send the session details list to the open gateway cluster, so that the open gateway cluster closes each SNA session connection in the session details list one by one.

[0082] Since the open gateway cluster closes each SNA session connection one by one according to the session details list, the open gateway cluster will not experience a business failure (transaction failure) during the period of closing each SNA session connection.

[0083] S208: Perform a shutdown operation on the target TOR process instance so that the target TOR process instance is no longer running.

[0084] The specific implementation logic of shutting down the target TOR process instance includes but is not limited to: FTORx, CEMT P SHUT, and specifically, TORx is the name of the target TOR process instance.

[0085] It should be noted that, based on the process shown in S201-S208 above, the problem of failure of in-transit transactions caused by the open gateway cluster disconnecting the SNA session connection before cooperating with the TOR process instance to go down can be solved. In other words, the downtime of the target AOR process instance and the target TOR process instance will no longer affect the execution of the ongoing business (in-transit transactions).

[0086] S209: After receiving the middleware restart command input by the user, turn off the preset switch of the target AOR process instance.

[0087] Among them, the preset switch is used to control the target AOR process instance to directly join the middleware cluster after startup. That is to say, when the preset switch is turned on, as long as the target AOR process instance is in the startup state, the target AOR process instance will automatically join the middleware cluster to enable the target AOR process instance to execute the transaction task forwarded by the TOR process instance.

[0088] It should be noted that if the transaction task is forwarded to the target AOR process instance without confirmation, and the state of the target AOR process instance is not completely correct, the transaction task will fail. In the context of a large transaction volume, the number of failed transaction tasks will increase, increasing the transaction failure rate. If the preset switch is set when starting the target AOR process instance, so that the target AOR process instance does not process transaction tasks by default at startup, and the operation and maintenance personnel confirm the startup state of the target AOR process instance, and manually open it after confirming that the startup state meets expectations, it can be ensured that the target AOR process instance will not fail to process transaction tasks due to abnormal states after startup.

[0089] Specifically, the specific implementation logic of closing the preset switch of the target AOR process instance includes but is not limited to: SAORx, START=INITIAL.

[0090] S210: Adjust the memory loading parameters of the target AOR process instance so that the target AOR process instance does not perform a memory loading operation after being started.

[0091] Among them, after the memory loading parameters are adjusted, the target AOR process instance will not perform memory loading operations after startup. In this way, the target AOR process instance will no longer be forced to load the application on the disk into the memory when running the transaction task for the first time, avoiding disk IO operations and solving the "slow heating" problem of the target AOR process instance within a few minutes after startup, so as to avoid the impact of this operation on business response time.

[0092] It should be noted that during the middleware startup phase, the preset switch of the target AOR process instance is turned off so that the target AOR process instance will not directly join the middleware cluster after startup. At the same time, the memory loading parameters of the target AOR process instance are adjusted so that the target AOR process instance does not perform memory loading operations after startup, thereby effectively avoiding transaction failures and long transaction response times on the host platform during the initial stage of middleware startup.

[0093] Specifically, the memory loading parameters of the target AOR process instance are adjusted so that the target AOR process instance does not perform a memory loading operation after startup. The specific implementation logic includes but is not limited to: LLACOPY=NO, where LLACOPY is a memory loading parameter.

[0094] S211: Start the target AOR process instance.

[0095] The restart command input by the user includes the name of the target AOR process instance and the name of the target TOR process instance.

[0096] Specifically, the specific implementation logic of starting the target AOR process instance includes but is not limited to: SAORx, START=INITIAL, LMAS=NO.

[0097] S212: Obtain log information of the target AOR process instance from the host platform.

[0098] S213: When the log information contains a preset keyword, determine that the target AOR process instance is in the startup state.

[0099] The preset keywords include but are not limited to normal startup.

[0100] S214: Turn on the preset switch of the target AOR process instance.

[0101] Among them, after the preset switch of the target AOR process instance is turned on, the target AOR process instance will automatically join the middleware cluster and process transaction tasks forwarded from each TOR process instance in the middleware cluster.

[0102] Specifically, the specific implementation logic of the preset switch for turning on the target AOR process instance includes but is not limited to: FAORx, COLM.

[0103] S215: Start the target TOR process instance to invalidate the target routing policy.

[0104] Among them, after the target routing policy becomes invalid, the target TOR process instance can establish an SNA session connection with the open gateway cluster, that is, the target TOR process instance can add a new SNA session connection.

[0105] It should be noted that the invalidation of the target routing policy actually means that the target routing policy is no longer in a state where new registration is not allowed.

[0106] Specifically, the specific implementation logic of starting the target TOR process instance includes but is not limited to: STORx, START=INITIAL.

[0107] S216: Control the open gateway cluster and the target TOR process instance to establish each SNA session connection in the session details table.

[0108] After the open gateway cluster and the target TOR process instance are controlled to establish each SNA session connection in the session details table, the target TOR process instance will receive the transaction task sent by the open gateway cluster through each SNA session connection.

[0109] To sum up, this embodiment can control the target AOR process instance to no longer process new transaction tasks and control the target TOR process instance to no longer create new SNA session connections during the downtime of the middleware, so that transaction tasks no longer fail due to the downtime of the middleware, thereby effectively avoiding the problem of a large number of business failures on the host platform during the downtime of the middleware.

[0110] It should be noted that S201 mentioned in the above embodiment is an optional implementation of the middleware control method shown in the embodiment of the present application. In addition, S216 mentioned in the above embodiment is also an optional implementation of the middleware control method shown in the embodiment of the present application. To this end, the process mentioned in the above embodiment can be summarized as follows: Figure 3 The method shown.

[0111] like Figure 3As shown, it is a flow chart of another middleware control method provided in an embodiment of the present application, including the following steps.

[0112] S301: Control the target AOR process instance to be in a static state and no longer receive transaction tasks sent by the TOR process instance.

[0113] S302: Perform a shutdown operation on the target AOR process instance so that the target AOR process instance is no longer running.

[0114] S303: Control the target TOR process instance to be in a state where new registration is not allowed.

[0115] S304: Control the open gateway cluster to close the SNA session connection of the target TOR process instance.

[0116] S305: Perform a shutdown operation on the target TOR process instance so that the target TOR process instance is no longer running.

[0117] To sum up, this embodiment can control the target AOR process instance to no longer process new transaction tasks and control the target TOR process instance to no longer create new SNA session connections during the downtime of the middleware, so that transaction tasks no longer fail due to the downtime of the middleware, thereby effectively avoiding the problem of a large number of business failures on the host platform during the downtime of the middleware.

[0118] Corresponding to the middleware control method provided in the above-mentioned embodiment of the present application, the embodiment of the present application also provides a middleware control device.

[0119] like Figure 4 As shown, it is a schematic diagram of the architecture of a middleware control device provided in an embodiment of the present application, including the units shown below.

[0120] The first control unit 100 is used to control the target AOR process instance to be in a static state and no longer receive the transaction task sent by the TOR process instance.

[0121] Optionally, the first control unit 100 is specifically used to: after receiving the middleware downlink command input by the user, identify the AOR process instance that needs to be downlinked in the host platform as the target AOR process instance, and identify the TOR process instance that needs to be downlinked as the target TOR process instance; change the state of the target AOR process instance so that the target AOR process instance is in a static state and no longer receives transaction tasks sent by the TOR process instance.

[0122] The first shutdown unit 200 is used to perform a shutdown operation on the target AOR process instance so that the target AOR process instance is no longer running.

[0123] The second control unit 300 is used to control the target TOR process instance to be in a state where new registration is not allowed.

[0124] Optionally, the second control unit 300 is specifically used to: filter the routing policy corresponding to the target TOR process instance from the various routing policies shown by the host platform as the target routing policy; change the state of the target routing policy so that the target TOR process instance is in a state where new registration is not allowed.

[0125] The third control unit 400 is used to control the open gateway cluster to close the SNA session connection of the target TOR process instance.

[0126] Optionally, the third control unit 400 is specifically used to: collect one or more SNA session connections of the target TOR process instance from the host platform, and build a session details list of the target TOR process instance based on the collected one or more SNA session connections; send the session details list to the open gateway cluster so that the open gateway cluster closes each SNA session connection in the session details list one by one.

[0127] The second shutdown unit 500 is used to perform a shutdown operation on the target TOR process instance so that the target TOR process instance is no longer running.

[0128] The process restart unit 600 is used to: after receiving the middleware restart command input by the user, turn off the preset switch of the target AOR process instance; the preset switch is used to control the target AOR process instance to directly join the middleware cluster after startup; adjust the memory loading parameters of the target AOR process instance so that the target AOR process instance does not perform memory loading operations after startup; start the target AOR process instance; obtain the log information of the target AOR process instance from the host platform; when the log information contains preset keywords, determine that the target AOR process instance is in the startup state and turn on the preset switch; start the target TOR process instance.

[0129] The process restart unit 600 is also used to control the open gateway cluster and the target TOR process instance to establish each SNA session connection in the session list; the session list includes one or more SNA session connections of the target TOR process instance collected in advance from the host platform.

[0130] To sum up, this embodiment can control the target AOR process instance to no longer process new transaction tasks and control the target TOR process instance to no longer create new SNA session connections during the downtime of the middleware, so that transaction tasks no longer fail due to the downtime of the middleware, thereby effectively avoiding the problem of a large number of business failures on the host platform during the downtime of the middleware.

[0131] The present application also provides a computer-readable storage medium, which includes a stored program, wherein the program executes the middleware control method provided by the present application.

[0132] The present application also provides a middleware control device, including: a processor, a memory and a bus. The processor and the memory are connected via a bus, the memory is used to store programs, and the processor is used to start the program, wherein when the program is started, the middleware control method provided by the present application is executed, including the following steps:

[0133] The target AOR process instance is controlled to be in a static state and no longer receives transaction tasks sent by the TOR process instance;

[0134] Performing a shutdown operation on the target AOR process instance so that the target AOR process instance is no longer running;

[0135] Control the target TOR process instance to a state where new registration is not allowed;

[0136] Controlling the open gateway cluster to close the SNA session connection of the target TOR process instance;

[0137] The target TOR process instance is shut down so that the target TOR process instance is no longer running.

[0138] Specifically, based on the above embodiment, the control target AOR process instance is in a static state and no longer receives transaction tasks sent by the TOR process instance, including:

[0139] After receiving the middleware downlink command input by the user, the AOR process instance that needs to be downlinked in the host platform is identified as the target AOR process instance, and the TOR process instance that needs to be downlinked is identified as the target TOR process instance;

[0140] The state of the target AOR process instance is changed so that the target AOR process instance is in a static state and no longer receives transaction tasks sent by the TOR process instance.

[0141] Specifically, based on the above embodiment, the control target TOR process instance is in a state where new registration is not allowed, including:

[0142] From the various routing policies displayed by the host platform, select the routing policy corresponding to the target TOR process instance as the target routing policy;

[0143] The state of the target routing policy is changed so that the target TOR process instance is in a state where new registration is not allowed.

[0144] Specifically, based on the above embodiment, the controlling the open gateway cluster to close the SNA session connection of the target TOR process instance includes:

[0145] Collecting one or more SNA session connections of the target TOR process instance from the host platform, and constructing a session detail table of the target TOR process instance based on the collected one or more SNA session connections;

[0146] The session details list is sent to an open gateway cluster, so that the open gateway cluster closes each SNA session connection in the session details list one by one.

[0147] Specifically, based on the above embodiment, it also includes:

[0148] After receiving the middleware restart command input by the user, turning off the preset switch of the target AOR process instance; the preset switch is used to control the target AOR process instance to directly join the middleware cluster after starting;

[0149] Adjusting the memory loading parameters of the target AOR process instance so that the target AOR process instance does not perform a memory loading operation after startup;

[0150] Starting the target AOR process instance;

[0151] Obtaining log information of the target AOR process instance from a host platform;

[0152] In the case where the log information contains a preset keyword, determining that the target AOR process instance is in a startup state, and turning on the preset switch;

[0153] Start the target TOR process instance.

[0154] Specifically, based on the above embodiment, after starting the target TOR process instance, the method further includes:

[0155] The open gateway cluster and the target TOR process instance are controlled to establish each SNA session connection in the session detail table; the session detail table includes one or more SNA session connections of the target TOR process instance collected in advance from the host platform.

[0156] If the functions described in the method of the embodiment of the present application are implemented in the form of software functional units and sold or used as independent products, they can be stored in a storage medium readable by a computing device. Based on this understanding, the part of the embodiment of the present application that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computing device (which can be a personal computer, server, mobile computing device or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories, random access memories, magnetic disks or optical disks.

[0157] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0158] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A middleware control method, characterized in that: include: Control the target AOR process instance to be in a dormant state and no longer receive transaction tasks sent by the TOR process instance; wherein, when the target AOR process instance just enters the dormant state, the unfinished transaction tasks started on the target AOR process instance will continue to be processed and completed; Performing a shutdown operation on the target AOR process instance so that the target AOR process instance is no longer running; Control the target TOR process instance to a state where new registration is not allowed; Controlling the open gateway cluster to close the SNA session connection of the target TOR process instance; The target TOR process instance is shut down so that the target TOR process instance is no longer running.

2. The method according to claim 1, characterized in that The control target AOR process instance is in a static state and no longer receives transaction tasks sent by the TOR process instance, including: After receiving the middleware downlink command input by the user, the AOR process instance that needs to be downlinked in the host platform is identified as the target AOR process instance, and the TOR process instance that needs to be downlinked is identified as the target TOR process instance; The state of the target AOR process instance is changed so that the target AOR process instance is in a static state and no longer receives transaction tasks sent by the TOR process instance.

3. The method according to claim 1, characterized in that The control target TOR process instance is in a state where new registration is not allowed, including: From the various routing policies displayed by the host platform, select the routing policy corresponding to the target TOR process instance as the target routing policy; The state of the target routing policy is changed so that the target TOR process instance is in a state where new registration is not allowed.

4. The method according to claim 1, characterized in that: The controlling the open gateway cluster to close the SNA session connection of the target TOR process instance includes: Collecting one or more SNA session connections of the target TOR process instance from the host platform, and constructing a session detail table of the target TOR process instance based on the collected one or more SNA session connections; The session details list is sent to an open gateway cluster, so that the open gateway cluster closes each SNA session connection in the session details list one by one.

5. The method according to claim 1, characterized in that Also includes: After receiving the middleware restart command input by the user, turning off the preset switch of the target AOR process instance; The preset switch is used to control the target AOR process instance to directly join the middleware cluster after startup; Adjusting the memory loading parameters of the target AOR process instance so that the target AOR process instance does not perform a memory loading operation after startup; Starting the target AOR process instance; Obtaining log information of the target AOR process instance from a host platform; In the case where the log information contains a preset keyword, determining that the target AOR process instance is in a startup state, and turning on the preset switch; Start the target TOR process instance.

6. The method according to claim 5, characterized in that After starting the target TOR process instance, the process further includes: The open gateway cluster and the target TOR process instance are controlled to establish each SNA session connection in the session detail table; the session detail table includes one or more SNA session connections of the target TOR process instance collected in advance from the host platform.

7. A middleware control device, characterized in that: include: A first control unit is used to control the target AOR process instance to be in a dormant state and no longer receive transaction tasks sent by the TOR process instance; wherein, when the target AOR process instance just enters the dormant state, the unfinished transaction tasks started on the target AOR process instance will continue to be processed and completed; A first shutdown unit, configured to perform a shutdown operation on the target AOR process instance so that the target AOR process instance is no longer running; The second control unit is used to control the target TOR process instance to be in a state where new registration is not allowed; A third control unit is used to control the open gateway cluster to close the SNA session connection of the target TOR process instance; The second shutdown unit is used to perform a shutdown operation on the target TOR process instance so that the target TOR process instance is no longer running.

8. The device according to claim 7, characterized in that The first control unit is specifically used for: After receiving the middleware downlink command input by the user, the AOR process instance that needs to be downlinked in the host platform is identified as the target AOR process instance, and the TOR process instance that needs to be downlinked is identified as the target TOR process instance; The state of the target AOR process instance is changed so that the target AOR process instance is in a static state and no longer receives transaction tasks sent by the TOR process instance.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program, when started by a processor, executes the middleware control method according to any one of claims 1 to 6.

10. A middleware control device, characterized in that: include: processor, memory, and bus; The processor is connected to the memory via the bus; The memory is used to store a program, and the processor is used to start the program, wherein the program, when started by the processor, executes the middleware control method described in any one of claims 1-6.

Images