CN101222371A - Client Component Operations Management System - Google Patents

Abstract

The invention discloses a client component operation management system, which can solve the problems of poor component interface expression and inability to perform security check on loaded components existing in the existing client webstart environment. The invention uses .net as the basic platform to construct a client component operating environment under the windows platform to form a client component operation management system. The client is built with a component acquisition module, a component loading module, a component verification module and a component management module. On the one hand, the present invention supports the client to dynamically load specified components on demand from the Internet or locally; Component performance; on the other hand, by passing user information to components to perform security verification, users can only access business components that they can access, effectively avoiding information leakage.

Description

Client Component Operations Management System

technical field

The invention relates to a client system, in particular to a client component operation management system, which belongs to the technical field of computer applications.

Background technique

Current network applications generally adopt the distributed computer architecture of client/server mode. Multiple clients can load components from the same server, and then run the loaded components in the client's operating environment to meet customer needs. Components usually refer to business components, such as Microsoft's COM components and SUN's EJB components. Different component systems depend on different component operating environments. With the development of computers and the improvement of customer needs, the existing component operating environment gradually presents its own disadvantages, for example, the interface affinity, operability and performance of the components running on the Java webstart environment and the native programs of the windows system There is a large distance; on the other hand, the webstart environment does not perform security checks on the loaded components, and it is impossible to know whether the user can load the component, and the user can access the business components at will, which has hidden dangers of information leakage; The environment cannot initialize the loaded and running components, and the data required by the components to run is completely obtained by the components themselves from other systems, which virtually increases the number of network and disk accesses.

.net is a development platform launched by Microsoft, which supports multiple languages. The winform of the .net platform is based on the interface of the windows local program, supported by many interface components, the interface aesthetics and user operability have great advantages compared with the swing framework of the non-local program.

Contents of the invention

The present invention solves the problem of poor interface affinity of components on the webstart environment existing in the prior art and no safety verification of loaded components, and constructs a client component operation management system under the windows platform based on .net, providing Component hot-swappable, dynamic deployment operation management system.

In order to solve the above-mentioned technical problems, the present invention adopts the following technical solutions to achieve:

It includes a client and a server. The client loads components from the server and runs the components in the corresponding operating environment of the client. It is characterized in that the client has the following built-in modules:

A1, component acquisition module: acquire the configuration file transmitted from the server, the configuration file contains the attribute parameters of the component;

A2. Component loading module: load the components required by the client;

A3. Component verification module: verify the identity and authority of the client user;

A4. Component management module: manage the loading and running process of components.

In the technical solution of the present invention, it also has the following technical features: the attribute parameters include server address, component name and component main boot program name, and the component acquisition module obtains the module information to be loaded according to these parameters, and stores the module in The directory where the running environment program is located.

In the technical solution of the present invention, it also has the following technical features: the component loading module accesses the directory where the operating environment is located according to the component name and the component main boot program name transmitted from the server, searches for the component corresponding to the component name, and loads The code segment with the same name as the main boot program in this component; after the component loading module loads the component, the obtained initialization parameter is passed to the component, and the component is initialized according to the incoming parameter; the initialization parameter includes the operating environment itself parameters, parameters entered by the user, and parameters specified in the configuration file.

In the technical solution of the present invention, it also has the following technical features: the component verification module transmits the user identity and authority information to the successfully initialized component, and the component checks whether the user can access the component according to the user information.

In the technical solution of the present invention, it also has the following technical features: the component management module displays the verified component on the computer screen, and clears the component after the component is closed.

In the technical solution of the present invention, it also has the following technical features: the server address includes a local file path and a network file path.

In the technical solution of the present invention, it also has the following technical features: the running forms of the components in the running environment include non-mode running and mode running.

In the technical solution of the present invention, it also has the following technical features: the running environment of the client component is based on the .net platform.

Compared with the prior art, the advantages and positive effects of the present invention are as follows: the present invention forms the client component operation management system with the . The windows system and the environment above .net 2.0 support the dynamic on-demand loading of specified components from the Internet or locally; on the other hand, after loading the components, the components are specified according to the parameters of the client's operating environment, the parameters entered by the user, and the configuration file. parameters to initialize itself, reducing the number of accesses to the network and disk, and optimizing component performance; on the other hand, the user information for operating RCMR is passed to the component to perform security verification, so that users can only access the business components that they can access, effectively Information leakage is avoided.

Description of drawings

FIG. 1 is a flow chart of loading and running components by a client in the client component operation management system.

Detailed ways

The present invention will be described in further detail below in conjunction with the accompanying drawings.

First introduce the basic principle of the present invention: the client has four main modules built in, and the name, function and working process of each module are described in detail as follows:

A1. Component acquisition module

This module obtains the corresponding file according to the server address attribute parameter in the incoming configuration file. The server address includes two forms of file paths, the local file path such as "D:/fileName" and the network file path such as "http://192.168.0.1:8082/fileName", wherein the network file path is based on the HTTP protocol. The configuration file also includes attribute parameters such as component name and component main boot program name, and the component obtaining module obtains the module information to be loaded according to these parameters, and stores the module into the directory where the operating environment program is located.

A2. Component loading module: The component loading module loads components according to the following steps:

1. Store the binary code file obtained from the component acquisition module into the directory where the running environment program is located.

2. Pass the name of the component to be loaded and the main bootloader of the component into the component loading module. The component loading module searches for the component corresponding to the component name from this directory according to the name of the incoming component and the main bootloader of the component, and loads the component. The code segment with the same name as the main boot program in the component, here is to call the system function of the .net framework.

3. The running environment obtains the loaded component, and passes the obtained parameters to the component to initialize the component. These parameters include the parameters of the running environment itself, the parameters entered by the user, and the parameters specified in the configuration file.

The component loading module can load the component according to the component file obtained from the component obtaining module, and the module calls the dynamic loading function of .net. All modules that can be loaded need to be a .net standard component, and the component must implement the dynamic loading component interface, which includes functions such as initializing the component, security verification, displaying the component in a modal dialog box, closing the component, etc. The runtime environment passes in parameters in XML format through this interface.

A3. Component Verification Module

After the component initialization is completed, the component verification module passes the user identity and authority information to the successfully initialized component, and the component verifies whether the user can access the component according to the user information. If the user cannot use the component, the component throws an exception, and the runtime environment will unload the module.

A4, component management module

After the components are loaded and verified, the component management module calls related functions to display the components on the computer screen.

After the component is closed, the component management module calls related functions to clear the resources maintained by the component itself, and then clears the component.

Figure 1 shows the flow chart of the .net-based client loading and running components. The specific execution process is as follows:

S01: The RCMR obtains the information of the program components to be loaded, and the information is automatically generated by the application system through the application of the user.

S02: Access the Internet or locally to obtain the components to be loaded. In this step, the loading component is obtained through the component acquisition module, and the component acquisition module can access the local file path or the network file path.

S03: RCMR loads the program component, and calls the initialization function of the component. RCMR passes the environment itself and the parameters entered by the user, or the parameter information specified in the configuration file transmitted from the server to the component. These parameters must be parameters in XML format.

S04: The program component initializes itself according to the input initialization parameters.

S05: RCMR invokes the check function of the component to pass in user information to perform authority verification. User information includes user code, user role, and user authority.

S06: The program component checks whether the user can access the component according to the incoming user information. If the user cannot access the component, an exception will be thrown, and the operating environment will uninstall the component; if it can be accessed, the component management module calls the system function, Display the components on the computer screen, and proceed to step S07.

S07: The RCMR runs the user component, and the RCMR supports two running modes: non-mode running and mode running. In a modal window, the parent window of the window cannot be edited, and in a non-modal window, the parent window of the window can also be edited.

S08: The user operates the component, processes the information; closes the component after processing.

S09: RCMR cleans up component data, and after the component is closed, the component management module clears the component.

The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention to other forms. Any skilled person who is familiar with this profession may use the technical content disclosed above to change or modify the equivalent of equivalent changes. Example. However, any simple modifications, equivalent changes and modifications made to the above embodiments according to the technical essence of the present invention without departing from the content of the technical solution of the present invention still belong to the protection scope of the technical solution of the present invention.

Claims (10)

1. a client terminal component operation management system comprises the client and server end, client from the server end charging assembly and the corresponding running environment of client operating component, it is characterized in that described client is built-in with following module:

A1, assembly acquisition module: obtain the configuration file that server end transmits, described configuration file includes the property parameters of assembly;

A2, assembly load-on module: load the assembly that client needs;

A3, component verification module: identity and authority to the client user are carried out verification;

A4, assembly management module: the loading of Management Unit and running.

2. client terminal component operation management system according to claim 1, it is characterized in that, described property parameters comprises server address, component Name and assembly main bootstrap program name, the module information that the assembly acquisition module will load according to these parameter acquiring, and assembly is deposited into the catalogue at running environment program place.

3. client terminal component operation management system according to claim 2, it is characterized in that, component Name and assembly main bootstrap program name that described assembly load-on module transmits according to server end, the catalogue at visit running environment place, the assembly of searching and component Name correspondence loads code segment identical with the main bootstrap program name in this assembly; Behind the assembly load-on module charging assembly, the initiation parameter that obtains is passed to described assembly, described assembly carries out initialization according to the parameter of importing into; Described initiation parameter comprises the parameter of running environment self, the parameter of user's typing, and designated parameters in the configuration file.

4. client terminal component operation management system according to claim 3, it is characterized in that, described component verification module passes to the assembly of initialization success with user identity and authority information, and whether described assembly can visit this assembly according to the user profile verified users.

5. client terminal component operation management system according to claim 4 is characterized in that, the assembly after described assembly management module will be verified is presented on the computer screen, and after assembly is closed assembly is removed.

6. according to each described client terminal component operation management system among the claim 2-5, it is characterized in that described server address comprises local file path and network file path.

7. according to each described client terminal component operation management system among the claim 1-5, it is characterized in that the form that described assembly moves comprises non-mode operation and mode operation in running environment.

8. client terminal component operation management system according to claim 6 is characterized in that the form that described assembly moves comprises non-mode operation and mode operation in running environment.

9. according to the described client terminal component operation management system of claim 7, it is characterized in that described client component running environment is based on the .net platform.

10. described according to Claim 8 client terminal component operation management system is characterized in that described client component running environment is based on the .net platform.