CN113590355A - Method for realizing workflow callback message and message gateway system - Google Patents
Method for realizing workflow callback message and message gateway system Download PDFInfo
- Publication number
- CN113590355A CN113590355A CN202110869852.4A CN202110869852A CN113590355A CN 113590355 A CN113590355 A CN 113590355A CN 202110869852 A CN202110869852 A CN 202110869852A CN 113590355 A CN113590355 A CN 113590355A
- Authority
- CN
- China
- Prior art keywords
- message
- callback
- workflow
- callback message
- configuration information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Entrepreneurship & Innovation (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure provides a method for realizing workflow callback message, which can be applied to the field of finance. The implementation method of the workflow callback message comprises the following steps: responding to a workflow center callback message sending request, and acquiring a service system ID, a service workflow process ID and a message to be recalled; determining callback message configuration information according to the service system ID and the service workflow process ID; and sending the message to be recalled according to the callback message configuration information, wherein the callback message configuration information comprises signature setting information, callback message link and transmission format information. The present disclosure also provides a workflow message gateway system, device, storage medium and program product.
Description
Technical Field
The present disclosure relates to the field of finance, and more particularly, to a method, a message gateway system, a device, a medium, and a program product for implementing a workflow callback message.
Background
In various office automation (oa) systems and enterprise Resource planning (erp) (enterprise Resource planning) systems, workflow is an important component, and in order to maintain consistent technology type selection, save development cost and deploy hardware resources, the workflow component is generally deployed independently into a flow jumping center, i.e., a workflow center, which can run independently. And each business system uploads the office flow and the approval flow required in the system to the workflow center and informs the callback address corresponding to the business system, and after the flow is skipped, the workflow center informs the business system of the message through the callback address.
Due to the existence of the callback address, the coupling degree of the workflow and each service system is deep, and for different requirements of different service systems, unique service callback design needs to be performed, for example, method differences, security differences, transmission protocol differences, retransmission differences and the like, and these differences cause low working efficiency and occupation of system resources when the workflow center callbacks messages.
Disclosure of Invention
In view of the foregoing, the present disclosure provides a workflow callback message implementation method, a message gateway system, a device, a medium, and a program product that improve workflow center callback message efficiency.
According to a first aspect of the present disclosure, a method for implementing a workflow callback message is provided, including: responding to a workflow center callback message sending request, and acquiring a service system ID, a service workflow process ID and a message to be recalled;
determining callback message configuration information according to the service system ID and the service workflow process ID; and
sending the message to be recalled according to the callback message configuration information,
the callback message configuration information comprises signature setting information, callback message link and transmission format information.
According to an embodiment of the present disclosure, the sending the message to be callback according to the callback message configuration information includes:
signing the message to be recalled according to the signature setting information; and
and sending a message to be recalled to the callback message link according to the transmission format information.
According to the embodiment of the present disclosure, the callback message configuration information further includes encryption configuration information, and before sending the message to be callback to the callback message link according to the transmission format information, the method further includes:
and encrypting the signed message to be recalled according to the encryption configuration information.
According to the embodiment of the disclosure, the transmission format information includes a message format based on XML, a message format based on json and an http protocol transmission mode.
According to an embodiment of the present disclosure, the determining callback message configuration information according to the service system ID and the service workflow process ID includes:
determining a callback message configuration table according to the service system ID and the service workflow process ID; and
and determining callback message configuration information according to the callback message configuration table.
According to an embodiment of the present disclosure, the callback message configuration information further includes retransmission policy setting information,
after the message to be recalled is sent according to the callback message configuration information, the method further includes:
receiving parameters returned by a service system;
determining a callback message sending state according to the parameters; and
and when the sending state of the callback message is determined to be sending failure, executing a retransmission strategy according to the retransmission strategy setting information, wherein the retransmission strategy setting information comprises the total number of times of retransmission and the retransmission interval time.
According to an embodiment of the present disclosure, after the sending the message to be callback according to the callback message configuration information, the method further includes:
obtaining the blocking time and the blocking quantity of callback messages of the current same service system ID; and
and if the blocking time of the callback message is determined to be greater than a first preset threshold and the blocking quantity is determined to be greater than a second preset threshold, executing a fusing strategy, reporting an error to a workflow center, and recording an error state.
According to an embodiment of the present disclosure, before the sending the message to be recalled according to the callback message configuration information, the method further includes:
obtaining the number of callback messages of the same service system ID; and
and if the number of the callback messages is larger than a third preset threshold value, limiting the ID of the service system.
According to the embodiment of the disclosure, the message to be recalled comprises a service system ID, a service workflow process ID, a response code, a response message, a current handler and a current processing result.
According to an embodiment of the present disclosure, the method further comprises:
and responding to a data synchronization request of a workflow center, and synchronizing newly-added process information into a gateway database, wherein the process information comprises a service system ID and a service workflow process ID.
A second aspect of the present disclosure provides a workflow message gateway system comprising:
the acquisition module is used for responding to a workflow center callback message sending request, and acquiring a service system ID, a service workflow process ID and a message to be recalled;
the determining module is used for determining callback message configuration information according to the service system ID and the service workflow process ID; and
the sending module is used for sending the message to be recalled according to the callback message configuration information;
the callback message configuration information comprises signature setting information, callback message link and transmission format information.
A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method for implementing the workflow callback message.
The fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions, which when executed by a processor, cause the processor to execute the method for implementing the workflow callback message.
The fifth aspect of the present disclosure also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the method for implementing the workflow callback message.
Drawings
The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:
FIG. 1 schematically illustrates a system architecture diagram for an implementation method that may be used for workflow callback messages according to an embodiment of the disclosure;
FIG. 2 schematically illustrates a flow chart of a method of implementing a workflow callback message according to an embodiment of the disclosure;
FIG. 3A is a flow chart that schematically illustrates another method for implementing a workflow callback message, in accordance with an embodiment of the present disclosure;
FIG. 3B schematically illustrates a flow diagram of a synchronization setting and a current limit fusing setting of a callback message according to an embodiment of the disclosure;
FIG. 4 schematically illustrates a block diagram of a workflow message gateway system according to an embodiment of the disclosure; and
fig. 5 schematically shows a block diagram of an electronic device adapted to implement an implementation method of a workflow callback message according to an embodiment of the disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
In various office automation (oa) systems and enterprise Resource planning (erp) (enterprise Resource planning) systems, workflow is an important component, and in order to maintain consistent technology type selection, save development cost and deploy hardware resources, the workflow component is generally deployed independently into a flow jumping center, i.e., a workflow center, which can run independently. And each business system uploads the office flow and the approval flow required in the system to the workflow center and informs the callback address corresponding to the business system, and after the flow is skipped, the workflow center informs the business system of the message through the callback address.
Due to the existence of the callback address, the coupling degree of the workflow and each service system is deep, and a unique service callback design is required for different requirements of different service systems, which is exemplified as follows:
the http protocol transmission method difference: some service systems only require the GET method to notify the callback message, and some service systems must require the POST method to send the request.
Safety differences: some service systems only require callback message signatures, and some service systems require callback messages to be not only signed and authenticated but also encrypted, thereby bringing key configuration and algorithm configuration with various characteristics.
Difference of transmission protocol: most systems receive messages using the HTTP RestFul interface based on application/json, but still the systems communicate with the outside world using XML based web-services. When various systems are coupled with a workflow system, the workflow system may need to design callback modes based on different transport protocols.
Retransmission difference: when the service system is abnormal and the callback message is not received, the workflow center is required to retransmit the callback message, different service systems have different requirements for retransmission time, and some workflow centers may also be required to support an inquiry interface to perform confirmation inquiry on unconfirmed workflow states.
Based on the above differences, the workflow center has low working efficiency when recalling messages, and occupies system resources.
The embodiment of the present disclosure provides a method for implementing a workflow callback message, where the method is applied to a message gateway system, and includes: responding to a workflow center callback message sending request, and acquiring a service system ID, a service workflow process ID and a message to be recalled; determining callback message configuration information according to the service system ID and the service workflow process ID; sending the message to be recalled according to the callback message configuration information; the callback message configuration information comprises signature setting information, callback message link and transmission format information.
Fig. 1 schematically illustrates a system architecture diagram of an implementation method that may be used for workflow callback messages according to an embodiment of the disclosure. It should be noted that the system architecture shown in fig. 1 is only an example of an application scenario and a system architecture in which the embodiments of the present disclosure may be used to help those skilled in the art understand the technical content of the present disclosure, but does not mean that the embodiments of the present disclosure may not be used in other devices, systems, environments or scenarios. It should be noted that the method for implementing a workflow callback message and the workflow message gateway system provided by the embodiments of the present disclosure may be used in related aspects in the financial field, and may also be used in any field other than the financial field.
As shown in fig. 1, in the present embodiment, the workflow gateway system 120 is independently deployed between the business system 130 and the workflow center 110, and the workflow gateway system 120 includes a user management authentication module 121, a callback message configuration module 122, a cockpit management module 123, a callback message sending module 124, and a data synchronization module 125. The workflow center 110 synchronizes the newly added process related information to a database table of the workflow gateway system 120 through the data synchronization module 125, and different business systems can maintain respective callback message parameters through the user management authentication module 121; a user may configure a callback message through the callback message configuration module 122 to support the requirement of customizing the callback message for each service, and after a workflow in the workflow center 110 is completed, the user needs to send the callback message to the corresponding service system 130, first, the workflow center 110 sends a callback notification to the workflow gateway system 120, and after receiving the callback notification, the workflow gateway system 120 sends the callback message to the service system 130 through the callback message sending module 124 according to the callback message configuration information of the callback message configuration module 122. Through the system architecture of the implementation, a workflow gateway system is arranged, and the gateway system sends callback messages to the service systems, so that the problem of differentiation of sending the callback messages to different service systems by a workflow center is solved, and the efficiency of sending the callback messages is improved.
The method for implementing the workflow callback message according to the disclosed embodiment will be described in detail with reference to fig. 2 to 5 based on the system architecture described in fig. 1.
Fig. 2 schematically illustrates a flow chart of an implementation method of a workflow callback message according to an embodiment of the disclosure.
As shown in fig. 2, the method for implementing the workflow callback message of this embodiment includes operations S210 to S230, and the method may be executed by the workflow network system.
In operation S210, in response to the workflow center callback message sending request, a service system ID, a service workflow process ID, and a message to be recalled are acquired.
In one example, if a business system needs to use a workflow center, a workflow file defined by the business system needs to be uploaded to the workflow center, and a business system ID and a business workflow ID that belongs to the business system flow are registered simultaneously, the business workflow ID is globally unique or unique within the business system, and the workflow center stores the business system ID and the business workflow ID into a database. After a certain workflow of the workflow center is executed, a message needs to be called back to a service system corresponding to the workflow, at this time, the workflow center sends a request to an externally exposed http address of the gateway system, and the http address is linked in the following form: http: and/or gateway system url/redirect/service system ID/service workflow process ID, and the gateway system receives the sending request of the workflow center callback message and simultaneously acquires the service system ID and the service workflow process ID. The format of the message to be recalled is predefined based on data available at the workflow center.
In operation S220, callback message configuration information is determined according to the service system ID and the service workflow process ID.
In one example, after a user can log in a gateway system, callback message configuration information is set in a callback message configuration module to adapt to callback message requirements customized by different business systems, such as whether encryption is required, which transmission format and transmission method are required, and the like, the callback message configuration information is stored in a database table of the gateway system in a corresponding relationship with a business system ID and a business workflow process ID, and the corresponding callback message configuration information can be determined according to the business system ID and the business workflow process ID.
In operation S230, a message to be recalled is sent according to the callback message configuration information.
According to an embodiment of the present disclosure, the callback message configuration information includes signature setting information, callback message link, and transmission format information.
In one example, the signature setting information includes a private key used for signature, a public key and an algorithm are exposed to the external service system, the external service system verifies the signature information according to the public key to verify the validity of the callback message, the message to be recalled of operation S210 is signed by the private key in the gateway system, the signed message to be recalled is sent according to the callback message configuration information, and specifically, the signed message to be recalled is sent to the callback message link according to the set transmission format information to complete the sending of the message to be recalled.
According to the method for realizing the workflow callback message provided by the embodiment of the disclosure, the workflow gateway system is arranged, and after the workflow center callback message sending request is received, the service system ID, the service workflow process ID and the message to be recalled are obtained; determining callback message configuration information according to the service system ID and the service workflow process ID; and sending the message to be recalled according to the callback message configuration information. And the decoupling of the workflow center and the service system is completed, and the sending efficiency of the callback message is improved.
Fig. 3A schematically illustrates a flowchart of another implementation method of a workflow callback message according to an embodiment of the present disclosure.
As shown in fig. 3A, the method for implementing the workflow callback message of this embodiment includes operations S310 to S350.
In operation S310, in response to the workflow center callback message sending request, a service system ID, a service workflow process ID, and a message to be recalled are acquired.
According to the embodiment of the disclosure, the message to be recalled comprises a service system ID, a service workflow process ID, a response code, a response message, a current handler and a current processing result. The response code is 0 to represent that the business workflow process is successfully executed, the response codes are not 0 to represent that the business workflow process is failed to be executed, and when the response codes are not 0, the response message is specific error reporting information.
The technical solution and principle of operation S310 are the same as those of operation S210 shown in fig. 2, and are not described again.
In operation S320, callback message configuration information is determined according to the service system ID and the service workflow process ID.
According to the embodiment of the present disclosure, operation S320 specifically includes determining a callback message configuration table according to the service system ID and the service workflow process ID; and determining callback message configuration information according to the callback message configuration table, wherein the callback message configuration information comprises signature setting information, callback message link and transmission format information.
In one example, when a business system uploads a new workflow to a workflow center, the workflow center configures a business workflow process ID, and at the same time, performs callback message configuration for the workflow, and stores the configuration in a database table of a gateway system in the form of a callback message configuration table.
In operation S330, a message to be recalled is sent according to the callback message configuration information.
Operation S330 includes the steps of:
in the first step, the callback message is signed according to the signature setting information.
The signature setting information comprises a private key for signature, a public key and an algorithm for exposing the external service system, and the external service system verifies the signature information according to the public key so as to verify the validity of the callback message.
And in the second step, the signed message to be recalled is encrypted according to the encryption configuration information.
In one example, the callback message configuration information further comprises encryption configuration information, the encryption configuration information comprises common DES/3DES/RSA/SM state secret series encryption algorithms, keys are respectively configured in the service system and the gateway system, keys configured by different users are only visible by the user, and keys configured by other users are not visible. The signed message to be recalled can be encrypted according to an encryption algorithm in the encryption configuration information.
And in the third step, the message to be recalled is sent to the callback message link according to the transmission format information.
In one example, after the first step and the second step, the message to be callback is linked to the callback message, and the message to be callback is sent after signature and encryption processing according to a preset transmission format, where the transmission format may be a message format based on XML or a message format based on json, and the http protocol transmission mode includes GET and POST.
In operation S340, parameters returned by the service system are received, and a callback message sending status is determined according to the parameters.
After the service system receives the callback message sent by the gateway system, the service system returns relevant parameters to represent that the service system has received the callback message, and the current callback message sending state can be determined according to the parameters returned by the service system.
In operation S350, when it is determined that the callback message transmission status is transmission failure, a retransmission policy is performed according to the retransmission policy setting information.
In order to ensure that the service system can receive the callback message, a retransmission policy needs to be executed according to the callback transmission state.
According to the embodiment of the present disclosure, the callback message configuration information further includes retransmission policy setting information, and the retransmission policy setting information includes a total number of retransmissions and a retransmission interval time, and is used for retransmission after transmission of the callback message fails. And when the callback message transmission state is determined to be transmission failure, executing a retransmission policy according to the retransmission policy setting information. In order to avoid that a certain service system occupies system resources for a long time due to system failure or other reasons, the total current retransmission times need to be judged according to the retransmission strategy setting information before the retransmission strategy is executed, and if the total retransmission times is greater than a preset threshold value, the retransmission is suspended.
Fig. 3B schematically illustrates a flow diagram of synchronization settings and current limit fusing settings for callback messages according to an embodiment of the disclosure.
As shown in fig. 3B, operations S301 to S302 are flows of callback message fusing setting, operations S303 to S304 are flows of callback message throttling setting, and operation S305 is a flow of callback message synchronization setting.
In order to prevent some service systems from deploying too many workflows in a workflow center, which causes too much callback message transmission to occupy system resources of the workflow center, a current limiting and fusing strategy can be executed on the service system according to a service system ID.
In operation S301, the callback message blocking time and the number of blocks of the current same service system ID are obtained.
In operation S302, if it is determined that the blocking time of the callback message is greater than the first preset threshold and the blocking number is greater than the second preset threshold, the fusing policy is executed, an error is reported to the workflow center, and an error state is recorded.
In one example, after the gateway system sends the callback message to the service system and does not receive the returned parameters, it is determined that the service system may be abnormal, resulting in a large amount of callback message blocking, at this time, the callback message blocking number and blocking time of the same service system ID may be obtained, if the callback message blocking time is greater than a first preset threshold and the callback message blocking number is greater than a second preset threshold, it is determined that the service system is blocked, a fusing policy needs to be executed, an error is reported to the workflow center, and an error state is recorded.
In operation S303, the number of callback messages of the same service system ID is acquired.
In operation S304, if it is determined that the number of callback messages is greater than the third preset threshold, the service system ID is limited.
In one example, the number of callback messages of the same service system is obtained, if the number of the callback messages is greater than a third preset threshold, it is determined that the service system occupies too many system resources, and the service system is limited in current, including suspending sending of the callback messages under the service system ID, reducing the priority of the callback messages of the service system, and the like. The first preset threshold, the second preset threshold and the third preset threshold are all empirical values and can be adjusted according to actual service requirements.
In operation S305, in response to a data synchronization request of the workflow center, newly added process information is synchronized into the gateway database, wherein the process information includes a service system ID and a service workflow process ID.
In one example, after a new workflow is added to the workflow center, a new service workflow process ID is configured for the new workflow, and the new workflow is synchronized with the gateway system, where the synchronized information at least includes the service system ID and the service workflow process ID. The synchronization mechanism may be implemented using conventional ETL tools, synchronizing only the latest data according to system time. The data synchronization module in the gateway system responds to a data synchronization request of a workflow center, synchronizes newly added process information to a gateway database, and when a latest service ID and a service workflow ID are synchronized to the gateway database, a timing task of the gateway system can detect that a new service workflow ID which is just synchronized and has not been configured by a callback message is newly added under a service system ID associated with a service system user when the service system user is registered, so that the user is reminded in various modes such as E-mail, short message, station mail and the like.
According to the method for realizing the workflow callback message, the callback message configuration information is set by deploying the workflow callback message gateway system, so that the gateway system sends the callback message to the service system according to the callback message configuration information, excessive system resources occupied by the service system when the callback message is sent abnormally are avoided by setting a current limiting and fusing mechanism, the workflow center and the service system are decoupled, and the efficiency of the workflow center is improved.
Based on the realization method of the workflow message, the invention also provides a workflow message gateway system. The apparatus will be described in detail below with reference to fig. 4.
Fig. 4 schematically shows a block diagram of a workflow message gateway system according to an embodiment of the present disclosure.
As shown in fig. 4, the workflow message gateway system 400 of this embodiment includes an obtaining module 410, a determining module 420, and a sending module 430.
The obtaining module 410 is configured to obtain a service system ID, a service workflow process ID, and a message to be recalled in response to a workflow center callback message sending request. In an embodiment, the obtaining module 410 may be configured to perform the operation S210 described above, which is not described herein again.
The determining module 420 is configured to determine callback message configuration information according to the service system ID and the service workflow process ID. In an embodiment, the determining module 420 may be configured to perform the operation S220 described above, which is not described herein again.
The sending module 430 is configured to send a message to be callback according to the callback message configuration information. In an embodiment, the sending module 430 may be configured to perform the operation S230 described above, which is not described herein again.
According to an embodiment of the present disclosure, wherein the callback message configuration information includes signature setting information, callback message link, and transmission format information.
According to the embodiment of the present disclosure, any plurality of the obtaining module 410, the determining module 420, and the sending module 430 may be combined and implemented in one module, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the obtaining module 410, the determining module 420, and the sending module 430 may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware by any other reasonable manner of integrating or packaging a circuit, or may be implemented in any one of or a suitable combination of software, hardware, and firmware. Alternatively, at least one of the obtaining module 410, the determining module 420 and the sending module 430 may be at least partially implemented as a computer program module, which when executed may perform the respective functions.
Fig. 5 schematically shows a block diagram of an electronic device adapted to implement an implementation method of a workflow callback message according to an embodiment of the disclosure.
As shown in fig. 5, an electronic device 500 according to an embodiment of the present disclosure includes a processor 501 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. The processor 501 may comprise, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 501 may also include onboard memory for caching purposes. Processor 501 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the disclosure.
In the RAM 503, various programs and data necessary for the operation of the electronic apparatus 500 are stored. The processor 501, the ROM 502, and the RAM 503 are connected to each other by a bus 504. The processor 501 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 502 and/or the RAM 503. Note that the program may also be stored in one or more memories other than the ROM 502 and the RAM 503. The processor 501 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in one or more memories.
According to an embodiment of the present disclosure, electronic device 500 may also include an input/output (I/O) interface 505, input/output (I/O) interface 505 also being connected to bus 504. The electronic device 500 may also include one or more of the following components connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include ROM 502 and/or RAM 503 and/or one or more memories other than ROM 502 and RAM 503 described above.
Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the implementation method of the workflow callback message provided by the embodiment of the disclosure.
The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 501. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of a signal on a network medium, downloaded and installed through the communication section 509, and/or installed from the removable medium 511. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511. The computer program, when executed by the processor 501, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.
Claims (14)
1. A realization method of workflow callback message, the method is applied to a message gateway system, and comprises the following steps:
responding to a workflow center callback message sending request, and acquiring a service system ID, a service workflow process ID and a message to be recalled;
determining callback message configuration information according to the service system ID and the service workflow process ID; and
sending the message to be recalled according to the callback message configuration information,
the callback message configuration information comprises signature setting information, callback message link and transmission format information.
2. The method of claim 1, wherein the sending the pending callback message according to the callback message configuration information comprises:
signing the message to be recalled according to the signature setting information; and
and sending a message to be recalled to the callback message link according to the transmission format information.
3. The method of claim 2, wherein the callback message configuration information further comprises encryption configuration information, and further comprising, before sending the pending callback message to the callback message link according to the transport format information:
and encrypting the signed message to be recalled according to the encryption configuration information.
4. The method of claim 2, wherein the transmission format information comprises XML-based message format, json-based message format, and http protocol transmission.
5. The method of claim 1, wherein determining callback message configuration information based on the business system ID and the business workflow process ID comprises:
determining a callback message configuration table according to the service system ID and the service workflow process ID; and
and determining callback message configuration information according to the callback message configuration table.
6. The method of claim 1, wherein the callback message configuration information further comprises retransmission policy setting information,
after the message to be recalled is sent according to the callback message configuration information, the method further includes:
receiving parameters returned by a service system;
determining a callback message sending state according to the parameters; and
and when the sending state of the callback message is determined to be sending failure, executing a retransmission strategy according to the retransmission strategy setting information, wherein the retransmission strategy setting information comprises the total number of times of retransmission and the retransmission interval time.
7. The method of claim 6, wherein after sending the pending callback message according to the callback message configuration information, the method further comprises:
obtaining the blocking time and the blocking quantity of callback messages of the current same service system ID; and
and if the blocking time of the callback message is determined to be greater than a first preset threshold and the blocking quantity is determined to be greater than a second preset threshold, executing a fusing strategy, reporting an error to a workflow center, and recording an error state.
8. The method of claim 1, wherein before sending the pending callback message according to the callback message configuration information, the method further comprises:
obtaining the number of callback messages of the same service system ID; and
and if the number of the callback messages is larger than a third preset threshold value, limiting the ID of the service system.
9. The method according to any one of claims 1 to 8, wherein the message to be recalled comprises a business system ID, a business workflow process ID, a response code, a response message, a current handler, and a current processing result.
10. The method according to any one of claims 1 to 8, further comprising:
and responding to a data synchronization request of a workflow center, and synchronizing newly-added process information into a gateway database, wherein the process information comprises a service system ID and a service workflow process ID.
11. A workflow message gateway system comprising:
the acquisition module is used for responding to a workflow center callback message sending request, and acquiring a service system ID, a service workflow process ID and a message to be recalled;
the determining module is used for determining callback message configuration information according to the service system ID and the service workflow process ID; and
the sending module is used for sending the message to be recalled according to the callback message configuration information;
the callback message configuration information comprises signature setting information, callback message link and transmission format information.
12. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-10.
13. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 10.
14. A computer program product comprising a computer program which, when executed by a processor, implements a method according to any one of claims 1 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110869852.4A CN113590355A (en) | 2021-07-30 | 2021-07-30 | Method for realizing workflow callback message and message gateway system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110869852.4A CN113590355A (en) | 2021-07-30 | 2021-07-30 | Method for realizing workflow callback message and message gateway system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113590355A true CN113590355A (en) | 2021-11-02 |
Family
ID=78252406
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110869852.4A Pending CN113590355A (en) | 2021-07-30 | 2021-07-30 | Method for realizing workflow callback message and message gateway system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113590355A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114710403A (en) * | 2022-03-30 | 2022-07-05 | 中国建设银行股份有限公司 | Data scheduling method, device, equipment, medium and program product |
-
2021
- 2021-07-30 CN CN202110869852.4A patent/CN113590355A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114710403A (en) * | 2022-03-30 | 2022-07-05 | 中国建设银行股份有限公司 | Data scheduling method, device, equipment, medium and program product |
| CN114710403B (en) * | 2022-03-30 | 2024-04-19 | 中国建设银行股份有限公司 | Data scheduling method, device, equipment, medium and program product |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230319534A1 (en) | Cross-resource subscription for m2m service layer | |
| US9934003B2 (en) | System and method for creating a development and operational platform for mobile applications | |
| US11750444B2 (en) | Implementation of compliance settings by a mobile device for compliance with a configuration scenario | |
| US9253265B2 (en) | Hot pluggable extensions for access management system | |
| CN109246197B (en) | Data processing method and device based on intelligent contract | |
| US9876703B1 (en) | Computing resource testing | |
| WO2019173245A1 (en) | System and method for establishing common request processing | |
| US10901817B1 (en) | Systems and methods for processing electronic requests | |
| CN112260863A (en) | Organization-level network equipment connection management method and device and computer equipment | |
| CN113590355A (en) | Method for realizing workflow callback message and message gateway system | |
| US9516109B2 (en) | Registry synchronizer and integrity monitor | |
| CN115934378A (en) | Service data processing method and device, electronic equipment and storage medium | |
| US20120254607A1 (en) | System And Method For Security Levels With Cluster Communications | |
| CN113296911B (en) | Cluster calling method, cluster calling device, electronic equipment and readable storage medium | |
| CN112953769B (en) | Data transmission method, device, computer system and readable storage medium | |
| CN115210698B (en) | Communication device, program, communication method, information processing device, and communication system | |
| CN112565340B (en) | Service scheduling method, device, computer system and medium for distributed application | |
| CN114257632A (en) | Disconnection reconnection method and device, electronic equipment and readable storage medium | |
| US11362843B1 (en) | Certificate rotation on host | |
| US20110167006A1 (en) | Method and system for a real-time case exchange in a service management environment | |
| US20140201839A1 (en) | Identification and alerting of network devices requiring special handling maintenance procedures | |
| US11943124B2 (en) | Data center asset remote workload execution via a connectivity management workload orchestration operation | |
| US11843706B1 (en) | Gradual certificate rotation | |
| US20230319559A1 (en) | Enrollment of enrollee devices to a wireless network | |
| EP3993458A1 (en) | Enrollment of enrollee devices to a wireless network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |