PSQL Optional Features

PSQL Optional Features

During a Custom install, PSQL features may be excluded with the PSQL product you are installing. The features listed here are optional, so if all the features in this section are excluded from the install, the PSQL product is still installed by default.

The following lists the optional features available with each PSQL installation, unless noted otherwise.

PSQL Access Methods

PSQL Access Methods include the PSQL Software Developer’s Kit (SDK) and the DOS Requester.

ActiveX Interface Controls

A set of nine custom controls that enable development environments that support ActiveX to easily access Btrieve data. The interface includes a data source control and eight bound data controls.

ADO.NET Provider

ADO.NET is a .NET managed data provider, built with 100% managed code. The data provider is a native wire protocol provider, which means that the data provider will not have to call out to unmanaged code-code outside of the .NET Framework-in the form of a database client.

The DOS VxD (Virtual eXtended Driver) (DOS client requester) is the Btrieve requester used for running DOS based applications via a Windows Command window. (Transactional access only)

The PSQL Distributed Tuning Objects (DTO) are used from visual development environments.

The Java Class Library (JCL) is used for direct transactional access to data files via Java.

The JDBC driver is used for relational access to data files using the Java programming language.

The OLE DB access method includes runtime binaries used for transactional and relational access to data files.

The PSQL Direct Access Components (PDAC) includes a set of Visual Component Library (VCL) components that allow direct transactional and relational access to PSQL Database Engines from within the Borland Delphi and C++ Builder Environments.

Note: Design time component and sample downloads will be available for each access method on the PSQL website.

The minimum set of utilities used to manage, configure and maintain the various components of the PSQL database engines. The utilities included in this base set are installed as a set for all PSQL products and may not be individually excluded from installation.

•

Function Executor

•

Btrieve Maintenance

•

•

Query Plan Viewer

•

License Administrator

•

Gateway Locator (Workgroup Engine only)

Cobol Schema Executor

The PSQL Cobol Schema Executor utility is used for providing SQL access to COBOL based applications.

Data Dictionary File Builder

PSQL Data Dictionary File Builder is used for creating and modifying Data Dictionary Files (DDFs).

PSQL Control Center

The PSQL Control Center is used for creating and manipulating database objects and accessing database tables via SQL.

PSQL System Analyzer

The PSQL System Analyzer utility is used for testing and troubleshooting network connectivity, viewing loaded modules and performing a component search.

The PSQL Engine and SDK user documentation is integrated into PSQL Control Center (PCC). The documentation library is accessed through the PCC interface on the Welcome view, in the Help menu, by pressing F1 (Windows) or Shift F1 (Linux). The Engine and SDK user documentation is also available online at the PSQL website.

Note: If you choose to not install the documentation, context sensitive (F1) help will be unavailable from all of the PSQL utility graphical user interfaces.

Java Runtime Environment (JRE)

The components of the JRE needed by the following features are installed as part of PSQL:

•

•

•

•

PSQL features use the local version of the JRE installed by PSQL. PSQL installs a local version of the JRE only if the minimum required JRE version is not installed. If the minimum required JRE version already exists, PSQL features will use those files instead of installing another local copy of that JRE.

Note: The installation of a local version of the JRE is for use only by the PSQL features listed above. The local version of the JRE does not affect the requirements for developing Java applications using the PSQL access methods Java Class Libraries (JCL) or JDBC. Those requirements, such as components obtained from java.sun.com, are discussed in the PSQL software development kit (SDK) documentation. See Java Class Library Guide and JDBC Driver Guide.