Installing PSQL on Windows Nano Server or Windows IoT Core
Adding PSQL to Specialized Windows Operating Systems
The following topics cover installation and configuration of PSQL Server, Client, and Client Reporting Engine on Windows Nano Server and Windows IoT Core:
Before You Install PSQL on Windows Nano Server or IoT Core
Before installing PSQL on these platforms, we recommend you review the release notes from the
Actian website. Also, be aware that throughout the PSQL documentation, all references to PSQL Server apply to installations on Windows Nano Server and IoT Core systems as well.
You must be logged in as administrator to install any of the products.
Installing PSQL Using PowerShell
Microsoft PowerShell and the .zip archive format are used to install PSQL on Windows Nano Server or IoT Core. The following topics explain how to use these to install PSQL.
Choosing a .Zip Archive for Installing PSQL
Depending on the operating system where you install PSQL, choose a .zip file from the following table.
Windows Platform | PSQL Products Supported | .Zip Archive |
Nano Server | Server, Client, Client Reporting Engine | Install-PSQL-Any-yy.yy-zzz.zzz-winuwp.x86_64.zip |
Windows IoT Core, x86 | Server, Client | Install-Zen-IoT-yy.yy-zzz.zzz-winuwp.x86.zip |
Windows IoT Core, ARM32 | Server, Client | Install-Zen-IoT-Any-yy.yy-zzz.zzz-winuwp.arm32.zip |
In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.
A server installation includes the engine and client files and selected utilities. Client installations provide only files and utilities needed to support a client. Client Reporting Engine installations are the same as those on other Windows platforms.
Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.
First-Time Installation on Windows Nano Server or IoT Core
After choosing a .zip file and copying it to the target system, proceed with the following steps. After completing them, see
Windows Firewall Configuration.
►To install PSQL using PowerShell
1 On the target system, start a PowerShell session as Administrator.
2 Expand the installation .zip archive.
You can use the PowerShell Expand-Archive cmdlet. For example, to extract an archive located in your temp folder to a new folder C:\temp, use the following PS command.
PS> Expand-Archive -Path "$env:temp\Install-Zen-IoT-13.20-014.000-winuwp.x86.zip" -DestinationPath "C:\temp"
3 Launch the installation using the PS command Install-PSQL.ps1 with an argument to select the PSQL product to install.
•For Windows Nano Server, the valid arguments are Server, Client, or Reporting.
•For Windows IoT Core, the valid arguments are Server and Client.
For example, if you extracted the .zip file to C:\temp\PSQL and want to install PSQL Server, you would use the following:
PS> C:\temp\PSQL\Install-PSQL.ps1 server
The installation displays progress information in the console and creates a log file in the user's temp folder $env:temp.
After installation, you can reclaim disk space by removing the .zip archive and its extracted files.
Windows Firewall Configuration
PSQL installation for Windows Nano Server and Windows IoT Core systems requires that Windows Firewall rules allow communication through the firewall. These rules are not enabled by default. To enable them, run the PowerShell script Enable-PsqlFirewallRules.ps1, which is included in a default PSQL installation in C:\Program Files\Actian\PSQL\bin. If needed, you can enter one of the following arguments to enable the rules only for the specified Windows Firewall profile:
•domain
•private
•public
•any (default)
The following example enables the firewall with the domain argument:
PS> & "C:\Program Files\Actian\PSQL\bin\Enable-PsqlFirewallRules.ps1" domain
If you enter no argument, then rules for all Windows Firewall profiles are enabled, the same as if you had entered the argument any. After the script is executed, it displays the current state of the rules for all profiles.
Upgrade Installation on Windows Nano Server or IoT Core
To upgrade an existing installed version of PSQL on Windows Nano Server and Windows IoT Core, repeat the installation steps using a new .zip archive.
You do not need to redo changes made to Windows Firewall rules after the first installation.
After Installing PSQL on Windows Nano Server or IoT Core
The following topics may be useful after you install PSQL. Throughout the PSQL documentation, references to PSQL Server apply to installations on Windows Nano Server and IoT Core systems.
Server Configuration
All configuration settings for PSQL Server are available on Windows Nano Server and IoT Core. Generally, the default configuration settings used for PSQL Server are sufficient. For information on these settings, see
Configuration Reference in
Advanced Operations Guide.
Client Configuration
Basic configuration settings for installations of PSQL Client are discussed in
Setting Up Network Communications for Clients. For information on all client settings, see
Windows Client Configuration Properties in
Advanced Operations Guide.
Licensing
On both Windows Nano Server and IoT Core, PSQL uses license keys instead of product keys.
Code Page Configuration on Windows IoT Core Systems
In the current release, the code page for a PSQL installation on Windows IoT Core defaults to Western European 1252. You can change the code page using PowerShell. For example, if you want to change the setting to Microsoft Windows 932 for Japanese systems, use the following command:
Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Nls\CodePage -Name ACP -Value 932
Common Questions After Installation
If you have problems with your installation, see
Troubleshooting After Installation or get help online from the PSQL knowledge base at the
Actian website. The following are common questions after installation of the products:
How Can I Verify That the Database Engine is Running?
After the installation script finishes, you can verify that the database engine is running with the PowerShell Get-Service command. To do so, enter the following at a command prompt:
Get-Service -DisplayName "Actian PSQL*"
If the engine is running, this command returns the following:
Status Name DisplayName
------ ---- -----------
Running Pervasive.SQL (... Actian PSQL Relational Engine
Running Pervasive.SQL (... Actian PSQL Transactional Engine
If the relational or transactional engine is stopped, you can use the following commands to manually start them, which must be run in the order given here:
Start-Service -DisplayName "Actian PSQL Transactional Engine"
Start-Service -DisplayName "Actian PSQL Relational Engine"
The engine services start automatically with the operating system. If you need to stop them, use the following command:
Stop-Service -DisplayName "Actian PSQL*"
After running this command, the Get-Service command returns the following:
Status Name DisplayName
------ ---- -----------
Stopped Pervasive.SQL (... Actian PSQL Relational Engine
Stopped Pervasive.SQL (... Actian PSQL Transactional Engine
What Utilities Are Installed?
On Nano Server systems, PSQL provides a subset of the command line utilities that are available in full installations. These utilities consist of the following:
bcfg | butil | dbdefrag |
bdu | clilcadm | pvddl |
bmon | clipaadm | pvnetpass |
On IoT Core systems, the utilities consist of the following:
bcfg | butil | dbdefrag |
bdu | clilcadm | pvddl |
bmon | clipaadm | pvnetpass |
Where Do Files Reside After Installing PSQL?
The following table lists the primary directories and files installed for PSQL products on Windows Nano Server or IoT Core. The variable %ALLUSERSPROFILE% is used to determine the location of some files, while others default to C:\Program Files\Actian\PSQL.
Location | File | Description | Installation |
C:\Program Files\Actian\PSQL | See description | License information in a file: •Windows Nano Server and IoT Core: EULA_en.rtf or EULA_Client_en.rtf •arm32: LICENSE | Server, Client |
C:\Program Files\Actian\PSQL\bin | | Binary files, executable utilities, and so forth | Server, Client, Client Reporting Engine |
%ALLUSERSPROFILE%\Actian\PSQL\Demodata | | Sample PSQL database to create from a set of SQL scripts in a directory named restore | Server |
%ALLUSERSPROFILE%\Actian\PSQL\samples | | Sample Btrieve files, alternate collating sequence file and the DefaultDB system database | Server |
%ALLUSERSPROFILE%\Actian\PSQL\. | dbnames.cfg | Master table of database names | Server |
%ALLUSERSPROFILE%\Actian\PSQL\log | | Transaction log files directory | Server, Client, Client Reporting Engine |
How Do I Access the Documentation?
No documentation is included in a PSQL installation on Windows Nano Server or IoT Core. You may use the documentation installed with other PSQL editions or posted on the
Actian website.
Where Are the Release Notes?
The release notes contain general information about the release, sometimes including late-breaking advice not yet covered in the user documentation. Although this document is not included in PSQL installations on Windows Nano Server or IoT Core, the
Actian website posts the latest version.
Uninstalling PSQL on Windows Nano Server or IoT Core
Use the following steps to remove PSQL from your system.
►To remove PSQL from Windows Nano Server or IoT Core
To remove PSQL from the system, you use the script Uninstall-PSQL.ps1. This script is located in the PSQL bin folder C:\Program Files\Actian\PSQL\bin. You should invoke it from a working directory located outside that path, as shown in the example used here.
1 On the system where PSQL is installed, start a PowerShell session as Administrator.
2 Set the location as shown here:
PS> Set-Location c:\
Note If the script is invoked from a location that is in the PSQL installation folder path, the PSQL files and directories are not removed, and you must manually delete them after running the removal script.
3 Run the removal script.
PS C:\> & "C:\Program Files\Actian\PSQL\Bin\Uninstall-PSQL.ps1"
The script displays status information in the console and creates a log file in the user's temp folder $env:temp.
Removal of PSQL is complete.