If you or your users are operating in a network environment, the final step is to start theAcuXDBC server daemon on the server. If you are operating on a stand-alone machine, this step is not necessary; you can begin using ODBC applications to access your data right away.
AcuXDBC Server can be started under any user ID on the system. In this mode, all file access will be performed using the user and group ID under which the daemon was started. You also have the option of startingAcuXDBC under the root or superuser account and turning on operating system (OS) authorization checking with the -a option. This option lets one user start a process and pass ownership to another. In this mode, you must pass a valid operating system user ID and password as part of the connect string. AcuXDBC Server will use this information to perform an OS authentication of the user and then spawn a process to handle the requests using this user information.
Note that to perform the functions described in this section on a UNIX server, you should be logged in as root or superuser. To perform these functions on a Windows NT or Windows 2000 server, you should be logged in from the administrator account or from an account that belongs to the administrators group.
Enter the following at the command prompt:
This runs a script that invokes the xdbcsrvr daemon on the default port, 20222, with the "-k" option to request data encryption over the network. If the xdbcsrvr daemon is already running, AcuXDBC Server displays the message:
The AcuXDBC Server 9.x.x on the default port <20222> service is already installed
A new xdbcsrvr process will not be started. You can, however, start multiple AcuXDBC Servers on different ports. If you want to start the AcuXDBC Server with new options, you must stop and restart xdbcsrvr.
If you would like to invoke the server daemon with different security, logging, or port options, you can issue the xdbcsrvr command directly. Following is the command syntax for xdbcsrvr.
xdbcsrvr [-a[l]] [-p] [-kn] [log]
acuxdbcs.exe -start [-n port] [-1]
Optional arguments to xdbcsrvr include:
|-a[l]||Activates the operating system (OS) authorization checking. This option lets one user start a process and pass ownership to
You must pass a valid OS user ID and password as part of the connect string, so the spawned service knows who owns it. xdbcsrvr performs a default OS authentication.
If the [l] modifier is specified, xdbcsrvr logs the outcome of the authentication request to the system log. On UNIX, this is syslogOn Windows, this is the event log
|-kn||Specifies a masking key value used to decrypt incoming OS and DBMS user ID and password information. Clients must have the same value in their net.ini file in the KEY_CONNECT variable|
|-pport_number||Assigns the listener port number for clients to request service. The default is 20222|
|log||Starts logging. It puts a log file named tcmprocessid.log in the directory in which xdbcsrvr is started|