Customized Installation Overview
This section covers the technology and customization settings used for PSQL product installations. On Windows systems, PSQL installation uses Microsoft Windows Installer (MSI). The PTKSetup.ini file contains default settings that you can change for custom installations.
Installer Executable
For most installation scenarios, the installer executable file should be used for installations. The installer is an InstallShield package that performs a variety of checks before installation. It also detects whether you have 32- or 64-bit Windows, launches the appropriate installation, and automatically provides all 32- and 64-bit client components appropriate to your system.
The following table describes PSQL installers on Windows operating systems.
Product
Installation Package
Description
Server Engine
Install_PSQL_Server_Engine.exe
•
Installs 32-bit engine on 32-bit operating system.
•
Installs 64-bit engine on 64-bit operating system.
•
Installs all client components.
Vx Engine
Install_PSQL_Vx_Server.exe
•
Installs 32-bit engine on 32-bit operating system.
•
Installs 64-bit engine on 64-bit operating system.
•
Installs all client components.
Workgroup Engine
Install_PSQL_Workgroup_Engine.exe
•
Installs 32-bit engine on both 32- and 64-bit operating systems.
•
Installs all client components.
Client
Install_PSQL_Client.exe
•
Installs 32-bit components on 32-bit operating system.
•
Installs both 32- and 64-bit components on 64-bit system.
PTKSetup.ini Settings
PTKSetup.ini contains all settings needed for a typical installation. This file is used by every PSQL product. On the installation media, it is located in the same folder as the .msi file that uses it.
PTKSetup.ini is divided into two parts:
•
Properties Section - Contains settings used during every installation.
•
Registry Migration Section - Contains settings used with versions of PSQL before PSQL v10
Each setting has a current value that is the default for a typical installation. Comments in the file explain the settings and give all accepted values.
*Caution: You must use the specific PTKSetup.ini file included with the version of the product that you are embedding. Because installer technology and installation settings can change from version to version, the file must match the product that it accompanies.
Properties Section
The following table lists settings in the PTKSetup.ini Properties section. The settings are grouped into categories. The value for each setting is contained in a key.
 
Table 1
PTKSetup.ini Property Categories and Keys 
Categories
Keys
Setup Type
PVSW_PSQL_INSTALL_TYPE
Destination Folder
(Custom Setup Only)
PVSW_PSQL_SKIP_INSTALLDIR
Directory Locations
(Custom setup only)
PVSW_PSQL_DATADIR
PVSW_PSQL_INSTDIR32
PVSW_PSQL_INSTDIR64
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)
PVSW_RUN_CCE_AS_SVC
PVSW_RUN_WGE_AS_SVC
PVSW_APP_WAIT_TIME
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
Registry Migration Section
The Registry Migration section of the PTKSetup.ini file can be used when upgrading from PSQL v9 or earlier. The settings in this section enable migration of selected registry values from the earlier to the later version.
All of the configuration settings are explained in detail in Advanced Operations Guide.
Registry Migration Settings Format
The Registry Migration section lists each setting for the previous PSQL version first, followed by an equal (=) sign. The setting for PSQL is listed to the right of the equal sign.
The format used for registry migration settings is <Setting for Prior Version>=<Setting for New Version>.
Using Registry Migration Settings
Comment out any settings that should not be migrated during installation from any version of PSQL before v10. If the key to be migrated already exists, the earlier registry setting replaces it.
*Note: When upgrading versions of PSQL v10 and later, the PSQL installations ignore this section and migrate all registry settings automatically.
To view your current settings, use the bcfg utility described in Advanced Operations Guide. This utility allows you to capture your current configuration settings in a report that may be useful for considering needed changes.
Configuring PSQL After Installation
After installing PSQL, you can use the configuration functions available in the Distributed Tuning Interface (DTI) to configure and tune your PSQL engines. The functions available in DTI allow you to perform a variety of tasks to check current settings and make changes to them programmatically.
For information on using the DTI functions to configure the PSQL engine after installation, refer to the list of Configuration Function Groups described in Distributed Tuning Interface Guide.
The PSQL DTO object is a COM Interface to perform PSQL configuration functions similar to the DTI interface.
Improving System Performance
In an enterprise environment where reimaging 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 restore points may be recovered and performance improved by disabling System Restore for installer activity. To disable System Restore, see the Microsoft help system for detailed information.
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 applicable only for corporate scenarios where the feature is not used.