User`s guide

S YSTEM I NSTALLATION
The SFVRA Connection Manager consists of four components: the Client, which is the user
interface to the database; the services, which control the Agents by the TCP/IP connection based
on the information stored in the database; the Agents, which are the Remote Access Switches; and
the Database. You also need an Open Database Connectivity (ODBC) software driver to connect
each of the components, and an NDIS driver for the SFVRA RIP Service and the SFVRA Proxy ARP
Service
This chapter provides instructions for installing the SFVRA Connection Manager system, and we
also include instructions for installing the Adobe Acrobat Reader. You will need this reader to view
the SFVRA-CONN user documentation.
INSTALLING THE SFVRA CONNECTION MANAGER SYSTEM
You must perform the following steps to install the SFVRA-CONN system.
1. Install the MS SQL Server
2. Install the ODBC Driver Pack 3.0
3. Install the SFVRA-CONN Software
4. Install the SFVRA Database
5. Install the NDIS driver
The following sections include instructions for performing each step.
INSTALLING THE MS SQL SERVER
Install the MS SQL Server according to the manufacturer’s instructions. Ensure that the MS SQL
Server Service is running.
INSTALLING THE ODBC DRIVE PACK 3.0
Each service for SFVRA Connection Manager requires a connection to the SQL Server. The
components are connected by a set of software drivers called the ODBC (Open Database
Connectivity). The ODBC hides the type of server, the location of the server, and the network
protocol used to access the server from the application. This is an important feature because it gives
the administrator the ability to control exactly how database is being used at any time. SFVRA-
CONN requires the use of a 32-bit ODBC driver.
If the database is on a different IP subnet than the Client interface, SFVRA Service, RIP Service, and
Proxy ARP Service, the ODBC drivers for these components must be configured to use IP rather
than NetBEUI. To use IP transport protocols, a Network Library and a Network Address must be
defined. If you are utilizing the password protection mechanism provided by the SQL Server, you
must use either the LMHOSTS file or WINS to resolve the server name to an IP address. Simply
configuring the ODBC Network Address will not be sufficient to read the remote registry.