Before installing or upgrading Zen Enterprise Server, Cloud Server, Edge Server, or Client, review the following information:
•System requirements listed in the Zen release notes, readme_zen.htm, which also includes other late-breaking updates that may not be included in the user documentation.
Zen offers the following 64-bit full and client installations:
•TAR packages for Linux, macOS, and Raspbian
•RPM packages for Linux
•DMG packages for macOS
A full installation includes the engine and client files, utilities, and the complete user documentation. Client installations provide only files needed to support a client, including utilities and documentation. If you have 32-bit applications, support is provided as an additional client access installation. The following table lists the installation packages.
Table 6 Full and Client Installations on Linux, macOS, and Raspbian
Zen Product
Installation
Contains
Enterprise Server 64-bit
Full
Engine and client files, utilities, and documentation.
Edge Server 32-bit (Raspbian only)
Subset of full server
Engine and client files, a subset of CLI utilities, no documentation. See Utilities on Raspbian for the list of items provided.
Cloud Server 64-bit
Full
Engine and client files, utilities, and documentation.
Client 64-bit
Client
Client files, utilities, and documentation.
Client 32-bit (Raspbian only)
Subset of client
Client files, a subset of CLI utilities, no documentation. See Utilities on Raspbian for the list of items provided.
Client Access 32-bit (Linux only)
Client
Client files and limited 32-bit utilities. Installed after one of the other three products to enable database access for 32-bit applications.
Note: Glibc and stdc++ packages are prerequisites for the Client Access installation. Before installing Client Access, you can add them from the repository of your Linux distribution using a yum command:
yum install glibc.i686 libstdc++.i686
Utilities on Raspbian
On Raspbian systems, Zen provides a subset of the command line utilities that are available in full installations. These utilities consist of the following:
bcfg
btadmin
clipaadm
dsnadd
psregedit
pvddl
bdu
butil
dbdefrag
isql
psregsvr
pvnetpass
bmon
clilcadm
dbmaint
licgetauth
pvdbpass
rbldcli
Connecting from a Linux-Based Client to a Windows Enterprise Server or Cloud Server
The Server Message Block (SMB) protocol enables network access to the Zen MicroKernel Engine from a Linux, macOS, or Raspbian client at the Btrieve file level. You can find information about SMB-compatible file sharing at www.samba.org. For more information on remote Btrieve-level access, see Supported Path Formats for Samba.
The package manager copies all necessary files onto disk (default location is /usr/local/actianzen) and runs a post-installation script which performs the following tasks:
•Creates user zen-svc and group zen-data
•Sets user:group ownership to zen-svc:zen-data for the installed files
•Authorizes a trial license
•Creates a new ODBC DSN (data source name) for the Demodata test database
•Creates startup and shutdown scripts for Zen daemons
•Launches the Zen daemon (mkded)
►To install Zen Enterprise Server or Cloud Server using RPM
Note If you have a previous version of Zen on your Linux machine, see Upgrade Installation.
1 Log in as the root user.
2 Assuming the RPM package is in the current directory, enter the following command:
rpm -ivh <server_package_name>
If the RPM package is in another directory, preface the package name with a path.
Upgrade Installation
If you have a previous version of Zen already installed, you must uninstall that version and then install the new release of the product. See Uninstalling Zen on Linux, macOS, or Raspbian for more information.
Installing Zen Client for Linux - RPM
The name of the Zen Client installation package uses the conventions in the following table.
Table 8 Client Package Names - RPM
Installation Type
Platform
Package Name
Client 64-bit
x86-64
Zen-Client-linux-yy.yy-zzz.zzz.x86_64.rpm
Client Access 32-bit
x86-64
Zen-Client-Access-linux-yy.yy-zzz.zzz.x86_64.rpm
In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.
Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.
First-Time Installation
If you need to provide 32-bit client access for an application, you must install the Zen Client 64-bit first, and then add Zen Client Access 32-bit. Otherwise, the steps are the same.
►To install Zen Client using RPM
1 Log in as the root user.
2 Assuming the RPM package is in the current directory, execute the following command.
rpm -ivh <client_package_name>
If the RPM package is in another directory, preface the package name with a path.
Upgrade Installation
If you have a previous version of Zen already installed, you must uninstall that version and then install the new release of the product. See Uninstalling Zen on Linux, macOS, or Raspbian for more information.
Installing Zen Using TAR
The tape archive (TAR) format allows you to install Zen on Linux, macOS, and Raspbian. The following topics explain how to install Zen products using TAR:
Upgrading a Zen Server Installation on Linux and Raspbian
If you have a previous version of Zen already installed, you must uninstall that version and then install the new Zen product. See Uninstalling Zen on Linux, macOS, or Raspbian for more information.
Installing a Zen Server on macOS - TAR
The name of the Zen server installation package uses the conventions in the following table.
Table 10 Server Package Names - TAR
Installation Type
Platform
Package Name
Enterprise Server 64-bit
x86-64
Zen-CloudServer-macos-x86_64-yy.yy.zzz.zzz.tar.gz
Cloud Server 64-bit
x86-64
Zen-CloudServer-macos-x86_64-yy.yy.zzz.zzz.tar.gz
In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.
Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.
If you have a previous version of Zen already installed, you must uninstall that version and then install the new Zen product. See Uninstalling Zen on Linux, macOS, or Raspbian for more information.
Installing Zen Client for Linux and Raspbian - TAR
The name of the Zen Client installation package uses the conventions in the following table.
In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.
Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.
First-Time Client Installation on Linux and Raspbian
If you need to provide 32-bit client access for an application, you must install the Zen Client 64-bit first, and then add Zen Client Access 32-bit. The installation steps are the same except for the pre- and post-installation scripts, as described below. Note that 32-bit client access does not apply to Raspbian systems.
►To install Zen Client for Linux Using TAR
1 Log in as the root user.
2 Change to the /usr/local directory.
cd /usr/local
3 Enter the following command to copy the .tar file to /usr/local.
For example, if you downloaded the installation package to /home/bholly:
cp /home/bholly/<client_package_name> .
4 Unpack the .tar file using the following command.
tar -zxf <client_package_name>
The unpacking action creates a directory named zenclient.
5 Change directories to the /usr/local/actianzen/etc folder where the Zen installation scripts reside.
cd actianzen/etc
6 Run the preinstallation script needed by the client package that you are installing:
Upgrading a Client Installation on Linux and Raspbian
If you have a previous version of Zen already installed, you must uninstall that version and then install the new version. See Uninstalling Zen on Linux, macOS, or Raspbian for more information.
Installing Zen Client for macOS - TAR
The name of the Zen Client installation package uses the conventions in the following table.
Table 12 Client Package Names - TAR
Installation Type
Platform
Package Name
Client 64-bit
x86-64
Zen-Client-macos-x86_64-yy.yy.zzz.zzz.tar.gz
In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.
Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.
First-Time Client Installation on macOS
►To install Zen Client for macOS using TAR
You must be logged in as a user with administrator rights to use the sudo command.
1 Open a terminal window by entering terminal in a Spotlight search.
2 At the prompt, enter a sudo command like the following to gain administrative rights to install applications:
sudo -i bash -l
3 Zen installation requires a /usr/local directory. Use the following command to create it:
mkdir /usr/local
4 Change directories to the newly created location.
cd /usr/local
5 Unpack the .tar file using the tar command.
For example, if you downloaded the installation package to your Desktop:
tar -zxf /Users/<name>/Desktop/<client_package_name>
The unpacking action creates a directory named zenclient.
6 Change directories to the /usr/local/actianzen/etc folder where the Zen installation scripts reside.
cd actianzen/etc
7 Run the preinstallation script needed by the client package that you are installing:
./clientpreinstall.sh
8 Run the postinstallation script needed by the client package that you are installing:
If you have a previous version of Zen already installed, you must uninstall that version and then install the new version. See Uninstalling Zen on Linux, macOS, or Raspbian for more information.
Installing Zen Using DMG on macOS
On macOS, you can install Zen using a native Apple disk image (DMG). A DMG is a container file commonly used to distribute applications for macOS.
The following topics explain how to install Zen products using DMG:
If you have a previous version of Zen already installed, you must uninstall that version and then install the new version. See Uninstalling Zen on Linux, macOS, or Raspbian for more information.
Installing Zen Client for macOS - DMG
The name of the Zen Client DMG uses the conventions in the following table.
Table 14 Client Disk Image - DMG
Installation Type
Platform
Disk Image
Client 64-bit
x86-64
Zen-Client-macos-x86_64-yy.yy.zzz.zzz.dmg
In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.
Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.
First-Time Client Installation on macOS
►To install Zen Client for macOS using DMG
1 Copy the .dmg file to your system.
2 Double-click the file to mount the disk image and open a window that shows three items:
•Zen installer
•Readme file containing release notes in HTML
•License agreement in PDF
3 To open the installer, double-click it and then follow the instructions.
4 When asked, enter an account name and password with administrator rights.
5 When the installer displays the dialog saying that Zen has been installed, you can click Show Me to see it or click Continue.
6 In the dialog offering information about Zen, you can click Show Me to see it or click Continue to unmount the .dmg file and finish.
If you have a previous version of Zen already installed, you must uninstall that version and then install the new version. See Uninstalling Zen on Linux, macOS, or Raspbian for more information.
After Installing Zen on Linux, macOS, or Raspbian
The following topics may be useful after you install Zen on Linux, macOS, or Raspbian:
The following table provides commands with which you can verify which packages the RPM packager installed. The commands are case sensitive.
Table 15 RPM Commands To Verify Zen Packages Installed
Zen Package
RPM Command to Verify Installation
Enterprise Server
rpm -q Zen-EnterpriseServer-linux
Cloud Server
rpm -q Zen-CloudServer-linux
Client 64-bit
rpm -q Zen-Client-linux
Returns the specific client version installed (Zen-Client-release-build).
Client Access 32-bit
rpm -q Zen-Client-Access-linux
Returns the specific client version installed (Zen-Client-Access-release-build).
Note: The 32-bit Client Access package should always be installed after a 64-bit product.
Community
rpm -q Zen-Community-linux
All installed
rpm -qa | grep Zen
Verifying Database Engine is Running
Optionally, after the installation script finishes, you can verify that the database engine is running with the ps command. To do this, enter the following at a command prompt:
ps -e | egrep mkded
Server Configuration
Generally, the default configuration settings for Zen Enterprise Server and Cloud Server are sufficient. See Configuration for settings that you may want or need to set.
If you want to explore all of the configuration settings, see Configuration Reference in Advanced Operations Guide.
Linux, macOS, and Raspbian Clients and the Monitor Utility
This information applies only to Linux, macOS, or Raspbian clients that use a static IP address. Ignore it if you use DHCP and have a DSN to resolve named addresses.
When you monitor clients using the Zen Monitor utility, the client IP address that gets transmitted across the network originates from the hosts file. If the system name and IP have not been added to the hosts file, network communication uses the local host IP address, which is 127.0.0.1 or ::1 (a loopback address).
If you change the loopback address to the correct IP, or if you add the system name and IP to the hosts file on the client, the client name is displayed correctly in the Monitor utility.
Licensing
Once you have completed installation, you may need to update your license to increase the user count for Zen Enterprise Server, or to increase the session count or data in use limits for Cloud Server. See Increase User Count or Data in Use in Zen User’s Guide.
Common Questions After Installation
If you have problems with your installation, see Troubleshooting After Installation or get help online from the Zen knowledge base at the Actian website. The following are common questions after installation of the products:
Where Do Files Reside After Installing Zen on Linux, macOS, and Raspbian?
The following table lists the primary directories and files that result from installation on Linux, macOS, or Raspbian. $ACTIANZEN_ROOT refers to the root directory where the files are installed. By default it is set to /usr/local/actianzen. Unless otherwise noted, the primary directories and files are the same for 32- and 64-bit products.
For an upgrade installation, your existing Zen files were updated to the latest versions.
Table 16 Primary Directories and Files for Zen Products Installed on Unix-based Systems
Path from $ACTIANZEN_ROOT
Primary Files
Description
Applies to Installation of
./
LICENSE
License information
Server
./bin
Binary files, executables
Server and Client
./bin/plugins
A directory of files for utilities and documentation
Server and Client
./data/Demodata
Sample Zen database
Server
./data/samples
Sample Btrieve files, alternate collating sequence file and the DefaultDB system database
Server
./etc
Server and Client
.PSRegistry
Zen registry of configuration settings (this directory and its subordinate directories)
Server
btpasswd
User passwords file
Server
dbnames.cfg
Master table of database names
Server
odbc.ini
ODBC settings
Server and Client
Shell scripts for the following:
•Pre-product installation
•Post-product installation
•Pre-product uninstall
•Post-product uninstall
Server and Client
./lib
Library of 32-bit shared objects
Server and Client
./lib64
Library of 64-bit shared objects
Server and Client
./log
Transaction log files directory
Server and Client
./man/man1
Man pages for the command-line utilities
Server and Client
How Do I Access the Documentation?
The documentation installed with Zen includes the following:
•Man pages for command line utilities
•Documentation Library
•Release Notes
Man Pages
Man pages are provided for the command line utilities. To make these man pages available, add $ACTIANZEN_ROOT/man to the MANPATH environment variable.
Man pages are installed with Zen Enterprise Server, Cloud Server, and Client. Command line utilities are also covered in the user documentation.
Documentation Library
The Zen documentation library contains the complete set of user documentation, including the user documentation for the Zen engine and software development kit.
The documentation library is integrated into Zen Control Center (ZenCC). You can access the documentation library in the Welcome tab opened from the Help menu or by pressing F1 (Windows) or Shift F1 (Linux) to open context-sensitive topics.
Release Notes
The release notes in readme_zen.htm contain general information about the release, sometimes including late-breaking advice not yet covered in the user documentation. These release notes are located in the /usr/local/actianzen/docs/ directory and are linked in the Welcome tab opened from the Help menu in ZenCC. The Actian website posts the latest version of the release notes.
What If I Get Errors Trying to Start the Utilities?
The following table lists the RPM commands to uninstall Zen packages on Linux. You must log in as the root user using the su command before executing any of the commands.
Table 17 RPM Commands to Uninstall the Zen Packages
To Uninstall This Package
Use This RPM Command
Enterprise Server 64-bit
rpm -e Zen-EnterpriseServer-linux
Cloud Server 64-bit
rpm -e Zen-CloudServer-linux
Client 64-bit
rpm -e Zen-Client-linux
Client Access 32-bit
rpm -e Zen-Client-Access-linux
Note: Client Access should be removed before removing the 64-bit package to which it has been added.
Community Edition
rpm -e Zen-Community-linux
Note Uninstalling does not remove the system databases DEFAULTDB and PERVASIVESYSDB.
Removing a Zen TAR Package
This topic provides a table that lists the shell scripts used to remove various Zen installations. The uninstalling of a TAR package is slightly different for Linux, macOS, and Raspbian, as shown in the following steps.
►To uninstall a Zen TAR installation on Linux and Raspbian
1 At a command prompt, log in as the root user using the su command.
2 Change directories to the /usr/local/actianzen/etc folder where the Zen installation scripts reside.
cd /usr/local/actianzen/etc
3 Use the uninstall scripts from the following table that apply to your installation.
►To uninstall a Zen TAR installation on macOS
You must be logged in as a user with administrator rights to use the sudo command.
1 Open a terminal window by entering terminal in a Spotlight search.
2 At the prompt, enter a sudo command like the following to gain administrative rights to install applications:
sudo -i bash -l
3 Change directories to the /usr/local/actianzen/etc folder where the Zen installation scripts reside.
cd /usr/local/actianzen/etc
4 Use the uninstall scripts from the following table that apply to your installation.
Table 18 TAR Commands to Uninstall the Zen Packages
Package To Uninstall
Scripts To Execute from /usr/local/actianzen/etc, Where They Reside
Enterprise Server 64-bit
Cloud Server 64-bit
./preuninstall.sh ./postuninstall.sh
The scripts must be executed in sequence: preuninstall first, followed by postuninstall.
Client 64-bit
./clientpreuninstall.sh ./clientpostuninstall.sh
The scripts must be executed in sequence: clientpreuninstall first, followed by clientpostuninstall.
The scripts must be executed in sequence: clientaccesspreuninstall first, followed by clientaccesspostuninstall.
Note: Client Access should be uninstalled before uninstalling the 64-bit package to which it has been added.
Note Uninstalling does not remove the system databases DEFAULTDB and PERVASIVESYSDB.
Removing a Zen DMG
1 In Finder, open Applications > Actian Zen vxx and double-click Zen Uninstaller.
2 The uninstaller displays a notice about license keys remaining authorized. Do one of the following:
•Click Cancel to exit from the uninstaller if you need to manage your product keys before continuing. For more information, see License Administration Tasks in Zen User’s Guide.
or
•Click Continue.
3 When asked, enter an account name and password with administrator rights.
4 When the installer displays the dialog saying that Zen has been uninstalled, click OK.
Note Uninstalling does not remove the system databases DEFAULTDB and PERVASIVESYSDB.