PrizmDoc v13.0 - Updated
Linux Installation
Get Started with PrizmDoc > 2 - Set up a Back-end > Install PrizmDoc Server > Install on Linux > Linux Installation

PrizmDoc installation is designed to be very straightforward for Linux environments. Follow the steps provided in this section.

PrizmDoc requires a clean installation when migrating from a version earlier than v12.0. You must first uninstall any previous versions of PrizmDoc and reboot your system. Only then should you install PrizmDoc v12.0 or later. Make sure you back up your configuration files before uninstalling any previous versions of PrizmDoc. Once you have installed v12.0, you do not need to uninstall if you want to migrate to v12.1 or later.
PrizmDoc relies on a fontconfig package that is not shipped with the product and that might be missing from some distributions of Ubuntu. This was resolved by adding automated checks in the PrizmDoc 13.0 installation scripts. As a workaround for older versions of PrizmDoc, we recommend installing the fontconfig package manually by using sudo apt-get install fontconfig.

Some steps may be specific to a particular Linux distribution; these steps will be labeled as being specific to one of the following: 

Make sure you log in as root to the machine.


Verify the System's Locale

  1. To ensure your system's locale is specified, run the command:
Copy Code
  1. If the LC_ALL entry is not set, you must specify it with the following:
Copy Code
export LC_ALL="en_US.UTF-8"
sudo locale-gen


Step 1 - Download PrizmDoc Server

Before you download PrizmDoc, note that packages are only available for 64-bit systems.

Before downloading PrizmDoc, you will need to purchase a license key or request a Trial Evaluation by filling out the following form:

Once you have purchased a license key or filled out the form for a Trial Evaluation, you can download PrizmDoc by:

  1. Following the link provided in the response email and selecting the desired Linux Distribution.


  1. Downloading directly to the Linux server using the 'wget' command for the specific distribution as shown below:
You must substitute the version of the package you are using in the code examples below. For example, if you are using v11.0, then specify "11.0" instead of "<version>". If the version is a hot fix, you will need to also specify the hot fix number, for example, "11.0.1".

Red Hat Enterprise Linux, CentOS (prior to v7) and Similar Older Linux Distributions

Copy Code

Red Hat Enterprise Linux and CentOS v7 (and later)

Copy Code

Ubuntu Linux Distributions

Copy Code

Generic .tar.gz Distribution

Copy Code

For license questions, fill out the form at  


Step 2 - Unpack & Install the Downloaded Archive

Open a command line and change to the location where you downloaded the tarball. Use the following command line examples appropriate for your distribution to:

  1. Decompress and unpack the downloaded file. After you have unpacked the archive, the contents will have been decompressed into a directory named prizmdoc_server_<version>.<arch>[.rpm|.deb]
  2. Change to the unpacked directory and install the packages.

Red Hat, Fedora, CentOS, and Older Linux Distributions

The following example is for Red Hat, Fedora, CentOS, and older Linux distributions:

Copy Code
tar -xzvf prizmdoc_server_*.rpm.tar.gz
cd prizmdoc_server_*.rpm
yum install --nogpgcheck *.rpm

Ubuntu Linux Distributions

The following example is for Ubuntu Linux distributions:

Copy Code
# Note for Ubuntu 16.04: PrizmDoc requires additional packages to be installed on
# Ubuntu 16.04. Run the following command to install them before installing PrizmDoc.
# sudo dpkg -i packages/*.deb
tar -xzvf prizmdoc_server_*.deb.tar.gz
cd prizmdoc_server_*.deb
sudo dpkg -i *.deb
# 'dpkg' does not resolve dependencies automatically, so please ignore possible errors, if there are errors about missing dependencies, invoke next command to install dependencies and complete configuration of the packages.
sudo apt-get -f install

Generic .tar.gz Distribution

We also provide a generic .tar.gz package. Please review the System Requirements and Supported Environments topic to ensure compatibility. You will also need to install the dependencies described in the Requirements section. Once the dependencies are installed, you can install the .tar.gz with the following commands as root:

Copy Code
tar -xzvf prizmdoc_server_*.tar.gz
cd prizmdoc_server_*
ls prizm-*.tar.gz | xargs -n1 tar zxf
cp -R prizm /usr/share/

Add symbolic links to the fonts directory and update system fonts cache to enable the usage of installed fonts by PrizmDoc services.

Copy Code
ln -s /usr/share/prizm/modules/poppler/fonts/accusoft_prizm_fonts.conf /etc/fonts/conf.d/99-accusoft_prizm_fonts.conf
fc-cache -f


Step 3 - Configure

  1. Continuing as root, change to the installation location: /usr/share/prizm and run This will run the Prizm Licensing Utility (PLU) and configure PrizmDoc for its first run: launches the Prizm License Utility (PLU), which is a GUI application. Depending on how you have X11 configured, you might need to run 'xhost +' as the logged in user to allow the PLU launched by the root user to access X11. You can disable X11 access for root by executing 'xhost -' when you are done.

Copy Code
Select the type of license you want to acquire:
                1) Evaluation [e]
                2) Deployment [d]
            Choose 1 or 2: d
            Select the type of deployment license you have:
                1) Node Locked [n]
                2) OEM         [o]
            Choose 1 or 2: o
            Provide the solution name: <MySolutionName>
            Provide the OEM license key provided to you: 2.0...
            Your deployment license was acquired successfully.
            ./scripts/ start
            Starting Prizm Content Connect Information Services...
            Starting PCCIS Watchdog process...
            PCCIS Watchdog has been started correctly. 
  1. For a production installation, you will want to configure where log files are stored. See the section How to Configure Log File Locations.  
  2. If you are licensed to use the Microsoft Office Conversion add-on for PrizmDoc Servers running on Linux, you need to configure your server as described in the topic: Configure Microsoft Office Conversion Connectivity


Step 4 - Verify that the Installation was Successful   

  1. Open the PrizmDoc Services Status Page as described in the Checking PrizmDoc Server Health topic and verify the PrizmDoc Services are running.
  1. Your installation is now complete.


Working with Sample Code

Sample code is included to demonstrate how PrizmDoc can be integrated into your Content Management solution. Sample applications using different languages are packaged with the product to demonstrate using a particular language. All of the product samples are located in the "Samples" folder within the installation directory. For more information, refer to the Code Samples topic.


How to Install Common Certificate Authority Root Certificates on Linux

The following commands should all be run as root. Additionally, if prompted for addition/removal permission, then yes/no should be entered as the response.

  1. Install all Mozilla's root certificates. This command will install all the root certificates Mozilla accepts, prompting only to remove certificates that Mozilla doesn't list, adding all it does trust without prompt. This should make HTTPS work for any system that Firefox works with:
Copy Code
/usr/share/prizm/mono/64/bin/mozroots --machine --import --ask-remove
  1. Pull certificates from an https connection to accept:
Copy Code
/usr/share/prizm/mono/64/bin/certmgr -ssl -m https://servertoadd/

As long as the server includes the entire chain to root, this will allow the certificate to authenticate. This will generally be the case for self-signed test certificates. For more complex situations, any required items from the chain will need to be added manually.

  1. Manually add the certificate from the file:
Copy Code
/usr/share/prizm/mono/64/bin/certmgr -add -c -m /path/to/certificatefile

The certificate stores the certificates at: /usr/share/.mono/certs/.