KR20040041138A - Method for automatic mapping version and client module distribution according to distributed server - Google Patents

Abstract

PURPOSE: A method for distributing a client module and automatically mapping a version by a distributed server is provided to minimize a system influence due to the technical advancement of the client module for the development and the expansion of a server system by basically removing dependency between the versions of the client module, and reducing a load for system maintenance. CONSTITUTION: A version verifier in the activated client obtains the information for a basic distribution server according to the contents of the HTML(Hyper Text Markup Language)(ST201). An environment configuration information file is received/analyzed by connecting to the basic distribution server(ST202). It is checked that the module of the corresponding version is present by confirming the modules installed to the client. In case that the module to be installed is present, a list of the distributed distribution servers is obtained(ST204). The distributed distribution server that the environment configuration information file is identical with the environment configuration information file of the basic distribution server is decided by connecting to the distributed distribution server in the order of the list(ST205).

Description

Method for automatic mapping version and client module distribution according to distributed server}

The present invention relates to a method for automatically distributing and automatically mapping versions of a client module under the X Internet. In particular, the present invention relates to a plurality of identical client modules having different versions and automatically finds and executes a version of a required client module according to the configuration information of a server system. The present invention relates to a method for distributing client modules and automatic version mapping by a distributed distribution server.

Current Internet applications are generalized to applications of the HTML document generation level based on the World Wide Web (WWW) using the HTTP protocol. It is difficult to develop and manipulate the real-time interaction with the user at the client end due to the presentation of the static document. However, it is difficult to develop a system for transaction processing that requires the implementation of a complex enterprise business. There is a side. In order to overcome this problem and provide a rich user interface (UI), under the X Internet environment, clients beyond the display level of HTML such as Viewer or Player based on ActiveX or application programs Is running independently, and client modules that can interpret information, make self-determination, and respond to each other have emerged, and various models have been tested in various business systems.

In the above, the X Internet is an Internet application that was developed using only pure HTML and a web browser by using a set of control methods and steps. It refers to the architecture of next-generation Internet application software that enables the interaction with dynamic users that could not be provided.

Currently, the client-side interface for interacting with the user in the development of the majority of Internet applications implements the presentation logic using pure HTML and processes the presentation using a web browser such as Internet Explorer or Netscape. Pure HTML is a document format designed to distribute static material in document form to a random public. Therefore, due to the limitations of the static data representation of web browsers and pure HTML, the functions that can be processed in HTML are limited. Therefore, the user-side presentation and interaction functions that can handle various and complex transactions required for business processing Incomplete As a result, for SI projects or packaged products that develop Internet applications, limited functions in the presentation layer may not be able to implement desired functions, or even if they are implemented, a lot of time and money must be invested. Due to low satisfaction, the situation is appealing.

The X Internet overcomes the limited functions of the presentation layer in developing Internet applications, which are limited by the characteristics of pure HTML and web browsers, and the 4th generation languages such as Power Builder, Delphi, etc. It was developed to provide the same or advanced user interface as 4GL) provided. In particular, the functions and expression methods frequently used in general system integration project (SI) development or general ERP / statistics package, such as management information system (MIS) or statistical system, can be used without any task dependence. By providing various kinds of generalized components such as Grid, Menu, Tree at the system level, it improves the development productivity of Internet application and enables smooth and rich interaction with users.

1 is a flowchart illustrating a method of distributing a client module in a general Internet environment. Where ST stands for STEP.

As shown therein, after accessing a web page and receiving an HTML full text and interpreting it (ST101), acquiring version information of an ActiveX control of HTML (ST102), and installing active-X control Acquiring version information (ST103), downloading the changed ActiveX control (ST104), registering the active-X control to the system (ST105), and activating the active-X control ( ST106), and a step of displaying the page (ST107).

The method of distributing the client module in the general Internet environment made as described above will be described in more detail as follows.

First, in step ST101, a web browser is started on the client according to a user's instruction. When a specific URL is input, the web browser requests the URL from the web server and receives the HTML full text of the specified URL so that it is displayed properly before displaying it on the screen. Formatting is performed.

Next, in step ST102, if there is an <Object> tag in the HTML source in the formatting process, and the object described therein is an Active-X control, the web browser displays the version information of the Active-X control to be used from the contents of the tag. Will be extracted.

Thereafter, in step ST103, it is checked whether the Active-X control is already installed in the system, whether it is operating normally, and whether the version matches that of the intended use.

As a result of the check, if the Active-X control has never been installed in the system, or the version has been changed or is abnormally installed, the corresponding Active-X control is downloaded from the designated location of the web server in step ST104 and stored in the corresponding location.

In step ST105, the system registry is prepared to be used in all subsequent web browsers.

In addition, if the corresponding Active-X control is normally registered in the system in step ST106, the web browser activates and prepares the active-X control in preparation for displaying the HTML on the screen, and in step ST107, places it in the appropriate area of the screen. After displaying the page for users to view, they wait for the user's command for the next action.

The current method of distributing client modules has the advantage of simplicity and simplicity of deployment, while the user does not know any information about which modules are being downloaded, running normally, and so on. have. In addition, it always installs the latest version, so if you need to work with the previous version, there is a disadvantage that you can not respond unless you manually delete the system registry. And unless you are a professional developer working in computer business, it is not easy for ordinary computer users to work safely to delete the registered information from the system registry and install the desired version, and it is very dangerous behavior that can make the computer impossible to operate. It is also.

With the goal of providing real-time two-way communication and a variety of UIs, the client modules, which are rapidly spreading in a short period of time with Active-X control, have exploded in number as users request more advanced and diverse functions. Functions are rapidly strengthening and continuously improving and developing.

Due to the development and improvement of this function, the client module has been upgraded in its completeness, the application technology has been developed, and the version is upgraded from time to time. Once complete, only improvements and maintenance at the maintenance level are being made while retaining the technology and structure of the initial development for a significant period of time. As a result, a new server system for the same user can be developed by using a new version of the client module that is newly added or operates differently than before, with the server system developed for the function of the client module months or years ago. If you want to do this, the company's officials are always in trouble because of version matching issues in the client module. In spite of the more stable and new functions, whether the newly developed system should be used with the same limitations of the previous version of the client module, or adopt the latest function client module and develop the new system. At the same time, you have to worry about whether to reorganize the old system to meet the latest features.

Once the policy for the applicable version of the client module is determined through the above process, the service developers of the server re-develop the service according to the interface of the finally selected client module version. Distributed to. At this time, since the size of the client module is never small, the network traffic generated from a large number of users at once is not negligible as the size of the company grows, and it is difficult to secure the stability of the system according to the deployment. While there is no right to find an alternative.

In particular, the distribution of Active-X control for clients over the Internet is almost universally recognized as the standard way of downloading and installing Microsoft's Internet Explorer. Therefore, there is little choice for changing the distribution method. In addition, there are many difficulties in concentrating server resources and network traffic by a single distribution server, difficulty in coping with the speed of technology development by single version management, and securing installation reliability due to instability and inconsistency of registry information.

Therefore, the present invention solves the disadvantage of not knowing any information about which modules are being downloaded, running normally, etc. in the related art as described above, and always installs the latest version. It is suggested to solve the disadvantage that you can't do anything unless you delete the system registry manually.

The object of the present invention is to fundamentally independence the dependency between versions of the client module, and to reduce the maintenance burden of the server from the situation of the lack of client compatibility between server system services with different development time in accordance with the technology development speed of the client module In the X Internet environment to minimize the system impact of client module technology development and expansion in server system development and expansion by providing efficient operation of investment resources through distribution of network resources and network traffic for client module distribution To provide a way to distribute and automatically map versions of client modules.

The present invention for achieving the above object,

When the client accesses the basic server on the web (WWW) for the first time and downloads and installs the version verifier, or installs the version verifier through the installer and connects to the basic server through the web, the version verifier receives the configuration information from the basic distribution server. Verifies whether the specified client modules and versions required by the client exist in the client, and if the module of the version does not exist or is abnormal, executes module saver and downloads the client modules of the version from the distribution server to the designated area of the client. Save it. To do this, the module store is given a list of distributed distribution servers that it is allowed to access from the server distributor, and accesses the distributed distribution servers sequentially in the order specified from the server distributor, changing or existing ones specified in the system. All client modules that do not have one are downloaded and stored in the client's location. When the module store successfully saves all client modules to the client, the version verifier runs the module register to find the correct version of each module needed by the system, registers it with the client, and activates it. Automatically build an operating environment to operate. Client modules stored or activated in the client can be checked by the module manager, registered and deleted, and controlled to activate / deactivate specific versions of the module.

1 is a flowchart illustrating a method of deploying a client module in a general Internet environment.

Figure 2 is a block diagram showing the configuration of the distribution system and its peripheral portion in the X Internet environment to which the present invention is applied,

3 is an internal configuration diagram for automatic mapping of the client distribution module according to the present invention,

4 is a flowchart illustrating a method of distributing a client module and automatically mapping versions in the X Internet environment according to the present invention.

<Explanation of symbols for the main parts of the drawings>

100 ..... Web Browser

200 ..... Client

210 ..... Controls

220 ..... storage

230 ..... Register

240 ..... Management

300 ..... Server

310 ..... Default Deployment Server

320 ..... Distributed Deployment Server

Hereinafter, described in detail with reference to the accompanying drawings, preferred embodiments of the present invention according to the technical spirit as described above.

Figure 2 is a block diagram showing the configuration of the distribution system and its peripheral portion in the X Internet environment to which the present invention is applied.

Version control system for the present invention is largely composed of the server 300 and the client (200).

The server 300 has a basic distribution server 310 that manages the overall information of the client module distribution and superset of the client module, and temporarily stores and distributes the modules to be actually distributed, and delegates the basic distribution server 310. It is composed of a plurality of distributed distribution server 320 used to distribute the central processing unit (CPU) and the load of the network.

The client 200 is used by the web browser 100 to communicate with the basic distribution server 310 and to check whether the module is distributed or not, and the specific client module from the distributed distribution server 320. Storage unit 220 for downloading and permanently storing the version on the hard disk for each version, the registration unit 230 to intelligently register and remove the stored client module to the system for use, to manage and remove the client module registered and installed in the system It consists of a management unit 240 for.

3 is an internal configuration diagram for automatic mapping of a client distribution module according to the present invention.

Here, reference numeral 311 denotes an environment configuration information providing unit configured in the basic distribution server 310 and defining information about the client module to be distributed and the configuration of the distributed distribution server 320, and 321 denotes the distributed distribution server. A core module 321 configured at 320 is indicated, and reference numeral 322 denotes a client module configured at the distributed distribution server 320.

In addition, the controller 210 includes a version verifier 211, a server distributor 212, and a core installer 213, and the storage unit 220 is a client downloaded from the module store 221 and the distribution server 320. The module is composed of a client module storage unit 222 permanently stored in the client computer, the register unit 230 is composed of a module register 231 and a version information store 232 for managing the version information finally registered in the system. .

Referring to Figures 2 and 3 attached to the distribution system and its peripheral portion in the X Internet environment to which the present invention configured as described above is applied as follows.

First, the server 300 is composed of a basic distribution server 310 for managing the overall information on the list and distribution of the client module, and a distributed distribution server 320 for distributing network and system resources to distribute the client module to the client do.

Basic distribution server 310 refers to a server that is the center of the task of providing services of the server system to the users. As a server that a user accesses for business purposes, it is used as a basic unit for recognizing a version set of a client module and performs a function as a representative server for all distributed distribution servers 320. In order to distribute the load of the network, the download request of the client is redirected to the distributed distribution server 320, but it is also responsible for the final distribution when a problem occurs in the distributed distribution server 320.

The environment configuration information providing unit 311 of the basic distribution server 310 should define information about the client module to be distributed and information about the configuration of the distributed distribution server 320.

The basic components and structure are as follows.

[Installation Info]

Apply = 2003/06/02/15: 30

TimeZone = 9

Installer = 1,0,0,1

Description = Test Team 4

Installation Info represents a baseline and basic information on the basic deployment server 310 for installing and applying the client module 322 to the local computer.

Apply: Specify the date and time to apply the distribution based on the system time of the basic deployment server (310). If you connect before this time, the distribution information is ignored.

TimeZone: Represents a difference between the system time of the basic distribution server 310 and the universal time. In other words, in order to correct the difference in application according to the time difference between the region where the basic distribution server 310 is located and the user's location, the globally unified accurate time point for distributing the client module 322 based on the standard time is provided.

Installer: Shows information about the version of the core installer 213 in the control unit 210. Verify that the version is upgraded or inconsistent so you can download it again.

Description: Provides a name (alias) that is easy to understand, recognize, and access to the basic deployment server 310.

[Recent Component Version]

Dataset = data.cab: data.dll1,0,7,2: {3267EA0D-B5D8-11D2-A4F9-00608CEBEE49}

Report = rep.dll: 1,0,7,2: {37D13B2F-E5EB-11D2-973D-00104B15E56F}

Tr = tr.cab: tr.dll: 1,0,7,2: {0A2233AD-E771-11D2-973D-00104B15E56F}

It informs the list of client modules 322 to be distributed and the change status information. Information on the global identifier of the client module 322, such as the name of the client module 322, a compressed file to be distributed, and a file name, version, and class ID to be typically handled among a plurality of files, are described.

Secondary Server List

1.http: //gaxa.sift.co.kr/AU4/

2.http: //210.124.184.33/AU4/

3.http: //127.0.0.1/AU4/

4.http: // localhost / AU4 /

The distributed distribution server 320 is then described as a pair of aliases for the distributed distribution server 320 and a Home URL to access. It is not necessary for all the distributed distribution servers 320 to have the same access path as the directory on the web, but the directory structure below the home URL should be the same. In addition, the version or information of the environment configuration information file existing in the distributed distribution server 320 must match that of the basic distribution server 310, and if it is determined that the mismatch is not synchronized with the basic distribution server 310 It is supposed to ban distribution.

[Recommended Server # 01]

Region = 210.124.184; 210.124.192; 110.132.179;

Server = 1

[Recommended Server # 02]

Region = 210.124.184.33

Server = 1,2,3,4

A mapping table for automatically routing the distributed distribution server 320 according to a user's connection is defined. Specifies the IP reference region of the client to be applied for each alias of the distributed distribution server 320 and the list and order of the distributed distribution server 320 to which clients belonging to this region are basically connected. In addition, to distribute the CPU and network load of the basic distribution server 310 means a distribution server that is operated for the purpose of supporting the distributed distribution of the client module 322. The function of the web server should be provided, and the basic configuration to be prepared in the basic distribution server 310 should be built as it is.

Next, the client 200 will be described in detail.

First, the version verifier 211 in the control unit 210 is called after accessing the work server system and before moving to the first work page after the authentication process is completed. If the version verifier 211 is not installed, the web browser 100 automatically downloads from the basic distribution server 310 and installs it in the system directory according to the flowchart of FIG. 1, and records the corresponding information in the version information repository 232. do. When the web page is executed by receiving the information (URL) and execution method of the basic distribution server 310 as a factor, the version verifier 211 provides an environment provided by the environmental configuration information providing unit 311 from the basic distribution server 310 Download the configuration file and save it in a temporary directory. At this time, the current time of the basic distribution server 310 is also acquired. If the configuration information file received from the basic distribution server 310 is received for the first time or if there is a change from the existing one, the existing installation is deleted and replaced with a new one. If the first contact attempt after the application time point is compared with the time received from the basic distribution server 310 by checking the contents from the environment configuration information file, the version verifier 211 is the client module 322 described in the environment configuration information file. While checking the list of these, it is compared whether or not the client module 322 of the corresponding version is installed to check whether there is any client module 322 not installed.

If it is determined that at least one installation target client module 322 exists, the version verifier 211 determines whether to execute the download and installation automatically according to a given execution mode or to execute it manually according to the user's confirmation. If necessary, a window is displayed to check whether the user is running. If the user cancels the download, the operation ends at this stage.

If the user wants to install the version verifier 211 waits to download all the client modules 322 to be installed by the module storage 221 to download from the basic distribution server 310, after the end of the module register ( 231) to configure the environment of the client system with the version described in the configuration file.

On the other hand, the core installer 213 in the control unit 210 is the core of the version control system, such as the version verifier 211, the server distributor 212, the module storage unit 221, the module register 231 and the module manager 241. A module for installing a core module 321 performing a functional function on a client.

Here, the core module 321 may be installed through various paths as follows.

Installation method 1 (online automatic installation using the Internet): The most basic and random distribution method to apply to the public to download the version verifier (211) using the automatic download and version control function of the web browser (100) When the version verifier 211 is executed, the version verifier 211 downloads and installs the core installer 213. This process is transparent to the user.

Installation method 2 (file download installation using the Internet): a method in which the user is installed as a subject, when the core installer 213 is stored in the server 300 in a compressed or uncompressed state, the users can download the file to the client Download and run the core installer 213 proceeds as directed by the core installer 213 and installs the core module 321.

Installation Method 3 (Installation Using Removable Storage Device): Save the installer to a portable storage device such as a CD, hard disk, floppy disk, etc., run the core installer 213 on the disk device of the client computer, and proceed as directed by the installer. The core module 321 is installed.

In addition, the server distributor 212 in the control unit 210 analyzes the mapping information defined in the client's IP information and the server's environment configuration information file and connects the client prior to downloading from the basic distribution server 310 for information. Determine the address of the distributed distribution server 320 to be processed. Configure a list of distributed distribution server 320 among the contents of the environment configuration information file, interpret the mapping table between the client IP address and the distributed distribution server 320, and list the distributed distribution server 320 that the client can access. The priority is determined and the version verifier 211 is informed.

Next, the storage unit 220 will be described.

The module storage unit 221 in the storage unit 220 receives the IP address information of the client and executes the server distributor 212 to receive a distributed distribution server 320 to download a file. Access to the designated distributed distribution server 320 to download the configuration file and compare with the basic distribution server 310 to check whether the distributed distribution server 320 is synchronized with the basic distribution server 310. If the synchronization verification is successful, the client module 322 and the version installed or stored locally are checked while checking each client module specified in the configuration information file sequentially. The module 320 is downloaded and stored in the file at the designated location of the client.

Next, the registration unit 230 will be described.

The module register 230 in the register 230 selects a version of the client module 322 most suitable for the environment defined in the server system to be connected among the client modules 322 stored in the client through the module store 221. By automating the task of finding and registering in the version information store 232 in a state where it can be used on the local computer, the user can configure the module to be used simultaneously with the service. Several different versions of the same client module 322 can be stored and stored on the local computer at the same time, and only one version can be active and used at a given time. The module register 231 organically manages the constraints so that version mapping with the server system is transparent to the user. The version verifier 211 performs a function of collectively managing the storage and registration states of the client module 322 installed in a series of orders. It manages the list of the basic distribution server 310 and performs operations such as adding and deleting. The status of the currently registered and activated client module 322 can be monitored and adjusted, and functions such as removing unnecessary modules or specific versions from the system are performed.

4 is a flowchart illustrating a method for distributing a client module and automatically mapping versions in the X Internet environment according to the present invention.

As shown here, the version verifier activated by starting the web browser acquires information on the basic distribution server according to the contents of the HTML (ST201); Accessing the basic distribution server with the obtained information to receive and interpret an environment configuration information file (ST202); Checking the modules installed in the client after the step ST202, checking whether a module of a corresponding version exists, and creating a list of modules determined as an uninstalled version (ST203); Obtaining a list of distributed distribution servers to be accessed when the non-installed module exists (ST204); Attempting to connect to the distributed distribution server according to the priority of the obtained list to determine the distributed distribution server whose environment configuration information file matches the environment configuration information file of the basic distribution server (ST205); Downloading the installer from the determined distributed distribution server and installing it on a client (ST206); Sequentially downloading the client modules according to the list of distribution modules obtained in the step ST204 and storing them in a corresponding location (ST207); When the download of the client module is completed, the step of finding and registering the client module in the system according to the contents of the configuration file of the basic distribution server (ST208).

The method for distributing and automatically mapping versions of a client module in the X Internet environment according to the present invention as described above is as follows.

First, when the web browser 100 is started and installed according to the installation method (installation method 1) of the core installer 213 by accessing a web page, the version verifier 211 is distributed by the method of FIG. It is installed and activated by the web browser 100.

The activated version verifier 211 obtains information on the basic distribution server 310 according to the contents of the HTML in step ST201, and accesses the corresponding basic distribution server 310 in step ST202 to receive the configuration file. Interpret

Next, in step ST203, the modules installed in the client are checked for each of the collected client modules to check whether a module of a corresponding version exists, and if there are modules determined to be an uninstalled version, a corresponding list is created. .

Next, when it is determined in step ST204 that the distribution target exists, the version verifier 211 informs the server distributor 212 of its own IP and environment configuration information file, and requests a list of distributed distribution servers to be accessed. The server divider 212 checks the region of each of the recommended servers in the configuration file, checks whether there is an IP group or IP list that matches the provided client IP, and adds to the list if there is an allowed recommendation server. do. Multiple recommendation servers are possible for a single IP, and the access priority is in the order described in the configuration file. After reviewing all the recommended servers, the server distributor 212 notifies the version verifier 211 of the list of the recommended servers and ends.

Next, in step ST205, if the version verifier 211 informs the module store 221 of the list of recommended servers obtained, the module store 221 attempts to access the recommendation server according to the priority of the list and the server normally. Check if it is working. When the server is operating normally, the module storage unit 221 requests the environment configuration information file from the recommendation server and determines that the synchronization is made with the basic distribution server 310 when the corresponding file matches that of the basic distribution server 310. Then, it is determined by the distributed distribution server 320.

When the distributed distribution server (eg, 320) is determined in step ST206, the module storage unit 221 checks whether the core installer 213 is normally installed, and if not, the core installer from the distributed distribution server 320. Download (213) and install it on the client.

Next, in step ST207, the client module is sequentially downloaded and stored in the corresponding location according to the list of distribution modules obtained in step ST203.

In step ST208, if all the client modules are successfully downloaded, the version verifier 211 executes the module register 231 to find the client module 322 according to the contents of the environment configuration information file of the basic deployment server 310 to the system. Register. If all the information is normally configured, the web browser 100 displays the web page after activating the client module.

According to the present invention described above, the existing server system and the client module operates as it is using the environment and functions at the time of development, and the newly developed server system and the client module By developing using the latest functions and technologies, the user can fundamentally eliminate customization tasks for server system version matching due to the change of client module version, and perform version mapping and management function that is transparent to users. Using client modules of the same product, it is effective to develop and use different server systems.

In addition, by efficiently distributing the CPU and network resources of the server by the distribution according to the change of the client module according to the system resource state of each company, it is also effective to maximize the resource utilization of the system.

Claims (3)

It manages supervision of client module distribution and superset of client module, and loads central processing unit (CPU) and network under the authority of basic distribution server and temporary distribution server that temporarily stores and distributes the modules to be actually distributed. A server composed of a distributed distribution server used for distribution, a version validator for downloading and registering a specific client module from the distributed distribution server, and managing and removing client modules registered and installed in the system, a server distributor, a core installer, In the distribution and version automatic mapping method of the client module by the distributed distribution server in the X Internet system consisting of a client having a module storage unit, a module register and a module manager, A first step of obtaining information on the basic distribution server according to a given content of HTML from a version verifier in the client activated and started by a web browser; A second step of connecting to the corresponding basic distribution server with the obtained information to receive an environment configuration information file and interpreting it; A third step of checking the modules installed in the client after the second step to check whether a corresponding version of the module exists, and creating a list of the modules if an uninstalled version exists as a result of the inspection; A fourth step of obtaining a list of distributed distribution servers to be accessed when the uninstalled module exists; A fifth step of determining a distributed distribution server in which an environment configuration information file of a distributed distribution server matches an environment configuration information file of a basic distribution server by attempting to access a distributed distribution server for each priority of the obtained list; A sixth step of downloading an installer from the determined distributed distribution server and installing it on a client; A seventh step of sequentially downloading the client modules according to the list of distribution modules obtained in the fourth step and storing them in a corresponding location; When the download of the client module is finished, the distribution and version of the client module by the distributed distribution server comprising the eighth step of finding and registering the client module in the system according to the contents of the configuration file configuration information of the basic distribution server Automatic mapping method. The method of claim 1, wherein the fourth step, If there is an uninstalled client module, transmitting a client IP and an environment configuration information file to the server distributor from the version verifier and requesting a list of distributed distribution servers to be connected to; In the server distributor, checking a region for each recommended server of the configuration information file, examining whether there is an IP group or a list of IPs that match the provided client IP, and adding to the list if there is an allowed recommendation server. Wow; Completing the distribution of the client module and the automatic version mapping by the distributed distribution server comprising the step of transmitting the list of the recommendation server to the version verifier as a distributed distribution server list when the review is completed for all the recommendation server in the server distributor Way. The method of claim 1, wherein the fifth step, Transmitting, by the version verifier, the list of the obtained recommendation servers to the module storage unit; Confirming whether the server is operating normally while attempting to access a recommendation server by the priority of the list in the module store; Requesting, by the module store, an environment configuration information file from the recommendation server when the connected server is normally operated; If the configuration information file received after the request is identical to that of the basic distribution server, the client module distribution and version automatic mapping by the distributed distribution server comprising the step of determining the recommendation server as a distributed distribution server Way.