OpenTP1 supports three different kinds of client/server communications that:
- use OpenTP1's remote procedure calls (RPCs)
This is a communication between UAP processes that uses OpenTP1's library functions. A UAP uses functions to issue service requests to a remote UAP. Normal RPC communication uses service information for the server UAPs that are managed by the name service at each node. The name service at each node manages the nodes in the network containing the target server UAP by exchanging service information. The optional function for service information searches enables you to choose a service request method that is appropriate to the communication mode in use. If OpenTP1-to-OpenTP1 communication is disabled by a network failure, you can prevent the subsequent RPC from resulting in an error by using node management.
For details, see the following:
- use the X/Open XATMI interface
This communication method complies with the DTP model stipulated by X/Open.
- use the X/Open TxRPC interface
This communication method supports DCE RPC with a transaction facility that is stipulated by X-Open. TxRPC communications directly call user-created functions.
If TCP/IP is used as a communication protocol, all of the above client/server configuration communications can be performed. If OSI TP is used as a communication protocol, communications use the XATMI interface. To perform OSI TP communications, you need TP1/NET/OSI-TP-Extended in your OpenTP1 system. For details about the OSI TP communications, see .3.6 Client/server communications using OSI TP.
- Organization of this section
- 3.2.1 Communication via RPCs that use the OpenTP1 library
- 3.2.2 Optional function for service information searches
- 3.2.3 Node management in OpenTP1
- 3.2.4 Communication via RPCs that use the XATMI interface
- 3.2.5 Communication via RPCs that use the TxRPC interface
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.