|
By default, ODXNET creates pooled processes for each application
type (ODBC, JDBC, OmniAccess) automatically when the listener
is started. Each client connection attempts to use a pooled
process unless explicitly directed through an option to have
a new process created.
Each application type comes with a generic application pool
that is used by ODXNET. Environment specific application pools
can be setup in the ODXNET configuration file for the listener.
 NSADMIN
works with ODXNET in the same manner as ODXSRVR.
Setup
Setting up ODXNET varies depending on the operating system
and intended use.
- First, create or modify the ODXNET
configuration file. This file contains settings that
ODXNET will use at run-time.
The configuration file is optional but recommended. Most
of the required settings have defaults that will be used
if the configuration file is omitted. However, some scenarios,
such as setting up a Windows NT Service or creating environment
specific application pools, require settings that can only
be defined in the configuration file.
- Set the environment
variables.
- Start the listener
process.
- Setup the client. Omnidex
client must be installed on each client machine intending
to connect to an Omnidex
environment.
- Test the connection.
It is always a good idea to test the connection before
trying to use a client application with the datasource.
The Windows client tool DS
EDIT is ideal for this.
- Run the client application.
top
|
