WO2019109957A1 - Procédé, appareil, et dispositif de fourniture de service basé sur un bus de service d'entreprise (esb), et support d'informations lisible - Google Patents

Procédé, appareil, et dispositif de fourniture de service basé sur un bus de service d'entreprise (esb), et support d'informations lisible Download PDF

Info

Publication number
WO2019109957A1
WO2019109957A1 PCT/CN2018/119392 CN2018119392W WO2019109957A1 WO 2019109957 A1 WO2019109957 A1 WO 2019109957A1 CN 2018119392 W CN2018119392 W CN 2018119392W WO 2019109957 A1 WO2019109957 A1 WO 2019109957A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
target
target service
service provider
consumption request
Prior art date
Application number
PCT/CN2018/119392
Other languages
English (en)
Chinese (zh)
Inventor
李天平
Original Assignee
深圳壹账通智能科技有限公司
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 深圳壹账通智能科技有限公司 filed Critical 深圳壹账通智能科技有限公司
Publication of WO2019109957A1 publication Critical patent/WO2019109957A1/fr

Links

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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/101—Collaborative creation, e.g. joint development of products or services
    • 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
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration

Definitions

  • the present application relates to the field of operation and maintenance technologies, and in particular, to an ESB-based service providing method, apparatus, device, and readable storage medium.
  • the main purpose of the present application is to provide an ESB-based service providing method, apparatus, device, and readable storage medium, which are intended to implement service integration and improve service capabilities of a business system.
  • the present application provides an ESB-based service providing method, where the service providing method includes the following steps:
  • the service provider Upon receiving the access request sent by the service provider, the service provider accesses the enterprise service bus ESB, and saves the service information corresponding to the service provider to a database that is connected to the ESB, where Service information includes service paths and service items;
  • the present application further provides an ESB-based service providing apparatus, where the service providing apparatus includes:
  • a service access module configured to: when receiving an access request sent by the service provider, access the service provider to the enterprise service bus ESB, and save the service information corresponding to the service provider to the ESB a docked database, wherein the service information includes a service path and a service item;
  • a request receiving module configured to determine, according to the consumption request, a corresponding target service item when receiving the consumption request sent by the service consumer, and query the target service information corresponding to the target service item in the database;
  • a service providing module configured to acquire a target service path of the corresponding target service provider according to the target service information, and send the consumption request to the target service provider according to the target service path, so that the target service is The provider provides services in accordance with the consumption request.
  • the present application further provides an ESB-based service providing device, including a processor, a memory, and a computer readable and executable by the processor and executable by the processor An instruction, wherein the computer readable instructions are executed by the processor, implements the steps of the service providing method described above.
  • the present application further provides a readable storage medium having computer readable instructions stored thereon, wherein the computer readable instructions are executed by a processor to implement a service as described above Provide steps for the method.
  • this application integrates a previously isolated business system (service provider) in a loosely coupled manner to build a unified service delivery system.
  • service provider business system
  • Discovery and communication improve the calling efficiency and service provisioning capability of each business system.
  • various protocols and tool libraries can be integrated in a standardized manner through the ESB, so that each business system can concentrate.
  • the large-scale business is decomposed into micro-services to improve the development efficiency and comprehensive service capabilities of the business system.
  • FIG. 1 is a schematic structural diagram of an ESB-based service providing device involved in an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a first embodiment of an ESB-based service providing method according to the present application
  • FIG. 3 is a service topology diagram of a first embodiment of an ESB-based service providing method according to the present application
  • FIG. 4 is the same as FIG. 2, when receiving an access request sent by a service provider, accessing the service provider to an enterprise service bus ESB, and saving service information corresponding to the service provider to the ESB a docked database, wherein the service information includes a detailed process flow diagram of service paths and service items;
  • FIG. 5 is a schematic diagram of the target service item determined according to the consumption request when the consumption request sent by the service consumer is received, and the target service information corresponding to the target service item is queried in the database. Schematic diagram of the process;
  • FIG. 6 is a schematic diagram of the target service item determined according to the consumption request when the consumption request sent by the service consumer is received, and the target service information corresponding to the target service item is queried in the database. Schematic diagram of the process;
  • FIG. 7 is a schematic flowchart diagram of a second embodiment of an ESB-based service providing method according to the present application
  • FIG. 8 is a schematic diagram of functional modules of a first embodiment of an ESB-based service providing apparatus according to the present application.
  • the ESB-based service providing method embodiment of the present application is implemented by an ESB-based service providing device, and the physical implementation of the server providing device may be a PC, or may be a mobile phone, a tablet computer, a portable computer, or the like having a display function. Terminal equipment.
  • FIG. 1 is a schematic structural diagram of an ESB-based service providing device involved in an embodiment of the present application.
  • the service providing device may include a processor 1001 (for example, a CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005.
  • the communication bus 1002 is configured to implement connection communication between the components;
  • the user interface 1003 may include a display, an input unit such as a keyboard;
  • the network interface 1004 may optionally include a standard wired interface and a wireless interface. (such as WI-FI interface);
  • memory 1005 can be high-speed RAM memory or stable memory (non-volatile Alternatively, the memory 1005 may alternatively be a storage device independent of the processor 1001 described above.
  • FIG. 1 does not constitute a limitation to the present application, and may include more or less components than those illustrated, or some components may be combined, or different component arrangements.
  • memory 1005 which is a computer readable storage medium, can include an operating system, a network communication module, and computer readable instructions.
  • the network communication module is mainly used to connect to a database and perform data communication with the database; and the processor 1001 can call the computer readable instructions stored in the memory 1005 and execute the ESB-based service providing method provided by the embodiment of the present application. .
  • the application provides an ESB-based service providing method.
  • FIG. 2 is a schematic flowchart diagram of a first embodiment of an ESB-based service providing method according to the present application.
  • the service providing method includes the following steps:
  • Step S10 When receiving the access request sent by the service provider, the service provider accesses the enterprise service bus ESB, and saves the service information corresponding to the service provider to the database that is connected to the ESB.
  • the service information includes a service path and a service item;
  • This embodiment proposes to integrate multiple isolated service subsystems (Services) in a loosely coupled manner based on the ESB (framework) to construct a unified service providing system.
  • Coupling can be understood as a measure of the degree of association between modules (or different systems), or as a dependency between modules, including control relationships, call relationships, and data transfer relationships. The more connections between modules, the more coupled they are. Strong (tight), at the same time, indicating that the independence is worse, for example, the stronger the coupling between A and B, the greater the impact of B when there is an abnormality in A; there are a large number of interface services directly called between various business systems.
  • This call relationship is logically presented as a complex mesh network connection; the interface service mesh network connection causes management and maintenance problems (ie, the above-mentioned strong coupling); and loose coupling means that the mutual dependence is small. Or they rely on a third party (instead of directly contacting each other), which in this embodiment is an ESB.
  • the ESB is the service backbone of the entire system, connecting various distributed business (heterogeneous) systems, passing data messages between the various systems, and past peer-to-peer
  • the interface relationship becomes a point-to-bus relationship.
  • service registration needs to be performed to the management system of the ESB; and for the management system, for the convenience of management thereof
  • the service provider will be required to provide relevant service information at the time of registration, including the host name, port number, service items, and other additional parameters of the service provider. Therefore, the service provider sends an access request to the management system, and the access request includes related service information.
  • the management system registers the service provider according to the service information in the access request.
  • the management system will access the service provider to the ESB, and save the service information corresponding to the service provider to the database connected to the ESB for query and service by other parties in the ESB or the external system. transfer.
  • the management system further provides a visual management interface, which is convenient for the management personnel to view and manage the accessed service provider.
  • the service provider that has accessed the ESB can be displayed in the form of a service topology diagram, as shown in FIG. 3; wherein the nodes of the topology (points A, B, and C in FIG. 3) represent the service provider.
  • the visual management interface can also display related service parameters (such as service online time, total online duration, port number, etc.).
  • Step S20 when receiving the consumption request sent by the service consumer, determining a corresponding target service item according to the consumption request, and querying, in the database, the target service information corresponding to the target service item;
  • the service provider accesses the ESB
  • the service can be provided based on the ESB.
  • the service consumer can directly send a consumption request to the ESB management system to apply for calling a service in the ESB (which can be called a target service).
  • the management system Upon receiving the consumption request, the management system will read the content in the consumption request and determine the target service item corresponding to the consumption request (ie, determine which service in the ESB needs to be invoked by the service consumer).
  • the query can be performed in the database to match the corresponding target service information.
  • Step S30 Acquire a target service path corresponding to the target service provider according to the target service information, and send the consumption request to the target service provider according to the target service path, so that the target service provider is based on the target service provider.
  • the consumption request provides a service.
  • the management system may acquire the target service path of the target service provider according to the target service information, and then send the consumption request to the target service provider according to the target service path.
  • the target service provider can process the consumption request to provide services to the service consumer.
  • the service consumer in this embodiment, it may be an external system or a service provider that has been accessed in the ESB.
  • the service provider in the ESB in some business processes, is Other services in the ESB can be invoked as a service consumer, so that each service in the ESB can discover each other and communicate with each other, thereby improving the service capability between the components.
  • the service provider it may be provided by a distributed hardware architecture; in this case, when the management system records the service information of the service provider, the service path may include Multiple. In order to achieve a balanced load, a plurality of corresponding message queues may be set for the distributed service provider, and when a new consumption request is received, the new consumption request is allocated according to the number of pending messages of each message queue. To balance the business pressure of different service devices. For example, for the service provider X, it has three service devices, namely, device A, device B, and device C. For this, the management system separately sets three message queues, which are queue a, queue b, and queue.
  • queue a corresponds to device A
  • queue b corresponds to device B
  • queue c corresponds to device C
  • the management system when the management system receives the consumption request of the target service provider for X, it queries the service information of the target service provider X, according to The service information indicates that the service provider X has three service devices and three corresponding message queues. In this case, the number of pending messages in the three message queues can be queried. After the query, it is known that there are 4 pending messages in the queue a. There are two pending messages in queue b, and there are three pending messages in queue c.
  • the management system can insert the consumption request into queue b to implement load balancing.
  • the manner in which the consumption request is allocated may also be defined by the administrator.
  • the examples in this embodiment do not constitute a limitation on the technical solution of the present application.
  • the service provider can set up a message queue for the service provider.
  • the management system needs to send a consumption request to the service provider that needs to return the service result, it only needs to insert the consumption request into the message queue, and can return to process other matters without waiting for the service provider's service result.
  • the management system calls back a method to obtain the service result, thereby implementing asynchronous processing, improving the business processing capability and processing efficiency of the management system.
  • the service provider when receiving the access request sent by the service provider, the service provider is connected to the enterprise service bus ESB, and the service information corresponding to the service provider is saved to be connected to the ESB.
  • the service information includes a service path and a service item; when receiving a consumption request sent by the service consumer, determining a corresponding target service item according to the consumption request, and querying the target service in the ESB Target service information corresponding to the item; acquiring a target service path corresponding to the target service provider according to the target service information, and transmitting the consumption request to the target service provider according to the target service path, so that the target The service provider provides services in accordance with the consumption request.
  • the present embodiment integrates a previously isolated service system (service provider) in a loosely coupled manner to construct a unified service providing system, and each service system ( Components) and the ability to discover and communicate with each other, improve the calling efficiency and service provisioning capability of each business system; and because each business system communicates and calls through the ESB, various protocols and tool libraries can be integrated in a standardized manner through the ESB.
  • service provider Service provider
  • Each business system can focus on the development and management of business logic, decompose large-scale business into micro-services, and improve the development efficiency and comprehensive service capabilities of business systems.
  • FIG. 4 is the same as FIG. 2, when receiving an access request sent by a service provider, accessing the service provider to an enterprise service bus ESB, and saving service information corresponding to the service provider to A database that interfaces with the ESB, wherein the service information includes a refinement flow diagram of service paths and service items.
  • step S10 includes:
  • Step S11 when receiving the access request sent by the service provider, verifying the service qualification of the service provider according to the access request;
  • Step S12 When the service qualification passes the verification, the service provider is accessed by the service provider, and the service information corresponding to the service provider is saved to a database that is connected to the ESB, where the service information is Includes service paths and service items.
  • the service provider can provide services for the service consumer after accessing the ESB.
  • the service provider In order to ensure the reliability and security of the service provided by the service provider, the service provider must first service the service before accessing the ESB. The provider's service qualification is verified to determine that it is trustworthy. Specifically, before the service provider accesses the ESB, the service provider sends an access request to the management system, where the access request includes the host name, port number, and service item of the service provider.
  • the management system When receiving the access request, the management system first queries according to the host name and port number to determine whether the identity of the service provider is real; if the host name and service provider are queried according to the port number If the information provided is consistent, the management system will send test information (or test message, test request) to the service provider according to the service item, and then receive the test result returned by the service provider, and judge the service according to the test information and the test result. Whether the service provided by the provider is consistent with the service item in the access request; if it is consistent, the service information provided by the service provider is considered to be authentic, and the reliability and security of the service provider are obtained at this time. It was confirmed that the service provider's service qualification was verified.
  • the verification of the service qualification may also include other aspects of the verification and verification, such as the communication protocol, the data transmission format, and the like.
  • the management system When the service provider's service qualification is verified, the management system will register the service provider according to the service information in the access request. When the registration is completed, the management system will access the service provider to the ESB, and save the service information corresponding to the service provider to the ESB database for query and service call by other parties in the ESB or the external system.
  • FIG. 5 is a method for determining, according to the consumption request, a corresponding target service item according to the consumption request when receiving a consumption request sent by a service consumer, and querying a target corresponding to the target service item in the database.
  • Schematic diagram of the detailed process of service information is a method for determining, according to the consumption request, a corresponding target service item according to the consumption request when receiving a consumption request sent by a service consumer, and querying a target corresponding to the target service item in the database.
  • step S20 includes:
  • Step S21 when receiving the consumption request sent by the service consumer, verifying the consumption qualification of the service consumer according to the consumption request;
  • step S22 when the consumption qualification passes the verification, the corresponding target service item is determined according to the consumption request, and the target service information corresponding to the target service item is queried in the database.
  • multiple service providers are accessed in the ESB to provide services to the service consumer.
  • data interaction is inevitably involved, and the interaction data may involve private data (or secret data).
  • the service provider's service qualification should be verified first to determine that it is trustworthy and avoid An illegal third party attacks the system or steals data in the ESB.
  • the consumption request includes information such as its own consumption host name, consumption port number, and request service item.
  • the management system When receiving the consumption request, the management system queries according to the host name and port number to determine whether the identity of the service consumer is real; if the identity of the service consumer actually exists, the service is considered The service information provided by the consumer is authentic, and the identity of the service consumer is confirmed at this time, and the consumption qualification of the service consumer has been verified. It should be noted that, in this embodiment, only the identity (address) of the service consumer is confirmed. If the service consumer is detected to have attacked the system or data is stolen, it may be taken according to the identity and address of the service consumer. Corresponding measures (such as IP forbidden access, port forbidden access, etc.); of course, in the specific implementation, the verification and verification of other aspects may be included in the verification process of consumption qualification.
  • the management system determines the target service implementation corresponding to the consumption request according to the requested service item in the consumption request (ie, determines which service in the ESB needs to be invoked by the service consumer).
  • the query may be performed in the database to match the corresponding target service information, and the target service path of the corresponding target service provider is obtained according to the target service information, so as to pass the target The service path sends the consumption request to the corresponding target service provider.
  • FIG. 6 is a schematic diagram of the target service item determined according to the consumption request when the consumption request sent by the service consumer is received, and the target corresponding to the target service item is queried in the database. Schematic diagram of the detailed process of service information.
  • step S20 further includes:
  • Step S23 when receiving the consumption request sent by the service consumer, parsing the message header of the consumption request, and determining a target service item corresponding to the consumption request;
  • Step S24 Query the corresponding target service information in the database according to the target service item.
  • the consumption request sent by the service consumer includes the target service information
  • the management system needs to parse the consumption request first, and the content in the consumption request is read (the target service information) And determining the target service item corresponding to the consumption request according to the content.
  • the message format of the consumption request may be limited, and the service consumer is required to place the target service information in the message header of the consumption request; in this case, management
  • the system can directly access the message header and parse it, so that the entire consumption request is not processed, and the efficiency of the analysis is improved.
  • the target service item corresponding to the message request may be determined according to the target service information therein, and the corresponding target service information is queried in the ESB according to the target service item.
  • the service consumer may be an external visitor (outside system) or a service provider in the ESB, and may have different system architectures and communication protocols for different service consumers, in order to ensure that the service consumers send
  • the consumption request can be transmitted quickly and accurately in the ESB system.
  • the consumption request can be pre-processed, the consumption request is serialized, and then parsed and forwarded; wherein, the serialization processing is performed. Is the process of converting an object into a sequence of bytes.
  • the ESB system of this embodiment may set the XML (Extensible Markup Language) format as the default transport format of the consuming request; upon receiving the consuming request sent by the service consuming party, the entity object of the consuming request is first serialized into The XML format, in which the message header (packet header) of the serialized consumption request includes target service information, of course, the message header may also include other information, such as the consumer's consumption host, port number, and the like. Taking a Java class consumption request as an example, serialization of Java class consumption requests can be done through JDK (Java).
  • JDK Java
  • the attribute information of the object is written into the serialization stream in the order of the basic data type to the java object type, and the java object type
  • the property will begin to recursively output until the properties of the java object type no longer exist; then the object can be converted to a streamed xml and output via the conversion class that comes with the JDK.
  • the message header is parsed, the target service item corresponding to the message request is determined according to the target service information therein, and the corresponding target service information is queried in the database according to the target service item.
  • the target service information therein can be represented by a specific string instead of a complete service description message.
  • the service item in the service information may be encoded, for example, the corresponding code of the service item A is a, and the corresponding code of the service item B is b; the service consumer is in need
  • the target service information in the consumption request can be represented by the code a, and it is not necessary to completely add the specific service description of the service item A, thereby reducing the data amount of the consumption request, and also facilitating the serialization and parsing of the management system. , improve request processing efficiency and response speed.
  • FIG. 7 is a schematic flowchart diagram of a second embodiment of an ESB-based service providing method according to the present application.
  • the method further includes:
  • Step S40 If the service result information returned by the target service provider is received within a preset time, the service result information is returned to the service consumer;
  • Step S50 If the service result information returned by the target service provider is not received within a preset time, the target service provider is marked as an abnormal state, and the alarm is performed in a preset manner.
  • the consumption path may be added to the consumption request.
  • the timing will start; if the service result information returned by the target service provider is received within the preset time, the management system will use the service result information according to the consumption path in the consumption request. Return to the corresponding service consumer for the service consumer to perform subsequent processing according to the service result information. If the management system does not receive the service result information returned by the target service provider within the preset time, the processing of the target service provider is considered abnormal, and the management system marks the target service party as an abnormal state, and The alarm is triggered in a preset manner.
  • the manner of the alarm can be set according to the specific situation. For example, different service items can be set to two levels: high and normal; when the service provider of the general level service item is abnormal, the corresponding visual management interface of the management system is corresponding. When the service provider of the high-level service item is abnormal, the corresponding topology node of the visual management interface will flash in the blinking manner, and the corresponding voice alarm information will be sent. Remind the manager.
  • the alarm can be set in other different ways.
  • the management system disables the service according to the target service path of the target service provider, and does not process the information sent by the target service provider in reverse, thereby avoiding abnormal target service provision.
  • the party interferes with other service providers in the ESB.
  • the information of the service provided by the abnormal target service provider may be suspended in the database, and the other consumer requester may continue to request the abnormal target service provider to provide the service, and then restart the service when the abnormal target service party returns to normal.
  • the present application also provides an ESB-based service providing apparatus.
  • FIG. 8 is a schematic diagram of functional modules of a first embodiment of an ESB-based service providing apparatus according to the present application.
  • the service providing apparatus includes:
  • the service access module 10 is configured to: when receiving the access request sent by the service provider, access the service provider to the enterprise service bus ESB, and save the service information corresponding to the service provider to the An ESB docked database, wherein the service information includes a service path and a service item;
  • the request receiving module 20 is configured to: when receiving the consumption request sent by the service consumer, determine a corresponding target service item according to the consumption request, and query the database for the target service information corresponding to the target service item;
  • the service providing module 30 is configured to acquire a target service path of the corresponding target service provider according to the target service information, and send the consumption request to the target service provider according to the target service path, so that the target The service provider provides services in accordance with the consumption request.
  • the virtual function modules of the ESB-based service providing apparatus are stored in the memory 1005 of the ESB-based service providing apparatus shown in FIG. 1 for implementing all functions of the computer readable instructions; when each module is executed by the processor 1001 It can realize the function of mutual discovery and communication between various business systems (components).
  • the service access module 10 includes:
  • a first verification unit configured to: when receiving the access request sent by the service provider, verify the service qualification of the service provider according to the access request;
  • a service access unit configured to: when the service qualification passes the verification, access the service provider to the ESB, and save the service information corresponding to the service provider to a database that is connected to the ESB, where
  • the service information includes a service path and a service item.
  • the request receiving module 20 includes:
  • a second verification unit configured to: when receiving the consumption request sent by the service consumer, verify the consumption qualification of the service consumer according to the consumption request;
  • the first query unit is configured to determine, according to the consumption request, a corresponding target service item when the consumption qualification passes the verification, and query the target service information corresponding to the target service item in the database.
  • the request receiving module 20 includes:
  • a message parsing unit configured to parse a message header of the consumption request, and determine a target service item corresponding to the consumption request, when receiving a consumption request sent by a service consumer;
  • a second querying unit configured to query, in the database, corresponding target service information according to the target service item.
  • the message parsing unit is further configured to, when receiving the consumption request sent by the service consumer, recursively output the class description information in the consumption request and the actual data value of the object domain according to a preset rule, and The class description information and the object domain actual data value are written into the serialization stream; the preset conversion class tool is invoked to convert the serialization stream to obtain a serialization request; and the message header of the serialized consumption request is parsed to determine The target service item corresponding to the consumption request.
  • the service providing apparatus further includes:
  • An information returning module configured to return the service result information to the service consumer if the service result information returned by the target service provider is received within a preset time
  • the abnormality alarm module is configured to: if the service result information returned by the target service provider is not received within a preset time, mark the target service provider as an abnormal state, and perform an alarm in a preset manner.
  • the service providing apparatus further includes:
  • a service suspension module configured to disable service of the target service provider according to the target service path, and issue target service suspension information in the database.
  • the present application also provides a readable storage medium, which may be a non-volatile readable storage medium.
  • the computer readable instructions are stored on the readable storage medium of the present application, wherein when the computer readable instructions are executed by the processor, the steps of the ESB based service providing method as described above are implemented.
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM as described above). , a disk, an optical disk, including a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in the various embodiments of the present application.
  • a terminal device which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Tourism & Hospitality (AREA)
  • Theoretical Computer Science (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Signal Processing (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Physics & Mathematics (AREA)
  • Finance (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Multimedia (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un procédé, un appareil et un dispositif de fourniture de service basé sur un bus de service d'entreprise (ESB), et un mécanisme de mémoire lisible, se rapportant au domaine technique de l'exploitation et de la maintenance. Le procédé consiste : lorsqu'une requête d'accès envoyée par un fournisseur de services est reçue, à connecter le fournisseur de services à un bus de service d'entreprise (ESB), et à mémoriser des informations de service correspondantes dans une base de données de l'ESB (S10) ; lorsqu'une requête de consommation envoyée par un consommateur de service est reçue, à déterminer un élément de service cible correspondant, et à interroger des informations de service cible correspondantes dans la base de données (S20) ; et à acquérir un trajet de service cible selon les informations de service cible, et à envoyer la requête de consommation à un fournisseur de service cible pour fournir un service (S30). Selon le procédé, un système de fourniture de service uniforme est construit sur la base d'une structure ESB, de telle sorte que divers systèmes de service peuvent se trouver et communiquer mutuellement, ce qui permet d'améliorer l'efficacité d'appel et la capacité de fourniture de service de divers systèmes de service.
PCT/CN2018/119392 2017-12-08 2018-12-05 Procédé, appareil, et dispositif de fourniture de service basé sur un bus de service d'entreprise (esb), et support d'informations lisible WO2019109957A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711292797.7 2017-12-08
CN201711292797.7A CN108074076A (zh) 2017-12-08 2017-12-08 基于esb的服务提供方法、装置、设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2019109957A1 true WO2019109957A1 (fr) 2019-06-13

Family

ID=62158110

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/119392 WO2019109957A1 (fr) 2017-12-08 2018-12-05 Procédé, appareil, et dispositif de fourniture de service basé sur un bus de service d'entreprise (esb), et support d'informations lisible

Country Status (2)

Country Link
CN (1) CN108074076A (fr)
WO (1) WO2019109957A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108074076A (zh) * 2017-12-08 2018-05-25 上海壹账通金融科技有限公司 基于esb的服务提供方法、装置、设备及可读存储介质
CN109062848B (zh) * 2018-08-01 2021-01-26 武汉索雅信息技术有限公司 基于esb总线平台的采购管理方法、装置及总线平台
CN109120684B (zh) * 2018-08-01 2021-10-01 武汉索雅信息技术有限公司 信息化管理方法、装置、esb总线平台以及存储介质
CN109150858A (zh) * 2018-08-01 2019-01-04 武汉索雅信息技术有限公司 数据交互总线的请求处理方法、设备、系统及存储介质
CN109298950A (zh) * 2018-08-15 2019-02-01 深圳壹账通智能科技有限公司 企业服务总线系统、数据处理方法、终端及存储介质
CN109525550B (zh) * 2018-09-30 2021-05-04 创新先进技术有限公司 一种数据报文的处理方法、装置以及系统
CN110287267A (zh) * 2019-06-28 2019-09-27 深圳前海微众银行股份有限公司 一种跨节点的数据处理方法及装置
CN111865746B (zh) * 2020-06-19 2022-08-19 苏宁云计算有限公司 基于环路总线的系统开发方法及装置
CN112732534B (zh) * 2021-03-30 2021-07-23 北京宇信科技集团股份有限公司 一种支持分布式微服务的esb系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102158548A (zh) * 2011-03-02 2011-08-17 山东中创软件工程股份有限公司 一种企业服务总线接入外部服务的方法
CN102364921A (zh) * 2011-11-21 2012-02-29 携程计算机技术（上海）有限公司 企业服务总线的实现方法、设备及相应的平台
CN102387075A (zh) * 2011-10-18 2012-03-21 成都康赛电子科大信息技术有限责任公司 面向企业服务总线的动态服务路由方法及装置
CN106331167A (zh) * 2016-10-13 2017-01-11 安徽鼎集信息科技有限公司 一种企业服务总线系统
CN108074076A (zh) * 2017-12-08 2018-05-25 上海壹账通金融科技有限公司 基于esb的服务提供方法、装置、设备及可读存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101674255B (zh) * 2008-09-12 2012-01-11 北京东方通科技股份有限公司 一种企业服务总线的消息转发方法、服务器及其系统
CN101610288B (zh) * 2009-06-16 2012-08-22 浙江大学 一种企业服务总线智能路由方法
CN101827115B (zh) * 2009-12-31 2012-11-21 厦门市美亚柏科信息股份有限公司 一种全息式企业服务总线
CN105812241A (zh) * 2016-03-24 2016-07-27 江苏物联网研究发展中心 基于Spring Integration的企业应用集成方法和系统
CN106713464B (zh) * 2016-12-27 2019-12-13 山东中创软件商用中间件股份有限公司 一种企业服务总线的服务管理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102158548A (zh) * 2011-03-02 2011-08-17 山东中创软件工程股份有限公司 一种企业服务总线接入外部服务的方法
CN102387075A (zh) * 2011-10-18 2012-03-21 成都康赛电子科大信息技术有限责任公司 面向企业服务总线的动态服务路由方法及装置
CN102364921A (zh) * 2011-11-21 2012-02-29 携程计算机技术（上海）有限公司 企业服务总线的实现方法、设备及相应的平台
CN106331167A (zh) * 2016-10-13 2017-01-11 安徽鼎集信息科技有限公司 一种企业服务总线系统
CN108074076A (zh) * 2017-12-08 2018-05-25 上海壹账通金融科技有限公司 基于esb的服务提供方法、装置、设备及可读存储介质

Also Published As

Publication number Publication date
CN108074076A (zh) 2018-05-25

Similar Documents

Publication Publication Date Title
WO2019109957A1 (fr) Procédé, appareil, et dispositif de fourniture de service basé sur un bus de service d'entreprise (esb), et support d'informations lisible
WO2020224250A1 (fr) Procédé, appareil et dispositif pour déclenchement de contrat intelligent, et support de stockage
WO2023038381A1 (fr) Système de collecte de données api et procédé associé
WO2014094300A1 (fr) Serveur et procédé de commande à distance du travail d'un terminal de communication et terminal de communication
WO2014112754A1 (fr) Procédé de pousser de service web, serveur de pousser de service web et serveur de fourniture de service web l'exécutant
WO2012169775A9 (fr) Système et procédé pour fournir une interface de service de contenu basée sur une api ouverte
WO2020253120A1 (fr) Procédé, système et dispositif d'enregistrement de page web, et support de stockage informatique
WO2012157940A2 (fr) Système et procédé permettant de mettre en œuvre un service de pousser au moyen d'un message de rétroaction
WO2013063897A1 (fr) Procédé et dispositif de remplissage d'identité fixe d'abonné
WO2020233073A1 (fr) Procédé, dispositif et appareil de traitement de test d'environnement de chaîne de blocs, et support de stockage
WO2020042471A1 (fr) Procédé, système, et dispositif de vérification de politique de pare-feu, et support de stockage lisible par machine
WO2021072881A1 (fr) Procédé, appareil et dispositif de traitement de demande fondée sur un stockage d'objet, et support de stockage
WO2018035929A1 (fr) Procédé et appareil de traitement de code de vérification
WO2016013718A1 (fr) Système et procédé permettant de fournir une publicité en ligne au moyen d'un réseau wi-fi
WO2017173838A1 (fr) Procédé d'affichage de message basé sur la vérification, et terminal de communication
WO2014035194A1 (fr) Système et procédé de service de messages push
WO2020224251A1 (fr) Procédé de traitement de transactions de chaîne de blocs, dispositif, appareil et support de stockage
CN111385147A (zh) 故障模拟方法、装置和计算机可读存储介质
WO2017028685A1 (fr) Procédé de messagerie instantanée, serveur, et support de stockage
WO2013123854A1 (fr) Procédé, dispositif à mise en œuvre informatique et support de stockage informatique pour l'interaction de client d'application de réseau
WO2020019405A1 (fr) Procédé, dispositif, appareil de surveillance de base de données et support d'informations informatique
WO2021078062A1 (fr) Procédé de vérification de certificat ssl, appareil et dispositif, et support de stockage informatique
WO2013176431A1 (fr) Système et procédé pour allouer un serveur à un serveur et pour une messagerie efficace
CN114338682A (zh) 流量身份标识传递方法、装置、电子设备及存储介质
WO2014021675A1 (fr) Procédé et appareil permettant une mise à jour d'informations personnelles dans un système de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18886965

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 13/10/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18886965

Country of ref document: EP

Kind code of ref document: A1