JPH07121484A - Application software starting/executing device - Google Patents

Abstract

PURPOSE:To facilitate the starting/executing of an application software by integrating an interface which is applied to the application software by means of a user at the time of providing required service to a related client. CONSTITUTION:The application software executed in some prescribed distribution environment 6 is concentrated and controlled by a common server 5 and required service is provided to the related client. At this time, the interface which is applied to the application software by the user is integrated. The client is the one such as a work station client 1, a personal computer client 2, a teletype client 3 and a telephone client 4, etc., and arranged in distribution environment 6 like a proper network together with the prescribed server 5. Thus, the application software is easily started/executed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an application software start / execution device, and more particularly to a process (such as double-clicking of a mouse or transcription) on a desktop for starting a normal file opening operation. To start / execute a specified application software
The present invention relates to an application software start / execution device which is extremely easy to start / execute in correspondence with and related to a process on a desktop for execution.

[0002]

2. Description of the Related Art When trying to share required application software in a distributed environment such as an appropriate network, [1] a server in the distributed environment temporarily stores the required application software in an appropriate storage means on the client side. Load it, take it out on the client side, and execute it. [2] Application software that has already been started on the server side (that is, the server side is in the so-called "running stage"), and is required according to the corresponding command. Execution is enabled immediately on the server side)
Is provided with a required communication protocol (protocol) for obtaining the execution request and the result of the execution.
The street way is traditionally adopted. by the way,
In the case of the method like [1], the client side needs to know for each application software which file to load. On the other hand, in the case of the method [2], the client explicitly specifies the application software on the server and performs the required processing. Here, in order to use the application software on the server, the client is [3] the type of application software existing on the server; and
[4] How to use all the existing application software must be known. Further, in order to display the result of processing by a certain predetermined application software on the client side in an optimum manner, a user interface corresponding to the corresponding application software must be prepared on the client side. There is. Further, in order to notify the server of the execution request of the new application software, there is a problem that the client side must know how to handle the new application software. Then, when it becomes necessary to add some new application software, it is required to rebuild the system itself to which this is added. Furthermore, there is no means for storing various parameters that need to be set on a file when activating a predetermined application software. That is, even if the server side is in a state of sharing a predetermined application software, various kinds of starting method / location / initial setting (of the corresponding application software) required when actually starting Corresponding parameter does not exist. In addition, since each application software has a different interface, the user has to learn how to use each. Even if the functions are the same in appearance, if the processing contents differ for each client, [5] the user must explicitly select the application software of the corresponding server. Needs to know the application software that suits the current client environment; [6] Each time a certain predetermined execution is requested, the user has to make settings corresponding to the client environment. There is also a problem. As a disclosure of prior technical matters relating to such a matter, for example, Japanese Patent Laid-Open No. 5-1198 / 1993 is disclosed.
Publication No. 7 [application program starting method] can be mentioned.

[0003]

In the conventional technique of this type, as described above, when trying to share required application software in an appropriate distributed environment, [1] the server in the distributed environment is required. Retrieve the required application software from the client to the client side, and extract and execute this on the client side;
[2] For the application software that is already in the run-up state on the server side, two execution methods have been conventionally adopted: an execution request and a communication protocol (protocol) for obtaining the result of the execution; In the former method [1], the client needs to know for each application software which file to load. On the other hand, in the latter case [2], the client explicitly specifies the application software on the server and performs the required processing. Here, in order for a given client to use the application software on the server, the client must:
It is required to know [3] the type of application software existing on the server; and [4] how to use all the existing application software. Further, in order to display the result of processing by a certain predetermined application software on the client side in an optimal manner, a user interface corresponding to the corresponding application software is
Must be prepared on the client side. Further, in order to notify the server of an execution request for new application software, the client must know how to handle the new application software. Then, when it becomes necessary to add some new application software, it is required to rebuild the system itself to which this is added. In addition, even if the functions are apparently the same, if the processing content differs for each client, [5]
The user needs to explicitly select the application software of the corresponding server, and the user is required to know the application software suitable for the current client environment; [6] Certain predetermined Each time the execution of is requested, the user must make the necessary settings according to the environment of the client. There are various problems such as.

The present invention has been made to address some of the problems described above. According to the application software starting / executing apparatus of the present invention, an application executed in a certain predetermined distributed environment. The software is managed by a common server and the required services are provided to related clients. At that time, the interface applied by the user to the application software is unified. That is, the application folder for the required application software is managed in the file system in the common server, and (such as a predetermined file folder) is managed.
The application software is started / processed by the same instruction as the operation for the actual folder. Thus, for example, even if new application software is added, the user does not need to learn the corresponding operation each time. That is, the client selects the corresponding application software for each function desired to be executed.
There is no need to learn to execute, and the server has the function of automatically selecting and executing the corresponding. Various parameters that must be specified when starting / processing application software are managed as additional information on the server side. As a result, the parameters once set are valid for all clients (in other words, they are resources common to all clients), and the user is relieved of the burden of holding extra information about them as knowledge. In addition, by standardizing the access method for application software (that is, incorporating the same operation as a certain predetermined file access), even if new application software is added later, it is necessary to change the correspondence on the client side. There is no need to change it, and you only have to change it on the server side. By managing the application software itself and the application folder separately, it is possible for multiple application folders to exist for one piece of application software (this makes it possible to flexibly respond to user requests). In addition, since the application software itself can exist in any place on the distributed environment, the system configuration can be made flexible. Even if similar processing is required to process different application software for each client, the server side manages the client and application software in correspondence so that the user can use There is no need to be particularly aware of the existing client environment.

[0005]

An application software starting / executing apparatus according to the present invention is provided in a distributed environment 6 in which a plurality of clients (1, 2, 3, 4) and a server 5 common to them are provided. An application software start / execution device for starting and executing desired application software in the server in response to a request from a predetermined client: corresponding to the application software start / execution device The server 5 is: an application software management unit 51 that performs necessary management such as reception and analysis of access to application software and / or file system requested by a certain client side; Application data to be registered / stored Database unit 52; and an application software processing unit 5A including at least one application software execution management unit 53 (54) for managing the execution of certain required application software; and a request from a predetermined client. A file system unit 55 which stores various files / directories stored therein, and which performs required management thereof, and a file system unit 5B: When a desired file / directory is opened on the client side. It is possible to start / execute desired application software in the same manner as the above; on the client side, in response to access to a specific file / directory in the server, the server and / or the client responds. It is possible to start / execute an equivalent application software; it is characterized in.

[0006]

According to the application software starting / executing device of the present invention, application software executed in a predetermined distributed environment is centrally managed by a common server, and required by related clients. Being offered a service. At that time, the interface applied by the user to the application software is unified. That is, the application folder for the required application software is managed in the file system in the common server, and the application is executed with the same instruction as the operation (such as the open instruction) for the actual folder (such as the predetermined file folder). The software is activated / processed. Thus, for example, even if new application software is added, the user does not need to learn the corresponding operation each time. The client does not need to learn to select and execute the corresponding application software for each function desired to be executed, and the server has a function of automatically selecting and executing the corresponding function. For various parameters that must be specified when starting / processing application software,
It is managed as additional information on the server side. As a result, the parameters once set are valid for all clients, and the user is relieved of the burden of holding extra information about them as knowledge. Various advantages such as are obtained.

[0007]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is an overall configuration diagram of a system including an application software starting / executing device according to an embodiment of the present invention. In FIG. 1, what is exemplified as a client is WS Client 1
(Work Station), PC Client 2 (Personal Computer), TTY Client 3
(Teletype), Phone Client 4 (telephone)
Etc., and is arranged in a distributed environment 6 such as an appropriate network together with a certain predetermined server 5. here,
Although the server 5 is illustrated as another structure,
There is no particular inconvenience even if it exists on the same hardware as the client described above. As a means (protocol) for performing the procedure between the client and the server, apparently only the access means for the file on the server exists, and the access for the specific application software managed on the server is made. There is no means. The server here also has a file system function and can be used as a distributed file server. Further, the application software managed by the server can also be managed separately from the application folder, and for this reason, the application software may be managed at another place on the distributed environment other than the server. The client here is WS
GUI (graphic user
In addition to the one having an interface), the one having no GUI such as TTY can be targeted. That is, all the clients that can request the operation related to the file can use the desired application software on the server.

FIG. 2 is a block diagram of a server corresponding to the application software starting / executing apparatus according to the above-described embodiment apparatus. As can be seen in FIG. 2, the server 5 can be divided into an application software processing unit 5A and a file system management unit 5B. Here, the application software processing unit 5A
Are included in the application software management unit 51, the application database unit 52, #
1 application software execution management unit 53 and # 2 application software execution management unit 54. The file system management unit 5B includes a file system unit 55. The application software management unit 51 is a unit that receives requests from clients, and various requests from clients are received and analyzed here. It should be noted that a predetermined process for accessing the file system is also managed here as one application software. The processing flow of this application software management unit 51 is shown in the flowcharts of FIGS. 3 and 4.
3 and 4 are flow charts for explaining the operation processing of application software management in the apparatus of the above embodiment. The operation processing of application software management in the apparatus of the above embodiment will be described below with reference to FIGS. 3 and 4 as appropriate. Now, an access request is issued from a certain predetermined application software (S3
01: refer to FIG. 3), it is judged whether or not the filing application is already activated (S3).
02). As a result of this determination, when it is determined that the filing application has not been activated yet, the filing application is newly activated (S303). Next, it is determined whether the object on the file system for which access is requested is an application folder (S304). If the result of this determination is that it is not an application folder, it is determined that the request is for normal filing, and the filing application is requested to perform the required processing (S305). As a result of the determination, when it is determined that the application folder,
The additional information attached to the application folder is read (S306). What is stored as additional information here is various parameters to be set at startup, conditions to be passed when executing the corresponding application software, and the like. Further, there is information stored in the application database unit 52 as the information required when the application software is started, and the application software management unit 51 makes a required inquiry. Here, there are two types of predetermined application software: 1) that executes the startup process on the server side, and 2) that transfers the substance of the application software to the client side and executes this on the client side. There are different forms. For example, even in the case of application software having a specific GUI, this management mechanism can manage, but it is necessary to entrust its execution to the client side. Further, with respect to the application software which outputs only the result without having the GUI, the processing is executed on the server side. Therefore, in S307, it is determined which form the corresponding application software belongs to. As a result of this determination, when it is determined that the operation is performed on the client side, the process proceeds to S41 (see FIG. 4) to make a required inquiry to the application database unit 52,
Acquires the entity of application software that can be executed on the client side. Here, in the application database unit 52, it is possible to manage entities that can be executed by each client even if they have the same function. That is,
When the substance of the application software is, for example, “automatic retrieval of document”, each client connected to the distributed environment 6 (WS 1, PC
2, the TTY 3 and the Phone 4 can be separately managed for each entity of the application software of the optimum form. Subsequent to this, in S42, it is determined whether or not the desired application file is found. When the result of this determination is affirmative, that is, when the desired application file is found, the desired entity is transferred to the client side (S44), and the processing of the application software management unit 51 is completed (S312). . Here, since the client receiving the entity of the application software executes and processes the entity under its own environment, there is no special exchange with the server thereafter. On the other hand, when the result of the determination in S42 is negative, that is, when the desired application file is not found, it is determined that an error has occurred, a predetermined error message is passed to the client side, and then the application The processing of the software management unit 51 is completed (S312). On the other hand, when it is determined as a result of the determination in S307 (the relevant application software belongs to a mode to be executed on the server side), it is determined whether the requested application software has already been started on the server side. (S308). If the result of this determination is negative, that is, if it has been determined that the application software has not been started yet, then the flow shifts to S309, and the target application software is started while using the necessary startup parameters as appropriate. On the other hand, S3
When the result of the determination in 08 is affirmative, that is, when the requested application software has already been started on the server side, the value of the filing operation information requested by the client and the value held as additional information of the application folder are set. It is passed to the application software side and the required processing is executed (S310). Then, the process proceeds to the next S311, and after a certain predetermined application software is executed, so to speak, a cleanup work is performed, and then the processing of the application software management unit 51 is completed (S31).
2).

The application database section 52 is
Management of application software itself and its accompanying information (for example, parameter settings for execution, conditions specific to application software, etc.)
The management of The application software may be managed by the database here, or may be managed externally (for example, on a file system). In addition, when the application software is managed outside the database as described above, a predetermined file in the database here functions as a directory that collects index information of the corresponding application software, for example. Become.

The # 1 application software execution management section 53 includes an application software management section 51.
The application software instructed by 1. is activated, and the application software itself may be activated therein. It is also possible to receive requests from a plurality of clients at the same time. In that case, in addition to the plurality of application software execution management units [that is, the # 2 application software execution management unit 53, the # 2 application A software execution management unit 54] can be provided. These application software execution management units fulfill the function of accessing the file system unit 55 as needed.

FIG. 5 is a view showing an example of a display on the desktop on the side of a predetermined client in the above embodiment. In FIG. 5, Document 1 corresponds to a given document. Folder 1
Corresponds to a normal folder (other than the application folder described later). ApplFolde
r 1, ApplFolder 2, ApplFolde
r 3 corresponds to different application folders. Where Folder1 and A
pplFolder 1, ApplFolder 2, A
There is no apparent difference on the desktop with pplFolder 3 and the normal start of operations for them (eg by double clicking on them with the mouse means attached to the client side) Both are possible. Here, A
The description will be made assuming that pplFolder 1 corresponds to a folder of application software for automatic search. This automatic search application software executes a search for a predetermined specified portion in the file system management unit 5B of the server 5 on the basis of set conditions and displays the corresponding display. Is.

FIG. 6 is a display example of the (search) additional information in the above-mentioned search application folder (that is, ApplFolder 1 as a folder of application software for automatic search). This Figure 6
In (1) [Search target folder name], specify the path name of the folder to be searched; (2) [Level] specify the depth of the search level; (3) In [Document type] , Specify the type of object to be searched; (4) [Format] specifies the format of the document to be searched; (5) [Modify after specified date] and [Modify before specified date] , And specify the selection of the search target based on the date and time; (6) [File name] is narrowed down based on the name of the document (here, it can be specified by WildCard); (7) [Create Person] narrows down based on the creator of the corresponding document; (8) [Keyword] narrows down based on the keyword set in the document. Set these search items as needed, and
At the time of opening the lFolder 1, a search is performed based on this search condition, and the result is displayed.
In the example shown in FIG. 6, the word [Technical] is designated as (8) [keyword].

Assuming that the file list in the [/ sample] section in FIG. 6 has the structure illustrated in FIG. 7, and if ApplFolder 1 is opened, a search is automatically executed. The result as shown in FIG. 8 is displayed. That is, as described above with reference to FIG. 6, (8) [Techni] as [keyword]
Since the word [cal] is specified,
From the file list of [Technica]
The word "l" will be displayed as having selected the file names B and C specified as [Keyword]. FIG. 9 shows an example of the contents of the application database in the case of the state shown in FIG.
Here, the application software name represented by the application folder cannot be seen concretely in the display example on the client of FIG. 5, but in reality,
An application folder is provided as invisible additional information in the corresponding client. The reason is that the correspondence between the expressed application folder and the application software name is not so important to the client, it is important what function is actually provided, and that is what is seen. This is because it doesn't matter if you can see it. ApplFo
Looking at lder 1, it uses application software named [X] in FIG. Here, the type of the application software is [server execution type]; the storage location of the entity is [/ ap
pl / server / X]; and the file name that defines the output format of the additional information displayed on the client is [/
profile / X]. Also,
The application software with the name [Y] is of a type that is executed on the client side.
It is managed by Table 1 in FIG.

In Table 1 of FIG. 10, the type of client; the operating hardware; O
S: version; and the storage location of the entity corresponding to them are specified. As a result, the substance of the application software corresponding to the type of client can be transferred to the client side. Then, when the entity of the application software corresponding to the accessed client is not stored, an error is notified to the client side.

[0015]

As described in detail above, according to the application software starting / executing apparatus according to the present invention (for example, the mouse means attached to a certain predetermined portion is used to duplicate the relevant one). Starting by correlating and relating the process on the desktop for starting a normal file opening operation (by clicking) to the process on the desktop for starting / executing a certain predetermined application software / Extremely easy to execute; and the application software is centrally managed by the server and the service is provided to the client, but at this time, the interface from the user to the application software is unified. The target application folder. Managed by the system, is to perform application software activated / treated according to the same instructions and operations for the actual folders, the user each time a new application software,
There is no need to learn the corresponding operation; for various parameters that must be specified when starting / processing application software,
It will be managed as additional information on the server side,
Once set, the parameters are effective for all clients (so to speak, a common resource), so the user is relieved of the burden of retaining extra information as knowledge; .

[Brief description of drawings]

FIG. 1 is an overall configuration diagram of a system including an application software activation / execution device according to an embodiment of the present invention.

FIG. 2 is a configuration diagram of a server corresponding to an application software starting / executing device according to the above-described embodiment device.

FIG. 3 is a flowchart illustrating an operation process of application software management in the apparatus of the above embodiment.

FIG. 4 is a flowchart illustrating an operation process of application software management in the apparatus of the above embodiment.

FIG. 5 is a diagram showing a display example on a display screen on the client side in the apparatus of the above embodiment.

FIG. 6 is a view showing a display example of additional information in the case of a search application drawer in the apparatus of the embodiment.

FIG. 7 is a view showing an example of a file list stored under a / sample item in the apparatus of the above embodiment.

FIG. 8 is a view showing an example of a list displayed when a search folder is opened in the apparatus of the above embodiment.

FIG. 9 is a view showing an example of registered items in an application database in the apparatus of the above embodiment.

FIG. 10 is a diagram showing an example of the configuration of a table for managing the substance of application software executed by a client in the apparatus of the above embodiment.

[Explanation of symbols]

1--WS Client; 2 --- PC Client;
3--TTY Client; 4--Phone Cli
ent; 5--server; 6--distributed environment; 51 --- application software management unit; 52 --- application database unit; 53 --- # 1 application software execution management unit; 54-# 2 application software execution Management unit: 55--File system unit.

Claims (1)

[Claims] 1. An application for starting and executing desired application software in a server in response to a request from a predetermined client in a distributed environment in which a plurality of clients and a server common to them are provided. A software activation / execution device, which is a server corresponding to the application software activation / execution device, receives and analyzes the access to the application software and / or the file system requested by a predetermined client side. Application software management section that manages the required applications, an application database section that registers and stores multiple application software, and at least one application that manages the execution of certain required application software. A software execution management unit, an application software processing unit including, and a file system unit accumulating various files / directories requested by a predetermined client,
It is composed of a file system management unit that executes the required management, and on the client side, it is possible to start / execute the desired application software in the same manner as when opening the desired file / directory. On the client side, it is possible to start / execute appropriate application software on the server and / or the client in response to access to a specific file / directory on the server. Start application software /
Execution unit.