US20160352843A1 - Data Processing Method, Device, and ESB System - Google Patents

Data Processing Method, Device, and ESB System Download PDF

Info

Publication number
US20160352843A1
US20160352843A1 US15/233,017 US201615233017A US2016352843A1 US 20160352843 A1 US20160352843 A1 US 20160352843A1 US 201615233017 A US201615233017 A US 201615233017A US 2016352843 A1 US2016352843 A1 US 2016352843A1
Authority
US
United States
Prior art keywords
service
instance
deployment node
service instance
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.)
Abandoned
Application number
US15/233,017
Other languages
English (en)
Inventor
Zhifeng Zong
Puchao ZHANG
Haijun HUANG
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Assigned to HUAWEI TECHNOLOGIES CO., LTD. reassignment HUAWEI TECHNOLOGIES CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HUANG, Haijun, ZHANG, Puchao, ZONG, Zhifeng
Publication of US20160352843A1 publication Critical patent/US20160352843A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H04L67/16—
    • 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/547—Remote procedure calls [RPC]; Web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5045—Making service definitions prior to deployment
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/567—Integrating service provisioning from a plurality of service providers

Definitions

  • the present embodiments of the disclosure relate to the field of computers, and in particular, to a data processing method, a device, and an enterprise service bus (ESB) system.
  • ESD enterprise service bus
  • a service-oriented architecture can link different functional units of an application program by defining a good interface and contract between services.
  • a key to supporting the SOA is an ESB for message transfer of the SOA.
  • An ESB system is a product of a combination of technologies such as a conventional middleware technology, an Extensible Markup Language (XML), and a Web service.
  • the ESB delivers, to a consumer, a service of an application provided by a provider. In this process, the ESB can eliminate a technical difference between different applications, and allow different application servers to operate in a coordinated manner such that communication and integration between services are implemented.
  • the ESB system includes a console, a deployment node, and a service registry.
  • a service identifier of a service and an address of a deployment node for deploying a service instance are stored in the service registry.
  • a deployment node for deploying the first service instance can invoke the second service instance only by first querying the service registry to obtain an address of the second service instance. If a problem occurs at the service registry, the service registry cannot provide the service identifier and the address of the deployment node, resulting in that a problem also occurs in invocation between the service instances.
  • Embodiments of the present disclosure provide a data processing method, a device, and an ESB system such that information is transferred in an ESB system more flexibly.
  • a first deployment node including a receiving unit configured to receive service information, sent by a console, of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, a generation unit configured to generate a first service instance according to the definition of the first service, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, and a sending unit configured to send first address information to service instances in an enterprise service bus ESB system except the first service instance using the first service instance, where the first address information includes the service identifier of the first service and an address of the first deployment node such that a second deployment node invokes the first service instance according to the first address information using a second service instance, where the second service instance is a service instance, deployed on the second deployment node, in service instances of a second service, and the second deployment node is any deployment node in the ESB system.
  • the first deployment node further includes a running unit, where the receiving unit is further configured to receive an invocation request that is sent by the second deployment node using the second service instance, where the invocation request is generated according to an invocation instruction sent by a consumer server, the invocation instruction is used to instruct the second service instance to invoke the first service instance, and includes the service identifier of the first service, a service identifier of the second service, and preset information, the preset information is sent by the consumer server, the invocation request includes the preset information, and the consumer server is a server that is using the second service instance, the running unit is configured to run the first service instance according to the preset information, to obtain a successful invocation response, and the sending unit is further configured to send the successful invocation response to the second deployment node using the first service instance such that the second deployment node receives the successful invocation response using the second service instance.
  • the receiving unit is further configured to receive an invocation request that is sent by the second deployment node using the second service instance, where the invocation request is generated according to
  • the first deployment node further includes a deletion unit, where the receiving unit is further configured to receive an instance deletion instruction sent by the console, where the instance deletion instruction instructs the first deployment node to delete the first service instance, the deletion unit is configured to delete the first service instance according to the instance deletion instruction, and the sending unit is further configured to send an address deletion instruction to the service instances in the ESB system, where the address deletion instruction is used to instruct the service instances in the ESB system to delete the first address information such that all deployment nodes in the ESB system delete the first address information according to the address deletion instruction.
  • a console including a generation unit configured to generate service information of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, and a sending unit configured to send the service information to a first deployment node such that after generating a first service instance according to the definition of the first service, the first deployment node sends first address information to service instances in an ESB system except the first service instance using the first service instance, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, and the first address information includes the service identifier of the first service and an address of the first deployment node.
  • the console further includes a determining unit configured to determine a deployment node of a to-be-deleted service, where the generation unit is further configured to generate a instance deletion instruction, where the instance deletion instruction is used to instruct the deployment node of the to-be-deleted service to delete a service instance of the first service, and the sending unit is further configured to if the deployment node of the to-be-deleted service includes the first deployment node, send the instance deletion instruction to the first deployment node such that the first deployment node deletes the first service instance according to the instance deletion instruction.
  • a data processing method is provided, where the method is applied to a first deployment node and includes receiving service information, sent by a console, of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, generating a first service instance according to the definition of the first service, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, and sending first address information to service instances in an enterprise service bus ESB system except the first service instance using the first service instance, where the first address information includes the service identifier of the first service and an address of the first deployment node such that a second deployment node invokes the first service instance according to the first address information using a second service instance, where the second service instance is a service instance, deployed on the second deployment node, in service instances of a second service, and the second deployment node is any deployment node in the ESB system.
  • the method further includes receiving an invocation request that is sent by the second deployment node using the second service instance, where the invocation request is generated according to an invocation instruction sent by a consumer server, the invocation instruction is used to instruct the second service instance to invoke the first service instance, and includes the service identifier of the first service, a service identifier of the second service, and preset information, the preset information is sent by the consumer server, the invocation request includes the preset information, and the consumer server is a server that is using the second service instance, running the first service instance according to the preset information, to obtain a successful invocation response, and sending the successful invocation response to the second deployment node using the first service instance such that the second deployment node receives the successful invocation response using the second service instance.
  • the method further includes receiving an instance deletion instruction sent by the console, where the instance deletion instruction instructs the first deployment node to delete the first service instance, deleting the first service instance according to the instance deletion instruction, and sending an address deletion instruction to the service instances in the ESB system, where the address deletion instruction is used to instruct the service instances in the ESB system to delete the first address information such that all deployment nodes in the ESB system delete the first address information according to the address deletion instruction.
  • a data processing method is provided, where the method is applied to a console and includes generating service information of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, and sending the service information to a first deployment node such that after generating a first service instance according to the definition of the first service, the first deployment node sends first address information to service instances in an ESB system except the first service instance using the first service instance, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, and the first address information includes the service identifier of the first service and an address of the first deployment node.
  • the data processing method further includes: when a preset deletion condition is met, determining a deployment node of a to-be-deleted service, generating a instance deletion instruction, where the instance deletion instruction is used to instruct the deployment node of the to-be-deleted service to delete a service instance of the first service, and if the deployment node of the to-be-deleted service includes the first deployment node, sending the instance deletion instruction to the first deployment node such that the first deployment node deletes the first service instance according to the instance deletion instruction.
  • an ESB system including any one of the foregoing first deployment nodes, and any one of the foregoing consoles.
  • the present embodiments of disclosure provide a data processing method, a device, and an ESB system, where the method includes receiving service information, sent by a console, of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, generating a first service instance according to the definition of the first service, where the first service instance is a service instance, deployed on a first deployment node, in service instances of the first service, and sending first address information to service instances in an ESB system except the first service instance using the first service instance, where the first address information includes the service identifier of the first service and an address of the first deployment node such that a second deployment node invokes the first service instance according to the first address information using a second service instance, where the second service instance is a service instance, deployed on the second deployment node, in service instances of a second service, and the second deployment node is any deployment node in the ESB system.
  • the first deployment node saves address information on each service instance instead of saving the address information in a service registry, and after the console sends the service information of the first service, the first deployment node generates the first service instance according to the definition of the first service, and notifies another deployment node that the first service instance is deployed on the first deployment node such that invocation may be directly performed between service instances of different services, therefore, information is transferred in the ESB system more flexibly.
  • FIG. 1 is a schematic structural diagram of a first deployment node according to an embodiment of the present disclosure.
  • FIG. 2 is a schematic structural diagram of another first deployment node according to an embodiment of the present disclosure.
  • FIG. 3 is a schematic structural diagram of a console according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic structural diagram of another console according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic structural diagram of still another first deployment node according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of still another console according to an embodiment of the present disclosure.
  • FIG. 7 is a flowchart of a data processing method according to an embodiment of the present disclosure.
  • FIG. 8 is a flowchart of another data processing method according to an embodiment of the present disclosure.
  • FIG. 9 is a flowchart of still another data processing method according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of an ESB system according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a first deployment node according to another embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a console according to another embodiment of the present disclosure.
  • the first deployment node 10 includes a receiving unit 101 configured to receive service information, sent by a console, of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, where a definition of the first service includes all files for installing the first service, such as an installation package and an upgrade package of the first service, a generation unit 102 configured to generate a first service instance according to the definition of the first service, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, and a sending unit 103 configured to send first address information to service instances in an ESB system except the first service instance using the first service instance, where the first address information includes the service identifier of the first service and an address of the first deployment node such that a second deployment node invokes the first service instance according to the first address information using a second service instance, where the second service instance
  • the first deployment node saves address information on each service instance instead of saving the address information in a service registry, and after the console sends the service information of the first service, the first deployment node generates the service instance according to the definition of the service, and notifies another service instance that the service instance of the first service is deployed on the first deployment node such that invocation may be directly performed between service instances of different services. Therefore, information is transferred in the ESB system more flexibly.
  • the first deployment node 10 further includes a running unit 104 .
  • the receiving unit 101 is further configured to receive an invocation request that is sent by the second deployment node using the second service instance, where the invocation request is generated according to an invocation instruction sent by a consumer server, the invocation instruction is used to instruct the second service instance to invoke the first service instance, and includes the service identifier of the first service, a service identifier of the second service, and preset information, the preset information is sent by the consumer server, the invocation request includes the preset information, and the consumer server is a server that is using the second service instance.
  • the running unit 104 is configured to run the first service instance according to the preset information, to obtain a successful invocation response.
  • the sending unit 103 is further configured to send the successful invocation response to the second deployment node using the first service instance such that the second deployment node receives the successful invocation response using the second service instance.
  • the first deployment node 10 further includes a deletion unit 105 .
  • the receiving unit 101 is further configured to receive an instance deletion instruction sent by the console, where the instance deletion instruction instructs the first deployment node to delete the first service instance.
  • the deletion unit 105 is configured to delete the first service instance according to the instance deletion instruction.
  • the sending unit 103 is further configured to send an address deletion instruction to the service instances in the ESB system, where the address deletion instruction is used to instruct the service instances in the ESB system to delete the first address information such that all deployment nodes in the ESB system delete the first address information according to the address deletion instruction.
  • the console 20 includes a generation unit 201 configured to generate service information of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, where a definition of the first service includes all files for installing the first service, such as an installation package and an upgrade package of the first service, and a sending unit 202 configured to send the service information to a first deployment node such that after generating a first service instance according to the definition of the first service, the first deployment node sends first address information to service instances in an ESB system except the first service instance using the first service instance, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, and the first address information includes the service identifier of the first service and an address of the first deployment node.
  • the service information includes a definition of the first service and a service identifier of the first service, where a definition of the first service includes all files for installing the first service, such as an installation package and an upgrade
  • the first deployment node saves address information on each service instance instead of saving the address information in a service registry, and after the console sends the service information of the first service, the first deployment node generates the service instance according to the definition of the service, and notifies another service instance that the service instance of the first service is deployed on the first deployment node such that invocation may be directly performed between service instances of different services, therefore, information is transferred in the ESB system more flexibly.
  • the console 20 further includes a determining unit 203 configured to determine a deployment node of a to-be-deleted service.
  • the generation unit is further configured to generate a instance deletion instruction, where the instance deletion instruction is used to instruct the deployment node of the to-be-deleted service to delete the first service instance.
  • the sending unit 202 is further configured to if the deployment node of the to-be-deleted service includes the first deployment node, send the instance deletion instruction to the first deployment node such that the first deployment node deletes the first service instance according to the instance deletion instruction.
  • the first deployment node 30 includes a receiver 301 configured to receive service information, sent by a console, of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, a processor 302 configured to generate a first service instance according to the definition of the first service, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, and a transmitter 303 configured to send first address information to service instances in an ESB system except the first service instance using the first service instance, where the first address information includes the service identifier of the first service and an address of the first deployment node such that a second deployment node invokes the first service instance according to the first address information using a second service instance, where the second service instance is a service instance, deployed on the second deployment node, in service instances of a second service, and the second deployment node is any deployment no
  • the first deployment node saves address information on each service instance instead of saving the address information in a service registry, and after the console sends the service information of the first service, the first deployment node generates the service instance according to the definition of the service, and notifies another service instance that the service instance of the first service is deployed on the first deployment node such that invocation may be directly performed between service instances of different services, therefore, information is transferred in the ESB system more flexibly.
  • the first deployment node 30 further includes the receiver 301 is further configured to receive an invocation request that is sent by the second deployment node using the second service instance, where the invocation request is generated according to an invocation instruction sent by the consumer server, the invocation instruction is used to instruct the second service instance to invoke the first service instance, and includes the service identifier of the first service, a service identifier of the second service, and preset information, the preset information is sent by the consumer server, the invocation request includes the preset information, and the consumer server is a server that is using the second service instance, the processor 302 is further configured to run the first service instance according to the preset information, to obtain a successful invocation response, and the transmitter 303 is further configured to send the successful invocation response to the second deployment node using the first service instance such that the second deployment node receives the successful invocation response using the second service instance.
  • the invocation request is generated according to an invocation instruction sent by the consumer server
  • the invocation instruction is used to instruct the second service instance to invoke the first service instance,
  • the first deployment node 30 further includes the receiver 301 is further configured to receive an instance deletion instruction sent by the console, where the instance deletion instruction instructs the first deployment node to delete the first service instance, the processor 302 is further configured to delete the first service instance according to the instance deletion instruction, and the transmitter 303 is further configured to send an address deletion instruction to the service instances in the ESB system, where the address deletion instruction is used to instruct the service instances in the ESB system to delete the first address information such that all deployment nodes in the ESB system delete the first address information according to the address deletion instruction.
  • the console 40 includes a processor 401 configured to generate service information of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, and a transmitter 402 configured to send the service information to a first deployment node such that after generating a first service instance according to the definition of the first service, the first deployment node sends first address information to service instances in an ESB system except the first service instance using the first service instance, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, and the first address information includes the service identifier of the first service and an address of the first deployment node.
  • the first deployment node saves address information on each service instance instead of saving the address information in a service registry, and after the console sends the service information of the first service, the first deployment node generates the service instance according to the definition of the service, and notifies another service instance that the service instance of the first service is deployed on the first deployment node such that invocation may be directly performed between service instances of different services, therefore, information is transferred in the ESB system more flexibly.
  • the console 40 further includes the processor 401 is further configured to determine a deployment node of a to-be-deleted service, the processor 401 is further configured to generate a instance deletion instruction, where the instance deletion instruction is used to instruct the deployment node of the to-be-deleted service to delete the first service instance, and the transmitter 402 is further configured to if the deployment node of the to-be-deleted service includes the first deployment node, send the instance deletion instruction to the first deployment node such that the first deployment node deletes the first service instance according to the instance deletion instruction.
  • An embodiment of the present disclosure provides a data processing method, applied to a first deployment node. Specific steps are shown in FIG. 7 and include the following steps:
  • Step 501 Receive service information, sent by a console, of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service.
  • a definition of the first service includes all files for installing the first service.
  • Step 502 Generate a first service instance according to the definition of the first service, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service.
  • Step 503 Send first address information to service instances in an ESB system except the first service instance using the first service instance.
  • the first address information includes the service identifier of the first service and an address of the first deployment node.
  • a second deployment node invokes the first service instance according to the first address information using a second service instance, where the second service instance is a service instance, deployed on the second deployment node, in service instances of a second service, and the second deployment node is any deployment node in the ESB system.
  • the second service instance may be a service instance deployed on the first deployment node other than the first service instance.
  • the first deployment node saves address information on each service instance instead of saving the address information in a service registry, and after the console sends the service information of the first service, the first deployment node generates the service instance according to the definition of the service, and notifies another service instance that the service instance of the first service is deployed on the first deployment node such that invocation may be directly performed between service instances of different services, therefore, information is transferred in the ESB system more flexibly.
  • step 503 of sending first address information to service instances in an ESB system except the first service instance using the first service instance the method further includes:
  • the first deployment node may receive an invocation request that is sent by the second deployment node using the second service instance, where the invocation request is generated according to an invocation instruction sent by a consumer server, the invocation instruction is used to instruct the second service instance to invoke the first service instance, and includes the service identifier of the first service, a service identifier of the second service, and preset information, the preset information is sent by the consumer server, the invocation request includes the preset information, and the consumer server is a server that is using the second service instance, run the first service instance according to the preset information, to obtain a successful invocation response, and send the successful invocation response to the second deployment node using the first service instance such that the second deployment node receives the successful invocation response using the second service instance.
  • the processing method further includes:
  • the first deployment node may receive an instance deletion instruction sent by the console, where the instance deletion instruction instructs the first deployment node to delete the first service instance, delete the first service instance according to the instance deletion instruction, and send an address deletion instruction to the service instances in the ESB system, where the address deletion instruction is used to instruct the service instances in the ESB system to delete the first address information such that all deployment nodes in the ESB system delete the first address information according to the address deletion instruction.
  • An embodiment of the present disclosure provides a data processing method, applied to a console. Specific steps are shown in FIG. 8 and include the following steps:
  • Step 601 Generate service information of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service.
  • Step 602 Send the service information to a first deployment node.
  • the first deployment node saves address information on each service instance instead of saving the address information in a service registry, and after the console sends the service information of the first service, the first deployment node generates the service instance according to the definition of the service, and notifies another service instance that the service instance of the first service is deployed on the first deployment node such that invocation may be directly performed between service instances of different services, therefore, information is transferred in the ESB system more flexibly.
  • the data processing method further includes:
  • the console determines a deployment node of a to-be-deleted service, generates a instance deletion instruction, where the instance deletion instruction is used to instruct the deployment node of the to-be-deleted service to delete a service instance of the first service, and if the deployment node of the to-be-deleted service includes the first deployment node, sends the instance deletion instruction to the first deployment node such that the first deployment node deletes a first service instance according to the instance deletion instruction, where the preset deletion condition includes many types, which may be classified into artificial deletion and automatic deletion.
  • the artificial deletion is that an administrator on a console side artificially triggers the console to generate a instance deletion instruction
  • the automatic deletion is that the console monitors a situation in which a consumer uses a service instance, and if a quantity of consumer servers that use the service instance is reduced, the console generates a deletion instruction, and sends the deletion instruction to a corresponding quantity of deployment nodes.
  • An embodiment of the present disclosure provides a data processing method. Specific steps are shown in FIG. 9 and include the following steps:
  • Step 701 A console generates service information of a to-be-deployed first service.
  • a service provided by a provider server is pre-stored on the console, and the console starts the first service according to an artificial operation of an administrator.
  • the administrator may set deployment nodes corresponding to the to-be-deployed first service, and trigger the console to generate the service information of the first service, where the service information of the first service includes a definition of the first service and a service identifier of the first service.
  • the definition of the first service includes all files for installing the first service, such as an installation package and an upgrade package of the first service.
  • Step 702 The console sends the service information of the first service to a first deployment node.
  • the first deployment node is a deployment node corresponding to the first service, and the console sends the service information only to each deployment node corresponding to the first service.
  • Step 703 The first deployment node generates a first service instance according to a definition of the first service.
  • the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service.
  • Step 704 The first deployment node sends first address information to service instances in an ESB system except the first service instance using the first service instance.
  • the first deployment node may send the first address information to the service instances deployed on the first deployment node except the first service instance using the first service instance, where the first address information includes the service identifier of the first service and an address of the first deployment node, and the address of the first deployment node is also an address of the first service instance such that the first deployment node saves address information of the first service using a service registry of each service instance deployed on the first deployment node, or may send the first address information to a service instance deployed on another deployment node other than the first deployment node, where the first address information includes the service identifier of the first service and an address of the first deployment node such that a second deployment node saves address information of the first service using a service registry of each service instance deployed on the second deployment node.
  • Step 705 A second deployment node receives an invocation instruction sent by a consumer server.
  • the invocation instruction includes the service identifier of the first service, a service identifier of a second service, and preset information, and the invocation instruction is used to instruct a second service instance to invoke the first service instance.
  • the preset information is information input by the consumer server, where the consumer server is a server that is using the second service instance.
  • the invocation instruction is generated when a user purchases nuts on a client of a shopping website using the consumer server, the client provides a shopping service instance, the user confirms payment after checking information about a weight, postage, and total costs of the purchased nuts, and a deployment node for deploying the shopping service instance invokes a payment service instance of a payment application, where the invocation instruction includes the information about the total costs, a service identifier of a shopping service, and a service identifier of the payment service instance.
  • Step 706 The second deployment node invokes the first service instance using a second service instance.
  • the second service instance is a service instance, deployed on the second deployment node, in service instances of a second service.
  • the second deployment node may be a deployment node different from the first deployment node, or may be the first deployment node.
  • the second service is a service different from the first service. In this embodiment, an example in which the second deployment node and the first deployment node are different deployment nodes is used.
  • the second deployment node obtains multiple addresses of the service instances of the first service by querying a service registry of the second service instance, and then determines a to-be-invoked service instance from the service instances of the first service according to a preset rule.
  • the to-be-invoked service instance is the first service instance
  • the second deployment node acquires the address of the first service instance, that is, the address of the first deployment node using the second service instance, and sends the invocation instruction to the first deployment node using the address of the first deployment node.
  • the first deployment node generates an invocation request according to the invocation instruction using the first service instance, where the invocation request includes the preset information, and runs the first service instance according to the preset information.
  • an operator client carries out a time-limited call fee recharge activity, in which 3 yuan is saved if 50 yuan is recharged and 10 yuan is saved if 100 yuan is recharged from 10:00 to 12:00 on Jan. 12, 2014.
  • Jack uses a call fee recharge service instance of the operator client at 11:23 using a mobile phone, and inputs, using the mobile phone, a mobile phone number that needs call fee recharge and an amount. It is assumed that the amount is 100 yuan. Jack confirms payment after checking the mobile phone number and the amount, and the call fee recharge service instance automatically changes the amount of call fee recharge to 90 yuan.
  • a deployment node for deploying the call fee recharge service instance sends an invocation instruction to an Internet bank payment service instance, where the invocation instruction includes the amount and the mobile phone number for call fee recharge, a service identifier of the Internet bank payment service instance, and a service identifier of the call fee recharge service instance.
  • the Internet bank payment service instance generates an invocation request according to the invocation instruction, where the invocation request includes the amount and the mobile phone number for call fee recharge.
  • the Internet bank payment service instance runs according to the amount and the mobile phone number for call fee recharge, and a successful invocation response is generated after payment is completed, where the successful invocation response is used to instruct the call fee recharge service instance to recharge a 100 yuan call fee to the mobile phone of the mobile phone number, to complete an entire call fee recharge process.
  • Step 707 The first deployment node sends a successful invocation response to the second deployment node using the first service instance.
  • Step 708 When a preset deletion condition is met, the console determines a deployment node of a to-be-deleted service, where the deployment node of the to-be-deleted service includes the first deployment node.
  • the preset deletion condition includes many situations, such as an artificial deletion situation and an automatic deletion situation.
  • the artificial deletion situation is that the administrator on a console side proactively triggers to stop one or more deployment nodes so as to delete a service instance.
  • the administrator may save a definition of the service and send the definition to a deployment node corresponding to the service, where the definition of the service may be an update package of the service instance, delete some service instances of the service, generate a service instance of the service using a definition of a service of a new version, then delete the other service instances of the service, and generate a service instance of the service using a definition of a service of a new version.
  • the automatic deletion situation may be deleting a service instance in a pre-determined time, or may be deleting a service instance by pre-determining an upper limit of consumer servers.
  • an operator client carries out a time-limited call fee recharge activity, in which 3 yuan is saved if 50 yuan is recharged and 10 yuan is saved if 100 yuan is recharged from 10:00 to 12:00 on Jan. 12, 2014, and when a quantity of users that perform call fee recharge is less than the pre-determined upper limit of consumer servers, a service instance is deleted according to a quantity of people who recharge a call fee in a unit time.
  • Step 709 The console generates an instance deletion instruction.
  • the instance deletion instruction is used to instruct the deployment node for deploying the to-be-deleted service to delete a service instance of the first service.
  • Step 710 The console sends the deletion instruction to the first deployment node.
  • Step 711 The first deployment node deletes the first service instance according to the instance deletion instruction.
  • Step 712 The first deployment node generates an address deletion instruction, where the address deletion instruction is used to instruct the service instances in the ESB system to delete the first address information.
  • Step 713 The first deployment node sends the address deletion instruction to the service instances in the ESB system.
  • the service instances in the ESB system include a service instance deployed on the second deployment node.
  • Step 714 The second deployment node deletes the first address information according to the address deletion instruction.
  • the second deployment node deletes the first address information, in other words, the first address information is deleted from a service registry of each service instance deployed on the second deployment node, and the second deployment node may be any one of all deployment nodes.
  • the deployment node of the present embodiment of disclosure not only can delete a service instance, but also can add a service instance to a new deployment node, and a specific method is the same as the method of steps 701 to 704 . Because multiple service instances are deployed on one deployment node, and one service instance may be deployed on multiple deployment nodes, when the ESB system runs multiple service instances at the same time, to prevent a mutual effect between the service instances, the deployment node manages running resources of the service instances, to divide a resource for a service instance of each service.
  • the present embodiment of disclosure provides a data processing method, including receiving service information, sent by a console, of a to-be-deployed first service, generating a first service instance according to a definition of the first service, and sending first address information to service instances in an enterprise service bus ESB system except the first service instance using the first service instance such that a second deployment node invokes the first service instance according to the first address information using a second service instance.
  • the first deployment node saves address information on each service instance instead of saving the address information in a service registry, and after the console sends the service information of the first service, the first deployment node generates the service instance according to the definition of the service, and notifies another service instance that the service instance of the first service is deployed on the first deployment node such that invocation may be directly performed between service instances of different services, therefore, information is transferred in the ESB system more flexibly.
  • the ESB system 80 includes a first deployment node 801 and a console 802 .
  • the first deployment node 801 is configured to receive service information, sent by the console, of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, generate a first service instance according to the definition of the first service, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, and send first address information to service instances in an ESB system except the first service instance using the first service instance, where the first address information includes the service identifier of the first service and an address of the first deployment node such that a second deployment node invokes the first service instance according to the first address information using a second service instance, where the second service instance is a service instance, deployed on the second deployment node, in service instances of a second service, and the second deployment node is
  • the console 802 is configured to generate the service information of the to-be-deployed first service, where the service information includes the definition of the first service and the service identifier of the first service, and send the service information to the first deployment node such that after generating the first service instance according to the definition of the first service, the first deployment node sends the first address information to the service instances in the ESB system except the first service instance using the first service instance, where the first service instance is a service instance, deployed on the first deployment node, in the service instances of the first service, and the first address information includes the service identifier of the first service and the address of the first deployment node.
  • FIG. 11 describes a structure of a first deployment node according to another embodiment of the present disclosure.
  • the first deployment node includes at least one processor 901 (for example, a central processing unit (CPU)), at least one network interface 902 or another communications interface, a memory 903 , and at least one communications bus 904 that is configured to implement connection and communication between these apparatuses.
  • the processor 901 is configured to execute an executable module stored in the memory 903 , for example, a computer program.
  • the memory 903 may include a high-speed random access memory (RAM), and may further include a non-volatile memory, for example, at least one magnetic disk storage.
  • RAM high-speed random access memory
  • non-volatile memory for example, at least one magnetic disk storage.
  • a communication connection between a system gateway of a browser and at least one other network element may be implemented through the Internet, a wide area network, a local area network, a metropolitan area network, or the like using the at least one network interface 902 (which may be wired or wireless).
  • the memory 903 stores a program 9031 , where the program 9031 may be executed by the processor 901 , and the program 9031 includes receiving service information, sent by a console, of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, generating a first service instance according to the definition of the first service, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, sending first address information to service instances in an ESB system except the first service instance using the first service instance, where the first address information includes the service identifier of the first service and an address of the first deployment node such that a second deployment node invokes the first service instance according to the first address information using a second service instance, where the second service instance is a service instance, deployed on the second deployment node, in service instances of a second service, and the second deployment node is any deployment node in the ESB system, receiving an invocation request
  • FIG. 12 describes a structure of a console according to another embodiment of the present disclosure.
  • the console includes at least one processor 1001 (for example, a CPU), at least one network interface 1002 or another communications interface, a memory 1003 , and at least one communications bus 1004 that is configured to implement connection and communication between these apparatuses.
  • the processor 1001 is configured to execute an executable module stored in the memory 1003 , such as a computer program.
  • the memory 1003 may include a high-speed RAM, and may further include a non-volatile memory, for example, at least one magnetic disk storage.
  • a communication connection between a system gateway of a browser and at least one other network element may be implemented through the Internet, a wide area network, a local area network, a metropolitan area network, or the like using the at least one network interface 1002 (which may be wired or wireless).
  • the memory 1003 stores a program 10031 , where the program 10031 may be executed by the processor 1001 , and the program 10031 includes generating service information of a to-be-deployed first service, where the service information includes a definition of the first service and a service identifier of the first service, sending the service information to a first deployment node such that after generating a first service instance according to the definition of the first service, the first deployment node sends first address information to service instances in an ESB system except the first service instance using the first service instance, where the first service instance is a service instance, deployed on the first deployment node, in service instances of the first service, and the first address information includes the service identifier of the first service and an address of the first deployment node, when a preset deletion condition is met, determining a deployment node of a to-be-deleted service, generating a instance deletion instruction, where the instance deletion instruction is used to instruct the deployment node of the to-be-deleted service to delete
  • the program may be stored in a computer-readable storage medium. When the program runs, the steps of the method embodiments are performed.
  • the foregoing storage medium includes any medium that can store program code, such as a random access memory (ROM), a RAM, a magnetic disk, or an optical disc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Telephonic Communication Services (AREA)
US15/233,017 2014-03-18 2016-08-10 Data Processing Method, Device, and ESB System Abandoned US20160352843A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201410101706.7 2014-03-18
CN201410101706.7A CN104935616A (zh) 2014-03-18 2014-03-18 一种数据处理方法、设备和esb系统
PCT/CN2014/090231 WO2015139461A1 (zh) 2014-03-18 2014-11-04 一种数据处理方法、设备和esb系统

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/090231 Continuation WO2015139461A1 (zh) 2014-03-18 2014-11-04 一种数据处理方法、设备和esb系统

Publications (1)

Publication Number Publication Date
US20160352843A1 true US20160352843A1 (en) 2016-12-01

Family

ID=54122588

Family Applications (1)

Application Number Title Priority Date Filing Date
US15/233,017 Abandoned US20160352843A1 (en) 2014-03-18 2016-08-10 Data Processing Method, Device, and ESB System

Country Status (4)

Country Link
US (1) US20160352843A1 (de)
EP (1) EP3079339A4 (de)
CN (1) CN104935616A (de)
WO (1) WO2015139461A1 (de)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108566412A (zh) * 2018-02-13 2018-09-21 深圳太极云软技术股份有限公司 一种数据服务方法及数据服务装置
CN110196723A (zh) * 2018-02-27 2019-09-03 广东神马搜索科技有限公司 流量数据拷贝的方法、装置以及计算机可读存储介质
WO2020258653A1 (zh) * 2019-06-28 2020-12-30 深圳前海微众银行股份有限公司 一种跨节点的数据处理方法及装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109412835B (zh) * 2018-09-11 2021-12-03 阿里巴巴（中国）有限公司 分布式系统及数据管理方法和装置、存储介质、计算设备
CN110035114A (zh) * 2019-02-28 2019-07-19 广州虎牙信息科技有限公司 多个虚拟币业务的配置方法、服务器、电子终端和装置
CN112965765B (zh) * 2021-02-02 2024-01-16 深圳市优必选科技股份有限公司 服务调用方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080140759A1 (en) * 2006-03-21 2008-06-12 Conner Peter A Dynamic service-oriented architecture system configuration and proxy object generation server architecture and methods
US20100131854A1 (en) * 2008-11-26 2010-05-27 Mark Cameron Little Graphical user interface for managing services in a distributed computing system
US20110289206A1 (en) * 2010-05-21 2011-11-24 Martin Vecera Automatic enterprise service bus deployment at the level of individual services
US20130219010A1 (en) * 2012-02-21 2013-08-22 Qualcomm Incorporated Internet protocol connectivity over a service-oriented architecture bus
US20130254328A1 (en) * 2012-03-20 2013-09-26 International Business Machines Corporation Inter-domain replication of service information
US20140006582A1 (en) * 2012-06-28 2014-01-02 International Business Machines Corporation Managing service specifications and the discovery of associated services

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101184056A (zh) * 2007-12-04 2008-05-21 浙江大学 一种分布式企业服务总线消息交换方法
CN101827115B (zh) * 2009-12-31 2012-11-21 厦门市美亚柏科信息股份有限公司 一种全息式企业服务总线

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080140759A1 (en) * 2006-03-21 2008-06-12 Conner Peter A Dynamic service-oriented architecture system configuration and proxy object generation server architecture and methods
US20100131854A1 (en) * 2008-11-26 2010-05-27 Mark Cameron Little Graphical user interface for managing services in a distributed computing system
US20110289206A1 (en) * 2010-05-21 2011-11-24 Martin Vecera Automatic enterprise service bus deployment at the level of individual services
US20130219010A1 (en) * 2012-02-21 2013-08-22 Qualcomm Incorporated Internet protocol connectivity over a service-oriented architecture bus
US20130254328A1 (en) * 2012-03-20 2013-09-26 International Business Machines Corporation Inter-domain replication of service information
US20140006582A1 (en) * 2012-06-28 2014-01-02 International Business Machines Corporation Managing service specifications and the discovery of associated services

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108566412A (zh) * 2018-02-13 2018-09-21 深圳太极云软技术股份有限公司 一种数据服务方法及数据服务装置
CN110196723A (zh) * 2018-02-27 2019-09-03 广东神马搜索科技有限公司 流量数据拷贝的方法、装置以及计算机可读存储介质
WO2020258653A1 (zh) * 2019-06-28 2020-12-30 深圳前海微众银行股份有限公司 一种跨节点的数据处理方法及装置

Also Published As

Publication number Publication date
CN104935616A (zh) 2015-09-23
EP3079339A4 (de) 2016-11-30
WO2015139461A1 (zh) 2015-09-24
EP3079339A1 (de) 2016-10-12

Similar Documents

Publication Publication Date Title
US20160352843A1 (en) Data Processing Method, Device, and ESB System
US11656852B2 (en) System and method for autowiring of a microservice architecture
US11310108B2 (en) Secure configuration of cloud computing nodes
CN110191063B (zh) 服务请求的处理方法、装置、设备及存储介质
EP2893443B1 (de) Rekonfiguration in cloud-computing-umgebungen
EP2947569A1 (de) Hybride Anwendungen in Betrieb zwischen vor Ort und in Cloud Plattforme
CN113742031B (zh) 节点状态信息获取方法、装置、电子设备及可读存储介质
CN108370328B (zh) 一种nfv mano策略描述符的管理方法及装置
WO2018166398A1 (zh) 一种nfv网络中许可证的管理系统
CN105744008B (zh) 智能家居平台、应用于该平台的系统更新方法和装置
US10810095B2 (en) Assigning network device subnets to perform network activities using network device information
WO2016121834A1 (ja) ネットワーク機能仮想化管理方法とシステムと装置とプログラム
US20220407795A1 (en) Centralized, scalable, resource monitoring system
CN111090495A (zh) 节点管理方法、装置、设备、存储介质和系统
CN110750780B (zh) 基于多业务系统的用户角色权限融合方法、装置以及设备
CN110781441A (zh) 基于微服务化架构的新零售业务中台
CN111008023B (zh) 一种实例部署方法及系统
CN109218259B (zh) 许可管理方法及装置、applm功能实体及计算机可读存储介质
CN105939384A (zh) 网络请求处理方法及系统
CN105338058A (zh) 一种应用更新的方法及装置
CN111061723A (zh) 工作流实现方法及装置
US20230040676A1 (en) Network service construction system and network service construction method
US20220027137A1 (en) Automatically orchestrating deployments of software-defined storage stacks
US10542119B2 (en) Multi-geographical processing of user requests
CN111857736A (zh) 云计算产品的生成方法、装置、设备及存储介质

Legal Events

Date Code Title Description
AS Assignment

Owner name: HUAWEI TECHNOLOGIES CO., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZONG, ZHIFENG;ZHANG, PUCHAO;HUANG, HAIJUN;REEL/FRAME:039395/0427

Effective date: 20160808

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION