A method and device for managing application services

Abstract

The present invention discloses a method and device for managing application services, and relates to the field of computer technology. A specific implementation of the method includes: obtaining the business attributes of each service under each application system according to a label; wherein each service references the label, and the management center and each application system are registered in the same registration center; storing the business attributes and node status of each service in the directory node of the registration center; and modifying the node status of any one or more services. This implementation can solve the technical problem of high maintenance cost of application services.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and device for managing application services. Background Art

[0002] With the rapid development of Internet technology, software developers have benefited greatly from the continuous iteration and optimization of various open source frameworks. For example, distributed message frameworks RocketMq, RabbitMq, ActiveMq, Kafka, etc., distributed task frameworks ElasticJob, saturn, Its, Quartz, etc. When maintaining an application online, software developers will choose between the following two methods.

[0003] Method 1: All services under the application system are enabled by default. Method 2: All services under the application system are disabled by default. After the application is successfully started, the software developer needs to log in to the management console of each application system to manually enable services such as message subscription or job scheduling.

[0004] In the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art:

[0005] Method 1: After the application is released and upgraded, all services are started and run immediately. If the newly launched logic is not effectively verified, once there is a problem with the new logic, a large amount of erroneous data will appear in a short period of time.

[0006] Method 2: During each application update, software developers need to spend a lot of effort to configure each service under each application system due to various business scenario restrictions. Summary of the invention

[0007] In view of this, an embodiment of the present invention provides a method and apparatus for managing application services to solve the technical problem of high maintenance cost of application services.

[0008] To achieve the above object, according to one aspect of an embodiment of the present invention, a method for managing application services is provided, which is applied to a management center and includes:

[0009] Acquire the business attributes of each service under each application system according to the tag; wherein each service references the tag, and the management center and each application system are registered in the same registration center;

[0010] Storing the business attributes and node status of each of the services in the directory node of the registration center;

[0011] Modify the node status of any one or more of the services.

[0012] Optionally, storing the business attributes and node status of each of the services in a directory node of the registration center includes:

[0013] For each service, storing the business attributes and node status of the service in the directory node corresponding to the service in the registration center;

[0014] The service attributes include name, type, description and IP address of the physical machine where the service is deployed, and the node status includes on and off.

[0015] In addition, according to another aspect of an embodiment of the present invention, a method for managing application services is provided, which is applied to an application system end and includes:

[0016] According to a pre-established label standard, reference the label corresponding to the service under the application system; wherein the label standard includes business attributes;

[0017] The node status stored in the directory node corresponding to the service of the monitoring registration center.

[0018] Optionally, it also includes:

[0019] If it is monitored that the node status stored in the directory node corresponding to the service of the registration center changes, the status information of the service is updated according to the changed node status;

[0020] The status information is turned on and off.

[0021] Optionally, it also includes:

[0022] After the application system is restarted, the service is controlled to be turned on or off according to the status information of the service.

[0023] Optionally, according to a pre-established label standard, before referencing a label corresponding to a service under the application system, the following may also be included:

[0024] Register the application system to the registration center.

[0025] In addition, according to another aspect of an embodiment of the present invention, there is provided a device for managing application services, which is arranged in a management center and includes:

[0026] An acquisition module, used for acquiring the business attributes of each service under each application system according to the tag; wherein each service references the tag, and the management center and each application system are registered in the same registration center;

[0027] A storage module, used to store the business attributes and node status of each of the services in the directory node of the registration center;

[0028] The modification module is used to modify the node status of any one or more of the services.

[0029] Optionally, the storage module is further used for:

[0030] For each service, storing the business attributes and node status of the service in the directory node corresponding to the service in the registration center;

[0031] The service attributes include name, type, description and IP address of the physical machine where the service is deployed, and the node status includes on and off.

[0032] In addition, according to another aspect of an embodiment of the present invention, there is provided a device for managing application services, which is arranged at an application system end and includes:

[0033] A reference module, used to reference the label corresponding to the service under the application system according to a pre-established label standard; wherein the label standard includes business attributes;

[0034] The monitoring module is used to monitor the node status stored in the directory node corresponding to the service of the registration center.

[0035] Optionally, the monitoring module is further used for:

[0036] If it is monitored that the node status stored in the directory node corresponding to the service of the registration center changes, the status information of the service is updated according to the changed node status;

[0037] The status information is turned on and off.

[0038] Optionally, it also includes:

[0039] The startup module is used to control the service to be turned on or off according to the status information of the service after the application system is restarted.

[0040] Optionally, it also includes:

[0041] The registration module is used to register the application system with the registration center before referencing the label corresponding to the service under the application system according to the pre-established label standard.

[0042] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, including:

[0043] one or more processors;

[0044] a storage device for storing one or more programs,

[0045] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the above embodiments.

[0046] According to another aspect of an embodiment of the present invention, a computer-readable medium is provided, on which a computer program is stored. When the program is executed by a processor, the method described in any one of the above embodiments is implemented.

[0047] One embodiment of the above invention has the following advantages or beneficial effects: because the technical means of storing the business attributes and node status of each service in the directory node of the registration center and modifying the node status of any one or more services is adopted, the technical problem of high maintenance cost of application services in the prior art is overcome. The embodiment of the present invention modifies the node status stored in the directory node of the registration center so that the application system modifies the status information of the service accordingly after monitoring the change of the node status, which facilitates the management of different types of services, thereby reducing the maintenance cost of online application services.

[0048] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0050] Figure 1 is a schematic diagram of the main process of the method for managing application services according to an embodiment of the present invention;

[0051] Figure 2 is a schematic diagram of a management interface of a management center according to an embodiment of the present invention;

[0052] Figure 3 is a schematic diagram of the underlying principle according to an embodiment of the present invention;

[0053] Figure 4 is a schematic diagram of the main process of the method for managing application services according to an embodiment of the present invention;

[0054] Figure 5 is a schematic diagram of the main process of a method for managing application services according to a reference embodiment of the present invention;

[0055] Figure 6 is a schematic diagram of main modules of an apparatus for managing application services according to an embodiment of the present invention;

[0056] Figure 7 is a schematic diagram of main modules of an apparatus for managing application services according to an embodiment of the present invention;

[0057] Figure 8is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0058] Fig. 9 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0059] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0060] Figure 1 Schematic diagram of the main process of the method for managing application services according to an embodiment of the present invention. Figure 1 As shown, the method for managing application services is applied to a management center and may include:

[0061] Step 101, obtaining the business attributes of each service under each application system according to the tag.

[0062] In an embodiment of the present invention, the management center needs to first create tags (such as scheduled task tags, message monitoring tags, etc.), and formulate usage standards for each tag, and then publish the supported tags to the outside world, and each service under each application system references the tags corresponding to each service according to the standards. For example, when a service under an application system references a tag, it is necessary to provide a unique identifier for the service, service name, service type, description, IP address of the physical machine where the service is deployed, execution cycle, etc., according to the annotation. Therefore, the management center can distinguish the characteristics of each service according to the tag and implement different management mechanisms. In an embodiment of the present invention, each of the services references the tag, and the management center and each of the application systems are registered in the same registration center. Optionally, the registration center can be Zookeeper, a distributed, open source distributed application coordination service.

[0063] Due to the different division of responsibilities, the services provided by various application systems will also be different. For example, system A is a task scheduling system, system B is a message production / subscription system, and system C only provides remote procedure call (RPC) services. System A performs scheduled tasks, such as sending daily reports to users at 8 o'clock every night; system B processes messages generated upstream. For example, the upstream order system sends an "order created" message, and system B starts to calculate the order's charge details after receiving the message. System C generally refers to ordinary service providers. For example, C is an inventory system, which needs to provide RPC services such as inventory modification and query to the front end.

[0064] The label has rich attributes, such as service type, service name, description, unique identifier, etc., and can be expanded as needed. If the service under the application system wants to be managed by the management center, it is necessary to reference the label to expose the business attributes such as the name and type of the service. In order to distinguish different services and manage them, the embodiment of the present invention uses Spring custom labels, provides flexible and changeable labels and defines usage standards for use by various application systems to distinguish different types of services, thereby realizing differentiated management of different services under various application systems.

[0065] Step 102: store the business attributes and node status of each of the services in the directory node of the registration center.

[0066] Since each service under each application system references a label, when the application system starts, the toolkit of the management center will automatically find the services that reference the label and persist the business attributes of the service to the directory node of the registration center (such as the directory node Znode of Zookeeper). Therefore, the management center can read this information in the registration center and manage it. It can also display the information of each service graphically. The management interface diagram of the management center is as follows Figure 2 As shown, batch processing can be performed through [Policy Enable] and [One-click Disable] on the upper left. Optionally, the service attributes include name, type, description, and IP address of the physical machine where the service is deployed.

[0067] In order to facilitate the management of the on and off status of each service, the management center also stores the node status of the service that references the label in the directory node of the registration center and manages it. Optionally, the node status includes on and off.

[0068] Optionally, step 102 includes: for each service, storing the business attributes and node status of the service in the directory node corresponding to the service in the registration center. Since the management center and each application system are registered in the same registration center, the management center can find the application systems registered in the registration center and obtain the configuration information of these application systems (such as the system name, which services are under the system, the business attributes and node status of each service, etc.), thereby achieving the purpose of managing each service under each application system.

[0069] It should be noted that the creation path of the directory nodes of the registration center is regular. For example, the root node is machine. Whenever a new system application is connected, a new secondary node will be created under machine. In this way, the management center only needs to traverse several secondary nodes of machine to find all application systems and manage them.

[0070] Optionally, you can create a directory node using the system name, application name, and service name, that is, machine+system name+application name+service name, so that you can view and manage each service.

[0071] For example, a directory node might look like this:

[0072] / machine / xstore / xstore-settle-center / settleStatementRecPayStatsConsumer

[0073] Optionally, you can create a directory node using the system name, application name, service name, and the IP address of the physical machine where the service is deployed, that is, baseTask+system name+application name+service name+IP, so that you can view which machines the service is deployed on and manage it.

[0074] For example, a directory node might look like this:

[0075] / baseTask / xstore / xstore-settle-center / settleStatementRecPayStatsConsumer / 128.11.9.1

[0076] The embodiment of the present invention maps application systems, services, and IPs to zookeeper directory nodes, and stores each directory node in a dictionary-like manner through a tree data structure, thereby achieving comprehensive management of multiple application systems.

[0077] Optionally, the embodiment of the present invention utilizes the characteristics of Zookeeper to store the configuration information of each application system in the directory node (Znode) of Zookeeper. The application system monitors the configuration information. Once the configuration information changes, each application system will receive a notification from Zookeeper, and then obtain the new configuration information from Zookeeper to the application system. In the embodiment of the present invention, the path of Znode is globally unique; the content of Znode can always exist in the memory for easy reading; znode can isolate each application system, thereby realizing the security management of each application system.

[0078] Curator is an open source client framework of Zookeeper, which encapsulates many interfaces. The embodiment of the present invention uses CuratorFramework (Zookeeper's client end, which can discover and manage znode nodes) to implement service discovery. Znode is isolated from each connected application system, and Znode is the system path of each system. Each application system has its own root path, and the service hosted under the application (such as a message listener or a job) as an instance service will also have a globally unique Znode, so that all application systems hosted in the registration center and the services under the application can be obtained through the interface provided by CuratorFramework, and these services can be managed in a unified manner. In an embodiment of the present invention, a message listener refers to a subscriber to a distributed message, which listens to messages sent by a message sender and processes business logic; a job refers to a system scheduled task.

[0079] It should be pointed out that when the application system accesses the registration center, it needs to configure the registration center like the management center, and use the namespace provided by the management center to declare the services that need to be hosted (such as message listeners or jobs, etc.). The hosted application system must share a set of registration centers with the management center, otherwise the management center cannot discover the services that need to be managed uniformly. Specifically, after the Zookeeper cluster is built, the management center introduces the dependency on Zookeeper and points to the Zookeeper cluster address in the configuration file. If the application system wants to be hosted in the management center, it must be configured with the same Zookeeper cluster address.

[0080] Step 103: modify the node status of any one or more of the services.

[0081] Developers can modify the node status of any one or more services through the management center as needed, such as changing the on state to off, or changing off state to on. Batch operations can be performed on the node status of multiple services, thereby improving management efficiency and reducing the maintenance cost of application services, solving the problem that the consoles of multiple application systems were scattered within each system, causing developers to be exhausted from decentralized management.

[0082] like Figure 3 As shown, each application system (such as application system A, application system B and application system C, etc.) monitors the node status stored in the corresponding directory node in real time. If it monitors that the node status stored in the directory node of the registration center changes, the status information of the service under the application system is updated according to the changed node status; wherein the status information is turned on and off. If the node status of the service is turned on, then the status information of the service is turned on, and when the application system of the service is started, the service is in the turned on state; if the node status of the service is turned off, then the status information of the service is turned off, and when the application system of the service is started, the service is in the turned on state.

[0083] According to the various embodiments described above, it can be seen that the embodiments of the present invention solve the technical problem of high maintenance cost of application services in the prior art by storing the business attributes and node status of each service in the directory node of the registration center and modifying the node status of any one or more services. The embodiments of the present invention modify the node status stored in the directory node of the registration center so that the application system can modify the status information of the service accordingly after monitoring the change of the node status, which facilitates the management of different types of services, thereby reducing the maintenance cost of online application services.

[0084] Figure 4 Schematic diagram of the main process of the method for managing application services according to an embodiment of the present invention. As another embodiment of the present invention, Figure 4 As shown, the method for managing application services is applied to the application system end and may include the following steps:

[0085] Step 401, according to the pre-established label standard, reference the label corresponding to the service under the application system.

[0086] In an embodiment of the present invention, the management center needs to first create tags (such as scheduled task tags, message monitoring tags, etc.), and formulate usage standards for each tag, and then publish the supported tags to the outside world, and each service under the application system references the tags corresponding to each service according to the standards. For example, when the service under the application system references the tag, it is necessary to provide the service unique identifier, service name, service type, description, IP address of the physical machine where the service is deployed, execution cycle, etc. according to the annotation, so the management center can distinguish the characteristics of each service according to the tag and implement different management mechanisms. Among them, the tag standard includes business attributes, and the business attributes may include service unique identifier, service name, service type, description, IP address of the physical machine where the service is deployed, etc. There are rich attributes on the tag, such as service type, service name, description, unique identifier, etc., and it can also be expanded as needed. If the service under the application system wants to be managed by the management center, it is necessary to reference the tag to expose the business attributes such as the name and type of the service.

[0087] Step 402: monitor the node status stored in the directory node corresponding to the service in the registration center.

[0088] Since each service under the application system references a label, when the application system starts, the toolkit of the management center will automatically find the services that reference the label and persist the business attributes of the service to the directory node of the registration center (such as the directory node Znode of Zookeeper). Therefore, the management center can read this information in the registration center and manage it. In order to facilitate the management of the on and off status of each service, the management center also stores the node status of the service that references the label in the directory node of the registration center and manages it. Optionally, the node status includes on and off.

[0089] For each service, the business attributes and node status of the service are stored in the directory node corresponding to the service in the registration center. Since the management center and the application system are registered in the same registration center, the management center can find the application systems registered on the registration center and obtain the configuration information of these application systems (such as the system name, which services are under the system, the business attributes and node status of each service, etc.), thereby achieving the purpose of managing each service under each application system.

[0090] The application system monitors the node status stored in the corresponding directory node in real time. If it monitors that the node status stored in the directory node of the registration center changes, the status information of the service under the application system is updated according to the changed node status; wherein the status information is turned on and off. If the node status of the service is on, then the status information of the service is on, and when the application system of the service is started, the service is in the on state; if the node status of the service is off, then the status information of the service is off, and when the application system of the service is started, the service is in the off state.

[0091] According to the various embodiments described above, it can be seen that the embodiments of the present invention solve the technical problem of high maintenance cost of application services in the prior art by referring to the labels corresponding to the services under the application system according to the pre-established label standard and monitoring the node status stored in the directory node corresponding to the service in the registration center. The embodiments of the present invention monitor the node status stored in the directory node corresponding to the service in the registration center, so that the application system can modify the status information of the service accordingly after monitoring the change of the node status, which facilitates the management of different types of services, thereby reducing the maintenance cost of online application services.

[0092] Figure 5 Schematic diagram of the main process of a method for managing application services according to a reference embodiment of the present invention. As another embodiment of the present invention, Figure 5 As shown, the method for managing application services is applied to the application system end and may include:

[0093] Step 501, according to the pre-established label standard, reference the label corresponding to the service under the application system.

[0094] Step 502: monitor the node status stored in the directory node corresponding to the service in the registration center.

[0095] Step 503: If it is monitored that the node status stored in the directory node corresponding to the service of the registration center changes, the status information of the service is updated according to the changed node status.

[0096] Step 504: After the application system is restarted, the service is controlled to be turned on or off according to the status information of the service.

[0097] The application system monitors the node status stored in the corresponding directory node in real time. If it monitors that the node status stored in the directory node of the registration center changes, the status information of the service under the application system is updated according to the changed node status; wherein the status information is turned on and off. If the node status of the service is on, then the status information of the service is on, and when the application system of the service is started, the service is in the on state; if the node status of the service is off, then the status information of the service is off, and when the application system of the service is started, the service is in the off state.

[0098] In addition, the specific implementation content of the method for managing application services in a reference embodiment of the present invention has been described in detail in the method for managing application services described above, so the repeated content will not be described here.

[0099] Figure 6 Schematic diagram of the main modules of the device for managing application services according to an embodiment of the present invention. Figure 6 As shown, the device 600 for managing application services is set in the management center, and includes an acquisition module 601, a storage module 602 and a modification module 603. The acquisition module 601 is used to acquire the business attributes of each service under each application system according to the label; each service references the label, and the management center and each application system are registered in the same registration center; the storage module 602 is used to store the business attributes and node status of each service in the directory node of the registration center; the modification module 603 is used to modify the node status of any one or more services.

[0100] Optionally, the storage module 602 is further used for:

[0101] For each service, storing the business attributes and node status of the service in the directory node corresponding to the service in the registration center;

[0102] The service attributes include name, type, description and IP address of the physical machine where the service is deployed, and the node status includes on and off.

[0103] According to the various embodiments described above, it can be seen that the embodiments of the present invention solve the technical problem of high maintenance cost of application services in the prior art by storing the business attributes and node status of each service in the directory node of the registration center and modifying the node status of any one or more services. The embodiments of the present invention modify the node status stored in the directory node of the registration center so that the application system can modify the status information of the service accordingly after monitoring the change of the node status, which facilitates the management of different types of services, thereby reducing the maintenance cost of online application services.

[0104] It should be noted that the specific implementation content of the device for managing application services in the present invention has been described in detail in the method for managing application services described above, so the repeated content will not be described here.

[0105] Figure 7 Schematic diagram of the main modules of the device for managing application services according to an embodiment of the present invention. Figure 7 As shown, the device 700 for managing application services is set at the application system end, and includes a reference module 701 and a monitoring module 702. The reference module 701 is used to reference the label corresponding to the service under the application system according to a pre-established label standard; wherein the label standard includes business attributes; the monitoring module 702 is used to monitor the node status stored in the directory node corresponding to the service in the registration center.

[0106] Optionally, the monitoring module 702 is further configured to:

[0107] If it is monitored that the node status stored in the directory node corresponding to the service of the registration center changes, the status information of the service is updated according to the changed node status;

[0108] The status information is turned on and off.

[0109] Optionally, it also includes:

[0110] The startup module is used to control the service to be turned on or off according to the status information of the service after the application system is restarted.

[0111] Optionally, it also includes:

[0112] The registration module is used to register the application system with the registration center before referencing the label corresponding to the service under the application system according to the pre-established label standard.

[0113] According to the various embodiments described above, it can be seen that the embodiments of the present invention solve the technical problem of high maintenance cost of application services in the prior art by referring to the labels corresponding to the services under the application system according to the pre-established label standard and monitoring the node status stored in the directory node corresponding to the service in the registration center. The embodiments of the present invention monitor the node status stored in the directory node corresponding to the service in the registration center, so that the application system can modify the status information of the service accordingly after monitoring the change of the node status, which facilitates the management of different types of services, thereby reducing the maintenance cost of online application services.

[0114] It should be noted that the specific implementation content of the device for managing application services in the present invention has been described in detail in the method for managing application services described above, so the repeated content will not be described here.

[0115] Figure 8 An exemplary system architecture 800 is shown to which the method for managing application services or the apparatus for managing application services according to the embodiments of the present invention can be applied.

[0116] like Figure 8 As shown, system architecture 800 may include terminal devices 801, 802, 803, a network 804, and a server 805. Network 804 is used to provide a medium for communication links between terminal devices 801, 802, 803 and server 805. Network 804 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0117] Users can use terminal devices 801, 802, and 803 to interact with server 805 through network 804 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 801, 802, and 803, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0118] The terminal devices 801 , 802 , and 803 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0119] The server 805 may be a server that provides various services, such as a backend management server (only an example) that provides support for shopping websites browsed by users using the terminal devices 801, 802, and 803. The backend management server may analyze and process the received data such as the item information query request, and feed back the processing results (such as target push information, item information - only an example) to the terminal device.

[0120] It should be noted that the method for managing application services provided in the embodiment of the present invention is generally executed by the server 805, and accordingly, the device for managing application services is generally set in the server 805. The method for managing application services provided in the embodiment of the present invention can also be executed by the terminal devices 801, 802, and 803, and accordingly, the device for managing application services can be set in the terminal devices 801, 802, and 803.

[0121] It should be understood that Figure 8 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0122] Reference below Fig. 9 , which shows a schematic diagram of the structure of a computer system 900 of a terminal device suitable for implementing an embodiment of the present invention. Fig. 9 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0123] like Fig. 9 As shown, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage part 908 into a random access memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the system 900 are also stored. The CPU 901, the ROM 902, and the RAM 903 are connected to each other via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0124] The following components are connected to the I / O interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, a modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed, so that a computer program read therefrom is installed into the storage section 908 as needed.

[0125] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 909, and / or installed from the removable medium 911. When the computer program is executed by the central processing unit (CPU) 901, the above-mentioned functions defined in the system of the present invention are executed.

[0126] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0127] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0128] The modules involved in the embodiments of the present invention may be implemented by software or hardware. The modules described may also be set in a processor, for example, it may be described as: a processor includes an acquisition module, a storage module and a modification module, wherein the names of these modules do not constitute a limitation on the modules themselves in some cases.

[0129] The modules involved in the embodiments of the present invention may be implemented by software or hardware. The modules described may also be set in a processor, for example, it may be described as: a processor includes a reference module and a monitoring module, wherein the names of these modules do not constitute a limitation on the modules themselves in some cases.

[0130] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device implements the following method: obtaining the business attributes of each service under each application system according to the label; wherein each of the services references the label, and the management center and each of the application systems are registered in the same registration center; storing the business attributes and node status of each of the services in the directory node of the registration center; modifying the node status of any one or more of the services.

[0131] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device implements the following method: according to a pre-established label standard, reference the label corresponding to the service under the application system; wherein the label standard includes business attributes; monitor the node status stored in the directory node corresponding to the service in the registration center.

[0132] According to the technical solution of the embodiment of the present invention, the technical problem of high maintenance cost of application services in the prior art is overcome because the business attributes and node status of each service are stored in the directory node of the registration center and the node status of any one or more services is modified. The embodiment of the present invention modifies the node status stored in the directory node of the registration center so that the application system modifies the status information of the service accordingly after monitoring the change of the node status, which facilitates the management of different types of services, thereby reducing the maintenance cost of online application services.

[0133] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for managing application services, characterized in that: Applied to the management center, including: Obtaining business attributes of each service under each application system according to the tag; wherein each service references the tag according to the tag standard, the tag standard includes business attributes, and the management center and each application system are registered in the same registration center; The business attributes and node status of each of the services are stored in a directory node of the registration center; wherein the directory node is created using a system name, an application name, and a service name, or is created using a system name, an application name, a service name, and an IP address of a physical machine where the service is deployed; Modify the node status of any one or more of the services.

2. The method according to claim 1, characterized in that Storing the business attributes and node status of each of the services in the directory node of the registration center includes: For each service, storing the business attributes and node status of the service in the directory node corresponding to the service in the registration center; The service attributes include name, type, description and IP address of the physical machine where the service is deployed, and the node status includes on and off.

3. A method for managing application services, characterized in that: Applied to the application system side, including: According to a pre-established label standard, reference the label corresponding to the service under the application system; wherein the label standard includes business attributes; The node status stored in the directory node corresponding to the service of the monitoring registration center; wherein the node status stored in the directory node corresponding to the service is stored in the directory node of the registration center by the management center, the node status is modified by the management center, and the management center and the application system are registered in the same registration center; the directory node is created using the system name, application name and service name, or, is created using the system name, application name, service name and the IP address of the physical machine where the service is deployed.

4. The method according to claim 3, characterized in that Also includes: If it is monitored that the node status stored in the directory node corresponding to the service of the registration center changes, the status information of the service is updated according to the changed node status; The status information includes on and off.

5. The method according to claim 4, characterized in that Also includes: After the application system is restarted, the service is controlled to be turned on or off according to the status information of the service.

6. The method according to claim 3, characterized in that According to the pre-established label standard, before referencing the label corresponding to the service under the application system, it also includes: Register the application system to the registration center.

7. A device for managing application services, characterized in that: Set up in the management center, including: An acquisition module, used for acquiring the business attributes of each service under each application system according to the tag; wherein each service references the tag according to the tag standard, the tag standard includes business attributes, and the management center and each application system are registered in the same registration center; A storage module, used to store the business attributes and node status of each of the services in a directory node of the registration center; wherein the directory node is created using a system name, an application name, and a service name, or is created using a system name, an application name, a service name, and an IP address of a physical machine where the service is deployed; A modification module is used to modify the node status of any one or more of the services.

8. A device for managing application services, characterized in that: Set up on the application system side, including: A reference module, used to reference the label corresponding to the service under the application system according to a pre-established label standard; wherein the label standard includes business attributes; A monitoring module is used to monitor the node status stored in the directory node corresponding to the service of the registration center; wherein the node status stored in the directory node corresponding to the service is stored by the management center in the directory node of the registration center, and the node status is modified by the management center, and the management center and the application system are registered in the same registration center; the directory node is created using the system name, application name and service name, or, is created using the system name, application name, service name and the IP address of the physical machine where the service is deployed.

9. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images