Configuring a Server for Remote Procedure Calls

Configure server installations to allow request for execution of stored procedures on a remote server from a local server. The result of this request is called a remote procedure call (RPC).

Your choice of RPC handling method affects SAP ASE configuration and login mapping for remote servers. To handle RPCs, you can use either a site handler, or Component Integration Services (CIS).

The default method for handling interaction between local and remote servers is through a site handler, which creates a physical connection between the local server and the remote server. It then creates a logical connection for each RPC to the remote server. SAP ASE creates a site handler for each remote server it connects to. A site handler is used only for connections between two server installations.

You can enable CIS for a server to request execution of stored procedures and access data on a remote server as if it were on the local server. CIS RPC handling is always used for connections involving proxy tables.

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 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 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.