Advanced Installation Customizations
This section details using advanced customization for your embedded installations of Pervasive PSQL. Pervasive PSQL supports the following methods for advanced installation customizations:
•
Changing Installation Package Size and Features Using CAB Files
•
Developing an Embedded Installation with Custom File Picking
•
Creating Transforms to Customize your Installation
Changing Installation Package Size and Features Using CAB Files
The Pervasive PSQL installation includes cabinet (CAB) files that can be removed from your installation package to decrease the overall size of the installation package and avoid using unnecessary files. Removing these files automatically removes the corresponding feature from the list of available features in the graphical user interface during a custom setup.
Working with CAB Files and Future Updates
CAB files are located in the same directory as the MSI and Setup executables. CAB files beginning with an underscore (_) are required for that install type. For a complete list of required files by installation type, see Required Files.
The core set of CAB files does not change. However, updates to Pervasive PSQL will contain additional CAB files from the original set released in Pervasive PSQL v11 to account for any newly added components or features. Updates to Pervasive PSQL may require generation of additional CAB files, if there are new CAB files present. Be sure and obtain the latest set of files for the installation type and optional features you are installing.
Required Files
CAB files that are required are designated by an underscore. The following table lists the cabinet files required for each installation type.
Table 3
Cabinet Files Required by Engine Installation Type
Cabinet File
Server VX 64
Server VX 32
Server 64
Server 32
Client 64
Client 32
Workgroup
_CE32.cab
 
 
 
 
 
* 
 
_CE32_64.cab
 
 
 
 
* 
* 
 
_Core.cab
* 
* 
* 
* 
 
* 
* 
_DbEng32.cab
 
* 
 
* 
 
 
* 
_DbEng.cab
* 
* 
* 
* 
 
 
* 
_PSQL32.cab
 
* 
 
* 
 
* 
* 
_PSQL64.cab
* 
 
* 
 
* 
 
 
_PSQL.cab
* 
* 
* 
* 
* 
* 
* 
_Srvr32.cab
 
* 
 
* 
 
 
 
_Srvr64.cab
* 
 
* 
 
 
 
 
_SrvrEng.cab
* 
* 
* 
* 
 
 
 
_WGC.cab
 
 
 
 
 
* 
* 
_WGE.cab
 
 
 
 
 
 
* 
Optional Features
The following table lists the optional features by installation type with which they can be applied.
Table 4
Optional Features Cabinet Files by Engine Installation Type
Cabinet File
Server VX 64
Server VX 32
Server 64
Server 32
Client 64
Client 32
Workgroup
ActiveX.cab
* 
* 
* 
* 
 
* 
* 
ADONET.cab
* 
* 
* 
* 
* 
* 
* 
BtreveDos.cab
* 
* 
* 
* 
 
* 
* 
CSE32Cmn.cab
* 
* 
* 
* 
 
* 
* 
CSE32Eng.cab
 
* 
 
* 
 
 
* 
CSE64Eng.cab
* 
 
* 
 
 
 
 
CSECmEng.cab
* 
* 
* 
* 
 
 
* 
DDFB.cab
* 
* 
* 
* 
 
* 
* 
Docs.cab
* 
* 
* 
* 
 
* 
* 
DocsVx.cab
* 
* 
 
 
 
 
 
DTO64.cab
* 
 
* 
 
* 
 
 
DTO.cab
* 
* 
* 
* 
* 
* 
* 
EclipRCP.cab
* 
* 
* 
* 
 
* 
* 
JCL.cab
* 
* 
* 
* 
 
* 
* 
JDBC.cab
* 
* 
* 
* 
 
* 
* 
JRE6.cab
* 
* 
* 
* 
 
* 
* 
JreUtils.cab
* 
* 
* 
* 
 
* 
* 
NVUtil.cab
* 
* 
* 
* 
 
 
* 
OLEDb.cab
* 
* 
* 
* 
 
* 
* 
PCC.cab
* 
* 
* 
* 
 
* 
* 
PDAC.cab
* 
* 
* 
* 
 
* 
* 
PSA.cab
* 
* 
* 
* 
 
* 
* 
Utils2.cab
* 
* 
* 
* 
 
* 
* 
Utils.cab
* 
* 
* 
* 
 
* 
* 
WPMCS32.cab
 
* 
 
* 
 
 
 
WPMCS64.cab
* 
 
* 
 
 
 
 
XIO.cab
 
 
 
* 
 
 
 
Optional Feature Requirements
Certain optional features require that other components accompany them in order to function. The following table lists the optional features that require other components.
Table 5
Optional Features Cabinet File Requirements
 
Cobol Schema Executor
Data Dictionary File Builder
Pervasive PSQL Control Center
Pervasive System Analyzer
Pervasive User Docs
Notification Viewer
CSE32Cmn.cab
* 
 
 
 
 
 
CSE32Eng.cab
* 
 
 
 
 
 
CSE64Eng.cab
* 
 
 
 
 
 
CSECmEng.cab
* 
 
 
 
 
 
DDFB.cab
 
* 
 
 
 
 
Docs.cab
 
 
 
 
* 
 
EclipRCP.cab
 
* 
* 
 
* 
* 
JRE6.cab
 
* 
* 
 
* 
* 
JreUtils.cab
 
 
 
 
 
* 
NVUtil.cab
 
 
 
 
 
* 
PCC.cab
 
 
* 
 
* 
 
PSA.cab
 
 
 
* 
 
 
Utils2.cab
* 
* 
* 
* 
 
 
Utils.cab
* 
* 
* 
* 
 
 
CAB File Installation Example
The following provides an example of customizing your installation using CAB files. This example installs the Workgroup engine with documentation as the only optional feature.
*Note: Documentation requires that you install the Eclipse framework and the Pervasive PSQL Control Center.
►
To package a Workgroup Engine with Documentation
1
Select the required CAB files for the Workgroup Engine (see Cabinet Files Required by Engine Installation Type). These files include the following:
•
_Core.cab
•
_DbEng32.cab
•
_DbEng.cab
•
_PSQL32.cab
•
_WGC.cab
•
_WGE.cab
2
Select the optional feature CAB files for the documentation (see Optional Features Cabinet File Requirements). These files include the following:
•
Docs.cab
•
EclipRCP.cab
•
PCC.cab
•
JRE6.cab
The files listed in these two steps are the only CAB files that you need in order to install the Workgroup Engine and documentation. All other CAB files may be removed from the installation package.
Developing an Embedded Installation with Custom File Picking
Another method for embedding the Pervasive PSQL installation with your application is by using custom file picking, which is sometimes referred to as cherry picking. This method allows you to select Pervasive PSQL components at the individual file level.
Please contact Pervasive Support if you want to embed the Pervasive PSQL installation by using custom file picking.
Creating Transforms to Customize your Installation
Another advanced method for customizing your embedded installation is to create a Windows Installer transform file (MST). Creating a transform file to customize your installation allows for greater flexibility in the features you select during installation, maintains the features associated with MSI technology and provides for easily applying upgrades and patches, unlike the custom file picking method for customized installations.
To generate a MSI transform, the installation database must be manipulated. There are several tools that can be used to generate a transform file. These include InstallShield, Microsoft Orca, or the MSI utilities in the Windows Platform SDK.
Creating an Embedded Installation Without Shortcuts
An example for using a transform file in a customized installation would be installing Pervasive PSQL without installing any of the shortcuts. The following outlines the steps you would follow for this type of procedure.
1
Make a copy of the original Pervasive PSQL MSI package. For example, PervasivePSQLv11WGE_x86_copy.msi.
2
Open the database copy using a Windows Installer table editor such as InstallShield or Orca.
3
In the Shortcut table, modify the InstallExecuteSequence record to change the Action=CreateShortcuts to change the Condition value.
Current InstallExecuteSequence record
CreateShortcuts <null_value> 5500
Revised InstallExecuteSequence record
CreateShortcuts NOSHORTCUTS 5500
*Note: Adding an undefined property name such as 'NOSHORTCUTS' causes the action to be skipped so no shortcuts are created.
4
Generate a MSI Transform File (MST) by comparing the original MSI install file PervasivePSQLv11WGE_x86.msi to the modified copy PervasivePSQLv11WGE_x86_copy.msi using a tool capable of comparing the two packages and generating a transform file (InstallShield/Orca/MSI utilities).
5
Name the generated transform file with a unique name, such as MyTransform.MST.
6
Include the transform file along with the installation files and modify the command line to set the property TRANSFORMS= to the name of the transform (TRANSFORMS=MyTransform.MST).
See the following modified examples for using the generated transform file.
Silent Install Examples Using Setup Executable
The following example creates a log file in the user's temp folder:
SetupWorkgroup_x86.exe /s /v"/qn REBOOT=ReallySuppress /leom \"%TEMP%\PSQL_version_Install.log\" TRANSFORMS=MyTransform.MST"
This example creates a log file in the user’s temp folder and specifies the license key and service install options:
SetupWorkgroup_x86.exe /s /v"/qn REBOOT=ReallySuppress PVSW_PSQL_LICENSE_KEY={key_value} PVSW_RUN_WGE_AS_SVC=Y TRANSFORMS=MyTransform.MST /leom \"%TEMP%\PSQL_version_Install.log\""
Silent Install Examples Using MSI Executable
The following example creates a log file in the user’s temp folder and specifies the license key and service install options:
msiexec.exe /i {path}\ PervasivePSQLversionWGE_x86.msi /qn REBOOT=ReallySuppress PVSW_PSQL_LICENSE_KEY={key_value} PVSW_RUN_WGE_AS_SVC=Y TRANSFORMS=MyTransform.MST /leom "%TEMP%\PSQL_version_Install.log"