Zen v14 Release Notes General Release

See What’s New in Zen for coverage of new and changed features in this release of Zen. This document is included with the installed documentation and at the Actian website on the download page. The download version may be updated after the product release, so we recommend you refer to that version for the latest information.

Installing Zen

This topic discusses installation of the product. Before reading further, be familiar with Product Authorization.

Installation files are available for download from the Actian website.

You must remove any previously installed prerelease version, such as a beta or release candidate from any edition, before installing a final General Availability (GA) release of Zen.

If you have not installed the product before or are upgrading for the first time and want to read about installation in detail, see Getting Started with Zen, available on the installation media or the Actian website.

Installation steps vary with the platform where Zen is to run:

•

Installing on Windows

•

Installing on Windows IoT Core

•

Installing on Linux

•

Installing on macOS

•

Installing on Raspbian 32-bit

The following topics provide additional installation information:

•

Important Notes about Installing or Upgrading on Windows

•

Important Notes about Installing on macOS and Raspbian 32-bit

•

Source Code for Zen unixODBC

•

JRE Components Included in Installation

Installing on Windows

To start the installation, run the installer application (Install_*.exe) for the Zen product that you want to install and follow the instructions displayed by the installer.

The Zen installer automatically detects the bit architecture of the operating system and installs the right components. You do not have to choose the 32- or 64-bit installer application.

The following table describes Zen installers on Windows operating systems.

Zen Installation Package (.exe)	Description
Install_Zen_EnterpriseServer	Installs 32-bit engine on 32-bit operating system. Installs 64-bit engine on 64-bit operating system. Installs all client components.
Install_Zen_CloudServer	Installs 32-bit engine on 32-bit operating system. Installs 64-bit engine on 64-bit operating system. Installs all client components.
Install_Zen_Workgroup_Engine	Installs 32-bit engine on both 32- and 64-bit operating systems. Installs all client components.
Install_Zen_Client	Installs 32-bit components on 32-bit operating system. Installs both 32- and 64-bit components on 64-bit system.
Install_Zen_Reporting_Engine	Installs 64-bit engine on 64-bit operating system. Installs all client components.

Important Notes about Installing or Upgrading on Windows

The following information applies only to Zen users on Windows systems.

Subject

Discussion

Windows Update

We recommend you apply the latest available Microsoft Windows software updates before installing Zen.

Applications

We recommend you close all Windows applications before installing Zen.

Installation prerequisites

For installation to succeed, Windows systems require the following updates:

•

Windows 7 or Server 2008 R2: Service Pack 1

•

Windows 8.1 or Server 2012 R2: Windows Update 3118401

Ecosystem product compatibility

AuditMaster, Backup Agent, and DataExchange installed with Zen versions before v14 are not compatible with the current release. They must be removed before installing Zen v14. Their v14 versions can be installed again after upgrading to Zen v14.

User settings for ZenCC tools

Upgrading from an earlier version of Zen to Zen v14 does not preserve Function Executor user settings, which return to their default values. After upgrading, users must reset Function Executor options if needed.

PSQL v11 and DataExchange v5.1 users upgrading to Zen v14 and DataExchange v14

On PSQL v11 systems that also run DataExchange v5.1, a known issue in PSQL installers before 11.31 blocks attempts to upgrade from PSQL v11 to Zen v14. Updating PSQL v11 to 11.31 before upgrading to Zen v14 resolves the issue.

Windows firewall and client/server applications

Zen installations add files to the firewall access list to enable client-server functionality. If the operating system security prompts you during installation of Zen to unblock or allow communication with a Zen component, select OK (yes).

Optionally disable restore points

The total installation time can usually be reduced on Windows 7 and Windows 2008 R2 and later systems by disabling Windows System Restore. Alternatively, the installation can be made to skip the creation of a system restore point without actually disabling Windows System Restore by setting the property “MSIFASTINSTALL=1” on the command line. For example:

Install_Zen_<InstallType>.exe /s /v" /l*v \"%temp%\Zenv14_InstallLogFileName.log\" MSIFASTINSTALL=1"

Characters to avoid in installation path

Do not use the characters for pound (#), percent (%), or double backslash (\\, used to specify a UNC path) in installation paths for Zen products if you plan to use Zen Control Center or DDF Builder. These two utilities cannot run if the installation path contains these characters.

Modifying to run Workgroup Engine as an Application

If you install Workgroup Engine as service, then later decide you want to run it as an application, uninstall the engine, then reinstall it as an application.

Upgrading to run Client Cache Engine as a Service

If you install Client Cache Engine as an application, then later decide you want to run it as a service, uninstall the client, then reinstall it as a service.

Changing Product Type

If your previous PSQL installation was a Workgroup Engine, and you want to replace it with Zen Enterprise Server or Cloud Server, you must uninstall Workgroup Engine first. Before doing so, we recommend that you review your current database configuration settings and record them so that you can recreate them after installing the new server product. To do the review, open PCC and right-click each database to select Properties and display the settings.

Authorization and security

You must have Administrator rights to run the installer.

Depending on the particular account, a local security policy called “Sharing and security model for local accounts” can adversely affect network logins. Be sure that this policy is set to Classic, which authenticates users as themselves.

PATH location

If you are installing a downloaded version of the product, do not place the setup files in a location that is listed in the Path environment variables. This can cause issues with file copying during installation. Place the setup files in a location such as the Windows temp directory.

Installing Silently on Windows

To install Zen silently, run the installation using the quiet command line option /qn, as shown in this example:

Install_Zen<InstallType>.exe /s /v"/qn /l*v \"%temp%\Zenv14_InstallLogFileName.log\""

This example creates an installation log file in the Windows temp directory.

Optionally, to authorize Zen after the installation has completed, use the License Administrator command line tool clilcadm.exe:

"<Zen_install_path>\bin\clilcadm.exe" -a <key>

Installing on Windows IoT Core

This release has been tested on Windows IoT Core. For information about installing or upgrading on these platforms, see Getting Started with Zen.

Installation Packages

On Windows IoT Core, Zen offers full server and client installations as noted in the following table. A full server installation includes necessary engine and client files and utilities. A client installation provides only files needed to support a client, including utilities. The following table lists the installation packages. Microsoft PowerShell and the .zip archive format are used for the installation.

Windows Platform	Zen Products Supported	.Zip Archive1
Windows IoT Core, x86	Enterprise Server, Client	Install-Zen-EnterpriseServer-yy.yy.zzz.zzz-winuwp.x86.zip
Windows IoT Core, ARM32	Enterprise Server, Client	Install-Zen-EnterpriseServer-Any-yy.yy.zzz.zzz-winuwp.arm32.zip
1 yy.yy and zzz.zzz represent the digits in the file name for the release and build numbers of the product.

Installing on Linux

Zen v14 has been tested on Red Hat Enterprise Linux 7, OpenSUSE, and CentOS. For information about installing or upgrading to Zen v14 on Linux, see Getting Started with Zen.

Installation Packages

On Linux, Zen offers full server and client installations as both RPM and TAR Linux packages. A full server installation includes engine and client files, utilities, and the complete user documentation. A client installation provides only files needed to support a client, including utilities and documentation. The following table lists the installation packages.

Zen Package	Contains	Package Names1
Enterprise Server 64-bit	Full installation of 64-bit engine, 64-bit client files, 64-bit utilities, documentation.	Zen-EnterpriseServer-linux-yy.yy-zzz.zzz.x86_64.rpm Zen-EnterpriseServer-linux-x86_64-yy.yy.zzz.zzz.tar.gz
Cloud Server 64-bit	Full installation of 64-bit engine, 64-bit client files, 64-bit utilities, documentation.	Zen-CloudServer-linux-yy.yy-zzz.zzz.x86_64.rpm Zen-CloudServer-linux-x86_64-yy.yy.zzz.zzz.tar.gz
Client 64-bit	64-bit client files, 64-bit utilities, documentation.	Zen-Client-linux-yy.yy-zzz.zzz.x86_64.rpm Zen-Client-linux-x86_64-yy.yy.zzz.zzz.tar.gz
Client Access 32-bit	32-bit client files for compatibility with 32-bit applications on 64-bit Linux. Installed after one of the other three packages. Note: Glibc and stdc++ packages are prerequisites for the Client Access installation. Before installing Client Access, you can add these packages from the repository of your Linux distribution using a yum command: yum install glibc.i686 libstdc++.i686 In LD_LIBRARY_PATH, add the /lib directory of the Client Access installation location so that your 32-bit application can find it. For example, /usr/local/actianzen/lib64:/usr/local/actianzen/lib.	Zen-Client-Access-linux-yy.yy-zzz.zzz.x86_64.rpm Zen-Client-Access-linux-x86_64-yy.yy.zzz.zzz.tar.gz
1 yy.yy and zzz.zzz represent the digits in the file name for the release and build numbers of the product.

Note To upgrade to Zen v14 from a previous PSQL version on Linux, you must first uninstall the current version. Also, you must stop any process owned by user psql that may still be running on your system.

Installing on macOS

Zen v14 has been tested on macOS 10.14. For information about installing or upgrading to Zen v14 on this operating system, see Getting Started with Zen.

Installation Packages

On macOS, Zen offers full server and client installations of both TAR and DMG packages. A full server installation includes necessary engine and client files, utilities, and the complete user documentation. A client installation provides only files needed to support a client, including utilities and documentation. The following table lists the installation packages.

Zen Package	Contains	Package Names1
Enterprise Server 64-bit	Full installation of 64-bit engine, 64-bit client files, 64-bit utilities, documentation.	Zen-EnterpriseServer-macos-x86_64-yy.yy.zzz.zzz.tar.gz Zen-EnterpriseServer-macos-x86_64-yy.yy.zzz.zzz.dmg
Cloud Server 64-bit	Full installation of 64-bit engine, 64-bit client files, 64-bit utilities, documentation.	Zen-CloudServer-macos-x86_64-yy.yy.zzz.zzz.tar.gz Zen-CloudServer-macos-x86_64-yy.yy.zzz.zzz.dmg
Client 64-bit	64-bit client files, 64-bit utilities, documentation.	Zen-Client-macos-x86_64-yy.yy.zzz.zzz.tar.gz Zen-Client-macos-x86_64-yy.yy.zzz.zzz.dmg
1 yy.yy and zzz.zzz represent the digits in the file name for the release and build numbers of the product.

Note To upgrade to Zen v14 from a previous version on macOS and Raspbian 32-bit, you must first uninstall the current version.

Installing on Raspbian 32-bit

This release has been tested on Raspbian 32-bit. For information about installing or upgrading on this platform, see the Linux documentation in Getting Started with Zen.

Installation Packages

On Raspbian 32-bit, Zen offers full server and client installations of TAR packages. A full server installation includes necessary engine and client files, utilities, and the complete user documentation. A client installation provides only files needed to support a client, including utilities and documentation. The following table lists the installation packages.

Zen Package	Contains	Package Names1
Enterprise Server	Full installation of engine, client files, utilities, documentation.	Zen-EnterpriseServer-linux-armhf-yy.yy.zzz.zzz.tar.gz
Client	Client files, Utilities, documentation	Zen-Client-linux-armhf-yy.yy.zzz.zzz.tar.gz
1 yy.yy and zzz.zzz represent the digits in the file name for the release and build numbers of the product.

Important Notes about Installing on macOS and Raspbian 32-bit

The following information applies when you install on macOS and Raspbian 32-bit systems. These notes all relate to access and authentication using the Samba implementation of the SMB/CIFS networking protocol. The instructions for configuring Samba on Linux also apply to macOS and Raspbian 32-bit, but with the exceptions shown here.

Subject

Discussion

Samba version

Samba (SMB) file sharing is required for remote Btrieve-level file access. Set native file sharing under System Preferences > Sharing or use an compatible Samba 3 package, such as SMBUp.

Authentication level

All three levels of authentication are supported. However, authentication through PVPIPE$ is not supported on that operating system.

Samba configuration file location

If your Samba package installs the Samba configuration file in a location other than one in the following list, you must enter that path name in the Properties > Access settings for your server.

•

/etc/samba/smb.conf

•

/etc/smb.conf

•

/usr/local/samba/lib/smb.conf

•

/usr/local/lib/smb.conf

•

/lib/smb.conf

•

/etc/samba.d/smb.conf

•

/opt/samba/lib/smb.conf

•

/usr/share/samba/smb.conf

•

/usr/local/share/samba/smb.conf

•

/home/samba/lib/smb.conf

•

/opt/local/etc/samba3/smb.conf (default location for Samba 3)

If you use native file sharing, Zen retrieves drive-sharing settings directly from the system. No smb.conf file is required. For more information, see the topic on native SMB file sharing in Getting Started with Zen.

For more information, see Server Configuration Parameters in Advanced Operations Guide.

PVPIPE$

PVPIPE$ applies only to Linux. Zen currently does not use this FIFO.

Source Code for Zen unixODBC

In accordance with GNU General Public Licensing (GPL), on Linux, macOS, and Raspbian 32-bit systems the source code for Zen unixODBC functionality is redistributed in the /etc directory of the installation as psql-unixODBC-2.2.11.tar.gz.

JRE Components Included in Installation

Zen bundles JRE 8 from OpenJDK in its installations on Windows, Linux-based systems, and macOS. The version is OpenJDK 8, Update 222, build 10 (8u222b10). You may replace this copy with a later update of OpenJDK 8 without interfering with the Zen installation.

Installing Backup Agent

Backup Agent does not require a separate license when used with Zen Enterprise Server. It is included with Zen Enterprise Server for Windows. To use Backup Agent with Zen Workgroup, you must have a separate license.

Windows IoT Core

Backup Agent v14 is not currently supported on Windows IoT Core.

Linux Red Hat, openSUSE, and CentOS

On Linux Red Hat, openSUSE, and CentOS before installing Zen v14, you must manually uninstall any existing version of Backup Agent. After installing Zen v14, you can manually install Backup Agent v14.

macOS

Backup Agent v14 is not currently supported on macOS.

Raspbian 32-bit

Backup Agent v14 is not currently supported on Raspbian 32-bit.

Fixed and Known Issues

The Actian community forums and knowledge base both enable you to search for a history log that lists issues fixed and enhancements added since the previous release. You can also find a list of current known issues.

Usage Notes

This topic discusses situations you might encounter using the product after installation.

For Windows

Subject

Discussion

Code page configuration on Windows IoT Core systems

In the current release, the code page for a Zen 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

Restore point errors in Zen install log

Failures pertaining to restore point can be ignored. Sometimes the Windows operating system fails to create a snapshot of the current disk (called a restore point) before allowing a new application installation. The restore point is not required. Uninstalling Zen completely removes the product from the system.

No right-click option to run utilities as administrator on Windows 7

Right-clicking an application utility in the Windows Start menu does not offer a Run As Administrator option. This is a limitation of Windows Installer 3.1.

If you want to run a Zen utility in an elevated mode, you have several options:

•

Run the utility from an elevated command prompt.

•

Create your own desktop shortcut to the utility executable.

•

Navigate to the utility executable with Windows Explorer.

Technical Support

You can find information and obtain help from several online options at the Actian website:

•

Community Forums. Join the technical discussion under Actian Zen.

•

Knowledge Base. Search articles for answers and solutions others have found useful.

•

Technical Support. Open a help ticket, submit a defect, or purchase services.

This Documentation is for the end user’s informational purposes only and may be subject to change or withdrawal by Actian Corporation (“Actian”) at any time. This Documentation is the proprietary information of Actian and is protected by the copyright laws of the United States and international treaties. The software is furnished under a license agreement and may be used or copied only in accordance with the terms of that agreement. No part of this Documentation may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or for any purpose without the express written permission of Actian. To the extent permitted by applicable law, ACTIAN PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, AND ACTIAN DISCLAIMS ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS OR IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTY OF MERCHANTABILITY, OF FITNESS FOR A PARTICULAR PURPOSE, OR OF NON-INFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT WILL ACTIAN BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF ACTIAN IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

The manufacturer of this Documentation is Actian Corporation.

For government users, the Documentation is delivered with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013 or applicable successor provisions.

Actian, Actian DataCloud, Actian DataConnect, Actian X, Avalanche, Versant, PSQL, Actian Zen, Actian Director, Actian Vector, DataFlow, Ingres, OpenROAD, and Vectorwise are trademarks or registered trademarks of Actian Corporation and its subsidiaries. All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

This product includes software developed by Powerdog Industries. © Copyright 1994 Powerdog Industries. All rights reserved. This product includes software developed by KeyWorks Software. © Copyright 2002 KeyWorks Software. All rights reserved. This product includes software developed by DUNDAS SOFTWARE. © Copyright 1997-2000 DUNDAS SOFTWARE LTD., all rights reserved. This product includes software developed by the Apache Software Foundation (www.apache.org).

This product uses the free unixODBC Driver Manager as written by Peter Harvey (pharvey@codebydesign.com), modified and extended by Nick Gorham (nick@easysoft.com), with local modifications from Actian Corporation. Actian Corporation will donate their code changes to the current maintainer of the unixODBC Driver Manager project, in accordance with the LGPL license agreement of this project. The unixODBC Driver Manager home page is located at www.unixodbc.org. For further information on this project, contact its current maintainer: Nick Gorham (nick@easysoft.com).

A copy of the GNU Lesser General Public License (LGPL) is included on the distribution media for this product. You may also view the LGPL at www.fsf.org/licensing/licenses/lgpl.html.