ODBC4x
Server Settings for Windows Server Configuration
  The server is configured in Windows via the ProvideX IO Server Settings interface, which can be accessed directly from the Start menu.

The default TCP/IP port number is 20222.

   
Activation As with most ProvideX products, valid activation information (serial number, number of users, and activation key) must be recorded in order to activate the ProvideX IO server. If the activation is accepted, the configuration program returns a confirmation message when you press Apply.

It is possible to change the activation at any time. For example, an increase in the number of users on the system could require a new license and new activation values. The ProvideX IO Server controls the number of concurrent client connections and denies access if the number of users is exceeded.

Because activations are only verified during the initialization process, the server must be restarted when a new activation is recorded.

   
NT Service The ProvideX IO Server installation program checks the operating system and, if it detects a NT/2000/XP system, it automatically sets it up as a service. On installation, the server’s Startup Type defaults to Automatic, which means that the ProvideX IO service will start automatically every time the system reboots and will run independently of any logged-on user. This setting is evident by the message displayed in the NT Service folder:

ProvideX IO Service is running.

As with other services, the IO service can be controlled (stopped, paused, etc.) using the Windows Services interface, which is accessed via the Control Panel (in the Administrative Tools subfolder on Windows 2000/XP). The ProvideX IO service can also be uninstalled (and reinstalled) via the NT Service panel.

*Note* The NT Service tab will be hidden if the server is installed on Windows 9x systems —they do not support applications running as services. While it is still possible to run the ProvideX IO Server as an application on a Windows 9x desktop, it is not recommended. Windows 9x is not designed to be a server class machine.
   
Permissions On installation, the server is set to default access permissions. These permissions can be viewed/changed in the Permissions folder of the ProvideX IO Server Settings interface:
Setting Default Definition
Access A Access allowed
R/W R Read only
User ID * Any users
Company Code * Any Company
Data Dictionary Path * Any Data dictionaries
INI file Path * Any INI files
  The above default settings grant users almost unrestricted read access to the server’s data sources. (An asterisk * indicates any.) Therefore, for security reasons, you should reset the parameters based on your own business rules immediately following installation.

The ProvideX IO Server checks access permissions by searching the permission rules from the maximum restriction to the lowest one. It is a method to grant access to specific directories on the server based on a client's User ID and Company Code.

If the check for a specific User ID and Company Code fails, then the User ID is substituted with * (any) and the combination for User ID = any with Company Code = specific is checked against the corresponding rule if it is present on the system. The next check is performed for User ID = specific, Company Code = any, and the last check is for User ID = any, Company Code = any. Refer to the following table:

Sequence User ID Company Code  
1. Specific Specific Highest Restriction
2. Any Specific  
3. Specific Any  
4. Any Any Lowest Restriction
  In the following example, user John from ABC company is granted access to the data files defined in the providex.ddf files located in c:\pvxdata and/or c:\pvx\mydatadirectories and in the test.ini file located in c:\nomtrain:

According to this example, the server administrator has temporarily denied John access; however, John would still have read-only access to directories as all users of all companies may access any directory.