DISC

Contents | What's New | Quick Links

 

ODXSRVR

Introduction

Software Installation

Concepts and Design

Designing Applications

Omnidex Environments

SQL Reference

Omnidex API's

Utilities

Interfaces

Performance Guide

Troubleshooting Guide

Appendix

 

 

Preconnected Processes

Mapped Memory TransportConfiguration File

 

Preconnected processes are multiple, pre-defined connections to a specified OmniAccess environment that are established when the odxsrvr listener is started. These connections run on the server, waiting for client requests, eliminating the connect wait-time. This is particularly useful in multi-user and web environments. All of these connections use connect options defined in the odxsrvr configuration, which overrides any settings specified in the client's datasource.

Each time a client request comes through the listener for a datasource that is configured with preconnected processes, one of the pre-established connections will be used. The number of connections can grow dynamically as demand increases, up to a limit that is defined in the configuration file.

ODXSRVR Setup

ODXSRVR Syntax

Windows Service

Interactive Process

Preconnected Processes

Mapped Memory Transport

Configuration File

Any connect options passed from the client will be ignored when connecting to a preconnected process.

 

Setup

The ODXSRVR configuration file contains all the necessary settings and is required when using preconnected processes.

  • Each environment that will have preconnected processes will have its own section in the configuration file where the connect options, initial number of connections, connection limit, connection growth rate, etc... are defined.
  • Adding the datasource tag to the [Preconnected Processes] section of the ODXSRVR configuration file. This datasource tag must match the DataSource name defined in the client datasource file.
  • Each datasource tag defined in the [Preconnected Processes] section must have a corresponding [Preconnect datasource] section. The environment specifications and all preconnect settings for this environment are defined in this section. Again, the datasource tag must match the datasource tag in the previous section and the client datasource file.
  • Add the PreConnect=1 setting to the client datasource file. If this is not set correctly in the client datasource file, the preconnected processes will not be used, but a new connection will spawn for this client request.

 

 

 

top

Dynamic Information Systems Corporation - Omnidex Version 3.8 Build 6 J15.03-Copyright © 2003

DISC | Documentation Home