 | What's New in Pervasive PSQL v10 (v10) |  |
|
This section discusses the enhancements to the Pervasive PSQL installation:
See also the Readme file provided with the product release for information that may not be included in this book.
The Pervasive PSQL installation on all Windows operating systems now uses Microsoft Windows Installer technology (MSI) for product installations, updates, and uninstalls. The MSI installer (msiexec.exe) uses the configuration settings specified in the ptksetup.ini file for customized installations.
The MSI technology provides better deployment and a standard format for component management. The overall flow and look-and-feel of the installation is similar to previous releases. The underlying technology, however, is new and improved.
See MSI Technology in Installation Toolkit Handbook.
A separate installation exists for each of the following:
For each component, the installation program is uniquely named in the format setupproduct-type.exe, where product-type indicates the type of product. For example, the program for the 32-bit Server product is SetupServer_x86.exe.
As with previous version of Pervasive PSQL, only a single database engine may be installed on the same machine at a time. Note, however, that both the 32-bit and the 64-bit Client can be concurrently installed on the same machine provided the machine is running a 64-bit operating system.
All Pervasive PSQL executable files, including the installation program, are now digitally signed. Some Windows operating systems check executable files to verify the authenticity of the executable. On such platforms, the authentication shows that the executable is from Pervasive Software Inc.
A client installation image is not included as a component of the Pervasive PSQL Server product. You must run the separate Client setup program to install a Pervasive PSQL Client on a machine that does not include the Pervasive PSQL Server or Workgroup product. The Pervasive PSQL Server and Workgroup products include the client components so a separate client installation is not necessary.
The data access methods are part of the Pervasive PSQL software development kit (SDK). A complete installation for any of the products also installs the runtime components for all of the data access methods:
A custom installation allows you to include or exclude specific access methods.
The headers, libraries, samples and so forth for each access method remain separate downloads from the Pervasive PSQL Web site.
For a complete installation, the Pervasive PSQL installation installs Java Runtime Environment version 6 (JRE 6). Previous versions installed JRE 5. The JRE is an optional component for a custom installation depending on which Pervasive PSQL components you select. Some components, such as Pervasive PSQL Control Center and DDF Builder, require the JRE.
Because of limitations with Microsoft Windows Installer technology, the JRE installation cannot be performed during a silent installation of Pervasive PSQL v10. You must install the JRE separately for a silent installation.
Certain Windows operating systems enable the firewall by default. On such platforms, the Pervasive PSQL installation adds executable files to the firewall access list. With the firewall enabled, users cannot access the database engine unless certain engine files are added to the firewall access list.
Refer to the operating system documentation about firewalls and access lists.
The installation for Workgroup Engine and for Client Cache Engine now offers a choice to install the engine as an application or as a service. Previous versions of Pervasive PSQL installed the engine as an application.
The default is to install the engine as an application unless Terminal Services is detected on the machine. If you install either engine on a Terminal Services machine, the default is to install the engine as a service using the "Local System" account.
If you install the product as a service, you must provide the installation program with an account under which the service runs. This can be the "Local System" account or a specific user account.
The default location of installed components differs in Pervasive PSQL v10 from previous releases. This change allows the Pervasive PSQL products to adhere to installation guidelines provided by the operating system vendor.
Installation now places files into different root locations depending on the product and platform. (See Where are the Pervasive PSQL v10 files installed? in Getting Started With Pervasive PSQL.)
The Pervasive System Analyzer (PSA) is now installed as part of the other Pervasive PSQL utilities and resides in the same location as the other utilities. Also, during installation, PSA no longer runs its tests of the network and database engines. (Many of the features formerly provided by PSA are now available through the Microsoft Windows Installer technology.) You may run those tests after installing the product if you choose.
Note that PSA no longer provides the following functionality:
See Pervasive System Analyzer (PSA) in Pervasive PSQL User's Guide.
The display names of the Pervasive PSQL transactional and relational services have changed. The display name is what you see in Pervasive PSQL Control Center and in Windows Services, for example. The service names-the name that identifies the service to the operating system-remain the same.
In addition, Pervasive PSQL v10 allows you to install the Workgroup Engine or the Cache Engine as a service. The service name and the display name for both products are new.
The following table summarizes this information.
Because the service names remain the same, any scripts or applications you coded that start or stop the Pervasive PSQL services should work as before provided the code refers to the services as Pervasive.SQL (transactional) and Pervasive.SQL (relational).
Pervasive PSQL v10 installs to its default locations, not to the location where the previous PSQL version was installed. See Default Location of Installed Components .
Versions prior to Pervasive PSQL v10 installed to a default location of C:\PVSW. Pervasive PSQL v10 no longer uses that default location.
The Pervasive PSQL installation archives the previous version of the product and places the archive in a folder under the application data location. See Table 1-2 in this book, and Where are the Pervasive PSQL v10 files installed? in Getting Started With Pervasive PSQL.
The uninstall program removes all of the Pervasive PSQL components except for the following:
User-created databases and data files are not removed.
An uninstall removes all Pervasive PSQL settings, including user-modified ones. If you reinstall the product, the default settings are applied.
If you set up the Workgroup Engine or Cache Engine as a service through the Pervasive PSQL installation, the Pervasive PSQL uninstall removes the service as well as the product.
However, it is possible to set up a service by other means, such as third-party utilities or Pervasive PSQL utilities. For those situations, the Pervasive PSQL uninstall may not detect the service. After uninstalling Pervasive PSQL, check if the Workgroup Engine or Cache Engine service still exists. If it does, delete the service through the operating system Service Manager or by some other means.
See Installing Using PTKSetup.ini Settings in Installation Toolkit Handbook.
|
Chapter contents
Prev topic: Performance
|