Customized Installation Overview

This section is an overview to the technology and customization settings used by Pervasive Software for Pervasive PSQL product installations. The technology used in the Pervasive PSQL installation is the Microsoft Windows Installer (MSI). The customization settings are located in the PTKSetup.ini file.

When to Use the Setup Executable

For most installation scenarios, the Setup executable file should be used for installations. The Setup executable file is an InstallShield bootstrapper package that performs a variety of checks prior to installation. The Setup executable also detects and installs the version of the Windows Installer Service required on the target system prior to launching the MSI installation. After determining whether the target system contains the prerequisite version of MSI, the Setup executable automatically launches the MSI installation. If you are uncertain as to if the system to which you are installing contains the version of MSI technology supported by the Pervasive PSQL installation, you should use the Setup executable for your installation.

When to Use the MSI

Pervasive Software recommends using only the Pervasive PSQL MSI file installation process when bundling Pervasive PSQL with your software applications. In this situation, the Pervasive PSQL installation can be invoked during the installation of your software when you are certain the target system already contains the version of Windows Installer supported by Pervasive PSQL. On Microsoft Vista or later, the process that calls the Pervasive PSQL installation must already be running with elevated user credentials before starting the Pervasive PSQL installation using the MSI file.

Tip: Pervasive PSQL uses Windows Installer v3.1. To see what version, if any, of the Windows Installer is present on your system, type MSIExec /? at a command prompt.

MSI Technology

The MSI technology is fully documented by Microsoft and is available from their Web site. The options and parameters available to use with the Windows Installer are available by entering the following command at a DOS prompt:

MSIEXEC.EXE /?

This guide does not replicate this information. Instead, this document provides real-world examples for using the technology to customize your Pervasive PSQL installation.

Note: When using the MSI technology to install on Windows Vista or later operating systems, you must run the install as an elevated administrator user account.

Using the MSI Technology

When performing command line installations using the MSI technology, use the MSI file to run the installation process.

The following table lists the Pervasive PSQL products, associated Setup executable and MSI file names available with the Pervasive PSQL product line.

Table 1

Pervasive PSQL MSI and Setup Executable File Names

Product Name

Setup Executable Files

MSI Executable File

Server Engine (64-bit)

SetupServer_x64.exe

PervasivePSQLv11Server_x64.msi

Server Engine (32-bit)

SetupServer_x86.exe

PervasivePSQLv11Server_x86.msi

Vx Engine (64-bit)

SetupServerVx_x64.exe

PervasivePSQLv11ServerVx_x64.msi

Vx Engine (32-bit)

SetupServerVx_x86.exe

PervasivePSQLv11ServerVx_x86.msi

Workgroup Engine (32-bit)

SetupWorkgroup_x86.exe

PervasivePSQLv11WGE_x86.msi

Client Engine (64-bit)

SetupClient_x64.exe

PervasivePSQLv11Client_x64.msi

Client Engine (32-bit)

SetupClient_x86.exe

PervasivePSQLv11Client_x86.msi

Tip: See Installing Using MSI Options and Installing Using MSI Options and PTKSetup.ini Settings for examples of how MSI options are used during a Pervasive PSQL product installation.

PTKSetup.ini

The PTKSetup.ini file is included with every Pervasive PSQL product installation. The file is located in the same folder as the MSI executable on the installation media. Each section in the PTKSetup.ini file includes a description of the supported keys and acceptable values.

The PTKSetup.ini file contains two primary sections. The Properties section provides the options available during either a silent or an attended installation. The Registry Migration section only applies to versions of Pervasive PSQL prior to Pervasive PSQL v10 and is described in detail later in this chapter.

Caution: Always use the version of the PTKSetup.ini file included with the version of the product you are embedding. Because of changes in technology and the installation, each version of the initialization file is specific to the product that it accompanies.

Properties Section

The following table provides an overview of the categories of customization available in the PTKSetup.ini Properties section and lists the keys for each category.

Table 2

PTKSetup.ini Properties Categories and Keys

Category

Keys

Setup Type

PVSW_PSQL_INSTALL_TYPE

Destination Folder

(Custom Setup Only)

PVSW_PSQL_SKIP_INSTALLDIR

PVSW_PSQL_ARCHIVE_DIR

Registration Page

PVSW_PSQL_UI_NO_REGISTER

PVSW_OEM_REGISTER_HTML

License

(Workgroup or Server Engines Only)

PVSW_PSQL_LICENSE_KEY

PVSW_PSQL_SKIP_LICENSE

Engine as Service or Application

(Workgroup or Cache Engines Only)

(32-bit Server Engines Only)

PVSW_PSQL_INSTALL_XIO

Optional Features - Custom Setup Only

Data Access Features

PVSW_PSQL_INSTALL_ACTIVEX

PVSW_PSQL_INSTALL_ADONET

PVSW_PSQL_INSTALL_BTRBOX

PVSW_PSQL_INSTALL_DTO

PVSW_PSQL_INSTALL_JCL

PVSW_PSQL_INSTALL_JDBC

PVSW_PSQL_INSTALL_OLEDB

PVSW_PSQL_INSTALL_PDAC

Java Utilities Feature

PVSW_PSQL_INSTALL_DDFB

PVSW_PSQL_INSTALL_PCC

PVSW_PSQL_INSTALL_DOCUMENTATION

PVSW_PSQL_INSTALL_NOTIFYVIEWER

PVSW_PSQL_INSTALL_JAVAUTILS

Other Utility Features

PVSW_PSQL_INSTALL_CBOL

PVSW_PSQL_INSTALL_COREUTILS

PVSW_PSQL_INSTALL_PSA

Tip: For detailed information on the Properties Keys, refer to the information in the PTKSetup.ini file included with your installation package.

Registry Migration Section

The second section of the PTKSetup.ini file can be used when upgrading from a version prior to Pervasive PSQL v10. The section is used to preserve configuration settings from Pervasive PSQL v9 or earlier by migrating the registry settings specified in the section during an upgrade to a later version of Pervasive PSQL.

Tip: All of the configuration settings are explained in detail in the Advanced Operations Guide.

Registry Migration Settings Format

The Registry Migration section lists the setting for the previous version first, followed by an equal (=) sign. The setting for Pervasive PSQL is listed to the right of the equal sign.

The format used for registry migration settings is
<Prior Version>=<New Version>

Using Registry Migration Settings

Comment out any settings that should not be migrated from any version of Pervasive PSQL prior to v10.0. during installation. If the key being migrated already exists, the previous registry settings are replaced with the migrated settings.

Note: When upgrading versions of Pervasive PSQL v10 and later, the Pervasive PSQL installs do not reference this section and will migrate all settings automatically.

To view your current settings, use the bcfg utility, as described in the Advanced Operations Guide. This utility allows you to capture your current configuration settings into a report that may be useful in determining needed changes.

Configuring Pervasive PSQL After Installation

After installing Pervasive PSQL, you can use the configuration functions available in the Distributed Tuning Interface (DTI) to configure and tune your Pervasive PSQL engines. The functions available in DTI allow you to perform a variety of tasks that allow you to determine your current settings and make changes to configuration settings programmatically.

For information on using the DTI functions to configure the Pervasive PSQL engine after installation, refer to the list of Configuration Function Groups, as described in the Distributed Tuning Interface Guide.

The Pervasive DTO object is a COM Interface to perform Pervasive configuration functions similar to the DTI interface.

Improving System Performance

In a corporate environment where re-imaging or some other technique may be the preferred method for workstation recovery, and System Restore is never used, the additional time and disk space required to create the System Restore Points may be recovered and performance improved by disabling System Restore for installer activity.

To disable System Restore refer to the Microsoft help system for detailed information specific to your operating system.

This setting affects only Installer-initiated restore activity and is available in Group Policy to aid its deployment to workstations.

Note: System Restore is a very important feature of Windows and in most circumstances it is recommended that you do not disable it. Disabling System Restore is only applicable for corporate scenarios where this feature is not used.