Advantage Developer Zone

 
 
 

Increase Security and Flexibility with Server-Side Aliases

Thursday, January 12, 2006

Traditionally, Advantage has only supported client-side aliases via entries in the ads.ini file. While convenient, a client-side alias must exist on every client machine and it could pose a security risk by exposing the data path. New server-side alias functionality, which was introduced in version 8.0, hides the path to the data and does not require a Windows share.
 
Currently, server-side aliases are only supported on the Windows platform. NetWare and Linux support will be included in a future release. Server-side aliases are not supported by the Advantage Local Server.
 
Configuration
Server-side aliases must be placed in a file called AdsServer.ini. This file must reside on the server.  Since it doesn’t exist by default, any text editor can be used to create the file. The Advantage server uses the error log path configuration value to locate the AdsServer.ini file (the default value is c:\).
 
An example AdsServer.ini file with three aliases: 
 
 
Usage
To use a server-side alias, simply reference the alias name where you would normally reference a file share in your connection path.
 
For example, a typical connection string \\myserver:6262\c$\data\northwind.add would change to \\myserver:6262\bikes\northwind.add.  The “bikes” server-side alias is substituted for the actual path, “c$\data”.
 
 
 
Server-side aliases must always be used in conjunction with the Ignore Rights setting of the Advantage client.  See the Advantage help file for additional information regarding “Ignore Rights” settings, AdsServer.ini configuration, and Network Attached Storage Support.