Configuring RPC handling

This topic discusses the mechanisms that Adaptive Server can use to manage RPCs and how to configure them. Your choice of RPC handling method affects Adaptive Server configuration and login mapping for remote servers. The options are site handler and CIS RPC handling.

The default method for handling interaction between local and remote servers is through a site handler. A site handler creates a physical connection between the local server and remote server. Then it creates a logical connection for each RPC to the remote server. Adaptive Server creates a site handler for each remote server it connects to. Site handler is used only for connections between two Adaptive Server installations.

CIS RPC handling is always used for connections involving proxy tables. It creates connections using Client-Library functions. You can also enable it for use with all RPCs.

The principal difference between the two methods of handling RPCs is how the remote server views the RPC:

If you use site handler, the remote Adaptive Server detects that the logical connection is made by another remote server and performs remote server verification through sysremotelogins.
If you use CIS RPC handling, the remote server sees the RPC as an ordinary client connection. There is no verification using sysremotelogins. Therefore, connections must have a valid Adaptive Server login account established prior to the connection request. You cannot use trusted mode.

Use of CIS RPC handling allows you to include RPCs in a transaction. Work done by an RPC can be committed or rolled back along with the other work performed in the transaction.