PreviousInstall Toolkit Handbook (v10) Next

Simple Installation Customizations

Chapter contents

Simple customizations can be made to the installation using one of the following three methods:

Installing Using MSI Options

This section describes a customized installation using the options and parameters included with the Windows Installer.

Quiet (Silent) Install

The following steps outline how to install Pervasive PSQL v10 from a command line where the Quiet option has been included. The quiet option is used so that the installation runs with no user interaction required.

To install Pervasive PSQL v10 using the quiet (silent) option

  1. From a DOS command prompt, enter the following command:
MSIEXEC.EXE /i <PervasiveProductName>.msi /qn 
  1. Press Enter.
  2. The installation program runs silently in the background with no user interaction needed.


    Note
    Consult the Windows ® Installer SDK for additional documentation about the command line syntax.
Special Consideration for Silent Installs

The Java Runtime Environment (JRE) is required for certain optional features. Due to MSI limitations, the JRE installation cannot be performed during the silent installation of Pervasive PSQL v10. If you are installing any of the features listed in this section as part of a silent installation, you must also install the JRE separately in order for these features to function properly. The following features require the JRE installation:

The JRE installation can be launched manually from the Redist folder on the Pervasive PSQL v10 installation CD.


Note
For detailed information on installing and using the Java Runtime Environment, refer to the documentation included in the Redist folder on the Pervasive PSQL installation media and the Sun Microsystems web site.

Installing Using PTKSetup.ini Settings

This section provides a working example of a customized installation using the PTKSetup.ini settings from a command line. Another method for installing using the PTKSetup.ini settings is to specify the settings in the ini file and run the install from the command line with no options.

It is important to note that you may set values in the PTKSetup.ini file but you may not add keys or values to this file. Any keys and values added to this file that have not been defined by Pervasive Software are ignored by the installation process.

Optional Features Install

The following steps outline how to install Pervasive PSQL v10 from a command line where the Documentation optional feature has been excluded. This type of installation would be used in a situation where the online documentation was not needed.

To install Pervasive PSQL v10 with no documentation

  1. Open a DOS command prompt window.
  2. Enter the following command:
MSIEXEC.EXE /i "<PervasiveProductName>.msi" 
PVSW_PSQL_INSTALL_DOCUMENTATION=0 
  1. Press Enter.
  2. The installation program runs interactively with the documentation option removed from the list of optional features.

Installing Using MSI Options and PTKSetup.ini Settings

You may customize your Pervasive PSQL v10 installation by using both the MSI options and parameters, as well as the PTKSetup.ini file settings. Using this method, you would disable the property in the ini file and run the install from the command line using any additional options.

This section provides a working example of a customized installation that utilizes both of these options. The example provided here combines the methods used in the previous examples by setting values in the ini file and specifying options at the command line.

To install Pervasive PSQL v10 using the quiet option and with no documentation

  1. In the PTKSetup.ini file, find the following property:
PVSW_PSQL_INSTALL_DOCUMENTATION=1 
  1. Change the value for this property to 0, so that it reflects the following:
PVSW_PSQL_INSTALL_DOCUMENTATION=0 
  1. Open a DOS command prompt window.
  2. Enter the following command:
MSIEXEC.EXE /i <PervasiveProductName>.msi /qn 
  1. Press Enter.
  2. The installation program runs silently in the background with no user documentation installed.

Using a Different Configuration File Location With the Setup Executable

The MSI Public Property PVSW_CFG_FILE can be set to use an alternative configuration file by passing a fully qualified file path name. This property must be passed to the Windows process (msiexec) on the command line.

Before passing the property, determine if the property contains a spaces. If the property does not contain spaces, use the following example:

SetupName.exe /V"PVSW_CFG_FILE=c:\temp\ConfigFile.ini" 
 

Note
Do not add a space after the /V command line option.

If the property does contain spaces, you must enclose the property value in double quotation marks preceded by a backslash (\"), as shown in the following example:

SetupName.exe /V"PVSW_CFG_FILE=\"c:\Documents and 
Settings\UserName\temp\ConfigFile.ini\"" 

Combinations of the examples above can also be used to pass multiple MSI property settings:

SetupName.exe /V"PROPERTY1=0 PROPERTY2=\"c:\My 
Path\Some File.txt\"" 

Using a Different Configuration File Location With the MSI Executable

Only use the MSI executable if the intended target system contains the currently supported version of the Windows Installer. Follow the instructions for specifying MSI Public Properties as documented in the MSDN Knowledge Base topic "Windows Installer Command-Line Options".

msiexec.exe /i "{path}\MSIPackage.msi" PROPERTY1="property 
value" PROPERTY2=0 

Chapter contents
Book contents

Prev topic: Installation Toolkit Overview
Next topic: Advanced Installation Customizations