sp_remoteoption sales, joe, bob, trusted, true
In this example, the remote login between sales.bob and inventory.joe is
trusted: No password needs to be supplied during the RPC. The network time
outs option indicates that connections used by the RPC will be held for
approximately 60 seconds before being closed (if off, this option allows the
connections to be held indefinitely), and the net password encrypted option
sends all RPC passwords in an encrypted form (more secure, but slower).
To report on the remote logins defined on a server, use sp_helpremote
CIS — Component Integration Services
An alternative to remote procedure calls was introduced in ASE 11.5: Com-
ponent Integration Services (CIS). Instead of requiring users to make explicit
calls of procedures in other servers, the SA may set up a logical data space
where multiple servers behave as if their objects were in a single server. A
user may query an object via a structure known as a proxy (a placeholder that
substitutes for the actual object), which is in the local server.
Behind the scenes, references to the proxy are translated into references
to the object’s actual physical location (server and database), transparent to
the user. When the results are returned to the user, it’s not apparent that they
came from “somewhere else.” Included within ASE are those portions of CIS
that communicate with Sybase server products (Adaptive Server Enterprise,
Adaptive Server Anywhere, Adaptive Server IQ); you may add licensed addi
tional code that will extend CIS’s capabilities to communicate with data
servers from other vendors, allowing for transparent, heterogeneous servers
(see Figure 14-2).
In ASE 12.5 and later, inter-server communication is made more secure
with the adoption of the Secure Sockets Layer (SSL) protocol. Most com
monly used with web servers, SSL allows for strong encryption of network
traffic using a well-publicized standard based on public key cryptography.
Additionally, Sybase has added support for the Lightweight Directory Access
Protocol (LDAP), which allows a small (lightweight), centralized service to
provide directory services. This can substitute for the presence of a separate
interfaces file on each node of the enterprise. In Windows NT, LDAP allows
the use of the registry to access servers; in Unix, another naming service can
be designated to supply server naming (but the traditional interfaces tech
nique is still used by default).
Only ASE-native CIS is the focus of our discussion.
302 Chapter 14: Remote Server Management