WO2017054501A1

WO2017054501A1 - Application management method, device and system

Info

Publication number: WO2017054501A1
Application number: PCT/CN2016/084952
Authority: WO
Inventors: 龚红星
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-09-30
Filing date: 2016-06-06
Publication date: 2017-04-06
Also published as: CN106559245A

Abstract

An application management method, device and system. The method comprises: receiving a management operation conforming to a java management extensions protocol; and managing, according to the management operation, based on the java management extensions protocol, a corresponding application deployed on a Tomcat server.

Description

Application management method, device and system

Technical field

This document relates to, but is not limited to, the field of application management, and in particular, to an application management method, apparatus and system configured to manage applications deployed on a Tomcat server.

Background technique

Tomcat (a free open source web application server name provided by Apache) as a free open source, lightweight World Wide Web (WEB) application server has been widely used around the world.

Currently, the Tomcat server on the physical server is not only used for a web application, but a plurality of web applications are deployed. In related technologies, when an application needs to be upgraded, the Tomcat server needs to be stopped, for an application. Updates, but must stop all other applications deployed on the Tomcat server; for example, a Tomcat server has five applications, which correspond to different services, and now need to upgrade a certain service, and need to stop all services, and if the service corresponds to The application is large, and it takes a lot of time to start and stop. It also affects the non-upgraded service usage; that is, the related application management method cannot implement separate management of the application, resulting in high application management cost.

Therefore, how to provide an application management method that can reduce the application management cost is a technical problem to be solved by those skilled in the art.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides an application management method, device and system, which can implement separate management of an application, thereby reducing application management costs.

An embodiment of the present invention provides an application management method, including: receiving a management operation based on a JAVA management extension protocol; and managing a corresponding application deployed on a Tomcat server according to a JAVA management extension protocol according to a management operation.

Optionally, the management operation includes a shutdown operation; and the corresponding application deployed on the Tomcat server is managed by: the background JAVA obtains the device proxy layer object of the Tomcat server, according to the obtained The managed application name in the device proxy layer object is obtained by the device corresponding to the application registered on the device proxy layer, and the application method of the corresponding application is closed by using the remote procedure call protocol to remotely invoke the stop application method provided by the device.

Optionally, the management operation includes: enabling the operation; managing the corresponding application deployed on the Tomcat server includes: the background JAVA obtains the device proxy layer object of the Tomcat server, and obtains the managed application name in the obtained device proxy layer object. The device that is registered on the device proxy layer is remotely invoked by the remote procedure call protocol to open the application method provided by the device, and the application service corresponding to the application is set to be available.

Optionally, the management operation includes a loading operation; and managing the corresponding application deployed on the Tomcat server includes: the background JAVA obtains the device proxy layer object of the Tomcat server, and obtains the managed application name in the obtained device proxy layer object. Correspondingly, the device registered on the device proxy layer remotely invokes the interface method provided by the device through the remote procedure call protocol, copies the application file package to the network application directory, and invokes the stop application method provided by the device to set the application service of the corresponding application to load.

Optionally, the management operation includes an uninstall operation. The management of the corresponding application deployed on the Tomcat server includes: the background JAVA obtains the device proxy layer object of the Tomcat server, and obtains the managed application name in the obtained device proxy layer object. Corresponding to the device registered by the application on the device proxy layer, remotely invoke the uninstall application method provided by the device through the remote procedure call protocol, stop the application service, and delete the application file.

Optionally, the management operation further includes an installation operation; the application management method further includes: uploading an application file package of the Tomcat specification to the Tomcat server.

Optionally, the management operation further includes an upgrade and/or a rollback operation. The management of the corresponding application deployed on the Tomcat server includes: uploading a user-developed upgrade package and/or rolling back the package to the Tomcat server, and upgrading the corresponding application. And/or rollback.

An embodiment of the present invention provides an application management apparatus, including:

a receiving module configured to receive a management operation based on a JAVA management extension protocol;

The management module is configured to manage the corresponding application deployed on the Tomcat server according to the management operation and based on the JAVA management extension protocol.

Optionally, the management operation includes a shutdown operation; the management module is configured to acquire a device proxy layer object of the Tomcat server, and obtain a device registered by the corresponding application on the device proxy layer according to the managed application name in the obtained device proxy layer object. The remote application process remotely invokes the stop application method provided by the device, and sets the application service of the corresponding application to be closed.

Optionally, the management operation includes: opening the operation; the management module is configured to acquire the device proxy layer object of the Tomcat server, and obtain the device registered by the corresponding application on the device proxy layer according to the managed application name in the obtained device proxy layer object. The remote application process is remotely invoked by the remote procedure call protocol to set the application service of the corresponding application to be available.

Optionally, the management operation includes a loading operation; the management module is configured to acquire a device proxy layer object of the Tomcat server, and obtain a device registered by the corresponding application on the device proxy layer according to the managed application name in the obtained device proxy layer object. Remotely invoke the interface method provided by the device through the remote procedure call protocol, copy the application file package to the network application directory, and invoke the stop application method provided by the device to set the application service of the corresponding application to be loaded.

Optionally, the management operation includes an uninstall operation; the management module is configured to obtain a device proxy layer object of the Tomcat server, and obtain a device registered by the corresponding application on the device proxy layer according to the managed application name in the obtained device proxy layer object. Remotely invoke the uninstall application method provided by the device through the remote procedure call protocol, stop the application service, and delete the application file.

Optionally, the management operation further includes an installation operation; the management module is further configured to upload an application file package of the Tomcat specification to the Tomcat server.

Optionally, the management operation further includes an upgrade and/or a rollback operation; the management module is further configured to upload a user-developed upgrade package and/or a rollback package to the Tomcat server, and upgrade and/or roll back the corresponding application.

The embodiment of the present invention provides an application management system, which includes a Tomcat server and an application management device provided by the embodiment of the present invention. The application management device performs a corresponding deployment on the Tomcat server based on the JAVA management extension protocol according to the management operation. The application is managed.

Advantageous effects of embodiments of the present invention:

An embodiment of the present invention provides an application management method, and according to a management operation, manages a corresponding application deployed on a Tomcat server based on a JAVA management extension protocol, because Within the framework of the JAVA management extension protocol, the applications on the Tomcat server exist as a single device. On this basis, if you upgrade an application on a Tomcat server, you do not need to stop the entire Tomcat server. The operational applications are processed separately, minimizing the impact and risk of operations, enabling separate management of applications, thereby reducing application management costs.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a schematic structural diagram of an application management apparatus according to a first embodiment of the present invention;

2 is a flowchart of an application management method according to a second embodiment of the present invention;

3 is a schematic diagram of networking of an application management system in a third embodiment of the present invention;

FIG. 4 is a schematic diagram of switching of an application state in a third embodiment of the present invention.

Embodiments of the invention

The invention will now be further illustrated by way of specific embodiments in conjunction with the accompanying drawings.

First embodiment:

FIG. 1 is a schematic structural diagram of an application management apparatus according to a first embodiment of the present invention. As shown in FIG. 1, in the embodiment, the application management apparatus 1 provided by the present invention includes:

The receiving module 11 is configured to receive a management operation based on the JAVA management extended protocol;

The management module 12 is configured to manage the corresponding application deployed on the Tomcat server according to the JAVA management extension protocol according to the management operation.

In some embodiments, the management operation includes a shutdown operation; the management module 12 in the above embodiment is configured to acquire a device proxy layer object of the Tomcat server, and obtain a corresponding application according to the managed application name in the obtained device proxy layer object. The device registered on the device proxy layer remotely invokes the stop application method provided by the device through the remote procedure call protocol, and sets the application service of the corresponding application to be closed.

In some embodiments, the management operation includes an open operation; the management module 12 in the above embodiment is configured to acquire a device proxy layer object of the Tomcat server, according to the obtained device proxy layer object The managed application name in the device is obtained by the device that is registered on the device proxy layer, and the application method provided by the device is remotely invoked through the remote procedure call protocol, and the application service corresponding to the application is set to be available.

In some embodiments, the management operation includes a loading operation; the management module 12 in the above embodiment is configured to acquire a device proxy layer object of the Tomcat server, and obtain a corresponding application according to the managed application name in the obtained device proxy layer object. The device registered on the device proxy layer remotely invokes the interface method provided by the device through the remote procedure call protocol, copies the application file package to the network application directory, and invokes the stop application method provided by the device to set the application service of the corresponding application to be loaded.

In some embodiments, the management operation includes an uninstall operation; the management module 12 in the above embodiment is configured to acquire a device proxy layer object of the Tomcat server, and obtain a corresponding application according to the managed application name in the obtained device proxy layer object. The device registered on the device proxy layer remotely invokes the uninstall application method provided by the device through the remote procedure call protocol, stops the application service, and deletes the application file.

In some embodiments, the management operation further includes an installation operation; the management module 12 in the above embodiment is further configured to upload the Tomcat-compliant application file package to the Tomcat server.

In some embodiments, the management operation further includes an upgrade and/or a rollback operation; the management module 12 in the above embodiment is further configured to upload a user-developed upgrade package and/or a rollback package to the Tomcat server, and upgrade the corresponding application. And/or rollback.

Correspondingly, the present invention provides an application management system, including a Tomcat server, and an application management apparatus 1 provided by the present invention. The application management apparatus 1 deploys on the Tomcat server based on the JAVA management extension protocol according to the management operation. Manage the application.

Second embodiment:

FIG. 2 is a flowchart of an application management method according to a second embodiment of the present invention. As shown in FIG. 2, in the embodiment, the application management method provided by the present invention may be implemented by using an application management apparatus, including the following steps:

S201: Receive a management operation based on a JAVA management extension protocol;

S202: Manage the corresponding application deployed on the Tomcat server according to the JAVA management extension protocol according to the management operation.

In some embodiments, the management operation in the foregoing embodiment includes a shutdown operation; managing the corresponding application deployed on the Tomcat server includes: acquiring a device proxy layer object of the Tomcat server through the background JAVA, according to the obtained device proxy layer object The managed application name is obtained by the device corresponding to the application registered on the device proxy layer, and the application method of the corresponding application is set to be closed by remotely calling the stop application method provided by the device through the remote procedure call protocol.

In some embodiments, the management operation in the foregoing embodiment includes an open operation; managing the corresponding application deployed on the Tomcat server includes: acquiring a device proxy layer object of the Tomcat server through the background JAVA, according to the obtained device proxy layer object The managed application name is obtained by the device corresponding to the application registered on the device proxy layer, and the application application provided by the remote calling device is remotely invoked by the remote procedure call protocol, and the application service corresponding to the application is set to be available.

In some embodiments, the management operation in the foregoing embodiment includes a loading operation; managing the corresponding application deployed on the Tomcat server includes: acquiring a device proxy layer object of the Tomcat server through the background JAVA, according to the obtained device proxy layer object The managed application name is obtained by the corresponding device registered on the device proxy layer, and the interface method provided by the remote calling device is remotely invoked by the remote procedure call protocol, the application file package is copied to the network application directory, and the stop application method provided by the device is invoked. , set the application service of the corresponding application to load.

In some embodiments, the management operation in the foregoing embodiment includes an uninstall operation; managing the corresponding application deployed on the Tomcat server includes: acquiring a device proxy layer object of the Tomcat server through the background JAVA, and obtaining, according to the managed application name, Corresponding to the device registered by the application on the device proxy layer, remotely invoke the uninstall application method provided by the device through the remote procedure call protocol, stop the application service, and delete the application file.

In some embodiments, the management operation in the foregoing embodiment further includes an installation operation; the application management method further includes: uploading an application file package of the Tomcat specification to the Tomcat server.

In some embodiments, the management operations in the foregoing embodiments further include an upgrade and/or a rollback operation; managing the corresponding application deployed on the Tomcat server further includes: uploading a user-developed upgrade package and/or rolling back the package to The Tomcat server upgrades and/or rolls back the corresponding application.

The present invention will be further explained in conjunction with specific application scenarios.

Third embodiment:

The purpose of this embodiment is that the user can customize the management mechanism of the Tomcat server, and implement the call management based on the JMX (Java Management Extensions) protocol on the remote Tomcat server in the customized system. Flexible management of applications. Through JMX technology, remotely call the MBean (that is, the device) provided by Tomcat, and perform separate operations on the application deployed on the Tomcat server, such as: deploy, start, stop, delete, and so on. For servers using the JMX framework, any object that needs to be managed is a device, MBean, which can be managed using the proxy layer, the MBeanServer. After the application is deployed to the Tomcat server, registering the MBean with the MBeanServer of the Tomcat server is done by the Tomcat server.

Compared with the prior art, the embodiment of the present invention can directly process the application that needs to be operated, and minimize the impact and risk of the operation, if the application is upgraded on a certain Tomcat and does not need to stop the entire Tomcat. . For example, a user has three applications on the Tomcat server, which correspond to different services. When upgrading a service, if you need to stop all services according to the existing management method, if the application is large, it needs to consume a large amount of time. Time, and also affects the non-upgraded service usage. After the method of the embodiment of the present invention is used, an application needs to be upgraded, and only the corresponding management platform is stopped, the corresponding application is stopped, and the application is upgraded. “Open” can save the time and cost and reduce the operational risk without stopping and starting the entire Tomcat server.

In this embodiment, the schematic diagram of the application management system provided by the present invention is shown in FIG. 3, which includes: JMX Manager (Administrator) 1, that is, the application management device 1, Tomcat2, and Web Browser provided by the present invention (Web browsing) 3) SNMP (Simple Network Management Protocol) Manager4; wherein Tomcat2 includes a plurality of device MBeans 21, a device proxy layer MBeanServer22, and an external interface (Adapter, which converts an interface of a class into what the client expects An interface that allows two classes that could not work together due to interface mismatch to work together. RMI (Remote Method Invocation) Adapter231, HTTP (HyperText Transfer Protocol) Adapter233 and SNMP Adapter234. In this embodiment, the application state transition provided by the present invention is as shown in FIG. 4, and may include operations such as opening, closing, loading, uninstalling, upgrading, and rolling back.

Now take the Linux operating system as an example, use the Tomcat server, set to automatically deploy the application. mode.

Install the Tomcat application. The Tomcat server has the installation management application provided by this method. The application provides "loading", "unloading", "closing", and "opening" operations.

The "loading" corresponds to the background JAVA to obtain the MBeanServer object of the Tomcat server. According to the managed application name, the MBean registered by the application on the MBeanServer is obtained, and the MBean is remotely called by the RPC (Remote Procedure Call Protocol). Interface method, copy the application file package to the web application Webapp directory, and call the stop application method in the MBean. After the method is successfully executed, the application state is loaded, that is, the system file is in the application server, but the service is unavailable and cannot be accessed. .

The "uninstall" corresponds to the background JAVA to obtain the MBeanServer object of the Tomcat server, according to the managed application name, obtain the MBean registered by the application on the MBeanServer, remotely invoke the uninstall application method provided by the MBean through the RPC, stop the application service, and delete the application. file. Application files are not retained.

For the application that is not "uninstalled", click "Open", corresponding to the background JAVA to obtain the MBeanServer object of the Tomcat server, according to the managed application name, get the MBean registered by the application on the MBeanServer, and remotely pass the RPC. Call the open application method provided by the MBean to set the application service to be available. In this case, the application can be accessed normally through the browser.

The "closed" for the "on" state of the application, click "close", corresponding to the background JAVA to obtain the MBeanServer object of the Tomcat server, according to the managed application name, get the MBean registered by the application on the MBeanServer, remotely call through RPC The MBean provides a method to stop the application, and the application service is set to be closed. At this time, the application cannot be accessed through the browser. The application file remains on the server.

The first time you install a new application, the user prepares the war package that needs to be deployed according to the Tomcat specification. Click “Load” to upload it to the Tomcat server. At this time, the application status is disabled by default. Go to the Webapp directory of the Tomcat server and you can see that the application war package has been automatically decompressed. And generate a new directory, the directory name is the file name of the package. At this point, you can perform the "uninstall", "open" operation

After the application is loaded, click “Open”. At this time, the application is in the service available state, and the application can be normal through the browser. At this point, you can perform the "close" and "uninstall" operations.

After the app is opened, click "Close", the app is in the service off state, and the app cannot be accessed through the browser. Looking at the Webapp file under Tomcat, the application files and directories still exist, indicating that the service was stopped. At this point, you can perform the "open" and "uninstall" operations.

Click "Uninstall", the application has been uninstalled, the application cannot be accessed through the browser, and the application related files are also deleted under the Webapp directory under Tomcat. "Unloading" is irreversible. After the "uninstallation" is completed, no operations can be performed.

In combination with "off" and "on", this embodiment can expand the "upgrade" and "rollback" interfaces, and can define the upgrade package specification for the user. The user uploads the upgrade or user back developed by the user through the method provided by the system. Roll the package to upgrade or roll back the application.

In summary, through the implementation of the present invention, at least the following beneficial effects exist:

The embodiment of the present invention provides an application management method, and manages a corresponding application deployed on a Tomcat server according to a JAVA management extension protocol according to a management operation, and an application on a Tomcat server in a framework based on the JAVA management extension protocol. All of them exist as a single device. On this basis, if you upgrade an application on a Tomcat and do not need to stop the entire Tomcat, you can separately process the application that needs to be operated, and the impact and risk of the operation. Minimized, enabling separate management of applications, reducing application management costs.

Embodiments of the present invention also provide a computer readable storage medium storing computer executable instructions for performing any of the methods described above.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware, such as a processor, which may be stored in a computer readable storage medium, such as a read only memory, disk or optical disk. Wait. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program in a storage and a memory by a processor. / instruction to achieve its corresponding function. The invention is not limited to any specific form of combination of hardware and software.

The above is only a specific embodiment of the present invention, and is not intended to limit the present invention in any way. Any simple modification, equivalent change, combination or modification of the above embodiments in accordance with the technical spirit of the present invention is still in the present invention. The scope of protection of the technical solution of the invention.

Industrial applicability

The above technical solution realizes separate management of applications, thereby reducing application management costs.

Claims

An application management method, including:

Receiving management operations based on the JAVA management extension protocol;

According to the management operation, the corresponding application deployed on the Tomcat server is managed based on the JAVA management extension protocol.
The application management method according to claim 1, wherein the management operation comprises a shutdown operation; and the managing the corresponding application deployed on the Tomcat server comprises:

Obtain the device proxy layer object of the Tomcat server through the background JAVA, obtain the device registered by the corresponding application on the device proxy layer according to the managed application name in the obtained device proxy layer object, and remotely invoke the stop provided by the device through the remote procedure call protocol. The application method is to set the application service of the corresponding application to be closed.
The application management method according to claim 1, wherein the management operation comprises an opening operation; and the managing the corresponding application deployed on the Tomcat server comprises:

Obtain the device proxy layer object of the Tomcat server through the background JAVA, obtain the device registered by the corresponding application on the device proxy layer according to the managed application name in the obtained device proxy layer object, and remotely invoke the device to provide the opening through the remote procedure call protocol. Application method, setting the application service of the corresponding application to be available.
The application management method according to claim 1, wherein the management operation comprises a loading operation; and the managing the corresponding application deployed on the Tomcat server comprises:

Obtain the device proxy layer object of the Tomcat server through the background JAVA, obtain the device registered by the corresponding application on the device proxy layer according to the managed application name in the obtained device proxy layer object, and remotely invoke the interface provided by the device through the remote procedure call protocol. Method, copy the application file package to the network application directory, and call the stop application method provided by the device, and set the application service of the corresponding application to be loaded.
The application management method according to claim 1, wherein the management operation comprises an uninstall operation; and the managing the corresponding application deployed on the Tomcat server comprises:

Obtain the device proxy layer object of the Tomcat server through the background JAVA, according to the obtained device The managed application name in the proxy layer object is obtained by the corresponding application registered on the device proxy layer, and the remote application call protocol remotely invokes the uninstall application method provided by the device, stops the application service, and deletes the application file.
The application management method according to any one of claims 1 to 5, wherein the management operation further comprises an installation operation; the application management method further comprises:

Upload the Tomcat-specific application package to the Tomcat server.
The application management method according to claim 6, wherein the management operation further comprises an upgrade and/or a rollback operation; and the managing the corresponding application deployed on the Tomcat server further comprises:

Upload the user-developed upgrade package and/or rollback package to the Tomcat server to upgrade and/or roll back the corresponding application.
An application management device comprising:

a receiving module configured to receive a management operation based on a JAVA management extension protocol;

The management module is configured to manage the corresponding application deployed on the Tomcat server according to the JAVA management extension protocol according to the management operation.
The application management apparatus according to claim 8, wherein said management operation comprises a shutdown operation; said management module is configured to acquire a device proxy layer object of the Tomcat server, according to the managed application in the obtained device proxy layer object Name, get the device registered on the device proxy layer corresponding to the application, remotely invoke the stop application method provided by the device through the remote procedure call protocol, and set the application service of the corresponding application to be closed.
The application management apparatus according to claim 8, wherein said management operation comprises an open operation; said management module is configured to acquire a device proxy layer object of the Tomcat server, according to the managed application in the obtained device proxy layer object Name, obtain the corresponding device registered on the device proxy layer, remotely invoke the open application method provided by the device through the remote procedure call protocol, and set the application service of the corresponding application to be available.
The application management apparatus according to claim 8, wherein said management operation comprises a load operation; said management module is configured to acquire a device proxy layer object of the Tomcat server, according to the managed application in the obtained device proxy layer object Name, get the device registered on the device proxy layer corresponding to the application, remotely invoke the interface method provided by the device through the remote procedure call protocol, copy the application The file package is sent to the network application directory, and the stop application method provided by the device is called, and the application service of the corresponding application is set to be loaded.
The application management apparatus according to claim 8, wherein said management operation comprises an uninstall operation; said management module is configured to acquire a device proxy layer object of the Tomcat server, according to the managed application in the obtained device proxy layer object Name, get the device corresponding to the application registered on the device proxy layer, remotely invoke the uninstall application method provided by the device through the remote procedure call protocol, stop the application service, and delete the application file.
The application management apparatus according to any one of claims 8 to 12, wherein the management operation further comprises an installation operation; the management module is further configured to upload an application file package of the Tomcat specification to the Tomcat server.
The application management apparatus according to claim 13, wherein said management operation further comprises an upgrade and/or a rollback operation; said management module is further configured to upload an upgrade package developed by the user and/or a rollback package to the Tomcat server, corresponding to The application is upgraded and/or rolled back.
An application management system, comprising a Tomcat server, and an application management device according to any one of claims 8 to 14, wherein the application management device deploys to the Tomcat server based on a JAVA management extension protocol according to a management operation. The corresponding application on the management.