Easy Updates

The Pervasive PSQL installer allows the end-user customer to install the main product as well as updates during a single installation procedure. There is no need for the customer to install updates separately. This feature is called "Easy Updates."

"Easy Updates" is convenient because you can add files to be installed by the Pervasive PSQL installation program simply by dropping the files into a specific directory location in the installation image. You do not need to change a single line of code in your installation program.

How Easy Updates Works

After the Pervasive PSQL installation program copies the main installation files to the installation target folders, it checks the installation media for a subfolder called UPD. This subfolder must reside in the same folder as the Pervasive PSQL installation program, SETUP.EXE. The UPD folder must be at the same level of the installation image as the folders named BOOKS and CLIENTS.

If the UPD folder exists at the specified location, then the installation program copies the contents of the folder to corresponding locations in the installation target folder. For example, if the engine installation program has been instructed to install Pervasive PSQL to target location D:\db_products\psql, then the contents of UPD\pvsw\bin are copied to d:\db_products\psql\bin.

This feature is also available for the client installation program. In this case, the UPD folder must be in the same folder as the client SETUP.EXE program. In other words, the client UPD folder must be created in the folder CLIENTS\WIN on the server installation image.

If the target folder already contains a file with the same name as a given "update" file, the installation program checks to see which file has a higher version number. If the existing file has a higher version, the installation program does not install the "update" file. This behavior prevents errors that can occur when a newer component is accidentally overwritten by an older one.

To maintain consistency of installed files, only the following subfolders of the UPD folder are recognized by the installation program:

Table 1-3 UPD Subfolders Recognized by the Installation Program
Subfolder	Description and Location Where Files Are Copied
ODBC	For NetWare only: The ODBC folder, usually F:\ODBC, if drive F: is mapped to the NetWare SYS folder.
PVSW	Main Pervasive PSQL target installation folder. The valid subfolders under PVSW are as follows (see also Figure 1-1): Bin Locales Locales\1033 For example, if the user specified C:\db\psql as the installation target, then the contents of UPD\PVSW\BIN are copied to C:\db\psql\BIN.
PVSWCMN	Auxiliary target installation folder. The auxiliary installation folder is located at Program Files\Common Files\Pervasive Software Shared. The valid subfolders for PVSWCMN are as follows (See also Figure 1-1): DOC PSA PSA\psa_msgs pvswcore For example, if the user specified C:\db\psql as the installation target, then the contents of UPD\PVSWCMN\pvswcore are copied to C:\Program Files\Common Files\Pervasive software SHARED\PVSWCORE.
SYSTEM	For NetWare only: The NetWare system folder, usually F:\SYSTEM, if drive F: is mapped to the NetWare SYS folder.

Note
Any other subfolders in the UPD folder are ignored.

The following figure shows the valid subfolders for the Windows platform.

Figure 1-1 Valid Easy Updates Subfolders for Windows Platform

How to Use Easy Updates

This section describes how to add Pervasive PSQL file updates to your installation program.

On your installation media image, create the folder UPD in the same folder as the Pervasive PSQL client and/or engine SETUP.EXE program(s).

Populate the UPD folder(s) you just created with the Pervasive PSQL folders and files that you want updated in the installation.

Within the UPD folder, each file and subfolder must correspond to the same location and file of the installation target. For example, if you want to install an update for a file that normally resides in the BIN directory of the installation location for Pervasive PSQL, then you must put this file in UPD\PVSW\BIN.

Within the UPD folder, you should always use "PVSW" to represent the main installation target folder, even if you are installing to a custom location, such as D:\mydb\dbfiles, rather than the default location C:\PVSW. The installation program automatically determines the folder to which you are installing. See Table 1-3, UPD Subfolders Recognized by the Installation Program .

Caution
Do not mix files for different products in the same directory. For example, do not put Workgroup Engine and Server Engine DLLs in the same UPD\PVSW\BIN directory. As well, do not mix files for different platforms in the same directory. For example, do not put NetWare Server Engine files and Windows Server Engine files in the same UPD\PVSW\BIN directory. You must store all files for each type of installation separately.

Pervasive Field Test Files (FTFs) are shipped with all platforms/components in the same directory. If you are using files from an FTF, you must separate the files appropriately.

Example of Using Easy Updates for an Engine DLL

You want to install engine DLL W3MIF150.DLL, because it contains a fix for a defect in W3MIF145.DLL, which is installed by the main installation program.

In your installation media image, create the folder UPD in the same folder as the Pervasive PSQL SETUP.EXE program.

Within the UPD folder you have created, create the subfolder PVSW. Within the PVSW subfolder, create another subfolder named BIN.

Copy your desired file update, in this case W3MIF150.DLL, to UPD\PVSW\BIN.

Re-master your installation media with the updated image.

Example of Using Easy Updates for a Client DLL

Since the same component, W3MIF145.DLL, also installs on the client, you want to add the W3MIF150.DLL to the clients folder as well.

In your installation media image, create the folder UPD in the same folder as the Pervasive PSQL client SETUP.EXE program. In other words, create a folder UPD in the folder CLIENTS\WIN32.

Note that you could also create the UPD folder in the CLIENTS\WIN32 folder of a Server engine installation. That way, any clients installed from the Server would automatically get the updated files.

Within the UPD folder you have created, create the subfolder PVSW. Within the PVSW subfolder, create another subfolder named BIN.

Copy your desired file update, in this case W3MIF150.DLL, to the folder CLIENTS\WIN32\UPD\PVSW\BIN that you have created.

Re-master your installation media with the updated image.

For both examples, when the installation program runs, W3MIF145.DLL is installed from the main component archive, then W3MIF150.DLL is installed from the UPD folder. W3MIF145.DLL is not deleted, but the Pervasive PSQL Smart Components architecture ensures that only the higher-numbered MIF component is ever used.

If the update file is not a Smart Component (that is, it does not use an incremental numbering scheme in the file name), the existing file is overwritten by the update file.

Note
Easy Updates does not modify the manifest.csv file. However, the manifest.csv file will automatically include any files that are present in the target install directories. The new files you include will appear in the generated manifest along with the files they replaced.