CN110474827B

CN110474827B - FIN message multi-environment forwarding method, equipment and system

Info

Publication number: CN110474827B
Application number: CN201910752265.XA
Authority: CN
Inventors: 牛丽敏
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2019-08-15
Filing date: 2019-08-15
Publication date: 2021-11-02
Anticipated expiration: 2039-08-15
Also published as: CN110474827A

Abstract

The invention provides a method, a system, computer equipment and a computer readable storage medium for transferring a FIN message from multiple environments, and relates to the technical field of data processing. The method comprises the following steps: an application system receives a FIN message through a bus system, wherein the FIN message reaches a receiving queue of a local queue of the application system; generating a trigger message to start a trigger process; and the trigger process writes the FIN message into a corresponding target queue. The invention uses the local forwarding queue and the triggering process, and the triggering process writes the message into the corresponding queue according to the message identifier of the message, BIC and MSGTYPE.

Description

FIN message multi-environment forwarding method, equipment and system

Technical Field

The present invention relates to the field of data processing technologies, and in particular to a packet processing technology, and more particularly to a FIN packet multi-environment forwarding method, a FIN packet multi-environment forwarding system, an application system, a computer device, and a computer readable storage medium.

Background

This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.

For the FIN message, the sender BIC and the receiver BIC are included in the header. The SIWFT network routes messages according to the BIC. For the production environment or the test environment, there are different BIC, for example, for swift nk system, the test BIC is BKCHCNB0, and the production BIC is BKCHCNBJ, but due to the different batch test requirements, the bank system usually has multiple test environments, which requires saa (lt) connected to the bank application system to switch to different test environments. The SAA (LT) is only one, different batches cannot be simultaneously tested, the portability and the universality are low, a table structure needs to be established, the incoming and outgoing reports cannot be simultaneously supported, the original system is high in coupling degree and low in expansibility, and the forwarding to multiple environments cannot be realized.

Therefore, how to provide a new solution, which can solve the above technical defects, is a technical problem to be solved in the art.

Disclosure of Invention

In view of the above, the present invention provides a FIN message multi-environment forwarding method, a FIN message multi-environment forwarding system, an application system, a computer device, and a computer readable storage medium, wherein a local forwarding queue and a trigger process are used, and the trigger process writes a message into a corresponding queue according to a message identifier of the message, a BIC identifier, a MSGTYPE identifier, and a system scalability is improved.

In order to achieve the above object, the present invention provides a FIN message multi-environment forwarding method, including:

an application system receives a FIN message through a bus system, wherein the FIN message reaches a receiving queue of a local queue of the application system;

generating a trigger message to start a trigger process;

and the trigger process writes the FIN message into a corresponding target queue.

One of the objectives of the present invention is to provide a method for forwarding a FIN packet in a multi-environment, where the method includes:

the application system writes the FIN message into a forwarding queue with the type of a local queue;

generating a trigger message to start a trigger process after the FIN message reaches a forwarding queue;

One of the objectives of the present invention is to provide an application system for forwarding FIN packet in multiple environments, where the application system includes:

the message receiving module is used for receiving a FIN message through a bus system, wherein the FIN message reaches a receiving queue of a local queue of the application system;

a message generation module for generating a trigger message to start a trigger process;

and the message writing module is used for writing the FIN message into a corresponding target queue through a triggering process.

the forwarding queue writing module is used for writing the FIN message into a forwarding queue with the type of a local queue;

the trigger message generation module is used for generating a trigger message to start a trigger process after the FIN message reaches a forwarding queue;

and the FIN message writing module is used for writing the FIN message into a corresponding target queue.

One of the objectives of the present invention is to provide a system for forwarding FIN packets in multiple environments, which includes an SAA, a bus system, and an application system.

One of the objectives of the present invention is to provide a computer device, which includes a memory, a processor and a computer program stored in the memory and running on the processor, wherein the processor implements a FIN message multi-environment forwarding method when executing the computer program.

One of the objects of the present invention is to provide a computer readable storage medium storing a program for executing a FIN message multi-environment forwarding method.

The invention has the advantages that the invention provides a FIN message multi-environment forwarding method, a FIN message multi-environment forwarding system, an application system, computer equipment and a computer readable storage medium, a local forwarding queue and a trigger process are used, and the trigger process writes the message into the corresponding queue according to the incoming and outgoing message identification, BIC and MSGTYPE of the message.

In order to make the aforementioned and other objects, features and advantages of the invention comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a flowchart of a FIN message multi-environment forwarding method according to an embodiment of the present invention;

fig. 2 is a detailed flowchart of a first embodiment of step S103 in fig. 1;

fig. 3 is a flowchart of a second embodiment of step S103 in fig. 1;

fig. 4 is a flowchart of a second implementation manner of a FIN message multi-environment forwarding method according to an embodiment of the present invention;

fig. 5 is a flowchart of another FIN message multi-environment forwarding method according to an embodiment of the present invention;

FIG. 6 is a flowchart of a first embodiment of step S303 in FIG. 5;

fig. 7 is a flowchart of a second embodiment of step S303 in fig. 5;

fig. 8 is a flowchart of another FIN message multi-environment forwarding method according to a second embodiment of the present invention;

fig. 9 is a schematic structural diagram of a system for forwarding a FIN message in a multi-environment according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of an application system for forwarding a FIN packet in multiple environments according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a first implementation manner of a message write module in an application system for FIN message multi-environment forwarding according to an embodiment of the present invention;

fig. 12 is a schematic structural diagram of a second implementation manner of a message write module in an application system for FIN message multi-environment forwarding according to an embodiment of the present invention;

fig. 13 is a schematic structural diagram of a second implementation manner of an application system for forwarding a FIN packet in multiple environments according to an embodiment of the present invention;

fig. 14 is a schematic structural diagram of another FIN packet multi-environment forwarding application system according to an embodiment of the present invention;

fig. 15 is a schematic structural diagram of a first implementation manner of a FIN packet write module in another FIN packet multi-environment forwarding application system according to an embodiment of the present invention;

fig. 16 is a schematic structural diagram of a second implementation manner of a FIN packet write module in another FIN packet multi-environment forwarding application system according to an embodiment of the present invention;

fig. 17 is a schematic structural diagram of a second implementation manner of another FIN packet multi-environment forwarding application system according to an embodiment of the present invention;

fig. 18 is a schematic diagram of FIN message multi-environment forwarding in an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

As will be appreciated by one skilled in the art, embodiments of the present invention may be embodied as a system, apparatus, method or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

The terminology of the present invention is first described below.

SWIFT: the Society For world bank Financial Telecommunication (SWIFT) is a non-profit international cooperation organization between international banks.

FIN: a SWIFT network provides a service for processing messages in real time, the messages having a fixed format and usage specifications. The application messages are 9 types of application messages, all the application messages comprise 5 parts (data blocks), and the heads and the tails of the parts are marked by brackets. The method comprises the following steps: basic header, application header, user header, telegram body, trailer.

MSGTYPE: each type of FIN contains several format (MSGTYPE) messages. For example: MT101, MT199, MT103, MT202, etc.

And (3) BIC: the SWIFT bank identification codes are used for each unit applying for adding SWIFT organization to work out SWIFT address codes of the line in advance according to the unified rule of the SWIFT organization, and the SWIFT bank identification codes take effect formally after being approved by the SWIFT organization.

SAA: the centralized platform of messages and files provided by SWIFT provides the functions related to the messages: entry, transmission, reception, storage, routing, etc., typically connected to a bus system of an enterprise or bank.

Reporting: messages sent externally to the application through the SWIFT network. The external message is sent out through the SWIFT network, and is also called as an o (output) message.

Reporting: the application sends messages to the outside through the SWIFT network. The message is sent to the SWIFT network, and therefore, the message is also called an i (input) message.

MQ trigger: by establishing a Trigger mechanism (Trigger) on the local queue, when a message arrives and meets a Trigger condition, a corresponding module is started to process.

MQ multi-stage jumping: the source queue manager and the target queue manager are not directly connected, and the message only passes through the transfer of the transmission queue and the channel in the routing process without the intervention of an intermediate program. For example: QM1 sends a message to QM3, which is automatically forwarded at QM2 without being processed by the application, i.e., the message does not land at QM 2.

Sample I, shown in Table 1:

TABLE 1

Wherein, the letter I indicates that the message is an I message, namely a forward message, 199, namely MSGTYPE is MT199, CRESCHZF is a receiver BIC, and the message is an MT199 message sent by BKCHNBJ to CRESCHZF.

Samples are reported in table 2:

TABLE 2

Wherein, the letter O indicates that the message is an O message, namely an incoming message, 101, namely MSGTYPE is MT101, CRESCHZF is sender BIC, and the message is the MT101 message sent to BKCHCNSBJ by CRESCHZF.

Currently, for FIN messages, the sender BIC and the receiver BIC are contained in the header. The SIWFT network routes messages according to the BIC. There are different BIC for production environment or test environment. For example, for the mid line swift nk system, the test BIC was BKCHCNB0 and the production BIC was BKCHCNBJ. However, due to the requirement of different batches of tests, the bank system usually has a plurality of test environments, which requires the saa (lt) connected with the bank application system to switch to different test environments. One and only one SAA (LT) can not be considered when different batches are tested simultaneously.

The present invention provides a FIN message multi-environment forwarding method, please refer to fig. 1, the FIN message multi-environment forwarding method provided by the present invention relates to incoming message processing, and includes:

s101: and the application system receives the FIN message through a bus system, wherein the FIN message reaches a receiving queue of a local queue of the application system.

In an embodiment of the present invention, since the FIN packet is transmitted through the Wesphere MQ, after the packet reaches the application local receive queue, the application starts a subsequent processing flow.

In one embodiment of the invention, the method further comprises:

and modifying the receiving queue of the remote queue of the bus system into the forwarding queue of the local queue.

Referring to fig. 1, the method further includes:

s102: a trigger message is generated to start the trigger process.

In an embodiment of the present invention, a receiving queue of a remote queue of an external system P may be modified into a forwarding queue of a local queue type, a trigger process is set on the forwarding queue, and when a FIN message arrives, an application system writes a trigger message and starts the trigger process.

S103: and the trigger process writes the FIN message into a corresponding target queue.

Fig. 4 is a flowchart of a second implementation manner of a FIN message multi-environment forwarding method according to an embodiment of the present invention, referring to fig. 4, in the second implementation manner, the method further includes:

s001: configuring a deployment file, wherein the deployment file comprises a target queue, a coming report identifier and type information;

s002: establishing a forwarding local queue, and establishing the trigger process on the forwarding local queue;

s003: and establishing a sending channel, a sending queue and a remote queue of the target environment.

That is, in the present invention, a deployment file is configured at a forwarding sending end, and the deployment file includes a target queue, an incoming call identifier, an MSTYPE, and a BIC, where the target queue may be a local queue or a remote queue; establishing an MQ forwarding local queue, and establishing a trigger process and an initial queue Initiation queue on the forwarding queue; a send channel, send queue, remote queue (remote queue in deployment configuration file) to the target environment is established.

Fig. 2 is a detailed flowchart of step S103, please refer to fig. 2, which includes:

s201: and the triggering process reads the FIN message to obtain the source information and the type information corresponding to the FIN message.

In one embodiment of the present invention, the source information may be sender BIC and the type information may be MSGTYPE.

S202: and inquiring a corresponding deployment file according to the source information and the type information to obtain entry information.

S203: and writing the FIN message into a target queue corresponding to the entry information, wherein the target queue is a remote queue or a local queue.

Specifically, the deployment file includes a plurality of items of information including a target queue, a report identifier, and type information, and reads an item meeting a condition from the deployment file according to the source information and the type information, and writes the FIN packet into the target queue as it is.

Fig. 3 is a flowchart of a second embodiment of step S103, please refer to fig. 3, in the second embodiment of the present invention, the steps further include:

s204: when the target queue is a remote queue, forwarding the FIN message to a receiving queue of a target environment to start a subsequent processing flow;

s205: and when the target queue is a local queue, starting the subsequent processing flow locally.

That is, the trigger process reads the FIN packet in the forwarding queue and writes the packet into the corresponding target queue according to the source (sender BIC), type (MSGTYPE) and the like of the packet. The target queue can be a remote queue or a local queue, and if the target queue is the remote queue, the message is automatically forwarded to a receiving queue of the target test environment, and then the application starts a subsequent processing flow. If a local queue, the message is processed locally.

The local forwarding queue and the triggering process are used in the process of time reporting of the FIN message multi-environment forwarding method provided by the invention, and the triggering process writes the message into the corresponding queue according to the message incoming and outgoing identifier, BIC and MSGTYPE of the message, so that the coupling degree between system modules is reduced, the system expansibility is improved, the configuration is simple, a plurality of environments can be forwarded at the same time, and the O report is supported.

The present invention also provides another FIN message multi-environment forwarding method, referring to fig. 5, the another FIN message multi-environment forwarding method provided by the present invention relates to the processing of the forwarding, and includes:

s301: and the application system writes the FIN message into a forwarding queue with the type of a local queue.

In an embodiment of the present invention, the application writes the message into a locally defined REMOTE queue, and since the REMOTE queue corresponds to a queue manager and a receiving queue of an external system, after the message is written into the REMOTE queue, the message is automatically forwarded to the receiving queue corresponding to the external system through a corresponding channel, and after the external system reads the message, the subsequent processing flow is started.

S302: and generating a trigger message to start a trigger process after the FIN message reaches a forwarding queue.

In an embodiment of the present invention, the application system may write the FIN packet into a forwarding queue of a local queue type, and trigger a corresponding process after the packet arrives.

S303: and the trigger process writes the FIN message into a corresponding target queue.

Fig. 8 is a flowchart of another second implementation manner of a FIN message multi-environment forwarding method according to an embodiment of the present invention, referring to fig. 8, in the second implementation manner, the method further includes:

s010: and configuring a deployment file, wherein the deployment file comprises a target queue, a report identifier and type information.

In one embodiment of the present invention, a deployment file is configured at a forwarding sending end, and the deployment file includes a target queue, an incoming call identifier, an MSTYPE, and a BIC, where the target queue may be a local queue or a remote queue; establishing an MQ forwarding local queue, and establishing a trigger process and an initial queue Initiation queue on the forwarding queue; a send channel, send queue, remote queue (remote queue in deployment configuration file) to the target environment is established. And deploying a receiving channel at the forwarding receiving end, wherein the name of the receiving channel is the same as that of a sending channel of the forwarding end, and if the forwarding message needs to be received, the default transmission queue, namely the DEFINMITQ parameter, needs to be modified to be the application transmission queue.

Fig. 6 is a detailed flowchart of step S303, please refer to fig. 6, which includes the following steps:

s401: and the triggering process reads the FIN message to obtain the receiver information and the type information corresponding to the FIN message.

In one embodiment of the present invention, the recipient information may be recipient BIC and the type information may be MSGTYPE.

S402: and inquiring a corresponding deployment file according to the receiver information and the type information to obtain entry information.

S403: and writing the FIN message into a target queue corresponding to the entry information, wherein the target queue is a remote queue used by an application system or a newly-built remote queue.

Specifically, the deployment file includes a plurality of items of information including a target queue, a report identifier, and type information, and reads an item meeting a condition from the deployment file according to the source information and the type information, and writes the FIN packet into the target queue as it is. If there are multiple eligible entries, then multiple target queues are written. When the message is written into the target queue, the forwarding log is recorded at the same time, and the function of the log of the message forwarding record is added, so that the maintenance and the query are convenient.

Fig. 7 is a flowchart of a second embodiment of step S303, please refer to fig. 7, in the second embodiment of the present invention, the steps further include:

s404: when the target queue is a remote queue used by an application system, the FIN message is sent to an external environment through a corresponding channel;

s405: and when the target queue is a newly-built remote queue, adding a corresponding channel, and sending the FIN message to an external environment through the channel, wherein the channel points to the external environment.

That is, the trigger process writes the message into the corresponding target queue according to the BIC (receiver BIC), the type (MSGTYPE), and the like of the message. The target queue can be a REMOTE queue used by the application or a newly-built REMOTE queue, and if the target queue is the REMOTE queue used by the application, the message is directly sent to an external environment through a corresponding channel; if the new REMOTE queue is newly built, a corresponding channel needs to be added, and the channel points to the receiving environment of the application target.

In one embodiment of the invention, the method further comprises:

and when the FIN message reaches the external environment through the channel, jumping to an external system through the channel corresponding to the default transmission queue.

That is, the newly created REMOTE queue corresponds to the queue manager and the receiving queue of the external system, and after the packet reaches the application target receiving environment through the newly added channel, because the queue manager of the external system cannot be found, the packet jumps to the external system through the channel corresponding to the default transmission queue, where the MQ multi-level jump technology is used. The default transmission queue and the corresponding channel are part of the original application function and do not need to be reestablished.

In the process of forwarding, the local forwarding queue and the triggering process are used, and the triggering process writes the message into the corresponding queue according to the message forwarding identifier, the BIC and the MSGTYPE of the message, so that the coupling degree between system modules is reduced, the system expansibility is improved, the configuration is simple, a plurality of environments can be forwarded at the same time, and the I-newspaper is supported.

The invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes a FIN message multi-environment forwarding method when executing the computer program.

The invention also provides a computer readable storage medium storing a method for executing the FIN message multi-environment forwarding.

It should be noted that while the operations of the method of the present invention are depicted in the drawings in a particular order, this does not require or imply that the operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions. Having described exemplary embodiments of the present invention, a system of exemplary embodiments of the present invention will now be described with reference to the accompanying drawings. The implementation of the system can be referred to the above overall implementation, and repeated details are not repeated.

Fig. 9 is a schematic structural diagram of a system for forwarding a FIN message in multiple environments according to an embodiment of the present invention, please refer to fig. 9, where the system includes an SAA, a plurality of bus systems and an application system, the SAA (lt) transmits an MT101/MT199 message through a bus system P and an application system T, and the bus system P and the application system T have a plurality of test environments respectively and correspond to each other. Since the multiple batches of tests are performed simultaneously, the connection between SAA (LT) and the multiple bus systems needs to be switched. In the invention, the FIN message can be forwarded to the target environment by deploying the application system in the T environment. The application system provided by the invention is specifically described below according to incoming telegrams and network telegrams respectively.

The present invention provides an application system related to incoming message processing for FIN message multi-environment forwarding, please refer to fig. 10, wherein a module related to incoming message processing in the application system includes:

the message receiving module 100 is configured to receive a FIN message through a bus system, where the FIN message reaches a receiving queue of a local queue of the application system.

In one embodiment of the present invention, the application system further includes:

and the queue modification module is used for modifying the receiving queue of the remote queue of the bus system into the forwarding queue of the local queue.

Referring to fig. 10, the application system further includes:

a message generating module 200 for generating a trigger message to start the trigger procedure.

A message writing module 300, configured to write the FIN message into a corresponding target queue.

Fig. 13 is a block diagram of a second implementation of an application system for forwarding a FIN packet in multiple environments according to an embodiment of the present invention, and referring to fig. 13, in the second implementation, the application system further includes:

a file configuration module 400 configured to configure a deployment file, the deployment file including a target queue, a come report identifier, and type information;

a queue establishing module 500, configured to establish a forwarding local queue, and establish the trigger process on the forwarding local queue;

a channel establishing module 600, configured to establish a sending channel, a sending queue, and a remote queue of a target environment.

Fig. 11 is a schematic structural diagram of a first embodiment of a message writing module in an application system, please refer to fig. 11, in which the message writing module 300 includes:

a message reading module 310, configured to read the FIN message, so as to obtain source information and type information corresponding to the FIN message.

And the file query module 320 is configured to query the corresponding deployment file according to the source information and the type information to obtain entry information.

A queue writing module 330, configured to write the FIN packet into a target queue corresponding to the entry information, where the target queue is a remote queue or a local queue.

Fig. 12 is a schematic structural diagram of a second embodiment of a message writing module in an application system, please refer to fig. 12, in which the message writing module 300 further includes:

a first write module 340, configured to forward the FIN packet to a receive queue of a target environment to start a subsequent processing flow when the target queue is a remote queue;

and a second writing module 350, configured to locally start a subsequent processing flow when the target queue is a local queue.

The application system for forwarding the FIN message in multiple environments provided by the invention relates to the module composition of incoming telegrams, a local forwarding queue and a triggering process are used, and the triggering process writes the message into the corresponding queue according to the incoming telegram identifier, the BIC and the MSGTYPE of the message, so that the coupling degree between system modules is reduced, the system expansibility is improved, the configuration is simple, multiple environments can be forwarded at the same time, and I O messages are supported.

Referring to fig. 14, another exemplary system for multi-environment forwarding of FIN packets according to the present invention includes:

and a forwarding queue writing module 10, configured to write the FIN packet into a forwarding queue of a local queue type.

And a trigger message generating module 20, configured to generate a trigger message to start a trigger process after the FIN packet reaches the forwarding queue.

A FIN packet writing module 30, configured to write the FIN packet into a corresponding target queue by the trigger process.

Fig. 17 is another exemplary embodiment of a FIN packet multi-environment forwarding application system relating to module composition during forwarding, referring to fig. 17, where the system further includes:

a deployment file configuration module 40, configured to configure a deployment file, where the deployment file includes a target queue, a report identifier, and type information.

Fig. 15 is a schematic structural diagram of a FIN packet writing module according to a first embodiment, referring to fig. 15, the FIN packet writing module 30 includes:

a FIN packet reading module 31, configured to read the FIN packet by the trigger process to obtain receiver information and type information corresponding to the FIN packet.

And the deployment file query module 32 is configured to query the corresponding deployment file according to the receiver information and the type information to obtain entry information.

And a target queue writing module 33, configured to write the FIN packet into a target queue corresponding to the entry information, where the target queue is a remote queue used by an application system or a newly-built remote queue.

Fig. 16 is a schematic structural diagram of a FIN packet writing module in accordance with a second embodiment, referring to fig. 16, the FIN packet writing module 30 further includes:

a first packet writing module 34, configured to send the FIN packet to an external environment through a corresponding channel when the target queue is a remote queue used by an application system;

and a second packet writing module 35, configured to, when the target queue is a newly-built remote queue, add a corresponding channel, and send the FIN packet to an external environment through the channel, where the channel points to the external environment.

In one embodiment of the invention, the system further comprises:

and the transmission channel skipping module is used for skipping to an external system through a channel corresponding to the default transmission queue after the FIN message reaches the external environment through the channel.

The present invention provides a FIN message multi-environment forwarding application system, which relates to the module composition of forward message, and uses a local forwarding queue and a triggering process, wherein the triggering process writes the message into the corresponding queue according to the forward message identifier, BIC and MSGTYPE of the message, thereby realizing the reduction of the coupling degree between the system modules, the improvement of the system expansibility, the configuration is simple, and the system can simultaneously forward a plurality of environments and support the I message.

Furthermore, although in the above detailed description several unit modules of the system are mentioned, this division is not mandatory only. Indeed, the features and functions of two or more of the units described above may be embodied in one unit, according to embodiments of the invention. Also, the features and functions of one unit described above may be further divided into embodiments by a plurality of units. The terms "module" and "unit" used above may be software and/or hardware that realizes a predetermined function. While the modules described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.

The technical solution of the present invention will be described in detail with reference to specific examples.

For the FIN message, the sender BIC and the receiver BIC are included in the header. The SIWFT network routes messages according to the BIC. There are different BIC for production environment or test environment. For example, for the mid line swift nk system, the test BIC was BKCHCNB0 and the production BIC was BKCHCNBJ. However, due to the requirement of different batches of tests, the bank system usually has a plurality of test environments, which requires the saa (lt) connected with the bank application system to switch to different test environments. One and only one SAA (LT) can not be considered when different batches are tested simultaneously.

Fig. 18 is a schematic diagram of FIN message multi-environment forwarding in an embodiment of the present invention, please refer to fig. 18, in the embodiment of the present invention, saa (lt) transmits MT101/MT199 messages through a bank bus system P and an application system T, and the bus system P and the application system T have 5 test environments respectively and correspond to each other. Since the multiple batches of tests are performed simultaneously, the connection between SAA (LT) and P1 to P5 needs to be switched. In this example, the FIN packet may be forwarded to the target environment by deploying an application system including incoming and outgoing times in the T environment. For example, after the device is deployed in the T1 environment, the incoming message MT101 may be forwarded to the target T4 environment; the report MT199 generated by the T4 environment can also be transmitted to the P1 bus environment and saa (lt) through the T1 environment. The coupling degree between the system modules is reduced, the system expansibility is improved, the configuration is simple, a plurality of environments can be simultaneously forwarded, and the I report and the O report are supported.

Specifically, the present invention is deployed at a forwarding transmitting end:

1. a deployment file, comprising content: target queue, incoming and outgoing newspaper identification, MSTYPE, BIC.

The target QUEUE may be LOCAL QUEUE, or REMOTE QUEUE.

2. And establishing an MQ forwarding local queue, and establishing Trigger Process and Initiation queue on the forwarding queue.

3. A transmission channel, a transmission queue, and a remote queue (REMOTEQUEE in a deployment configuration file) to the target environment are established.

Deploying at a forwarding receiving end:

1. and the receiving channel has the same name as the sending channel of the forwarding end.

2. If the report needs to be received, the default transmission queue, i.e. the DEFINMITQ parameter, needs to be modified into the application transmission queue.

The process mainly comprises the following steps:

1. the remote sender server sends the FIN message to the forwarding queue, and writes a trigger message to the Initiation queue and triggers the Process if a message arrives. Here, the remote sending-side server needs to modify the receiving QUEUE corresponding to its own REMOE QUEUE, and modify from the application QUEUE to the forwarding QUEUE.

And 2, reading the message type, BIC and MSGTYPE of the FIN message by the Process. Here, BIC and MSGTYPE are different in position and identical in length in the incoming or outgoing report.

3. Reading the entry meeting the conditions from the deployment file according to the message type, BIC and MSGTYPE in the message, and writing the FIN message into the target queue in the original state. If there are multiple eligible entries, then multiple target queues are written. When writing into the target queue, and simultaneously recording the forwarding log. The target queue may be a local queue or a REMOTE REMOTE queue.

4. After the message is written into the target queue, the message is forwarded to a target test environment application local queue (incoming call) through a channel corresponding to the target queue, or is jumped to an external application system through a route.

Specifically, for the incoming call scenario: since the target test environment is fixed, there is only one. Therefore, for the incoming telegram, only one entry needs to be configured in the deployment file, for example, for the incoming telegram of the MT101(MSGTYPE) sent by the sender vwagdebb (bic), the target environment is T4, and the forwarding environment is T1, only the file configured as table 3 needs to be deployed in the T1 environment.

TABLE 3

Since there is only one entry that meets the condition, the FIN packet is written into the TO _ T4_ REMOTE _ QUEUE, which is a REMOTE QUEUE, so the FIN MT101 packet sent by VWAGDEBB is forwarded TO the application QUEUE of the T4 target environment. The T4 environment application reads the FIN message from the application queue and starts the subsequent operation (application flow).

If the sender is not VWAGDEBB, the FIN message is written into the swift.to.bps.recvqa local application queue, i.e. the MT101 message sent by the non-VWAGDEBB is processed in the T1 environment.

If it can not be determined which P-system the saa (lt) is connected to, the apparatus is deployed in all T-systems in case of normal P-system to T-system connection. In this way, whichever P environment receives the packet, the FIN packet can be forwarded to the T4 local application queue.

For the report scenario: if the report needs to be sent to the remote system, the device is deployed in a report generation environment. For example, after the forward report is generated in the T4 environment, the application writes the FIN message into the forwarding queue, and reads the message type, BIC, and MSGTYPE of the FIN message after the Process is triggered. The deployment configuration file is shown in table 4.

TABLE 4

Wherein, BPS.DSWIFTI.REMOTE.QUEUE is the application REMOTE queue on the T4 environment, and when the device is installed, the device does not need to be established again. JUMP.T1.REMOTE.QUEUE is MQ three-level long-jump queue, after the FIN message is written into JUMP.T1.REMOTE.QUEUE, it jumps from T1 environment to P1 environment, and then sends it to SAA (LT). Here, the reason why the FIN is sent from T4 to P1 environment by establishing forwarding channel hopping at T4 and T1 instead of directly using the application channel is that, when T1 and T4 environments are tested simultaneously, T4 to P1 channels are connected, and T1 to P1 cannot be used simultaneously.

In this scenario, the apparatus need not be installed in the T1 environment, but only needs to establish a receiving channel with the name of the T4 sending channel in the T1 environment. After the FIN packet in the T4 environment is sent to the T1 through the channel, since the designated queue manager and receiving queue in the P1 environment cannot be found in T1, the FIN packet is forwarded to the application receiving queue in the P1 environment through the application channel in T1 (the default transmission queue of T1, that is, the DEFXMITQ parameter, needs to be modified as the application transmission queue).

If it cannot be determined which P-environment the LT is connected to, then multiple entries, e.g. table 5, are provided in the configuration file.

TABLE 5

MT199 sent to VWAGDEBB will write 4 simultaneously REMOTE queues, jump from T1 to T5 to P1 to P5 environment, respectively, and finally to saa (lt).

In a specific embodiment, the MQ trigger manager is used to monitor whether the forwarding queue FIN.

TABLE 6

In a specific embodiment, the FIN _ TRANSFER reads a FIN message in the FIN. If the target queue does not exist, writing to a default deadlock queue.

In summary, the present invention provides a FIN message multi-environment forwarding method, a FIN message multi-environment forwarding system, an application system, a computer device, and a computer readable storage medium, wherein a local forwarding queue and a trigger process are used, and the trigger process writes a message into a corresponding queue according to a message identifier of the message, a BIC, and an MSGTYPE, and the beneficial effects brought by the present invention include:

1. a set of complete and comprehensive FIN message forwarding mechanism is provided.

2. The installation configuration is simple, and the popularization nature is high.

3. The test information is improved, and the communication cost is saved.

Improvements to a technology can clearly be distinguished between hardware improvements (e.g. improvements to the circuit structure of diodes, transistors, switches, etc.) and software improvements (improvements to the process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardbyscript Description Language (vhr Description Language), and the like, which are currently used by Hardware compiler-software (Hardware Description Language-software). It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: the ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory.

Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially or partially implemented in the form of software products, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and include instructions for causing a computer system (which may be a personal computer, a server, or a network system, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present application.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The application is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable systems, tablet-type systems, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics systems, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or systems, and the like.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing systems that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage systems.

While the present application has been described with examples, those skilled in the art will appreciate that there are numerous variations and permutations of the present application without departing from the spirit of the application, and it is intended that the appended claims encompass such variations and modifications as fall within the true spirit of the application.

Claims

1. A FIN message multi-environment forwarding method is characterized by comprising the following steps:

the step of writing the FIN message into a corresponding target queue by the trigger process comprises the following steps:

the triggering process reads the FIN message to obtain receiver information and type information corresponding to the FIN message;

inquiring a corresponding deployment file according to the receiver information and the type information to obtain entry information;

and writing the FIN message into a target queue corresponding to the entry information, wherein the target queue is a remote queue used by an application system or a newly-built remote queue.

2. The method of claim 1, wherein the triggering process writing the FIN packet to the corresponding target queue further comprises:

when the target queue is a remote queue used by an application system, the FIN message is sent to an external environment through a corresponding channel;

and when the target queue is a newly-built remote queue, adding a corresponding channel, and sending the FIN message to an external environment through the channel, wherein the channel points to the external environment.

3. The method of claim 2, further comprising:

4. The method of claim 1, further comprising:

and configuring a deployment file, wherein the deployment file comprises a target queue, a report identifier and type information.

5. An application system for multi-environment forwarding of FIN packets, the application system comprising:

a FIN message writing module, configured to write the FIN message into a corresponding target queue; the FIN packet writing module includes:

the FIN message reading module is used for reading the FIN message to obtain the receiver information and the type information corresponding to the FIN message;

the deployment file query module is used for querying the corresponding deployment file according to the receiver information and the type information to obtain entry information;

and the target queue writing module is used for writing the FIN message into a target queue corresponding to the entry information, wherein the target queue is a remote queue used by an application system or a newly-built remote queue.

6. The application system of claim 5, wherein the FIN packet writing module further comprises:

the first message writing module is used for sending the FIN message to an external environment through a corresponding channel when the target queue is a remote queue used by an application system;

and the second message writing module is used for increasing a corresponding channel and sending the FIN message to an external environment through the channel when the target queue is a newly-built remote queue, wherein the channel points to the external environment.

7. The application system of claim 6, further comprising:

8. The application system of claim 5, further comprising:

the deployment file configuration module is used for configuring a deployment file, and the deployment file comprises a target queue, a report identifier and type information.

9. A system for FIN message multi-environment forwarding, the system comprising an SAA, a bus system and an application system according to any one of claims 5 to 8.

10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the FIN message multi-environment forwarding method of any one of claims 1 to 4 when executing the computer program.

11. A computer-readable storage medium storing a method for performing FIN message multi-environment forwarding according to any one of claims 1 to 4.