CN110942372B - Butt joint method and gateway of business end and ERP system - Google Patents

Butt joint method and gateway of business end and ERP system Download PDF

Info

Publication number
CN110942372B
CN110942372B CN201911148682.XA CN201911148682A CN110942372B CN 110942372 B CN110942372 B CN 110942372B CN 201911148682 A CN201911148682 A CN 201911148682A CN 110942372 B CN110942372 B CN 110942372B
Authority
CN
China
Prior art keywords
service
erp system
erp
information
session
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.)
Active
Application number
CN201911148682.XA
Other languages
Chinese (zh)
Other versions
CN110942372A (en
Inventor
戴飞飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou Tuya Information Technology Co Ltd
Original Assignee
Hangzhou Tuya Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou Tuya Information Technology Co Ltd filed Critical Hangzhou Tuya Information Technology Co Ltd
Priority to CN201911148682.XA priority Critical patent/CN110942372B/en
Publication of CN110942372A publication Critical patent/CN110942372A/en
Application granted granted Critical
Publication of CN110942372B publication Critical patent/CN110942372B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
    • G06Q30/0635—Processing of requisition or of purchase orders
    • 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/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Abstract

The invention relates to a docking method of a service end and an ERP system, which comprises the steps of creating an ERP-Proxy gateway, decoupling the service end and the ERP system, enabling the ERP-Proxy gateway to be respectively communicated with the service end and the ERP system, storing instructions in the ERP-Proxy gateway, and enabling the ERP-Proxy gateway to execute the following operations when being executed by a processor: receiving a session message from a service end; adding the session message into a session list; inquiring session information in a session list according to the preset polling time, and generating information to be processed; calling a service corresponding to the information to be processed to the ERP system, and returning a calling result; and updating the state information of the session message corresponding to the service end according to the calling result. According to the technical scheme, the coupling problem of the ERP-Proxy gateway, the service end and the ERP system is solved, the service problem of the service end cannot be influenced due to updating of the ERP system, and the coupling degree requirement is reduced.

Description

Butt joint method and gateway of business end and ERP system
Technical Field
The invention relates to the technical field of computer application, in particular to a method for butting a service end and an ERP system and an ERP-Proxy gateway.
Background
At present, two docking schemes with ERP systems exist:
1) Each business system or only 1 business system is directly connected with the ERP system, and then the business is invoked, including functions of ordering, inquiring and the like.
2) And establishing a gateway layer to connect with the ERP system and provide an interface for calling ERP service. The business system calls the gateway layer to complete the task according to the requirement.
Disadvantages:
in the first approach, each business layer needs to make such connection establishment, docking and invocation, which can result in repeated labor and more time consuming. The advantages are that: short and flat. But is slower when there are more traffic layers.
In the second scheme, although a gateway layer is extracted, only simple connection and calling services are maintained, and each service to be docked needs to be written in a service system of the user and complex ERP service calling rules. The intrusion into the business system code is high. Subsequent maintenance and release can affect the on-line service. The advantages are that: the gateway is made lighter and does not change frequently.
Disclosure of Invention
The present invention aims to solve at least one of the technical problems existing in the prior art or related art.
Therefore, the invention aims to provide a method for interfacing a service end with an ERP system and an ERP-Proxy gateway, which solve the coupling problem of the ERP-Proxy gateway, the service end and the ERP system, and can not influence the service problem of the service end due to updating of the ERP system, thereby reducing the coupling degree requirement.
To achieve the above object, a technical solution of a first aspect of the present invention provides a method for interfacing a service end with an ERP system, creating an ERP-Proxy gateway, and decoupling the service end and the ERP system, so that the ERP-Proxy gateway can communicate with the service end and the ERP system, respectively, where the ERP-Proxy gateway stores instructions that, when executed by a processor, cause the ERP-Proxy gateway to perform the following operations: receiving a session message from a service end; adding the session message into a session list; inquiring session information in a session list according to the preset polling time, and generating information to be processed; calling a service corresponding to the information to be processed to the ERP system, and returning a calling result; and updating the state information of the session message corresponding to the service end according to the calling result.
In the technical scheme, an ERP-Proxy gateway is established between the business end and the ERP system and decoupled from the business end, so that the problem of coupling between the ERP system and the business end is solved, and the problems that the business end needs to write repeated business codes of ERP and the business end has heavy work due to the complexity and stability of the ERP system are shielded; on the other hand, the ERP-Proxy gateway can separate the further processing process of the corresponding product from the service end, reduce the consumption of service end resources and the work of less service ends, and avoid the repeated labor of the service ends and ERP systems.
In the above technical solution, preferably, the ERP-Proxy gateway communicates with the service end and the ERP system in real time based on the dubbo service framework.
In the above technical solution, preferably, the session message is a kafka message.
In the above technical solution, preferably, when the session message is transaction information of a product, a service corresponding to the information to be processed is invoked to the ERP system, including the following steps:
inquiring whether the client information corresponding to the transaction information exists or not from the ERP system according to the transaction information, and if not, storing the client information in the ERP system as a new client;
calling a service of creating a transaction order of the ERP system according to the transaction information;
invoking a service of auditing the transaction order of the ERP system according to the transaction information;
invoking a service of locking inventory of the ERP system according to the transaction information;
calling a service of creating a shipping notice of the ERP system according to the transaction information;
invoking a service of auditing the transaction order of the ERP system according to the transaction information;
and calling the service of the timing polling delivery order of the ERP system according to the transaction information.
In the above technical scheme, preferably, the pre-configured polling time is 1min-10min, and the optional values are 3min, 5min and 7min; and/or the time of the timing polling is 3min-5min, and the optional value is 3.5min, 4min and 4.5min.
The technical solution of the second aspect of the present invention provides a gateway, configured to be capable of communicating with a service end and an ERP system after decoupling the service end and the ERP system, including: a memory having instructions stored thereon; a processor for executing instructions; the interaction module is used for receiving the session message from the service end and updating the state information of the session message corresponding to the service end according to the service calling result; a session management module arranged to add session messages to the session list; the polling module is used for inquiring session messages in the session list according to the preset polling time and generating information to be processed; and the service calling module is used for calling the service corresponding to the information to be processed to the ERP system and returning a service calling result.
In the technical scheme, an ERP-Proxy gateway is established between the business end and the ERP system and decoupled from the business end, so that the problem of coupling between the ERP system and the business end is solved, and the problems that the business end needs to write repeated business codes of ERP and the business end has heavy work due to the complexity and stability of the ERP system are shielded; on the other hand, the ERP-Proxy gateway can separate the further processing process of the corresponding product from the service end, reduce the consumption of service end resources and the work of less service ends, and avoid the repeated labor of the service ends and ERP systems.
In the above technical solution, preferably, the interaction module communicates with the service end and the ERP system in real time based on the dubbo service framework.
In the above technical solution, preferably, the session message is a kafka message.
In the above technical solution, preferably, when the session message is transaction information of a product, the service calling module includes: the client inquiry unit is used for inquiring whether the client information corresponding to the transaction information exists or not from the ERP system according to the transaction information, and if the client information does not exist, the client information is stored in the ERP system as a new client; a creation service calling unit configured to call a service of creating a transaction order of the ERP system according to the transaction information; the audit order service calling unit is arranged to call the service of audit transaction orders of the ERP system according to the transaction information; an inventory locking service calling unit configured to call a service of locking inventory of the ERP system according to the transaction information; a shipment notification creation service calling unit configured to call a service for creating a shipment notification of the ERP system according to the transaction information; an order auditing service calling unit which is set as a service for calling an auditing transaction order of the ERP system according to the transaction information; and the ex-warehouse inquiry service calling unit is set as a service for calling the timing polling ex-warehouse of the ERP system according to the transaction information.
In the above technical solution, preferably, the pre-configured polling time is 1min-10min; and/or the time of the timing polling is 3min-5min.
Drawings
The foregoing and/or additional aspects and advantages of the invention will become apparent and may be better understood from the following description of embodiments taken in conjunction with the accompanying drawings in which:
FIG. 1 illustrates a block flow diagram of a docking method according to an embodiment of the present invention;
figure 2 shows a block flow diagram of step S6 according to an embodiment of the invention;
figure 3 shows a block diagram of a gateway according to an embodiment of the invention;
fig. 4 is a block diagram illustrating a service call module according to an embodiment of the present invention.
Detailed Description
In order that the above-recited objects, features and advantages of the present invention will be more clearly understood, a more particular description of the invention will be rendered by reference to the appended drawings and appended detailed description. It should be noted that, in the case of no conflict, the embodiments of the present application and the features in the embodiments may be combined with each other.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention, however, the present invention may be practiced in other ways than those described herein, and the scope of the invention is therefore not limited to the specific embodiments disclosed below.
ERP is an enterprise resource planning (Enterprise resource planning) short, is an information system integrating enterprise material flow, fund flow and information flow, can effectively integrate the existing production resources of enterprises, and promotes the real-time and lean management of the enterprises.
The following describes a method and gateway for interfacing a service end with an ERP system according to some embodiments of the present invention with reference to fig. 1 to 4.
As shown in fig. 1, a method for interfacing a service end with an ERP system according to an embodiment of the present invention includes the following steps:
s1, creating an ERP-Proxy gateway;
s2, decoupling the service end and the ERP system to enable the ERP-Proxy gateway to be respectively communicated with the service end and the ERP system;
the ERP-Proxy gateway stores instructions that, when executed by the processor, cause the ERP-Proxy gateway to:
s3, receiving a kafka message from a service end;
s4, adding the session message into a session list;
s5, inquiring session messages in the session list according to the preset polling time (inquiring every 3 minutes at regular time), and generating information to be processed;
s6, calling the service corresponding to the information to be processed to the ERP system, and returning a calling result;
s7, updating the state information of the session message corresponding to the service end according to the calling result.
As shown in fig. 2, according to another embodiment of the present invention, when a session message is transaction information of a product, S6, a service corresponding to information to be processed is invoked to the ERP system, including the following steps:
s61, inquiring whether the client information corresponding to the transaction information exists or not from the ERP system according to the transaction information, and if not, storing the client information in the ERP system as a new client;
s62, calling service of creating a trade order of the ERP system according to the trade information;
s63, invoking service of auditing transaction orders of the ERP system according to the transaction information;
s64, calling the service of locking the inventory of the ERP system according to the transaction information;
s65, calling a service of creating a shipping notice of the ERP system according to the transaction information;
s66, invoking service of auditing transaction orders of the ERP system according to the transaction information;
s67, calling the service of timing polling (timing inquiry every 5 minutes) of the ERP system to take a bill according to the transaction information.
As shown in fig. 1, a method for interfacing a service end with an ERP system according to still another embodiment of the present invention includes the following steps:
s1, creating an ERP-Proxy gateway;
s2, decoupling the service end and the ERP system, so that the ERP-Proxy gateway can be respectively communicated with the service end and the ERP system based on the dubbo service framework;
the ERP-Proxy gateway stores instructions that, when executed by the processor, cause the ERP-Proxy gateway to:
s3, receiving a session message from a service end;
s4, adding the session message into a session list;
s5, inquiring session messages in the session list according to the preset polling time (inquiring every 5 minutes at regular time), and generating information to be processed;
s6, calling the service corresponding to the information to be processed to the ERP system, and returning a calling result;
s7, updating the state information of the session message corresponding to the service end according to the calling result.
As shown in fig. 3, a gateway 100 according to a fourth embodiment of the present invention is configured to be capable of communicating with a service end and an ERP system after decoupling the service end and the ERP system, and includes:
a memory 10 having instructions stored thereon;
a processor 20 for executing instructions;
an interaction module 30 configured to receive the kafka message from the service end and update the state information of the session message corresponding to the service end according to the service invocation result;
a session management module 40 arranged to add session messages to the session list;
a polling module 50 arranged to query the session list for session messages according to a pre-configured polling time (a timed query every 5 minutes), generating information to be processed;
the service calling module 60 is configured to call the service corresponding to the information to be processed to the ERP system, and return a service call result.
As shown in fig. 3, a gateway according to a fifth embodiment of the present invention is configured to be capable of communicating with a service end and an ERP system based on a dubbo service framework after decoupling the service end and the ERP system, and includes:
a memory 10 having instructions stored thereon;
a processor 20 for executing instructions;
an interaction module 30 configured to receive the session message from the service end and update the state information of the session message corresponding to the service end according to the service call result;
a session management module 40 arranged to add session messages to the session list;
a polling module 50 arranged to query the session list for session messages according to a pre-configured polling time (a timed query every 5 minutes), generating information to be processed;
the service calling module 60 is configured to call the service corresponding to the information to be processed to the ERP system, and return a service call result.
As shown in fig. 4, when the session message is transaction information of a product, the service invocation module 60 according to the sixth embodiment of the present invention includes:
a client query unit 61 configured to query the ERP system for the presence or absence of client information corresponding to the transaction information according to the transaction information, and if not, the client information is stored as a new client in the ERP system;
a creation service calling unit 62 configured to call a service of creating a trade order of the ERP system according to the trade information;
an audit order service calling unit 63 configured to call a service of audit transaction orders of the ERP system according to the transaction information;
an inventory locking service calling unit 64 configured to call a service of locking an inventory of the ERP system according to the transaction information;
a shipment notification creation service calling unit 65 configured to call a service of creating a shipment notification of the ERP system according to the transaction information;
an order auditing service calling unit 66 configured to call a service for auditing a transaction order of the ERP system according to transaction information;
the delivery form inquiry service calling unit 67 is configured to call a service of the delivery form of the timing poll (every 4 minutes timing inquiry) of the ERP system according to the transaction information.
In any of the above embodiments, preferably, the preconfigured polling time is 1min-10min, and the optional values are 3min, 5min, and 7min; and/or the time of the timing polling is 3min-5min, and the optional value is 3.5min, 4min and 4.5min.
Compared with the prior art, the butt joint method and gateway of the business end and the ERP system have the advantages that the ERP-Proxy gateway is established between the business end and the ERP system and decoupled from the business end, so that the coupling problem between the ERP system and the business end is solved, and the problems that the business end needs to write repeated business codes of ERP and the business end is heavy in work due to the complexity and stability of the ERP system are shielded; on the other hand, the ERP-Proxy gateway can separate the further processing process of the corresponding product from the service end, reduce the consumption of service end resources and the work of less service ends, and avoid the repeated labor of the service ends and ERP systems.
In the present invention, the terms "first," "second," "third," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance; the term "plurality" means two or more, unless expressly defined otherwise. The terms "mounted," "connected," "secured," and the like are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; "coupled" may be directly coupled or indirectly coupled through intermediaries. The specific meaning of the above terms in the present invention can be understood by those of ordinary skill in the art according to the specific circumstances.
In the description of the present invention, it should be understood that the directions or positional relationships indicated by the terms "upper", "lower", "left", "right", "front", "rear", etc. are based on the directions or positional relationships shown in the drawings, are merely for convenience of describing the present invention and simplifying the description, and do not indicate or imply that the devices or units referred to must have a specific direction, be constructed and operated in a specific direction, and thus should not be construed as limiting the present invention.
In the description of the present specification, the terms "one embodiment," "some embodiments," "particular embodiments," and the like, mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (8)

1. The method for interfacing a service end and an ERP system is characterized by creating an ERP-Proxy gateway, decoupling the service end and the ERP system, enabling the ERP-Proxy gateway to communicate with the service end and the ERP system respectively, wherein the ERP-Proxy gateway stores instructions which, when executed by a processor, enable the ERP-Proxy gateway to perform the following operations:
receiving a session message from the service end;
adding the session message into a session list;
inquiring the session information in the session list according to a preset polling time to generate information to be processed;
when the session message is transaction information of a product, calling a service corresponding to the information to be processed to the ERP system, and returning a calling result, wherein the method comprises the following steps of:
inquiring whether client information corresponding to the transaction information exists or not from the ERP system according to the transaction information, and if not, storing the client information in the ERP system as a new client;
calling a service of creating a transaction order of the ERP system according to the transaction information;
invoking a service of auditing the transaction order of the ERP system according to the transaction information;
invoking a service of locking inventory of the ERP system according to the transaction information;
invoking a service of creating a shipping notice of the ERP system according to the transaction information;
invoking a service of timing polling out of a warehouse of the ERP system according to the transaction information; and updating the state information of the service end corresponding to the session message according to the calling result.
2. The method for interfacing a business end with an ERP system according to claim 1, wherein: the ERP-Proxy gateway communicates with the service end and the ERP system in real time based on a dubbo service framework.
3. The method for interfacing a business end with an ERP system according to claim 1, wherein: the session message is a kafka message.
4. The method for interfacing a business end with an ERP system according to claim 1, wherein: the preconfigured polling time is 1min-10min; and/or the time of the timing polling is 3min-5min.
5. A gateway configured to be capable of communicating with a service end and an ERP system after decoupling the service end and the ERP system, respectively, comprising:
a memory having instructions stored thereon;
a processor for executing the instructions;
the interaction module is arranged to receive a session message from the service end;
a session management module arranged to add the session message to a session list;
the polling module is used for inquiring the session messages in the session list according to the preset polling time and generating information to be processed;
the service calling module is used for calling the service corresponding to the information to be processed to the ERP system and returning a service calling result;
when the session message is transaction information of a product, the service calling module comprises:
the client inquiry unit is used for inquiring whether the client information corresponding to the transaction information exists or not to the ERP system according to the transaction information, and if the client information does not exist, the client information is stored in the ERP system as a new client;
a creation service calling unit configured to call a service of creating a transaction order of the ERP system according to the transaction information;
an audit order service calling unit configured to call a service of audit transaction orders of the ERP system according to the transaction information;
an inventory locking service calling unit, configured to call a service of locking inventory of the ERP system according to the transaction information;
a shipment notification creation service calling unit configured to call a service of creating a shipment notification of the ERP system according to the transaction information;
the ex-warehouse list query service calling unit is set to be used for calling the timing polling ex-warehouse list service of the ERP system according to the transaction information;
the interaction module is also used for updating the state information of the service end corresponding to the session message according to the service calling result.
6. The gateway of claim 5, wherein: the interaction module is respectively communicated with the service end and the ERP system in real time based on the dubbo service framework.
7. The gateway of claim 5, wherein: the session message is a kafka message.
8. The gateway of claim 1, wherein the preconfigured polling time is 1min-10min; and/or the time of the timing polling is 3min-5min.
CN201911148682.XA 2019-11-21 2019-11-21 Butt joint method and gateway of business end and ERP system Active CN110942372B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911148682.XA CN110942372B (en) 2019-11-21 2019-11-21 Butt joint method and gateway of business end and ERP system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911148682.XA CN110942372B (en) 2019-11-21 2019-11-21 Butt joint method and gateway of business end and ERP system

Publications (2)

Publication Number Publication Date
CN110942372A CN110942372A (en) 2020-03-31
CN110942372B true CN110942372B (en) 2023-05-12

Family

ID=69907772

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911148682.XA Active CN110942372B (en) 2019-11-21 2019-11-21 Butt joint method and gateway of business end and ERP system

Country Status (1)

Country Link
CN (1) CN110942372B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112559553A (en) * 2020-12-24 2021-03-26 上海明略人工智能(集团)有限公司 Method, system, electronic device and storage medium for viewing session content

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102137102A (en) * 2011-03-07 2011-07-27 南京麦伦思科技有限公司 Realizing method of service supporting platform for supporting multiclass information publishing modes
WO2015096005A1 (en) * 2013-12-23 2015-07-02 华为技术有限公司 Message processing method and gateway
CN108305010A (en) * 2018-02-10 2018-07-20 西安精雕软件科技有限公司 A kind of workflow engine system and its flow propulsion method cross-platform, across application
CN108874567A (en) * 2018-07-19 2018-11-23 广州市创乐信息技术有限公司 A kind of service processing method and system

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10560541B2 (en) * 2010-05-26 2020-02-11 Sap Se Service delivery management for brokered service delivery
CA2773342A1 (en) * 2012-03-30 2013-09-30 Disternet Technology, Inc. System and method for managing streaming services
CN103379096B (en) * 2012-04-18 2018-07-06 中兴通讯股份有限公司 Internet and carrier network business sharing method, service side and web gateway
CN104966185B (en) * 2015-06-19 2018-09-18 浙江双商信息科技有限公司 Method for processing business between ERP system and device
CN105260842B (en) * 2015-10-12 2020-05-15 用友网络科技股份有限公司 Communication method and system between heterogeneous ERP systems
CN106936701A (en) * 2015-12-30 2017-07-07 欧普照明股份有限公司 A kind of cloud gateway, cloud connection system and the method using cloud gateway communication
CN107332877A (en) * 2017-06-02 2017-11-07 上海金大师网络科技有限公司 It is route based on message and buffer context removes statusline feelings gateway system
US20170357678A1 (en) * 2017-07-31 2017-12-14 Qiang Wang Internet Map Macro Marker Management Theory and Control System

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102137102A (en) * 2011-03-07 2011-07-27 南京麦伦思科技有限公司 Realizing method of service supporting platform for supporting multiclass information publishing modes
WO2015096005A1 (en) * 2013-12-23 2015-07-02 华为技术有限公司 Message processing method and gateway
CN105009521A (en) * 2013-12-23 2015-10-28 华为技术有限公司 Message processing method and gateway
CN108305010A (en) * 2018-02-10 2018-07-20 西安精雕软件科技有限公司 A kind of workflow engine system and its flow propulsion method cross-platform, across application
CN108874567A (en) * 2018-07-19 2018-11-23 广州市创乐信息技术有限公司 A kind of service processing method and system

Also Published As

Publication number Publication date
CN110942372A (en) 2020-03-31

Similar Documents

Publication Publication Date Title
US8984535B2 (en) System and method for facilitating the exchange of information among applications
US7886295B2 (en) Connection manager, method, system and program product for centrally managing computer applications
US7761319B2 (en) Supply chain management
US9229998B2 (en) Method and system for exchanging information between back-end and front-end systems
US8036939B2 (en) Reporting in a supply chain
US6738975B1 (en) Extensible distributed enterprise application integration system
US7509326B2 (en) Central master data management
EP0806731A2 (en) Database network
US8526316B2 (en) System and method for dynamically modifying synchronized business information server interfaces
US20070079168A1 (en) Exception handling in content based routing solutions
US20070156538A1 (en) Architectural design for product catalog management application software
US20040103103A1 (en) Collaborative master data management
AU2012228693A1 (en) Method and system for synchronization mechanism on multi-server reservation system
WO2004017165A2 (en) System and method for inter enterprise conversation
CN112860342B (en) Method, device, equipment, system and storage medium for micro-service configuration
Busi et al. Towards a formal framework for choreography
GB2407658A (en) Computer network for processing received event data
CN110942372B (en) Butt joint method and gateway of business end and ERP system
CN112418784A (en) Service arranging and executing system and method
Abiteboul et al. The AXML artifact model
CN111460038A (en) Quasi-real-time data synchronization method and device
US7684349B2 (en) Method and system for transparently controlling the behavior of service methods in a service oriented architecture
US8863132B2 (en) Using abstraction layers to facilitate communication between systems
US20030177279A1 (en) Creation of middleware adapters from paradigms
CN102103717A (en) Defining additional resources in a MES user management system

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
GR01 Patent grant
GR01 Patent grant