Installation Review
This section provides you with a checklist to prepare you for installation and a set of commonly asked questions you should consider prior to installation. Please use this section as a review and a guide for a successful installation.
Quick Checklist
This checklist provides a review of the requirements needed in order to install PSQL. Each of these items should be met prior to beginning the install process.
*
Your system hardware meets the minimum requirements to install PSQL.
*
Your operating system and network environment is supported by PSQL.
*
You have full administrator-level rights on the system where you plan to install PSQL.
*
You understand the different options available in the Complete and Custom installation setup so you can install only the set of components you need.
*
You have reviewed the release notes in readme_psql.htm on the installation media for important, late-breaking warnings and information that could not be included as part of the user documentation but may be essential to your installation and use of the product.
*
If you are using a proxy server, you need to configure it to allow authorization of PSQL. Configure the proxy server before you install PSQL, or omit product authorization during installation and authorize the product after configuring the proxy server. See Authorization Access Through a Proxy Server in PSQL User's Guide.
*
You have a good understanding of User Access Control (UAC), as well as the differences and limitations of Standard Users versus Administrators and also have the appropriate permissions to install on the target system.
*
Your application vendor supports the PSQL engine.
*Tip: If you are uncertain, contact your application vendor or review the documentation provided by your vendor to ensure that they support the PSQL engine version and mode that you want to install.
Common Preinstallation Questions
This section contains some of the most common questions asked prior to installing PSQL. These questions represent special case scenarios that could possibly prevent a successful first-time installation. Before you begin installation, consider the situations represented by these questions, along with the Quick Checklist to determine if you have met all the requirements and if there are situations that need special attention.
Where do I install the PSQL Server or Vx Server?
The Server engine must be installed on the same computer where the database files are located.
What about the Server’s client software?
The PSQL Client is installed with every engine. So, if you have a PSQL engine installation, you can use your machine to connect to other remote engines as a client.
The PSQL Client software must be installed on every computer that is expected to access the database.
Where do I install the PSQL Workgroup?
PSQL Workgroup can be installed on the same computer where the database files are located, or it can be installed on other computers to access the data over the network.
What about the Workgroup’s Client software?
The PSQL Client is installed with every engine. If you access remote files through another Workgroup engine, the Client software is already installed, so you do not need to install the Client separately.
How do I install PSQL in a Microsoft Cluster Services environment?
If you plan to install PSQL in a clustered environment using Microsoft Cluster Service (MSCS), you should first refer to High Availability Support in Advanced Operations Guide. This topic provides instructions for installing or patching PSQL in a clustering environment.
Running virtual machines (VMs) within an MSCS environment is typically quite involved. Consequently, running PSQL on VMs within an MSCS environment is more complicated than when not using VMs. Refer to the documentation from the various hypervisor vendors for running VMs within MSCS.
How do I install PSQL in a Microsoft Terminal Services or XenApp environment?
If you plan to install PSQL to a Microsoft Terminal Server or XenApp environment, you must be logged on to the console of the server as a user with system administrator rights to install. This can either be the physical console on the server or a remote console session.
If you install the Workgroup or the Client Cache Engine on a Terminal Services Environment, install the Engine to run as a service. For Workgroup, the default installation for a fresh install is to run as a service. For Client, the default installation is to run as an application, so you need to specify “run as a service” instead. If installed as a service, the Client Cache Engine service is set by default to auto-start. However, even though the Cache Engine service is running, an application does not use the Cache Engine unless the configuration setting for it is turned “on” (it is “off” by default). See Use Cache Engine in Advanced Operations Guide.
Only one instance of the database engine may run on any terminal server platform. You cannot run separate copies of the database engine within two or more terminal sessions. Refer to the PSQL website for the list of Terminal Server Environments supported by PSQL Server, Vx Server, Workgroup and Client.
*Note: If a user starts the Workgroup Engine or Cache Engine in a Terminal Services session or in a multi-user environment where fast-user switching is used, other users on the system cannot access that engine nor can they start their own copy of the engine.

Status code 3032 results if a second user attempts to access another user's engine through the MicroKernel Engine.

If it is desirable to have multiple local users accessing a local engine, ensure that the Workgroup or Client Cache Engine runs as a service. See information above about installing Workgroup Engine or Cache Engine in a Terminal Services environment.
How do I install my PSQL database engine in a Microsoft Active Directory environment?
The installation of the PSQL database engine in an Active Directory environment requires no special steps. Follow the installation steps as described in this manual for the product you have purchased.
You may install the PSQL database engine on a domain controller if you choose. Be aware, however, that activity on the domain controller may affect the performance of the database engine. For this reason, you may prefer to install PSQL on a server that is not a domain controller.
Where do I install my PSQL Clients accessing Web applications?
For Web applications, the Client must be installed on the same computer as the Web server. Multiple Web server platforms require a client on each platform.
Does it matter if I use PSQL Clients that are of a different version than that of the database engine?
Actian Corporation recommends that you use Clients that are the same version as the database engine. If you choose, you may use a Client that is an older version than the database engine with which it interacts. In some situations, depending on the type of SDK access method used by your application, an older version requester will not work with the database engine. Your application will be unable to communicate with the database engine. For those situations, you must use Clients that are the same version as the database engine.
Clients that are a newer version than the database engine may or may not function correctly. Actian Corporation does not guarantee that newer versions of Clients will function correctly with older versions of the engine. Therefore, Actian Corporation recommends that you avoid the use of newer version Clients with an older engine.
Does it matter where I download the PSQL v12 install file?
Yes, it does matter. If you are installing a downloaded version of PSQL, do not place the install file in a location that is listed in the PATH environment variables, as this can cause issues with file copying during install. Place the setup files in a location such as the Windows %temp% directory.
My system runs 24/7, is any time better than another for installing or upgrading to PSQL v12?
The installation and upgrade should be performed during a period when all users are logged off the system and all data files are closed. As with any significant software installation, be sure to back up any important files on the target hard drive, including data files, before you begin the installation.
If you are performing an upgrade, keep the installation media and instructions from the old installation, in the unlikely event that you need to fall back to the previous version of the product.
How can I restrict users running in Terminal Services from changing PSQL configuration settings, creating DSNs, and using the Monitor utility?
PSQL clients running within Terminal Services client sessions can perform PSQL administrative functions by default. For example, a user with such a client can change configuration settings for PSQL, create DSNs, and use the Monitor utility. In prior releases, the ability to perform administrative functions was prohibited from the client.
To restrict this capability, a system administrator should follow these steps:
1
From PCC, open the properties for the MicroKernel Router under Local Client.
2
On the Properties dialog, check the option Restrict Administrative Functions from a WTS Client.
3
Click OK, then exit PCC and start it again for the setting to take effect.
Are there any special settings I need to make for my configuration that aren’t listed here?
Yes, there are some default settings in PSQL that need to be adjusted if your configuration includes certain situations. For example, the default settings need adjustment if you have:
•
Multiple network interfaces
•
Database Files that must not include Embedded Spaces
•
Microsoft Active Directory Service
•
A Network that is subject to outages
Please review Configuration for Special Installation Situations for these or other relevant issues, especially if you encounter problems after installation.