CN101221498A - A system and method for managing business modules - Google Patents

Abstract

The present invention relates to a system for managing business modules, including a plug-in manager, and the plug-in manager specifically includes: a container server, which includes a plurality of Java business modules, and is used for decoupling Java components and managing Java business modules The life cycle and dependency relationship; the Java management extension server, which is used to provide multiple management interfaces, and manage the Java business modules through the management interfaces. The invention also discloses a method for managing the business modules at the same time. The implementation of the present invention makes the management, calling and deployment of the business modules more convenient and reduces the complexity of development.

Description

A system and method for managing business modules

technical field

The present invention relates to the Java technology of software development, more specifically, to a system based on Java Management Extension (JMX for short) and inversion of control (Inversinon of Control, IoC for short) container to manage business modules and method.

Background technique

In Java technology, a component (Bean) is a reusable Java business module based on the Java software component model (JavaBeans). In components, a "method" is a module of code that produces the behavior of an object instance, and is similar to a function in procedural programming languages. In order to define a method, the component provider must declare the method and then implement its body. The client can obtain and set the properties of the component by calling the method of the component, and complete various operations on the component.

In the definition of Java management extension, the management component (MBean, MBean is the abbreviation of Managed Bean), which provides a series of methods for managing components, and the management component server (MBeanServer) is responsible for managing a series of management components.

The inversion of control container is used to decouple components and manage the life cycle and dependencies of Java business modules, so that the configuration and dependency specifications of the application are separated from the actual application code. The currently well-known inversion of control containers include: Pico Container, Avalon Container, Spring Container, JBoss Container, HiveMind Container, Enterprise Java Component (EJB) Container, etc.

Plug-in Architecture, as a pluggable architecture, makes it easier for software modules to be assembled according to specific requirements, thus making software development more componentized and modularized.

In the prior art, Eclipse (Eclipse is a Java development tool) generally adopts Open Service Gateway Initiative (OSGi for short) as its plug-in architecture. The Open Service Gateway specification defines a standard, component-oriented computing environment for network services, which is divided into sub-modules (Bundle) and services (Service), mainly through the module manager to manage the life cycle of the module, and the service is the The external service object of the module, so as to realize the separation of management and static structure.

However, due to the insufficient definition of the management mechanism of the open service gateway, there is a lack of a complete management mechanism like the Java management extension, and the definition of the messaging mechanism between modules is insufficient. Only the monitoring mechanism of the framework, modules, and services is defined. However, other modules cannot be notified. In addition, the open service gateway is based on an embedded system, and if it is migrated to an enterprise-level application, there will be performance problems.

Another solution in the prior art is a plug-in architecture based on Java management extension and inversion of control, which mainly uses the function of dynamic loading of the existing inversion of control module and uses Java management extension to provide a complete management mechanism to realize the module management, call, deployment, etc. For example, every time a method is defined, the Java management extension must declare the method, and call the method of the component to obtain and set the properties of the component, and complete various operations on the component.

However, because the Java management extension technology is too complicated, it takes a long time for general developers to master the Java management extension technology. Moreover, there are many types of IOC container architectures that are incompatible with each other, and most of them are open source frameworks. There are problems with stability and service sustainability, which makes the plug-in architecture related to the IOC container architecture and increases the portability. the complexity.

Contents of the invention

The technical problem to be solved by the embodiments of the present invention is that the above-mentioned open service gateway management mechanism in the prior art is insufficiently defined, and the Java management extension technology is complex and the structure stability and sustainability of the control inversion container have problems, etc. A system and method for managing business modules are provided.

The technical solution adopted by the embodiments of the present invention to solve its technical problems is: a method for managing business modules, said method comprising the following steps:

a. The Java management extension server receives the service request;

b. The Java management extension server sends the service request to the container server;

c. The container server generates a corresponding service module according to the service request;

d. The container server manages the service modules.

The embodiment of the present invention also discloses a system for managing business modules, including a plug-in manager, and the plug-in manager specifically includes:

The Java management extension server is used to receive the service request and send the service request;

The container server is configured to receive the service request, generate a corresponding service module according to the service request, and manage the service module.

Implementing the embodiment of the present invention can reduce the complexity of software development plug-ins, reduce the complexity of Java management extension technology, and encapsulate the control inversion container mechanism inside the framework, so that the module does not depend on specific control inversion Containers, thereby reducing the risk of using open source inversion of control container software, making the management, calling, and deployment of business modules more convenient, and reducing the complexity of development.

Description of drawings

The present invention will be further described below in conjunction with accompanying drawing and embodiment, in the accompanying drawing:

Fig. 1 is the frame structure schematic diagram that the present invention manages business module;

Fig. 2 is the flow chart that the present invention manages business module;

Fig. 3 is the schematic diagram of the life cycle of the manageable unit that the present invention manages Java component;

Fig. 4 is a sequence diagram of the status change of the service module according to the present invention.

Detailed ways

In order to make the purpose, technical solution and advantages of the present invention clearer, the present invention will be described in detail below through examples and with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a framework structure of a preferred embodiment for managing business modules, as shown in the figure. A system for managing business modules, including a plug-in manager (UniBeanManager), which includes a container server (such as IoC Server) and a Java management extension server (JMXServer), that is to say, the plug-in manager itself encapsulates the container Server and Java management extension server, the main framework of the system is composed of container server and Java management extension server. The Java management extension server is used to receive the service request and send the service request; the container server is used to receive the service request, generate a corresponding service module according to the service request, and manage the service module.

Among them, the container server includes multiple Java business modules, and is used to decouple the Java components and manage the life cycle and dependencies of the Java business modules. Each business module specifically includes one or more manageable units (UniBean), and each manageable unit includes a manageable unit interface module for managing the life cycle of the business module.

The manageable unit interface module specifically includes: a startup module, which is used to provide a method for starting the service module; a stop module, which is used for providing a method for stopping the service module; an installation module, which is used to provide a method for A method for installing a module; an uninstall module for providing a method for uninstalling the service module; a suspend module for providing a method for suspending the service module.

Wherein, the Java management extension server is used to provide multiple management interfaces, and manage the Java business modules through the management interfaces. The Java management extension server specifically includes multiple management components (MBeans). Each management component provides a method for managing Java components. The management component completes the management of the business module by calling the manageable unit interface module.

The working process of each of the above modules will be described in detail below through the method for managing business modules according to the present invention.

A method for managing business modules, as shown in Figure 2, the method includes the following steps:

Step S1: the Java management extension server receives the service request. Since the Java management extension provides a set of standard management interfaces, the management components in the Java management extension can complete the management of the Java business modules.

Step S2: The management component in the Java management extension server sends the service request to the container server through the management interface. The container server contains multiple business modules, and each business module is generated and maintained by the container server.

Step S3: The container server generates a corresponding business module according to the service request, and each business module is loaded with multiple manageable units. The container server can generate an instance of the manageable unit through inversion of control according to the configuration file that records the class information and class name of the manageable unit.

Step S4: The manageable interface module in the manageable unit manages the life cycle of the service modules (including dynamic loading, modification, deletion, etc. of the service modules).

Since the manageable unit includes a series of manageable interface modules, such as starting module, stopping module, installing module, uninstalling module, suspending module, suspending module, etc., the management, calling, and Deployment is more convenient.

Among them, in the embodiment of the present invention, the lifecycle management interface method defined for the manageable unit interface module is as follows:

UniBeanLifeCycle //Lifecycle management interface

public interface UniBeanLifeCycle

{

public void start()throws Exception;//Define the method of starting the business module

public void stop()throws Exception;//Define the method of stopping the business module

public void install() throws Exception;//Define the method of business module installation

public void uninstall()throws Exception;//Define the method of uninstalling business modules

public void dofail();//Define the method of suspending the business module

}

FIG. 3 is a schematic diagram of the life cycle of a manageable unit for managing Java components in the present invention, as shown in the figure. A manageable unit is installed through the installation module, after the installation is successful, it is started by the start module, stopped by the stop module, and finally deleted by the uninstall module. If an abnormal situation occurs in the above process, the suspend module can be called to handle the corresponding exception.

The working process of starting the service module will be described in detail below with a specific embodiment.

When the system is started, the container server is first started, and the container server generates an instance of the manageable unit through inversion of control according to the configuration file that records the class information and class name of the manageable unit. Since the plug-in manager will give each manageable unit a unique identifier, a manageable unit can have multiple runtime instances. At this point, each manageable unit is in a state of completion of installation, that is, a state of completion of loading.

Then, use the functions provided by the Java management extension server to complete the start-up operation of each manageable unit according to the above configuration file. If the start of the manageable unit is completed, it will enter the running state. If each manageable unit in the business module is started successfully, it means that the business module has also been started successfully. After the start-up of the business modules that need to be started is completed, the start-up of the entire system ends. However, if an exception occurs in the above process, the suspension method defined by the management unit needs to be called to handle the corresponding error.

However, in the above, if the business module that a certain business module depends on is not installed, then the dynamic proxy (Dynamic Proxy) method can be used to complete the call between business modules, so that even if the business module that a certain business module depends on is not installed, only The dependent part of this business module is affected, and other parts are not affected.

Dynamic proxy is a feature of the Java language. The basic principle of dynamic proxy technology is to scan all public methods of the proxy class, and automatically generate a class inherited from the proxy class, and then override these public methods in the generated class.

Fig. 4 is the sequence diagram of the business module state change that the present invention manages Java component, as shown in the figure:

Step 1: When the business module needs to be installed.

Step 2: The business module manager first calls the container server to generate an instance of a corresponding manageable unit.

Step 3: The management component server of the Java management extension finds the corresponding management component.

Step 4: Call the installation method of the manageable unit to complete the installation of the business module.

Step 5: When the business module needs to be started.

Step 6: The management component server of the Java management extension finds the corresponding management component.

Step 7: Call the start method of the manageable unit to complete the start of the business module.

Step 8: When the business module needs to be stopped,

Step 9: The management component server of the Java management extension finds the corresponding management component.

Step 10: Call the stop method of the manageable unit to complete the stop of the business module.

Step 11: When the business module needs to be uninstalled.

Step 12: The management component server of the Java management extension finds the corresponding management component.

Step 13: call the unloading method of the manageable unit to complete the unloading of the business module.

Step 14: At the same time, the container server is notified to log out the corresponding manageable unit instance.

In summary, because the embodiment of the present invention reduces the complexity of the Java management extension technology, the Java management extension is transparent to the developers of the business modules, reducing the complexity of software development; moreover, because the container is encapsulated inside the framework The mechanism makes business modules independent of specific containers (such as IoC containers), thereby reducing the risk of using open source software.

Therefore, the present invention makes full use of the perfect management mechanism provided by the Java management extension and the dynamic loading function of the business module of the container (such as the IoC container), making the management, calling and deployment of the business module more convenient.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of the present invention. included.

Claims (14)

1. the method that business module is managed is characterized in that, described method comprises the following steps:

A, Java administration extensions server receive services request;

B, described Java administration extensions server send to the container server with described services request;

C, described container server generate a corresponding business module according to described services request;

D, described container server manage described business module.

2. the method that business module is managed according to claim 1 is characterized in that, described step b is specially:

Described its Management Unit of Java administration extensions server calls sends to the container server by management interface with described services request.

3. the method that business module is managed according to claim 1 is characterized in that, described steps d is specially:

But but the administrative unit in the business module of described container server is carried out life cycle management by its management interface module to described business module.

4. the method that business module is managed according to claim 3, it is characterized in that, but but the administrative unit in the business module of described container server by its management interface module the step that described business module carries out life cycle management is specifically comprised:

The step of d1, the described business module of startup;

D2, stop the step of described business module;

D3, the step that described business module is installed;

The step of d4, the described business module of unloading;

The step of d5, the described business module of hang-up.

5. the method that business module is managed according to claim 4 is characterized in that, described steps d 1 specifically comprises:

The Management Unit whois lookup of d11, Java administration extensions is to corresponding Management Unit;

But d12, the startup module of calling administrative unit are finished the startup of module.

6. the method that business module is managed according to claim 4 is characterized in that, described steps d 2 specifically comprises:

The Management Unit whois lookup of d21, Java administration extensions is to corresponding Management Unit;

But d22, the stopping modular that calls administrative unit are finished stopping of module.

7. the method that business module is managed according to claim 4 is characterized in that, described steps d 3 specifically comprises:

But d31, call the example of a corresponding administrative unit that produces in the container server;

The Management Unit whois lookup of d32, Java administration extensions is to corresponding Management Unit;

But d33, the installed module that calls administrative unit are finished the installation of business module.

8. the method that business module is managed according to claim 4 is characterized in that, described steps d 4 specifically comprises:

The Management Unit whois lookup of d41, Java administration extensions is to corresponding Management Unit;

But d42, the discharging method that calls administrative unit are finished the unloading of module, but and notify the container server to carry out corresponding administrative unit example cancellation work simultaneously.

9. the method that business module is managed according to claim 4 is characterized in that, when the management to described business module occurs when unusual, and execution in step d5, described steps d 5 specifically comprises:

But but call the hang-up module of the management interface module of described administrative unit, described business module is carried out corresponding error handle.

10. the method that business module is managed according to claim 1 is characterized in that, described method further comprises step:

Also do not finish corresponding operation when another business module that business module relied on, then adopt the mode of dynamic proxy to finish calling between the described business module.

11. the system that business module is managed comprises plugin manager, it is characterized in that, described plug-in management implement body comprises:

Java administration extensions server is used to receive services request, and sends described services request;

The container server is used to receive described services request, generates the corresponding business module according to described services request, and described business module is managed.

12. the system that business module is managed according to claim 11 is characterized in that, but described each business module specifically comprises one or more administrative units;

But but described each administrative unit comprises an administrative unit interface module that is used to manage described business module life cycle.

13. the system that business module is managed according to claim 12 is characterized in that, described Java administration extensions server specifically comprises a plurality of Management Units;

Described each Management Unit is finished management to described business module but be used for calling described administrative unit interface module by its management interface.

14., it is characterized in that, but described administrative unit interface module specifically comprises according to claim 12 or the 13 described systems that business module is managed:

Start module, be used to start described business module;

Stopping modular is used to stop described business module;

Installed module is used to install described business module;

Unload module is used to unload described business module;

Hang up module, be used for management at described business module and occur hanging up described business module when unusual.

Images