Version 9.6
 —  EntireX RPC Programming  —

Common Features of Wrappers and RPC-based Components

This document provides additional information on concepts and features common to all wrappers and RPC-based components. It covers the following topics:

Change RPC Password by Wrappers and RPC Clients

The application programmer can embed an RPC password change in an application. This is useful if the application programmer wants to provide this functionality to end users of RPC applications. It is necessary if the RPC server forces alteration of the RPC password, otherwise denying use of the RPC server.

The functionality is provided with a special-purpose IDL:

Library 'SAGCRPW' : 'SagChangeRPCPassword' is
  Program 'SAGCRPW' : 'changeRPCPassword' is
    Define Data Parameter
	      1 newRPCPassword (A8) in

The prefix "SAG" is reserved and is used for Software AG delivered IDL files and must not be used by customer applications; see Rules for Coding Library, Library Alias, Program, Program Alias and Structure Names under Software AG IDL File.

Proceed as follows:

Natural RPC Server running under Natural Security

Other RPC Servers

Top of page

Natural Logon or Changing the Library Name

The library name sent with the RPC request to the EntireX RPC or the Natural RPC Server is specified in the Software AG IDL file (see library-definition under Software AG IDL Grammar). The library name can be overridden by wrapper-specific methods, see your wrapper documentation.

For EntireX RPC Servers, depending on the target server, the library name

For Natural RPC servers, the library name

Top of page

Conversational RPC

EntireX RPC and Natural RPC also supports conversational communication (also known as connection-oriented communication), where the two partners (client and server) retain a communication link over several remote procedure calls.

A context can be maintained on the server side when a Natural RPC Server is in use. See the DEFINE DATA CONTEXT statement in the appropriate Natural documentation.

EntireX Wrappers and RPC clients allow termination of an RPC conversation either successfully or abnormally by offering two different methods or function calls for ending an RPC conversation. See the appropriate EntireX Wrapper or RPC client documentation for information on how to initiate the end of an RPC communication.

If communicating with a Natural RPC Server and

See your Natural and Natural RPC documentation for more information.

If communicating with an EntireX RPC Server

Top of page

Non-conversational RPC

The basic method of communication for both the EntireX and the Natural RPC is non-conversational (also known as connectionless communication).

Using this method,

Top of page

Natural Security

A Natural RPC Server may run under Natural Security to protect RPC requests. RPC clients need to be

See your Natural Security documentation for more information.

Top of page

RPC Compression

RPC compression is a feature used to reduce network data sizes. EntireX tries to select RPC compression automatically. If RPC compression is supported by your RPC server, we recommend using it.

Natural RPC Servers

Natural RPC Servers running under Natural version 3.1.6 and later support RPC compression. If you are communicating with Natural RPC version 5.1.1 and later, RPC compression is selected automatically. To enable connection to earlier versions of Natural RPC Servers, EntireX wrappers and RPC technology allow you to switch off RPC compression.

EntireX RPC Servers

All versions of the EntireX RPC server support RPC compression. If you are communicating with an RPC server using EntireX 5.3.1 and later, RPC compression is selected automatically.

Top of page