Users on a local Adaptive Server can execute stored procedures on a remote Adaptive Server. Executing an RPC sends the results of the remote process to the calling process—usually displayed on the user’s screen.
To enable RPCs, the System Administrator and System Security Officer of each Adaptive Server must execute the following steps:
On the local server:
System Security Officer – use sp_addserver to list the local server and remote server in the system table master..sysservers.
List the remote server in the interfaces file or directory service for the local server.
Restart the local server so the global variable @@servername is set to the name of the local server. If this variable is not set properly, users cannot execute RPCs from the local server on any remote server.
On the remote server:
System Security Officer – use sp_addserver to list the server originating the RPC in the system table master..sysservers.
To allow the user who is originating the remote procedure access to the server, a System Security Officer uses sp_addlogin, and a System Administrator uses sp_addremotelogin.
Add the remote login name as a user of the appropriate database and grant that login permission to execute the procedure. (If execute permission is granted to “public,” the user does not need to be granted specific permission.)
Figure 15-1 shows how to set up servers for remote access.
Figure 15-1: Setting up servers to allow remote procedure calls
For operating-system-specific information about handling remote servers, see the the installation documentation for your platform.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
