Configuring Component Integration Services Remote Procedure Calls

CIS uses persistent client-library connections to handle the RPC request.

CIS handles outbound RPCs by determining whether the client already has a client-library connection to the server in which the RPC is intended. If no connection exists, it will be established.

To enable the CIS RPC handling mechanism, set the configuration option cis rpc handling to 1. When not enabled, the Kerberos user needs to temporarily enable CIS RPC for the current session to use this feature.

This command enables CIS RPC handling for the current login session:

set cis_rpc_handling on

In the following example, user1 is a Kerberos user who logins into SAP ASE S1 and request RPC to the remote SAP ASE S2.

Add an entry to the interfaces file or the Directory Service for both servers S1 and S2 and a secmech line for the Kerberos security mechanism.
Add a login for the Kerberos user if one does not exist.
```
create login user1 with password pwuser1
```
Enable the use of security mechanisms by setting the configuration option to on.
```
sp_configure "use security services", 1
```
On the local server S1, enable Kerberos Authentication for CIS to remote server S2.
Note: This assumes that remote server S2 only receives CIS command requests from S1. However, if S2 can also request CIS commands to other servers and requires enabling Kerberos Authentication, than similar configuration on S2 will be required.
1. On the local server S1, add the remote server S2.
  sp_addserver S2
2. Enable Kerberos security mechanism on S1 for outbound RPC requests to S2. The following command enables CIS RPC handling for the current login session.
  sp_serveroption S2, "security mechanism", csfkrb5