JP2001337935A - Application wrapping method in dispersed object environment, its communication management device, and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To update wrapper program operation without any alteration of a wrapper program itself even when definition information necessary for wrapping is changed in wrapping over a dispersed object environment of application on a non-dispersed object environment. SOLUTION: When a general-purpose wrapper program 121 refers to a definition information storage part 141 storing definition information necessary for wrapping, operation of the general-purpose wrapper program 121 is decided. When information necessary for the wrapping such as server application 101 to be wrapped and an interface for a client application 111 is changed, the definition information in the definition information storage part 141 is changed without changing any general-purpose wrapper program 121 itself, so that operation of the general-purpose wrapper program 121 can be changed.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of wrapping an application in a distributed object environment, and a communication management apparatus and a recording medium in which the method is programmed and recorded. With the application in the object environment, one can request the other, and the requested application can return the processing result to the requested application.
The present invention relates to a method of wrapping an application in a distributed object environment, a communication management device thereof, and a recording medium on which the method is programmed and recorded.

[0002]

2. Description of the Related Art OMG (Object Management Group)
CORBA (Common Object Request)
In a distributed object environment represented by the Broker Architecture, for example, a method of using an existing non-distributed object environment application, such as a transaction system on a general-purpose computer, in a distributed object environment can be applied to a non-distributed object environment application. There is a method of converting input / output into an interface on a distributed object environment. As above,
The appearance of an application in a non-distributed object environment as an object in a distributed object environment is called wrapping, and a functional unit for realizing this is called a wrapper.

FIG. 8 shows an example of a wrapping system.
As shown, the wrapping system includes a server computer 100, a client computer 110,
It comprises a communication management device 120, a distributed object network 130, a storage device 140, and an object management server computer 150. The server computer 100 includes a server application 101. The server application 101 is a program having an input / output interface to the outside of the server computer 100, executing a specific process in response to a request from the outside, and returning an execution result. The client computer 110 has a client application 111. The client application 111 has an input / output interface to the outside of the client computer 110, requests the server application 101 for processing, and reflects the result.
This is a program that performs a specific process.

The communication management device 120 has a wrapper program 122. The wrapper program 122 is
This is a program generated by the wrapper source code generation unit 123 and the compiler 125, and performs conversion between the interface of the client application 111 and the interface of the server application 101 and communication management. The storage device 140 includes a definition information storage unit 141. The definition information storage unit 141 is a functional unit that stores definition information necessary for wrapping an application in a non-distributed object environment, such as interface information of the server application 101.

[0005] Object management server computer 15
0 has an object management service 151.
The object management service 151 is a program for managing information for uniquely identifying an object in a distributed object environment. A client program obtains information for uniquely identifying an object by inquiring of the object management service 151. By using this information, it is possible to request processing of the target object.

[0006] The conventional wrapping system having such a configuration operates as follows. First, the wrapper source code generation unit 123 generates the wrapper source code 124 with reference to the definition information stored in the definition information storage unit 141. And the wrapper source code 12
4 is compiled and linked by the compiler 125 to generate the wrapper program 122.

[0007] The generated wrapper program 122 includes:
An object for the server application 101 is registered in the object management service 151. The client application 111 communicates with the wrapper program 122 by referring to the object information on the object management service 151. The wrapper program 122 that has received the input data from the client application 111 converts the input data into the input format of the server application 101 and passes it to the server application 101. Server application 1
When 01 returns the output data to the wrapper program 122, the wrapper program 122 converts the output data into a format required by the client application 111 and returns it.

By performing the above processing, it becomes possible for the client application 111 on the distributed object environment to use the server application 101 on the non-distributed object environment.

[0009]

According to the above-mentioned prior art, an interface of an application in a non-distributed object environment to be wrapped, and a distributed object environment for transferring processing to and from an application in the non-distributed object environment. The definition information required by the wrapper, such as the definition of applications in the non-distributed object environment and communication in the distributed object environment, is 1
Whenever it changes, the wrapper program itself must be regenerated. In other words, according to the conventional wrapping method, based on each definition information required for wrapping, a method of generating a corresponding wrapper program source code, compiling and linking the source code is adopted, so a wrapper is required. When even one piece of definition information changes, the wrapper program itself needs to be generated again. Therefore, the burden on the programmer was large and the efficiency was low.

The present invention has been made in view of the above circumstances, and refers to information necessary for wrapping an application existing on a non-distributed object environment as an object on the distributed object environment, thereby making the non-distributed object available. By determining the wrapping method of the application that exists on the object environment and determining the operation according to the method, even if the definition information required for wrapping changes, without regenerating the object code of the wrapper program It is an object of the present invention to provide a method of wrapping an application in a distributed object environment capable of updating the operation of a wrapper program, a communication management device therefor, and a recording medium on which the method is programmed and recorded.

[0011]

According to an aspect of the present invention, at least one application existing in a non-distributed object environment can be used as an object in a distributed object environment. A method of wrapping an application in a distributed object environment in which processing is passed between applications, and refers to information necessary for wrapping an application existing in a non-distributed object environment as an object in the distributed object environment. As a result, the method of wrapping the application existing on the non-distributed object environment is determined, and the operation is determined according to the method. As a result, since the wrapper program operates with reference to the definition information of the interface, the change of the interface is reflected in the wrapper program only by changing the definition information, and therefore, the application of the application in the non-distributed or distributed object environment is changed. When a change occurs in the interface, the interface change can be reflected in the wrapper program without changing the wrapper program itself.

According to a second aspect of the present invention, in the method for wrapping an application in a distributed object environment according to the first aspect, the wrapping is performed on an object management service which manages an available object on the distributed object environment. Registers or deletes an application that exists on the non-distributed object environment, and converts the format of a message sent from the application that exists on the distributed object environment into a message format that is sent to the application that exists on the non-distributed object environment. In addition, the format of a message sent from an application existing on the non-distributed object environment is converted into a message format sent to an application existing on the distributed object environment. As a result, since the wrapper program operates by referring to the definition information regarding the communication in the distributed object environment and the non-distributed object environment, the change in the communication definition is reflected in the wrapper program only by changing the definition information. As a result, when the definition of communication in the distributed object environment and the non-distributed object environment changes, the change of the communication definition can be reflected to the wrapper program without changing the wrapper program itself. .

According to a third aspect of the present invention, there is provided the method for wrapping an application in a distributed object environment according to the first or second aspect, further comprising creating an application existing on the distributed object environment from information necessary for wrapping. It was decided to create interface definition information to support. As a result, an interface definition in the distributed object environment, for example, an IDL is automatically created from the interface information stored in advance, thereby automatically creating an interface definition in the distributed object environment using the application in the non-distributed object environment. It is also possible to reduce the trouble of creating a client application.

According to a fourth aspect of the present invention, there is provided a communication management system for transferring processing between applications so that at least one application existing in a non-distributed object environment can be used as an object in a distributed object environment. The apparatus determines a wrapping method of an application existing in a non-distributed object environment by referring to information necessary for wrapping an application existing in the non-distributed object environment as an object existing in the distributed object environment. Then, a wrapping means for determining an operation according to the method is provided. According to the above configuration, the wrapper program operates with reference to the definition information of the interface. Therefore, just by changing the definition information, the change of the interface is reflected in the wrapper program,
Therefore, when a change occurs in the interface of the application in the non-distributed or distributed object environment, the change in the interface can be reflected on the wrapper program without changing the wrapper program itself. Therefore, it is possible to provide a new management device that greatly reduces the load on the programmer when the interface of the application in the non-distributed or distributed object environment is changed, and it is possible to construct an efficient wrapping system.

According to a fifth aspect of the present invention, in the communication management apparatus according to the fourth aspect, the wrapping means is configured to perform the non-operation with respect to an object management service which manages an available object existing in a distributed object environment. Means for registering or deleting an application existing on the distributed object environment, and converting a format of a message sent from the application existing on the distributed object environment into a message format to be sent to the application existing on the non-distributed object environment And means for converting the format of a message sent from an application on the non-distributed object environment into a message format to be sent to an application on the distributed object environment. With the above configuration, since the wrapper program operates by referring to the definition information regarding the communication in the distributed object environment and the non-distributed object environment, the change in the communication definition is reflected in the wrapper program only by changing the definition information. As a result, when the definition of communication in the distributed object environment and the non-distributed object environment changes, the change of the communication definition can be reflected to the wrapper program without changing the wrapper program itself. . Therefore, it is possible to provide a communication management device that greatly reduces the load on the programmer when the definition of communication in the distributed object environment and the non-distributed object environment is changed, and it is possible to construct an efficient wrapping system.

According to a sixth aspect of the present invention, in the communication management apparatus according to the fourth or fifth aspect, the wrapping means supports creation of an application existing on the distributed object environment from information necessary for wrapping. Means for creating interface definition information is further included. With the above configuration, an interface definition in a distributed object environment, for example, an IDL, is automatically created from interface information stored in advance, so that an interface definition in a distributed object environment using an application in a non-distributed object environment is created. It is possible to provide a communication management device that reduces the trouble of creating a client application, and to construct an efficient wrapping system.

[0017] According to a seventh aspect of the present invention, there is provided a distributed processing method for transferring processing between applications so that at least one application existing on a non-distributed object environment can be used as an object on the distributed object environment. A program for performing a wrapping process of an application in an object environment, wherein the program refers to information necessary for wrapping an application existing in a non-distributed object environment as an object in the distributed object environment; and Determining a method of wrapping the application residing on the distributed object environment and determining the operation accordingly, is programmed and recorded. When the computer reads and executes the above-described program, the wrapper program operates with reference to the definition information of the interface. Therefore, only by changing the definition information, the change of the interface is reflected in the wrapper program. Alternatively, when the interface of the application in the distributed object environment changes, without changing the wrapper program itself,
Interface changes can be reflected in the wrapper program. For this reason, the load on the programmer can be greatly reduced when the definition regarding communication in the distributed object environment and the non-distributed object environment is changed.

According to an eighth aspect of the present invention, in the recording medium according to the seventh aspect, the step of deciding a wrapping method and deciding an operation according to the wrapping method manages available objects in a distributed object environment. A step of registering or deleting an application on the non-distributed object environment with respect to the object management service, and a message format for transmitting a message format sent from the application on the distributed object environment to the application on the non-distributed object environment And a step of converting the format of a message sent from an application on the non-distributed object environment into a message format to be sent to an application on the distributed object environment. When the computer reads and executes the above program, the wrapper program operates by referring to the definition information regarding the communication in the distributed object environment and the non-distributed object environment. Therefore, the communication definition can be changed only by changing the definition information. Is reflected in the wrapper program, so that when the definition of communication in the distributed object environment and the non-distributed object environment changes, the wrapper program The change of communication definition can be reflected. For this reason, the load on the programmer can be greatly reduced when the definition regarding communication in the distributed object environment and the non-distributed object environment is changed.

According to a ninth aspect of the present invention, in the recording medium according to the seventh or eighth aspect, the step of determining a wrapping method and determining an operation according to the wrapping method further includes distributing information based on information necessary for wrapping. A step of creating interface definition information for supporting creation of an application on the object environment is included.
By reading and executing the above program by a computer, an interface definition in a distributed object environment, for example, an IDL is automatically created from interface information stored in advance, thereby enabling application in a non-distributed object environment to be executed. The burden of creating a client application in a distributed object environment to be used can be reduced.

[0020]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of a wrapping system to which the present invention is applied. In FIG. 1, a wrapping system includes a server computer 100, a client computer 110, and a communication management device 120 that operate under program control.
, Distributed object network 130, storage device 1
40, and an object management server computer 150. The server computer 100 includes a server application 101, and the client computer 110 includes a client application 111
including. The communication management device 120 includes a general-purpose wrapper program 121, and the storage device 140 includes a definition information storage unit 141. Further, the object management server computer 150 includes an object management service 151.

The server application 101 has an input interface with the outside of the server computer 100 or both an input interface and an output interface, and executes a specific process in response to a request from the outside. The client application 111 runs on the client computer 110, requests processing from the server application 101 via the distributed object network 130 and the general-purpose wrapper program 121, and performs a specific processing such as utilizing the execution result. Execute. General-purpose wrapper program 121
Registers the object for the server application in the object management service 151 according to the information stored in the definition information storage unit 141, and converts the input information from the client application 111 into the input format of the server application 101. The client application 111 converts the output information from the server application 101 into an output format to be passed to the client application 111 and transfers the output information.

The definition information storage section 141 stores information defining data conversion between input / output of the server application 101 and input / output of the client application 111.
General-purpose wrapper program 121, server application 101 and client application 111
It stores various information unique to the server application 101 and the client application 111 required by the general-purpose wrapper program 121 for wrapping, such as definition information on communication with the client application 111. The object management service 151 manages information such as an identifier and a location of an object that can be used in the distributed object environment, and registers an object usable in the distributed object environment in response to a request from each application in the distributed object environment. , Delete, search. When the application in the distributed object environment registers the object in the object management service 151, the registered object becomes available in the distributed object environment, and the application in the distributed object environment wants to use the object. Information of the object management service 151
By querying and obtaining information, the application can call the object you want to use.

FIGS. 2 and 3 are views cited for explaining the operation of the embodiment of the present invention shown in FIG. 1, and show a control procedure in a flowchart and an operation concept in a block, respectively. is there. Hereinafter, the operation of the embodiment of the present invention shown in FIG. 1 will be described with reference to FIGS.

First, the general-purpose wrapper program 121
The object for the server application is registered in the object management service 151 (step A1 in FIG. 2). The client application acquires object information for the server application by inquiring the object management service 151 of object information corresponding to the server application 101 requesting the processing (step A2). The client application 111 calls an object for the server application using the acquired information, so that data to be passed to the server application 101 is transmitted to the general-purpose wrapper program 121 (step A3).

The general-purpose wrapper program 121 receives input data from the client application 111 (step A4), and converts the data into the input format of the server application 101 based on the information in the definition information storage unit 141 (step A5). ). Next, the general-purpose wrapper program 121 transmits the converted input data in a format conforming to the interface of the server application 101 (step A6), and the server application 101 receives this (step A7). The server application 101 that has received the input data executes the program based on the input data (step A).
8) The output data including the execution result is transmitted (step A9).

The general-purpose wrapper program 121 receives the output data of the server application 101 (step A10) and converts it into output data required by the client application 111 based on the information in the definition information storage unit 141 (step A11). . Finally, the general-purpose wrapper program 121 transmits the converted output data (step A12), and the client application 111 receives it (step A13), whereby the execution of the server application 101 from the client application 111 is completed.

In the embodiment of the present invention described above,
The operation of the general-purpose wrapper program 121 itself is the same as that of the conventional wrapper program (FIG. 8, 122), but data conversion between input / output of the server application 101 and input / output required by the client application 111 and communication with the server application 101 are performed. The general-purpose wrapper program 121 itself is stored in the definition information storage unit 141 with respect to information necessary for communication between the client application 111 and the server application 101, such as information necessary for performing the communication and information registered in the object management service 151. Since the information stored in the definition information storage unit 141 is changed only when the specification of the server application 101 or the client application 111 is changed, the information stored in the definition information storage unit 141 is changed. It is possible to change the behavior of generic wrapper program 121.

That is, the general-purpose wrapper program 121
The change of the server application 101 or the client application 111 can be reflected on the general-purpose wrapper program 121 without any modification to itself. In the above-described embodiment of the present invention, the server computer 100 and the client computer 1
10, the communication management apparatus 120 and the object management server computer 150 can be made communicable without changing the general wrapper program 121 itself even if the definition information relating to the communication is changed.
That is, the definition information storage unit 141 also includes definition information regarding communication on each of the distributed object environment side and the non-distributed object environment side, and the general-purpose wrapper program 121 generates communication means by referring to the information. That's why.

Next, the operation of the embodiment of the present invention will be described in detail using a specific example. As shown in FIG. 3, for example, the format of a message in the distributed object environment is interface name, operation name, input / output attribute, type, value, attribute, type, , The message for the server application is in the form of a function name, input value, input value, etc. as in the message 21, the up message is in the form of the message 22, and the down message is in the format of the message 22 as in the message 22. , Function name, output value, output value,... At this time, the general-purpose wrapper program 121
Is an uplink message 11 in the distributed object environment as the uplink message 21 for the server application, and a downlink message 22 for the server application as the downlink message 1 in the distributed object environment.
Convert to 2. Between message 11 and message 12 and message 21
The interface definition information 31 defines a conversion rule between the message 22 and the message 22, and is stored in the definition information storage unit 141. Then, the interface definition information 31 is reflected on the general-purpose wrapper program 121.

In the example shown in FIG. 3, the interface definition information 31 includes client-side method names, client-side operation names, client-side input information, client-side output information, server-side function names, server-side input information, and server-side output information. Are described in the order of, and the information on the client side and the information on the server side are separated by “::”, and both the client information and the server information are distinguished from each other by the identifier, and between the input information and the output information by “::”. : ". When there are a plurality of elements in each piece of information, the information is separated by ",".

Here, a definition example in the interface definition information 31 will be described by taking the first line of the interface definition information 31 in FIG. 3 as an example. If the interface name of the distributed object called by the client application 111 is Intf_A and the operation name is Mtd_A, it means that Tx_A in the server application 101 is called, and two inputs from the client are performed. Both data types are long types, and when using them as arguments of the server application 101, both data types are set to INT.
Conversion to type 4 means that the data type of the output on the server side is INT4 type, and when it is output to the client, the data type is converted to long type.

The client application 11
1 and the general-purpose wrapper program 121, and between the general-purpose wrapper program 121 and the server application 1
01 is stored in the definition information storage unit 141 as communication definition information 32. In FIG. 3, the first line of the communication definition information 32 indicates the IP address of the object management server computer.
The second line defines the identification name of the server computer where the server application 101 exists. By referring to the interface definition information 31 and the communication definition information 32 by the general-purpose wrapper program 121, the general-purpose wrapper program 121 registers the object in the object management service 151 and performs the communication between the client and the wrapper or between the client and the wrapper. Communication and telegram conversion can be performed.

FIG. 4 is a block diagram showing another embodiment (second embodiment) of the wrapping system to which the present invention is applied. The difference from the first embodiment shown in FIG. 1 is that the communication management device 170 includes an IDL (Interface Definition Language) in addition to the configuration of the communication management device 120 shown in FIG.
e) having the generation means 171; The IDL generation unit 171 generates IDL, which is information for defining an interface in the distributed object environment, by referring to the interface definition information stored in the definition information storage unit 141. When the client application 111 is created, by translating the IDL, a source code corresponding to the interface portion of the client application can be generated.
It can be created based on the source code. Here, the trouble of creating the client application 111 can be reduced by automatically creating the interface definition in the distributed object environment.

In the above-described second embodiment shown in FIG. 4, the case where the IDL generation unit 171 operates on the communication management device 170 has been described.
1 may be operated on any computer capable of referring to the information in the definition information storage unit 141 in FIG. Also, in the first and second embodiments shown in FIGS. 1 and 4, the case where the general-purpose wrapper program 121 operates on the communication management device 120 has been described. However, as shown in FIG. 121
May be operated on the server computer 160, or may be operated on the client computer 110 as shown in FIG.

Further, in the first and second embodiments shown in FIGS. 1 and 4, a client application existing on the distributed object environment side requests processing from a server application existing on the non-distributed object environment. Although the form has been described, when an application existing in the non-distributed object environment requests processing from an application existing in the distributed object environment, or when an application existing in the distributed object environment and an application existing in the non-distributed object environment The same applies to the case where applications existing in each other request mutual processing. Further, in the first and second embodiments, the case where the object management service 151 operates on the object management server computer 150 has been described. However, the object management service 151 is not limited to the client computer 110 or the communication management device 120 shown in FIG.
Alternatively, it may be operated on any computer existing in the distributed object environment including the server computer 160 in FIG.

FIG. 7 is a block diagram showing still another embodiment (third embodiment) of a wrapping system to which the present invention is applied. Referring to FIG. 7, the third embodiment of the present invention includes a recording medium 400 on which a general-purpose wrapper program is recorded. The recording medium 400 may be a magnetic disk, a semiconductor memory, or another recording medium.
The general-purpose wrapper program is read from the recording medium 400 into the communication management device 300, and controls the operation of the communication management device 300. The communication management device 300 performs the following processes under the control of the general-purpose wrapper program, that is, the first and second processes.
The same processing as the processing by the communication management apparatuses 120 and 170 in the embodiment is executed.

First, the general-purpose wrapper program registers an object for a server application in the object management service 151. The client application acquires object information for the server application by querying the object management service 151 for object information corresponding to the server application 101 requesting the processing.
The client application 111 calls an object for the server application using the acquired information, so that data to be passed to the server application 101 is transmitted to the general-purpose wrapper program. Next, the general-purpose wrapper program receives the input data from the client application 111 and converts the data into the input format of the server application 101 based on the information in the definition information storage unit 141. Then, the general-purpose wrapper program transmits the converted input data in a format conforming to the interface of the server application 101, and the server application 101 receives this.

The server application 101 that has received the input data executes the program based on the input data, and transmits output data including the execution result. The general-purpose wrapper program is a server application 101
Is converted into output data requested by the client application 111 based on the information in the definition information storage unit 141. Finally, the general-purpose wrapper program transmits the converted output data, and the client application 111 receives this, whereby the execution of the server application 101 from the client application 111 is completed. Also, the recording medium 40
0 in the general-purpose wrapper program stored in
When the generation unit 171 is included, the IDL generation unit 171 refers to the interface definition information stored in the definition information storage unit 141 to obtain information for defining an interface on the distributed object environment. Generate an IDL. When the client application 111 is created, a source code corresponding to the interface portion of the client application is generated by using the IDL translation means, and can be created based on the source code.

First, second and third shown in FIG. 1, FIG. 4 and FIG.
In the third and third embodiments, the case has been described where the correspondence between the server application and the client application that pass the processing is one-to-one, but the correspondence between the server application and the client application that pass the processing is one-to-many and many. It may be one-to-one or many-to-many, and the number is not limited. In this case, the number of server computers on which the server application operates and the number of client computers on which the client application operates may be respectively plural, and the number is not limited.

[0040]

As described above, according to the present invention, since the wrapper program operates with reference to the definition information of the interface, the change in the interface is reflected in the wrapper program only by changing the definition information.
Therefore, when a change occurs in the interface of the application in the non-distributed object environment, the interface change can be reflected on the wrapper program without changing the wrapper program itself. This greatly reduces the burden on the programmer when the interface of the application in the non-distributed object environment changes.

For the same reason, when the interface of the application in the distributed object environment is changed, the change of the interface can be reflected on the wrapper program without changing the wrapper program itself. This greatly reduces the burden on the programmer when the interface of the application in the distributed object environment changes.

Further, since the wrapper program operates with reference to the definition information regarding the communication in the distributed object environment and the non-distributed object environment, the change in the communication definition is reflected in the wrapper program only by changing the definition information. Therefore, when the definition of communication in the distributed object environment and the non-distributed object environment is changed, the change of the communication definition is reflected to the wrapper program without changing the wrapper program itself. it can. This greatly reduces the burden on the programmer when a change is made to the definition of communication in the distributed object environment and in the non-distributed object environment.

Also, by automatically creating IDL, which is an interface definition in a distributed object environment, from the interface information stored in the definition information storage unit, a distributed object using an application in a non-distributed object environment can be created. It can also reduce the trouble of creating a client application in the environment.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a first exemplary embodiment of the present invention.

FIG. 2 is a flowchart showing the operation of the embodiment shown in FIG.

FIG. 3 is a diagram showing a specific example of the operation of the embodiment shown in FIG. 1;

FIG. 4 is a block diagram showing a configuration of a second exemplary embodiment of the present invention.

FIG. 5 is a block diagram showing a configuration in a case where a general-purpose wrapper program is included in a server computer in the first embodiment shown in FIG.

FIG. 6 is a block diagram showing a configuration in a case where a general-purpose wrapper program is included in a client computer in the first embodiment shown in FIG.

FIG. 7 is a block diagram illustrating a configuration of a third exemplary embodiment of the present invention.

FIG. 8 is a block diagram illustrating a configuration example of a conventional wrapping system.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 11 Uplink message in distributed object environment 12 Downlink message in distributed object environment 21 Uplink message for server application 22 Downlink message for server application 31 Interface definition information 32 Communication definition information 100, 160 Server computer 101 Server application 110, 180 Client computer 111 Client application 120, 170, 300 Communication management device 121 General-purpose wrapper program 122 Wrapper program 123 Wrapper source code generation means 124 Wrapper source code 125 Compiler 130 Distributed object network 140 Storage device 141 Definition information storage unit 150 Object management server computer 151 Object management service 171 IDL Generation means 00 recording medium

Claims (9)

[Claims] 1. A method of wrapping an application in a distributed object environment for passing processing between the applications so that at least one application existing in the non-distributed object environment can be used as an object in the distributed object environment. A method of wrapping an application existing on the non-distributed object environment by referring to information necessary for wrapping an application existing on the non-distributed object environment as an object on the distributed object environment. Wrapping an application in a distributed object environment, wherein the wrapping of the application is performed. 2. The distributed object environment according to claim 2, wherein said wrapping registers or deletes an application existing on said non-distributed object environment with respect to an object management service which manages an available object on said distributed object environment. The format of a message sent from an application existing on the non-distributed object environment is converted into a format of a message sent to an application existing on the non-distributed object environment. 2. The method of wrapping an application in a distributed object environment according to claim 1, wherein the application is converted into a message format to be sent to an application existing on the distributed object environment. 3. The distribution according to claim 1, wherein interface definition information for supporting creation of an application existing on the distributed object environment is created from information necessary for the wrapping. How to wrap the application in the object environment. 4. A communication management device for transferring a process between respective applications so that at least one application existing in a non-distributed object environment can be used as an object in the distributed object environment. A method for wrapping an application existing on the non-distributed object environment is determined by referring to information necessary for wrapping an application existing on the non-distributed object environment as an object existing on the distributed object environment. A communication management device comprising wrapping means for determining an operation according to the following. 5. A means for registering or deleting an application existing on the non-distributed object environment with respect to an object management service managing an available object existing on the distributed object environment. Means for converting the format of a message sent from an application existing on the distributed object environment into a message format to be sent to an application existing on the non-distributed object environment; The communication management apparatus according to claim 4, further comprising means for converting a format of the received message into a message format to be sent to an application existing on the distributed object environment. 6. The wrapping unit according to claim 4, further comprising: a unit that creates interface definition information that supports creation of an application existing on a distributed object environment from information necessary for the wrapping. Item 6. The communication management device according to item 5. 7. A wrapping of an application in a distributed object environment in which processing is passed between the respective applications so that at least one application existing in the non-distributed object environment can be used as an object in the distributed object environment. A program for performing a process, wherein information for wrapping an application existing on the non-distributed object environment as an object on the distributed object environment is referred to. Determining a wrapping method of an application existing in the computer, and determining an operation according to the wrapping method. 8. The method of determining the wrapping method and determining an operation according to the wrapping method comprises: providing an object management service managing an available object on the distributed object environment to an application on the non-distributed object environment. Registering or deleting, and converting the format of a message sent from an application on the distributed object environment into a message format sent to an application on the non-distributed object environment; Converting the format of a message sent from an application to a format of a message to be sent to an application in the distributed object environment. 9. The step of determining the wrapping method and determining an operation according to the method further includes a step of creating interface definition information for supporting creation of an application in a distributed object environment from information necessary for wrapping. 9. The recording medium according to claim 7, wherein the recording medium is readable by a computer.