Successfully issuing
the LIBNAME statement or SQL pass-through statements initiates an
SPD Server client session. The client session operates using a combination
of the following four components.
SPD Server name server
The name server acts
like a traffic cop and serves as command central between clients and
SPD Server hosts. The name server maintains a list of LIBNAME domains
associated with each SPD Server host. Client sessions always connect
to an SPD Server host through a name server. The name server resolves
the submitted LIBNAME domain name (a logical entity) to a physical
path (usually a UNIX or Windows directory). The name server connects
you to the SPD Server that servers the domain without requiring you
to know physical addresses. An SPD Server administrator sets up the
LIBNAME domains in a parameter file for SPD Server, which then registers
its domains with the name server.
SPD Server host
Each SPD Server host
controls security access to the domain resources that it manages.
When an SPD Server host starts, it registers its LIBNAME domains with
the name server. Clients can connect to an SPD Server host only through
a name server. Direct connections between clients and SPD Server hosts
are not permitted. The SPD Server host validates the client user ID
and password (passed in the LIBNAME statement), launches the system
process (client proxy) for each client, and grants access to the appropriate
SPD Server domain.
SQL server
The SQL server parses
and processes the SQL pass-through syntax submitted by the SAS client.
SPDSSNET server
The SPDSSNET server
enables access between clients without SAS and SPD Server. The SPDSSNET
server runs as a stand-alone process on either the client or SPD Server
host machine. It acts as a bridge between the SAS ODBC driver and
the SPD Server host. You can use SPDSSNET with JDBC drivers and with
htmSQL drivers. SPDSSNET can run multiple processes concurrently and
perform parallel processing.