Installation Toolkit Overview

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

Two types of executable files are available with Pervasive PSQL v10. Both files use the MSI technology. Their differences and a brief discussion on when to use each one is also included.

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 in order to customize your Pervasive PSQL v10 installation.

Note
When using the MSI technology to install on Windows 64-bit Vista 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 either the MSI or the Setup executable file to run the installation process.

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

Table 1-1 Pervasive PSQL v10 MSI and Setup Executable File Names
Product Name	Setup Executable Files	MSI Executable File
Server Engine (64-bit)	SetupServer_x64.exe	PervasivePSQLv10Server_x64.msi
Server Engine (32-bit)	SetupServer_x86.exe	PervasivePSQLv10Server_x86.msi
Client Engine (64-bit)	SetupClient_x64.exe	PervasivePSQLv10Client_x64.msi
Client Engine (32-bit)	SetupClient_x86.exe	PervasivePSQLv10Client_x86.msi
Workgroup Engine (32-bit)	SetupWorkgroup_x86.exe	PervasivePSQLv10WGE_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 v10 product installation.

When to Use the MSI Executable

Use the MSI executable when you are certain that the system environment on which you are installing contains the version of Windows Installer supported by your Pervasive PSQL v10 installation.

Tip
Pervasive PSQL v10 utilizes 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.

When to Use the Setup Executable

The Setup executable file is an InstallShield bootstrapped package that includes the same MSI technology supported in the Pervasive PSQL v10 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 v10 installation, you should use the Setup executable for your installation.

Both the MSI and Setup executables use the PTKSetup.ini file for migrating configuration settings and configuring customizable settings, as described in the following sections.

PTKSetup.ini

The PTKSetup.ini file is included with every Pervasive PSQL v10 product installation. The file is located on the root directory of the installation media. Each section in the PTKSetup.ini file includes a description of the supported keys and acceptable values.

The PTKSetup.ini file has been revised for Pervasive PSQL v10. The file contains two primary sections. The Properties section provides the options available during either a silent or an attended installation. The Registry Migration section includes the configurations settings that are migrated during an upgrade installation to Pervasive PSQL v10.

Caution
The PTKSetup.ini file should only be used with Pervasive PSQL v10 and higher. Because of changes in technology and the installation, previous versions of Pervasive PSQL are not supported with this initialization file.

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 1-2 PTKSetup.ini Properties Categories and Keys
Category	Keys
Directory Locations (Custom Setup Only)	PVSW_PSQL_DATADIR PVSW_PSQL_INSTDIR32 PVSW_PSQL_INSTDIR64 PVSW_PSQL_ARCHIVE_DIR
License (Workgroup or Cache Engines Only)	PVSW_PSQL_LICENSE_KEY PVSW_PSQL_INSTALL_TYPE PVSW_PSQL_SKIP_LICENSE PVSW_PSQL_SKIP_INSTALLDIR
Registration Page	PVSW_PSQL_UI_NO_REGISTER
Engine as Service or Application	PVSW_RUN_CCE_AS_SVC PVSW_RUN_WGE_AS_SVC
Running Engine as Service Options	PVSW_PSQL_SVC_TYPE PVSW_PSQL_SVC_USERNAME PVSW_PSQL_SVC_USERPASSWD
Xtreme I/O (XIO)	PVSW_PSQL_INSTALL_XIO
Optional Features - Custom Setup Only
Documentation	PVSW_PSQL_INSTALL_DOCUMENTATION
Data Access Features	PVSW_PSQL_INSTALL_ACTIVEX PVSW_PSQL_INSTALL_BTRBOX PVSW_PSQL_INSTALL_ADONET21 PVSW_PSQL_INSTALL_ADONET30 PVSW_PSQL_INSTALL_DTO PVSW_PSQL_INSTALL_JCL PVSW_PSQL_INSTALL_JDBC PVSW_PSQL_INSTALL_OLEDB PVSW_PSQL_INSTALL_PDAC
Utility Features	PVSW_PSQL_INSTALL_CBOL PVSW_PSQL_INSTALL_DDFB PVSW_PSQL_INSTALL_PCC PVSW_PSQL_INSTALL_PSA PVSW_PSQL_INSTALL_COREUTILS
Java Runtime Environment	PVSW_INSTALL_JRE PVSW_JRE_INSTALLDIR PVSW_JRE_SETUP_PATH PVSW_JRE_SETUP_CMDLINE

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 contains the configuration settings that are migrated during an upgrade to Pervasive PSQL v10. The Pervasive PSQL v10 installation copies existing configuration settings and values and retains the values specified for a particular environment.

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 v10 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 during installation. The Pervasive PSQL v10 default settings are applied to any settings that are not commented out. If the key being migrated already exists, the previous registry settings are replaced with the migrated settings.

To locate the settings in the registry, see the entries from the Root that contain SOFTWARE\Pervasive Software\.

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 snapshots during installation use the following per-machine policy setting:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

LimitSystemRestoreCheckpointing = 1

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. This rule is only applicable for corporate scenarios where this feature is not used.