PreviousGetting Started with Pervasive PSQL v9 SP2 (9.5) (Server Edition) (v9 SP2 (9.5) revision 1) Next

Installing the Pervasive PSQL Client Components

Chapter contents

To install the Pervasive PSQL v9 Service Pack 2 client software:

  1. Launch the installation selection program from your Windows machine.
    1. Insert the Pervasive PSQL Server for Windows CD in the CD-ROM drive of your Windows server.
    2. If the installation does not start automatically, click Start then Run, and type drive:\autorun\autorun where drive is the drive letter of your CD-ROM device.
    3. The installation selection dialog displays.

  2. Click the button for the "Client" installation.
  3. The installation program begins its initial preparation. After the preparation completes, the Welcome screen appears.

  4. Click Next to proceed with the installation.
  5. Click the setup type desired: Complete or Custom (the default is Complete).
  6. Figure 5-1 Setup Type Dialog Box

    The Complete installation, which is recommended for most users, takes default actions for operations performed during the installation. The Complete server installation installs the following components to the local machine:

    • Transactional and relational interfaces
    • Client requesters (DOS, Trace, and Win32 requesters)
    • Utilities
    • Online documentation in JavaHelp format
    • The Custom installation is typically for advanced users. It allows you to specify the installation location, select the components to install, and determine the space requirements for the components.

  7. Click Next, then continue based on your choice of Complete or Custom:
    • If you choose a Complete install, continue with the next step.
    • If you choose a Custom install, skip now to Custom Installation Path . At the end of that section you will return to this set of steps to continue the installation.
    • At this point, if you want, you may click Back to change or review any of the installation settings, or click Cancel to exit the installation program. After you click Install, you may still exit the installation, but you will be unable to change or review settings.

  8. Click Install.
  9. If required, close any running applications that may interfere with the Pervasive PSQL installation.
  10. A dialog box appears if applications are running that can interfere with the installation of Pervasive PSQL.

    Figure 5-2 Example Dialog Box for Programs that May Interfere

    Decide how to continue with the installation. Your choices are:

    1. To exit all of the programs that may interfere, then click Next.
    2. Not to exit all of the programs that may interfere, then click Ignore.

    3. Note
      Next does not proceed with the installation unless you exit all programs that will interfere.

      If you wish to leave one or more programs running that may interfere, you must click Ignore to continue. Unpredictable results may occur during the Pervasive PSQL installation if you ignore programs that may interfere.

      If installed files could not be copied because they were locked in memory, a reboot may be necessary at this point. Setup only prompts for a reboot if a locked file or some other event was detected that requires a reboot. Please reboot your system if prompted to do so in order to ensure proper operation of your Pervasive PSQL product.

      If no running applications interfere with the Pervasive PSQL installation, the installation process continues. A dialog box appears that gives you a status.

      Figure 5-3 Installation Status Dialog Box

      Installation actions include, but are not limited to, the following:

    4. Script operations
    5. Component registration
    6. File copying
    7. Shortcut creation
    8. System registry updates
    9. After the initial actions, the installation process launches the Pervasive System Analyzer (PSA) Wizard. The PSA Wizard can also test network communications from the client machine to the machine running Pervasive PSQL Server. The Wizard initiates this test automatically.

  11. Test the network communications from the client machine to the machine running Pervasive PSQL Server.
  12. For Target Machine, type the name or IP address of the machine running Pervasive PSQL Server. For example, the following example shows that the machine name is MachineA.

    Figure 5-4 Network Communication Test

    The communication test transmits a series of 75 test messages between the two machines. Click Advanced Settings if you want to change the number of messages transmitted or the type of protocol used for the communication test.

  13. Click Next.
  14. Figure 5-5 Network Transmission of Test Messages

    After all test messages are transmitted and received correctly, a dialog confirms that all messages were successfully transmitted.

    Figure 5-6 Successful Transmission of Test Messages

  15. Click Next.
  16. The PSA Wizard also allows you to test the transactional and relational interfaces. These tests ensure that the database engine on the machine running Pervasive PSQL Server is working as expected.

    Figure 5-7 Transactional Engine Test



    By default, the option for the transactional tests is selected.

  17. Type the location of the Pervasive PSQL samples directory on the machine running Pervasive PSQL Server.
  18. By default, the directory is located on the server at C:\PVSW\samples. Suppose, for example, that you have mapped drive "P" to the machine running Pervasive PSQL Server. You would specify the samples directory as shown in the figure above.

  19. Click Next to run the transactional tests and to see the results.
  20. PSA performs a series of tasks to ensure that the transactional engine is working properly.

    PSA displays a check mark for each test that passes and an X for each task that fails during the transaction engine test. A summary report is also provided in the information window, as shown in the following figure.

    Figure 5-8 Transactional Engine Test Results from PSA



  21. Once your transactional tests are successful, click Next to proceed with the PSA Wizard.
  22. PSA is now ready to ensure that the relational engine is working properly.

    Figure 5-9 Relational Engine Test



    If necessary for Machine Name, type the name of the machine running Pervasive PSQL Server. Note that the test uses the sample demodata database.

  23. Click Next to run the relational tests and to see the results.
  24. PSA displays a check mark for each test that passes and an X for each task that fails during the relational engine test. A summary report is also provided in the information window, as shown in the following figure.

    Figure 5-10 Relational Engine Test Results from PSA



  25. Once your relational engine tests are successful, click Next.
  26. The final dialog of the PSA Wizard displays and provides a summary of the tasks completed by the Wizard.

    If you want to view the PSA log file, it is named by default PSALog.txt and is located by default at <OSdrive>\Program Files\Common Files\Pervasive Software Shared\PSA, where <OSdrive> is the drive letter where your operating system is installed.

  27. Click Finish to complete the PSA Wizard.
  28. The final dialog of the Installation Wizard displays along with a registration page.

  29. Register your product.
  30. Pervasive Software recommends that you register your product to receive news about future updates, and other timely information. You can also register later using a web, e-mail, or print-based registration form.

    Figure 5-11 Product Registration Page

    If you did not read the README file prior to installation as described in Before You Begin , please do so now from the registration page.

  31. Click Readme on the registration page to read the README file.
  32. Figure 5-12 View Readme

  33. Close the Registration page (click the "X" in the upper right corner).
  34. Click Finish to complete the Installation Wizard.
  35. Thank you for choosing Pervasive PSQL.

Restarting Your Computer After Installation

You should restart your Windows machine at the end of the installation process if any of the following are true:


Chapter contents
Book contents

Prev topic: Understanding Client Requesters
Next topic: Custom Installation Path