JPH07319831A - Api coexistence system in distributed transaction processing system - Google Patents

Abstract

PURPOSE:To use an interface in the same distributed transaction system by properly using an interface to be used for communication among programs in the range of an original API from an interface to be used for communication among programs in the range of a standard API conforming to X/Open. CONSTITUTION:Respective programs 51 to 53 access data resources 21 to 23 and server types 31 to 33 and a manager selects an interface appropriate for an opposite program to execute the communication among programs. When a server starting request under the management of the manager is outputted, an object name and an object attribute are obtained to judge the object attribute. In the case of indicating an original application program interface(API), a server to be used for the original API is started. In the case of indicating XATMI, the existence of a server UAP is judged, and when the server UAP exists, a false object name is registered and the starting operation of a server to be used for an XATMI interface is executed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention is a unique AP of a client / server type distributed transaction processing system.
"XATMI interface" compliant with I and X / Open
APIs different from standard APIs such as
AP of computer system that sends and receives data between multiple programs created in the same range
I mixed system.

[0002]

2. Description of the Related Art Conventionally, a program / program communication method in a client / server type distributed transaction processing system is a manager that manages data resources processed by programs in a system in which a plurality of computers containing a plurality of programs are connected by a network. In the definition format of the manager, an object name that represents a data resource to be managed is provided, and when requesting inter-program communication, the object name and the program name that processes the data resource are specified, and the partner program Regardless of the location of the communication partner program (for example, even when the communication partner program exists in the same computer), communication with the partner program is performed through the same programming interface.

In addition, "Nikkei Computer, 1993.
6.14, pp. 51 ”describes a“ distributed transaction processing (DTP) model ”showing a component configuration required for transaction processing defined by X / Open, which these distributed transaction processing systems comply with. According to this, interoperability between different models will be enhanced by proceeding with the standardization work of the interface between each component. Among them, there are currently three A in the standard interface for program communication.
The PI is specified, and the XATMI interface is one of them. If these standard APIs for inter-program communication are supported, application programs can be easily transferred, and interoperability in inter-model communication is enhanced.

[0004]

The above-mentioned prior art is a client / server type distributed transaction processing system having a unique interface for program-to-program communication, and when the standard interface compliant with X / Open is supported, the same system is used. There is no processing for mixing different APIs, and the processing method is X
/ Open is not standard.

An object of the present invention is to distinguish between interfaces used for communication between programs created in the range of a unique API and communication between programs created in the range of a standard API conforming to X / Open so that the same distribution can be achieved. An object of the present invention is to provide a mixed method of APIs that enables an interface suitable for each communication in a transaction processing system.

[0006]

In order to achieve the above object, a method of mixing APIs in the same distributed transaction processing system of the present invention is such that a computer having a plurality of programs created in the range of different APIs uses a network. In a system in which a plurality of programs are connected to each other, a manager for controlling inter-program communication is provided, and in the definition format of the manager, a server type indicating the type of API used for each server is provided to request inter-program communication. By specifying the server type, you can select the API to use when starting the server
In the case of PI, the object name and the program name for processing the data resource are specified as usual, and in the case of the XATMI interface, the pseudo object name representing the data resource to be managed is registered for communication, and the client / server distributed processing system has its own It is characterized in that the API and the standard API compliant with X / Open can be communicated with one system. Further, in the program-to-program communication by the manager, application programs created within the respective API ranges have compatibility with each other in the same system,
It is characterized by performing communication.

[0007]

In the present invention, programs created in the range of different APIs of the original API of the client / server type distributed transaction processing system and the standard X / Open-compliant API "XATMI interface" are distributed transactions. When performing inter-program communication in the processing system, each A used for each server to define the manager that controls inter-program communication
By specifying the PI server type, it is possible to use the unique interface and the XATMI interface properly in the same system. As a result, inter-program communication in which different APIs are mixed in the same system becomes possible, and application programs created within the range of each API are compatible in the same system and can communicate.

[0008]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing an example of the configuration of a system that applies the API mixed method in the distributed transaction processing system of the present invention to inter-program communication. In this embodiment, the computers 11, 12 and 13 are connected to the network. Then, each computer 11, 12,
13 includes data resources 21, 22, 23, server types 31, 32, 33 and servers 41, 42, 43, respectively.
Exists. Further, each server 41, 42, 43 has programs 51, 52, 53 created by either its own API or XATMI-API. The computer 11 has a manager 60-1 for managing the data resource 21 and the server type 31, the computer 12 has a manager 60-2 for managing the data resource 22 and the server type 32, and the computer 13 has a data resource 23. And a manager 60-3 for managing the server type 33. In FIG. 1, each of the programs 51, 52, 53 is a data resource 21, 2 respectively.
2, 23 and server types 31, 32, and 33 are accessed, the manager selects an appropriate interface with the partner program, and performs inter-program communication.

FIG. 2 is a diagram showing a definition format designated to the manager in FIG. Manager 60-of FIG.
The definition format for Nos. 1 and 60-2 includes 71 for designating the data resource managed by the manager. This definition 71
Is an object name 71 representing the data resource.
1 and an object attribute 712 indicating whether the type of the server used to operate the data resource is the original API or the XATMI interface.

FIG. 3 is a flow chart showing the server starting operation of the manager in FIG. In this embodiment,
When there is a server activation request under the management of the manager (1001), the object name and the object attribute are acquired from the definition shown in FIG. 2 (1002), and the object attribute is determined (1003). If you show your own API,
Start the server used for the original API (100
7). If it indicates XATMI, it is determined whether it is a server UAP (1004). If it is a server UAP, a pseudo object name is registered (1005), and XATMI is registered.
Start the server used for the interface (1
006).

[0011]

According to the present invention, in a client / server type distributed transaction processing system in which a plurality of computers having a plurality of programs are connected by a network, the conventional API and X /
It becomes possible to perform inter-program communication in which different APIs different from the standard API "XATMI interface" compliant with Open are mixed, and application programs created in the respective API ranges have compatibility in the same system.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration example of a system in which an API mixed method in a distributed transaction processing system of the present invention is applied to inter-program communication.

FIG. 2 is a diagram showing a definition format designated to a manager in FIG.

FIG. 3 is a flowchart showing a server starting operation of the manager in FIG.

[Explanation of symbols]

 10 ... Communication network, 11, 12, 13 ... Computer, 21, 22, 23 ... Data resource, 31, 32, 33 ... Server type, 41, 42, 43 ... Server, 51, 52, 53 ... Data processing program, 60 -1, 60-2, 60-3 ... Manager, 71 ... Object definition, 711 ... Object name, 712 ... Object attribute.

Claims (3)

[Claims] 1. An inter-program communication method of a client / server type distributed transaction processing system in which a plurality of computers having a plurality of programs created in the range of different application program interfaces (API) are connected by a network. A manager for controlling inter-program communication is provided, and a server type that indicates the type of API for each server used by the system is provided in the definition format of the manager. When requesting inter-program communication, the server type is specified. By doing so, the client / server distributed transaction processing system has its own API and X / Ope
A mixed API method in a distributed transaction processing system, characterized in that a standard API "XATMI interface" compliant with n can be used in the same system. 2. Inter-program communication by the manager,
Original API of client / server type distributed transaction processing system and standard AP compliant with X / Open
Each API with I "XATMI interface"
2. The mixed system of APIs in the distributed transaction processing system according to claim 1, wherein the application programs created in the range are compatible with each other in the same system and communicate with each other. 3. The manager is X / other than XATMI.
As for the Open-compliant standard API, by specifying the server type indicating the API type for each server used in the system, which AP can be used for inter-program communication.
The mixed system of APIs in the distributed transaction processing system according to claim 1, wherein the server to be used is started after determining whether to use I.