Home

Getting Started

Utilities

Indexing

Omnidex

Development

Tutorials

Quick Links

 

Utilities

ODXNET

Configuration

 

ODXNET

Directives

Unix

Windows

Pooled Processes

Preconnected Processes

Configuration File

Pooled Processes

Pooled processes are processes established when the ODXNET listener is started, that run on the server waiting for client requests. Libraries are loaded and memory is allocated in advance, eliminating much of the overhead of connecting to an environment. ODXNET automatically creates 5 pooled processes for each client application type, ODBC, JDBC and CLOA, when the listener is started. These processes are reused and can automatically grow and shrink in number as needed.

Pooled processes are not the same as preconnected processes, which establish connections to a specific environment catalog. Pooled processes are generic processes can connect to any Omnidex environment.

Pooled processes can be defined explicitly for an application type in the ODXNET configuration file. At this time, the only configuration available for pooled processes is whether or not to use them for an application type. See Configuration below for details.

If an ODXNET configuration file is not used, pooled processes for the different application types will be created when the ODXNET listener is started, using default settings, unless the -nopools option is used. In which case, no processes will be started and no connections will be opened to any Omnidex environments until a client request is received. However, client connection times can be greatly reduced by using a waiting process, therefore, we do not recommend using the -nopools option unless specific application needs require it.

 

Configuration

Configuring pooled processes is done in the ODXNET configuration file.

At the beginning of the configuration file is a section labeled "[General]". In this section is a directive called "SkipProcessPooling" which, by default, is set to zero ( 0 ), meaning OFF. If you want to prevent any pooled processes from being established, change this setting to 1.

 

A little farther down the configuration file is a section labeled "[Applications]". Applications refers to the three different application types available for Omnidex development, that will go through Omnidex Network Services. The types are ODBC, JDBC and CLOA, specified as ODXODBC, ODXJDBC and OMNIACCESS respectively in the ODXNET configuration file. You can turn off pooled processes for one of these application types by commenting out the application tag in this section.

For example, if your application is strictly ODBC, meaning no JDBC or CLOA applications will run through this ODXNET listener, you can comment out both the JDBC and CLOA tags. This will allow pooled process to be established for ODBC application but not JDBC and CLOA applications.

[Applications]

ODXODBC=Omnidex ODBC Driver
;ODXJDBC=Omnidex JDBC Driver
;OMNIACCESS=Omnidex Access API

DSEDIT required both ODBC and CLOA pooled processes in order to test a connection. If you've turned off pooled processes for either of these application types, DSEDIT will not be able to test a connection.

 

Each application type, from the Applications section, has its own sub-section with configuration information specific to that application type. These sections are labeled "[ODXODBC]", "[ODXJDBC]" and "[OMNIACCESS]".

[ODXODBC]

LibraryName=odxdbcnet
; Library name where the connect and transmit
; interface routines are kept.

TransmitRoutineName=odbc_transmit
; Routine name

This section defined the library and transmit routines used by each application type.

 

 

 

Top