Installing PSQL Clients for Windows
Instructions for Installing Various PSQL Clients on Windows
The following topics cover PSQL Client installation:
Before You Install the Windows Client
Before you install any edition of PSQL, you should be familiar with the following information:
•
Preparing to Install PSQL - Important information, including system requirements and platform specific notes, relevant to your operation.
•Release Notes - The release notes are located in readme_psql.htm on the distribution media and contain late-breaking news that could not be included in the user documentation.
Installing PSQL Client for Windows
You must install PSQL Client for Windows at the client machine itself. You cannot install it remotely from a server machine.
PSQL Client is installed by default with PSQL Server, PSQL Vx Server, and PSQL Workgroup.
After you run the installer, you can find the installation log file in the Windows %Temp% directory. This log may be useful if the installation fails.
►To install PSQL Client for Windows
1 Launch the PSQL installer from your Windows machine in one of the following ways:
•Download and run the installer.
•Insert the PSQL CD into the CD-ROM drive. If the installer does not start automatically, then open the CD root directory and run autorun.exe.
2 In the installer selection list, click Client Only to install the components appropriate for your 32- or 64-bit Windows system.
3 If prompted, close or uninstall any running applications that may interfere with PSQL installation. If you wish to leave any of these programs running, you must click Ignore to continue. However, unpredictable behavior may occur during PSQL installation that cause it to fail.
4 In the Welcome screen, click Next.
5 Choose the type of installation:
•Select the default Run as a Service if either or both of the following is true:
•You want to run Client Cache Engine when the machine starts.
•You will run Client Cache Engine in a Terminal Services or multiuser environment with fast user switching.
•Select Run as an Application if:
You will run Client Cache Engine only as needed. After it starts, an icon in the notification area at the far right of the taskbar allows you to manage engine caching.
Note Running Client as a service requires the Log On as Service privilege. If you select to run Client as a service under a user account other than the default Local System account, ensure that you modify the Log On Properties for the Service using the Windows Control Panel. If installed as a service, the Client cache service is set by default to start automatically. However, even though the Client cache service is running, an application does not use Client cache unless the configuration setting for it is turned on.
The Client Cache Engine is a specialized version of the MicroKernel Engine that caches data for reading purposes and runs as a separate process. By default, whether installed as a service or as an application, use of the Client Cache Engine is turned off to disabled it. Disabling it means that nothing is cached on the Client side. Read requests from an application retrieve data from the remote database Engine. Enabling the Client Cache Engine means that it acts as an intermediary between the Client and the remote database Engine to cache data.
See the
Use Cache Engine property in
Advanced Operations Guide.
6 On the License Agreement page, read and accept the Software License Agreement, then click Next.
7 Select one of the following setups:
•Complete setup is recommended for most users. It installs all PSQL components using the default options and locations. If you choose this setup, click
Next and continue with step
12.
•Custom setup is for advanced users. It allows you to choose installation locations and control the number of PSQL components installed. If you choose Custom, continue with the next step.
8 To choose different installation locations, click Change for any of the directories listed. When you have made your choices, click OK.
9 Click Next to continue.
10 By default, all PSQL components and features are selected for installation. If needed, select from the following items to exclude them from installation and click Next.
•Data Access
•ActiveX Interface Controls
•ADO.NET Providers
•Btrieve DOS (32-bit only)
•DTO/DTI
•JCL
•JDBC Driver
•OLE DB
•PDAC
•Utilities
•Java Utilities
•PSQL Control Center (PCC)
•Documentation plug-in for PCC
•Data Dictionary File Builder
•Other Utilities
•Cobol Schema Executor
•PSQL System Analyzer
11 Click Next to continue.
12 Click Install to begin the installation.
13 Once the installation is complete, the wizard indicates that it was successful. Click Finish.
If you are prompted to restart your system, please do so to ensure proper operation of your PSQL product.
Note The installer modifies selected system environment variables.
Installing the BTRBOX Requester
PSQL v13 supports DOS Btrieve applications with the BTRBOX requester for Windows platforms. Use this Requester for legacy DOS applications.
A separate installation is no longer needed for the DOS Requester. The DOS Requester is automatically installed during a complete PSQL v13 engine installation. In the case of a Custom installation, you must select the Btrieve DOS optional feature in the PSQL Access Methods group to install the DOS Requester.
Note Clients using the DOS operating system will have only transactional access to the data files. No relational access is available for this platform.
Win32 DOS Box Support
BTRBOX allows a DOS application to run in a DOS box on a Windows workstation. This enables direct communication to the Windows 32-bit workstation components rather than to the database engine. This configuration can be used with either a local PSQL v13 Workgroup engine, or a remote PSQL v13 server engine. The TCP/IP or SPX protocol supported for client-server access depends on the configuration of the Windows 32-bit components.
DOS applications are not supported on 64-bit Windows platforms. Therefore, BTRBOX is not supported on 64-bit Windows platforms.
Understanding Client Requesters
A workstation that needs to access database files is considered a client to the machine running the PSQL Server. A piece of software called a client requester, or requester for short, is required to access database files from a PSQL database server. Your application’s PSQL calls go through the requester, which sends them to the PSQL Server for processing and then returns the reply to your application.
Refer to the release notes provided with the product for a list of the platforms on which PSQL requesters are supported. The requesters use the TCP, SPX or NetBIOS protocols to communicate with the server MicroKernel, depending on the type of server you have. Ensure that your workstation has the appropriate network protocol software installed.
Note Clients using DOS operating systems will have only transactional access to the data files. No relational access is available for this platform.
Types of Windows Requesters
PSQL includes the following types of requesters for Windows:
•DOS
•Trace
You do not load or unload the Requester explicitly; the system loads the Requester with the first application call to PSQL and unloads the Requester when you exit your application.
DOS Requesters
This type of requester is used for applications that run under the DOS operating system.
Trace Requesters
Trace requesters are used for troubleshooting (tracing) client problems at a low level. Generally, you will never need to perform this type of tracing. The low-level tracing is intended for use by trained support staff. Your product vendor or PSQL Support will direct you on how to conduct low-level client tracing, which includes how to use the trace requesters.
Note that the tools provided with PSQL solve most troubleshooting issues. For example, you would run the network connectivity tests in PSQL System Analyzer to verify network connectivity. Also at your disposal is the knowledge base at the
Actian website, through which you may search for information about particular client issues.
Where to Go from Here
A proper configuration is essential to smooth operation of your PSQL Client. See
Setting Up Network Communications for Clients for detailed information on how to do this task.