JPH03256160A - Methods of starting, transferring and registering application program in network system - Google Patents

Abstract

PURPOSE:To easily start an application program by storing whether each application is stored in a server device or a client device in a client side management file in each application. CONSTITUTION:Whether each application is stored in a client 8 or a server 14 is decided from the client side management file MENU.AZM. Since a word processor 3 is stored in the server 14 in this case, the MENUSRV, AZM of the server 14 is read out. A CPU 81 forms and executes a network starting command. Then the CPU 81 reds out the file MENU.AZM of the server 14 side. In the file MENU.AZM the word processor 3 is stored in a director YenAPYenAP01. The CPU 81 allocates the dirctory concerned in a virtual drive based upon the stored contents. The the application is started in accordance with the procedure of a starting procedure file CONFIG, AZM stored in the directory YenAPYenAP01 of the server 14.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to the management and operation of application programs in a network system, and in particular to facilitating the activation, transfer, and registration of application programs.

[Background Art] There are cases in which a plurality of computers are connected via communication lines to configure and operate a network system. An example of such a network system is shown in FIG. A connector 4 is provided on the communication line 2 such as a coaxial cable, twisted pair cable, or optical fiber, and the computer 6.8
, 10, 12.14.16 are connected. Computers 14 and 16 are used to centrally manage data and programs within the network, and are called servers. In contrast, the computers 6.8, 10.12 are called clients (workstations) as they are served by the server 14.16.

Various application programs and data are stored in the hard disks 14d and 16d of the servers 14.16. This application and data can be shared between clients 6.8 and 10.12.
This is an advantage of network systems.

From the client 6 to the hard disk 16 of the server 16
An example of executing word processing software stored in d will be explained. The operating system (hereinafter referred to as O8) will be Microsoft's MS-DO8.
(Trademark) and MS-NETWORKS (Trademark) will be given as examples.

First, the size of the work area buffer when accessing the disk and the front-end processor (FEP) used.
etc. are specified in advance as the operating environment. The operating environment is described in files named C0NFIG, SYS. An example of C0NF IG and SYS is shown in FIG. The first line describes the number of files that can be opened simultaneously, the second line describes the buffer size, and the third line describes the type of FEP to be used. These operating environment files C0NFIG and SYS are referenced when O8 is started.
be incorporated into the system. That is, in MS-DO3, when changing the type of FEP to be used, etc., it is necessary to change the contents of the operating environment files C0NFIG and SYS and then restart the system by resetting or the like.

Next, the word processing program of the server 16 is activated via the communication line 2. The operation for starting is also on the keyboard 6F.
Start from This operation is shown in FIG.

First, as shown in the first line, start up the network system. Next, the directory on the hard disk 16 in which the word processing software is stored is virtually assigned as the C drive (second line). This shows the 5Rvl server 16, and APOOI shows the directory of the word processing software. Next, the directory DOCOOI prepared on the hard disk 16d is virtually assigned as the D drive in order to store the document file created with the word processing software (third line). Next, server 16
Allocate the printer 16e for use (4)
line).

After allocating network resources as described above, the word processing software is started. First, in the 6th line, the current drive is changed to the C drive (virtual drive where the word processing software is stored), and then in the 7th line, a word processing software startup command (in this case, WP) is executed. In this way, the word processing software is started.

After editing or printing a document using word processing software, it is necessary to disconnect network resources. First, after changing the current drive to A, the network resources allocated in lines 2 to 4 are disconnected (lines 8 to 10).

In the manner described above, the application of the server 16 can be started and used from the client 6. This can be done similarly from any client 8, 10, 12.

Note that in order to perform the above operation, the server 1 must be configured in advance.
It is necessary to store applications on the 4.16 hard disks 14d and 16d. Applications are typically supplied stored on floppy disks.

Therefore, the application on the floppy disk must be transferred to the hard disk 14d, 16d.

[Problems to be Solved by the Invention] However, the application management method in the conventional network system has the following problems.

First, starting the application was not easy.

In other words, the application cannot be started unless the operating environment settings, network resource allocation, etc. are entered from the keyboard. Moreover, operations such as setting the operating environment and allocating network resources are complicated. Therefore, the operation for starting an application is complicated, and it takes time to start the application. In particular, when using many types of applications, it is necessary to remember the operating environment and resource allocation for each application, which is not easy to operate.

Second, it was not easy to transfer the application to the server. When transferring, in addition to providing a directory for each application, a directory for necessary files such as document files must also be provided.

As application programs become more complex, applications are made up of many files. It is also necessary to transfer the application so that it has an organized directory structure that is easy to use at startup. Therefore, the transfer operation is complicated, and a lot of operation time is consumed for the transfer.

It is an object of the present invention to provide a system that can solve the above-mentioned problems and easily transfer, start, etc. an application.

[Means and effects for solving the problem] In the application program starting method of claim 1, a list of application programs is displayed on the display device of the client device in a menu format, and a desired one is selected from among the displayed ones. The present invention is characterized in that by selecting an application program, the application program is started.

Therefore, it is possible to start an application program simply by selecting the desired application program from the menu.

In the application program starting method according to claim 2, the server device in which the application is stored is known based on the client-side management file, and the starting procedure file for the application program is found based on the server-side management file of the server device; The application program is characterized in that the application program is started according to the start procedure file.

Therefore, the startup operation can be performed simply by reading the client management file, making it easy to start the application.

In the application program starting method of claim 3, the client-side management file also describes the scales of the front-end processor used in correspondence with each application program as one of the management data. It is characterized by incorporating the described front-end processor.

Therefore, it becomes easy to select and rearrange front-end processors for each application program.

In the application program starting method of claim 4, it is also determined based on the client side management file whether the application is located in the server device or the client device.

Therefore, regardless of whether the application program is stored in the client device or the server device, it can be started by reading the management data.

In the application program transfer method according to claim 5, when an application program stored in an external storage medium is to be stored in a desired server device, a transfer procedure file containing a transfer procedure is prepared corresponding to each application program. It is characterized in that the data is transferred to the server device according to the transfer procedure file.

Therefore, simply by preparing a transfer procedure file, various application programs can be easily transferred. In addition, the transfer can be performed appropriately no matter who makes the transfer.

The application program transfer method according to claim 6 is characterized in that, when transferring the application program, a startup procedure file is also transferred to the server device.

Therefore, when starting an application program after transferring it, referring to the starting procedure file makes the starting operation easier.

In the application program transfer method of claim 7, when the application program is transferred to the server device, the storage location in which the startup procedure of the application 17 program is stored is stored as management data in the server side management file. It is characterized by what it did.

Therefore, after transferring the application program, referring to the server-side management file to start the application program facilitates the start-up operation.

In the application program registration method according to claim 8, the server device stores a startup procedure file for each application program, and also stores a storage location in the server device in which the startup procedure of each application program is stored. It is stored as management data in a server-side management file, and when registering an application program, a client-side management file is created based on the information on which server device the application program is to be used. It is characterized by

8- Therefore, when starting the application program,
It can be started by referring to the client-side management file, making the start-up operation easy.

The application program registration method according to claim 9 is characterized in that, when registering the application program, the type of front-end processor to be used corresponding to each application program is also stored in the client side management file as one of the management data. It is said that

Therefore, a front-end processor can be selected and registered for each application, and there is no need to select a front-end processor at startup.

In the application program registration method according to claim 10, when registering the application program stored in the server device, the client side When creating a management file and registering an application program stored on the client device, the client-side management file should be used as management data indicating in which storage location on the client device the application program is stored. It is characterized by creating.

Therefore, whether each application is stored in the server device or the client device is stored in the client side management file. Therefore, by referring to the client side management file,
Application programs stored in any device can be easily started.

[Embodiment] FIG. 12 shows an example of the system configuration of a network system used in the transfer, registration, and activation method according to the present invention. This system configuration itself is the same as the conventional system described above, so the explanation will be omitted.

Taking the server 14 and client 8 as an example, a block diagram thereof is shown in FIG. Note that other servers and clients have similar configurations. In the server 14, the path line 146 includes RAM 142, ROM 143, and
Each peripheral device is connected. CPU 141 is R
These are controlled via the pass line 146 according to the program of the AM 142. Further, communication with other computers via a communication line is performed by a communication IF 145. Note that the client 8 also has a similar configuration. Further, the configuration of peripheral devices including a hard disk and a floppy disk drive is arbitrary, and it is not necessary to include all of them.

The transfer method, registration method, and startup method will be explained below in this order.

Transfer method First, the application stored on the floppy disk is transferred from the client 6.8.10 or 12 to the hard disk 14d or 16 of the server 14 or 16.
The case where the data is transferred to and stored in d will be explained.

In addition, in the following explanation, MS-DO8 and MS
-N1- Although ETWORKS is cited as an example, O8 and network systems are not limited to this.

For example, it can be similarly applied to UNIX (NFS, etc.), Ethernet, etc.

FIG. 3 shows the structure of files stored in each client 6.8, 10.12 (if there is no hard disk, the files are stored on a floppy disk). In this embodiment, each client stores a network-specific transfer procedure file that defines transfer procedures for each application. In the figure, Warb ol
, IBN, word processor 2, IBN, word processor 3.
IBN, data base, IBN, etc. are the transfer procedure files.

The main body of the program for transfer is MENU, EXE.
It is. This program is shown in a flowchart in FIG. Client 8's CPU 81 executes MENtl, E
When the XE transfer program is executed, the transfer procedure file is displayed in a menu format on the display 8C, as shown in FIG. If you want to transfer the word processor 3 to the server 14 now, use the mouse, keyboard, etc. to type '7-7' 03 on this screen.
Select IBN (step S+). Next, the server name and directory name of the built-in optical system are entered manually using the keyboard 8f or the mouse 84 (step S2). CPU81
In accordance with this, the hard disk 14d of the server 14
Create a directory for embedding the application in (
Step Sa). For example, as shown in FIG. 7, a directory called APol is created. When the directory is created, the CPU 81 transfers the selected transfer procedure file'
7-7' []3. Transfer is performed according to the contents of the IBN.

FIG. 6 shows the transfer file Wharf °o3. Indicates the contents of the IBN. It consists of a data part α for displaying operation guidance on the screen and a part β describing which file of the application (floppy disk) is to be transferred. Note that the part γ is a startup procedure part that describes a startup command.

The CPU 81 displays guidance α to prompt the user to insert the floppy disk. When the floppy disk is inserted, based on the description γ and taking into account the contents of the startup file (AUTOEXEC, BAT) on the floppy disk,
Startup procedure files C0NFIG and AZM are created (step S5). This startup procedure file CONFIGAZ
M is stored in the directory APO1 of the hard disk 14d of the server 14 specified in step S2 (7th
(see figure).

Next, the CPU 81 reads the application file specified by the description β from the floppy disk and transfers it to the server 14 (step SO). server 1
The application files transferred to 4 are stored in the directory APO1 in the same way as the startup procedure files C0NFIG and AZM (in the figure, word processor
, word processor 3. (indicated by INT).

If the application is contained in a plurality of floppy disks, guidance is displayed (step S8) and the above operations are repeated.

When the transfer of the application file is completed, in step S9, the server side management file MENUSRV is
, Create AZM and install hard disk 1 of server 14.
4d (see Figure 7). Server-side management files MENUSRV and AZMLt are files for managing in which directory of each application covered disk 14d each application is stored. In this embodiment, conditions necessary for startup are also described. Table 1 shows examples of the server side management files MENUSRV and AZM.

Table 1 Application Directory Conditions etc. As described above, the application program is installed on the server 14.
will be forwarded to. Server 14.16 has client 6
．． It is a good idea to register all the applications that you plan to use in 8.10.12.

-Registration method- Next, among the application programs stored in the server 14.16, the client 8 (6°10, 12
The operation of registering an application to be used in (the same applies to ) will be explained below. Program for application registration (MENU, EX
E) is shown in a flowchart as shown in FIG.

When you run this program, the display 8c will first appear.
A display like that shown in FIG. 9 is displayed. That is, a box BOX for registration is displayed (in this example, 20
), prompting you to select a registration location for your application. In this figure, the bar BAR indicating the registered position is
It is located on the upper level on the left.

The bar BAR is moved to a desired position using the mouse 84 or the keyboard 8f, and the registration position is specified (step 51o).

Next, the CPU 81, based on the server side management file,
A list of applications stored in the servers 14 and 16 is displayed on the display 8C. A desired application is selected from the displayed applications using the mouse 84 or the keyboard 8f (step S, 1).

Next, the CPU 81 reads the list of front-end processors (Brosefusa 1.DRV and Brosefsa 2.DRV in FIG. 3) stored in the hard disk 8d.
Day Suf.

6- Display on Ray 8c. A front-end processor to be used in the application is selected from the displayed front-end processors using the mouse 84 or the keyboard 8f (step 512).

Note that the front end processor is the server 14゜16
It is also possible to use the one stored in .

Next, the CPU 81 creates management data that describes the name of the server where the application is stored, the directory name of the front-end processor used, and the like. When the management data is created, it is written to the client side management files MENU and AZM on the hard disk 8d (
Step S, 8). Table 2 shows an example of the client side management files MENU and AZM.

[As is clear from Table 2 below, it can be seen that the drawing application Cab5 is stored in the server 16 (indicated as SRV2). For other applications, it is also possible to know in which directory on which server they are stored.

Note that the application may be stored in the hard disk 8d of the client 8. In this case, as shown in the fourth row of data in Table 2, the directory of the hard disk 8d of the own machine (client 8) is written without writing the server name.

One application is registered with the client 8 through the above series of operations. By repeating this operation, applications to be used on the client 8 are registered in advance. FIG. 10 shows the display on the screen after registering multiple applications.

Incidentally, files related to the front-end processor are stored in a directory structure as shown in FIG. In this embodiment, a front end processor VJE is stored in FEPOI, and a front end processor MTTK2 is stored in FEPO2. Note that when using a front-end processor stored in a server, the server name and directory name are written as shown in Database 2 in Table 2. Note that since the front end processor is frequently used, it is preferable to store it on the client side.

1 Starting Method Finally, the starting method will be explained. Now, assume that the application is started from client 8. It is assumed that the directory structures of the hard disks of the server 14 and the client 8 are as shown in FIG. In the figure, the contents of files necessary for explanation are shown on the right side.

The program to start is MEN on the client 8 side.
U, EXE. The flowchart is shown in FIG. When the startup program is executed, the CPU 81 executes the following operations based on the client side management files MENU and AZM.
A list of applications as shown in FIG. 1O is displayed on the display 8C. From this list of menu formats,
An application to be started is selected using the mouse 84 or the keyboard 8f (step S2). Here, the explanation will proceed assuming that word processor 3 is selected.

The CPU 81 reads the management data of the selected word processor 3 from the client side management files MENU and AZM (step S2□). As a result, the user knows that the front end processor MTTK2 to be used is stored in a directory called FEPO2. Each directory stores files C0NFIG and AZM in which procedures for incorporating a front-end processor are described. The CPU 81 reads this and performs 30-incorporation of the front end processor. Here, the front-end processor program MTTK2.3Y
Install S as a device driver. That is, C0
NF IG, AZM second line description “DEVICE”
=MTTK2SYS”, delete the previously installed front-end processor from RAM82,
MTTK2 instead. Incorporate SYS. In this way, since the front-end processor is installed without using the O8 environment setting files C0NFIG and SYS, it is possible to change the front-end processor without having to restart by resetting or other means. .

Next, it is determined from the client-side management files MENU and AZM whether the application is on its own machine (client 8) or on the server (step 528).

The word processor 3 is now stored in the server 14 (SRm), so it executes step S24.

Here, the CPU 81 generates and executes the network startup command (see the first line in FIG. 14). Next, the CPU
81 is the server side management file MENU on the server 14 side.
Read SRV and AZM. In the server side management file, as shown in Figure 1, the word processor 3 has \AP\AP
It is written that it is stored in a directory called O1. Based on this, the CPU 81 allocates the directory to the virtual drive (see line 2 in FIG. 14). Also, the printer to be used is assigned based on the startup conditions and the like.

Next, the corresponding directory\AP\APO1 of the server 14
The startup procedure file C0NF IG stored in
The application is started according to the AZM procedure (step 525). For example, startup procedure file C0
NFIG.

AZM is described as shown in FIG. The first line is a display line for the application name. 2nd line (7)
DEVICE=MOUSE and SYS are data for operating environment settings required to execute the application. According to this setting, the CPU 81
Incorporate the device driver into RAM82. At this time, as mentioned above, the O8 environment setting files C0NFIG, SYS
The device driver is installed without using .

WP on the fourth line is a startup command for the word processor 3. C
The PU 81 starts up based on this.

In this way, the application on the server 14 can be launched and executed from the client 8.

Note that if an application stored in the client 8 is selected in step 5112, (
For example, if Utility is selected), step S
At 26, the application is launched without going through the network.

As described above, a desired application can be activated simply by selecting it from the menu screen as shown in FIG. 10.

In this embodiment, the client side management file M
Register the server name where the application is stored in ENU and AZM, and save the server side management files MENUSRV and A.
The directory in which the application is recorded is registered in the ZM. Therefore, if you change the application storage directory or startup conditions on the server, the client side management file ME
There is no need to change the contents of NU and AZM, and the server side management file MENUSRV
, it is possible to start correctly by simply changing AZM. This facilitates application maintenance (changes as described above) in networks where many clients are connected.

In the above embodiment, each file is stored on a hard disk, but a storage device such as an optical disk or a floppy disk may be used.

In addition, if the application is to be stored only on the server side, steps S2s and s2a in FIG.
does not need to be provided.

[Effect of the invention 1] In the application program starting method of claim 1, a list of application programs is displayed on the display device of the client device in the form of a menu, and the desired application program is selected from the displayed ones. It is characterized by starting an application program.

34. Therefore, it is possible to start an application program by simply selecting the desired application program from the menu.

In the application program starting method according to claim 2, the server device in which the application is stored is known based on the client-side management file, and the starting procedure file for the application program is found based on the server-side management file of the server device; The application program is characterized in that the application program is started according to the start procedure file.

Therefore, the startup operation can be performed simply by reading the client management file, making it easy to start the application. Additionally, even if you change the storage location of an application program stored on the server, you only need to change the server-side management file.
Maintenance becomes easier.

In the application program starting method according to claim 3, the client-side management file also describes the type of front-end processor used for each application program as one of the management data, and when starting the application program, It is characterized by incorporating the described front-end processor.

Therefore, it becomes easy to select and rearrange front-end processors for each application program.

In the application program starting method of claim 4, it is also determined based on the client side management file whether the application is located in the server device or the client device.

Therefore, regardless of whether the application program is stored in the client device or the server device, it can be started by reading the management data.

In the application program transfer method according to claim 5, when an application program stored in an external storage medium is to be stored in a desired server device, a transfer procedure file containing a transfer procedure is prepared corresponding to each application program. It is characterized in that the data is transferred to the server device according to the transfer procedure file.

Therefore, simply by preparing a transfer procedure file, various application programs can be easily transferred. In addition, the transfer can be performed appropriately no matter who makes the transfer.

The application program transfer method according to claim 6 is characterized in that, when transferring the application program, a startup procedure file is also transferred to the server device.

Therefore, when starting an application program after transferring it, referring to the starting procedure file makes the starting operation easier.

In the application program transfer method of claim 7, when the application program is transferred to the server device, the storage location in which the startup procedure of the application program is stored is stored as management data in a server-side management file. It is characterized by what it did.

Therefore, after transferring the application program, referring to the server-side management file to start the application program facilitates the start-up operation.

In the application program registration method according to claim 8, the server device stores a startup procedure file for each application program, and also stores a storage location in the server device in which the startup procedure of each application program is stored. It is stored as management data in a server-side management file, and when registering an application program, a client-side management file is created based on the information on which server device the application program is to be used. It is characterized by

Therefore, when starting the application program 8, it can be started by referring to the client-side management file, which facilitates the starting operation.

The application program registration method according to claim 9 is characterized in that, when registering the application program, the type of front-end processor to be used corresponding to each application program is also stored in the client side management file as one of the management data. It is said that

Therefore, a front-end processor can be selected and registered for each application, and there is no need to select a front-end processor at startup.

In the application program registration method according to claim 10, when registering the application program stored in the server device, the client side When creating a management file and registering an application program stored on the client device, the client-side management file should be used as management data indicating in which storage location on the client device the application program is stored. It is characterized by creating.

Therefore, whether each application is stored in the server device or the client device is stored in the client side management file. Therefore, by referring to the client side management file,
Application programs stored in any device can be easily started.

[Brief explanation of drawings]

FIG. 1 is a diagram showing the file structure and contents on the server side and client side in an application startup method according to an embodiment of the present invention. FIG. 2 is a diagram showing the hardware configuration in each startup, registration, and transfer method. 3 is a diagram showing the directory structure of the hard disk 8d of the client 8, FIG. 4 is a diagram showing a flowchart of an application transfer method according to an embodiment, FIG. 5 is a diagram showing a menu format screen at the time of transfer, and FIG. 7 is a diagram showing the directory structure of the hard disk 14d of the server 14, FIG. 8 is a diagram showing a flowchart of an application registration method according to an embodiment, and FIG. 9 is a diagram showing the contents of a transfer procedure file as an example. FIG. 10 is a diagram showing a menu format screen before registration, FIG. 10 is a diagram showing a menu format screen after registration, FIG. 11 is a flowchart of an application startup method according to an embodiment, and FIG. 12 is a diagram showing a network system configuration. Figure shown, 1st
FIG. 3 is a diagram showing an example of the contents of an operating environment setting file, and FIG. 14 is a diagram showing an operation for starting an application on a network using a conventional command. 2...Communication line 6.8, 10.12...Client 1416...
Server MENUSRV, AZM...Server side management file C0NFIG, AZM...Startup procedure file MEN
U, AZM...Client side management file FE
P, AZM...Front-end processor management file 1 42- Figure 6 *MENULAN BF ■1 This word processor 3 γ\WP3 7--' Please enter the system information for Word Processor 3. C0PY%IWP3・* %2\8 *US Figure 8 Figure 61 A>NET 5TART RED[RECTORW
SIA>NET USE C: ¥¥5RV1¥
APOOIA>NET USE D: ¥¥5R
V1*DOC01A>NET tJsE PRN
¥¥5RV1¥NETPRNArc: C>WP C>A:

Claims (10)

[Claims] (1) In a network system equipped with one or more server devices storing application programs and one or more client devices connected to the server device via a data communication line, a list of application programs can be displayed on the client devices in a menu format. 1. A menu-based method for starting an application program, characterized in that the application program is displayed on a display device, and the desired application program is started by selecting the desired application program from among the displayed ones. (2) In a network system that includes one or more server devices storing application programs and one or more client devices connected to the server device via a data communication line, the server device has a system for starting each application program. In addition to storing the procedure file, a server-side management file is stored that stores the storage location in which the startup procedure file for each application program is stored. Prepare a client-side management file that describes the information stored in the device as management data for each application program, and when executing an application program stored in the server device from the client device side, Application program startup characterized by reading management data corresponding to the application program in a side management file, finding a startup procedure file for the application program based on this, and starting the application program according to the startup procedure file. method. (3) In the application program starting method of claim 2, the client-side management file also describes the type of front-end processor used for each application program as one of the management data, and the application program starting method An application program startup method characterized by incorporating the described front-end processor. (4) In a network system comprising one or more server devices storing an application program, and one or more client devices connected to the server device via a data communication line and storing the application program, the server device and the client The device stores a startup procedure file for each application program, and also stores a server-side management file that stores the storage location in which the startup procedure file for each application program is stored. Information on whether it is stored in the server device or the client device,
Which server device stores the startup procedure file for the target application program, or
A client side management file is stored in the client device as management data for each application program, and when the application program is executed, the client side An application program that reads management data corresponding to a target application program from a management file, finds a startup procedure file for the application program based on this, and launches the application program according to the startup procedure file. Starting method. (5) In a network system configured by connecting at least one server device and at least one client device via a data communication line, when an application program stored in an external storage medium is stored in a desired server device, An application program transfer method characterized in that a transfer procedure file containing a transfer procedure is prepared corresponding to each application program, and transfer to a server device is performed in accordance with the transfer procedure file. (6) In the application program transfer method according to claim 5, a startup procedure file containing a startup procedure is prepared corresponding to each application program, and when the application program is transferred according to the transfer procedure file, the startup An application program transfer method characterized in that a procedure file is also transferred to a server device. (7) In the application program transfer method according to claim 6, when the application program is transferred to the server device, the storage location in which the startup procedure of the application program is stored is stored in the server side management file as management data. An application program transfer method characterized by: (8) An application program stored in the server device, assuming a network system comprising one or more server devices storing an application program, and one or more client devices connected to the server device via a data communication line. Of these,
In an application program registration method in which application programs to be used on the client device are determined in advance, the server device stores a startup procedure file for each application program, and the startup procedure for each application program is The information stored in the storage location is stored as management data in the server side management file, and when registering an application program, the client side An application program registration method characterized by creating a management file. (9) In the application program registration method according to claim 8, when registering an application program, the type of front-end processor to be used corresponding to each application program is also stored in the client side management file as one of the management data. An application program registration method featuring: (10) Assuming a network system comprising one or more server devices storing application programs, and one or more client devices connected to the server device via a data communication line and storing application programs, the server device or In an application program registration method in which the application programs to be used on the client device are determined in advance among the application programs stored in the client device, the server device stores a startup procedure file for each application program, and The storage location on the server device in which the startup procedure of each application program is stored is stored as management data in the server side management file, and when registering the application program stored in the server device, it is necessary to When creating a client-side management file based on the information on whether to use an application program stored on the server device and registering the application program stored on the client device, the application program must be An application program registration method characterized in that a client-side management file is created using management data as to which storage location in a client device the application program is stored.