Export to PDF
eazyBI for Jira
eazyBI for Confluence
On this page:
If you would like to export reports or dashboard pages to PDF, or if you would like to send regular emails with dashboards as PDF attachments, then you need to install the headless Google Chrome browser on your Jira Server or on all nodes in Jira Data Center.
See the alternative for Windows below). eazyBI will use Google Chrome on the server to convert eazyBI web pages to PDF files.
Install Microsoft's Core Fonts
To get the best looking PDF export, eazyBI needs mscorefonts package.
Install the mscorefonts package on your server. Here is an example of how to do it on Ubuntu and RedHat.
The mscorefonts package is available in the main repository:
sudo apt-get install ttf-mscorefonts-installer
The mscorefonts package should be installed from its home page as described there.
Please run the following commands if mscorefonts package homepage instructions failed:
yum install curl xorg-x11-font-utils fontconfig rpm -i https://www.cabextract.org.uk/cabextract-1.9.1-1.i386.rpm rpm -i https://downloads.sourceforge.net/project/mscorefonts2/rpms/msttcore-fonts-installer-2.6-1.noarch.rpm
#Installing mstt fonts sudo zypper install msttcore-fonts
Install Google Chrome on the server
google-chrome-stable package on your server. Here are examples of how to do it on Ubuntu and RedHat.
For Google Chrome, there could be additional package dependencies needed to be installed.
Install from the Google Chrome repository.
wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - echo 'deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main' | sudo tee /etc/apt/sources.list.d/google-chrome.list sudo apt-get update sudo apt-get install google-chrome-stable
Enable Google YUM repository:
cat << EOF > /etc/yum.repos.d/google-chrome.repo [google-chrome] name=google-chrome - \$basearch baseurl=http://dl.google.com/linux/chrome/rpm/stable/\$basearch enabled=1 gpgcheck=1 gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub EOF
Install the package:
yum install google-chrome-stable
#Installing chrome sudo zypper addrepo http://dl.google.com/linux/chrome/rpm/stable/x86_64 Google-Chrome sudo zypper refresh wget https://dl.google.com/linux/linux_signing_key.pub sudo rpm --import linux_signing_key.pub # There could be an error about missing dependency libvulkan, proceed installation without it. sudo zypper install --no-confirm google-chrome-stable
Download and install Google Chrome for Windows. Please ensure that you have version 62 or later.
As an alternative on the Windows server, the Microsoft Edge 79 (or newer, see https://www.microsoft.com/en-us/edge) can be used instead of Google Chrome. In such a case specify the location of the msedge.exe file as described in the troubleshooting section below.
If you have your local Jira Server on macOS then also just download and install the Google Chrome for macOS. Please ensure that you have version 62 or later.
After you have installed Google Chrome please disable and re-enable eazyBI app from Jira Administration / Manage Add-ons.
During the startup, eazyBI will detect installed Google Chrome and will start to use it for PDF exports. Please visit any dashboard page and try to export it to PDF.
If you see an error message "Google Chrome is not found on the server" then you can try to specify the path to it manually via advanced settings:
[google_chrome] location = '/usr/bin/google-chrome'
If you have any problems with PDF export after Google Chrome is installed then check:
- System Administration / System Events page and see if you have any errors there.
eazybi-web.logfile from the Troubleshooting page.
Please download eazyBI log files from the Troubleshooting page and send them to eazyBI support if you need help with solving PDF export problems.
If you see an error message
Unable to connect [localhost:9250] then it probably means that Google Chrome failed to start.
- It could fail to start if you are trying to start the process using user root, try to use a different user.
- It could fail to start if you are using docker, then you can override the default security profile with
--security-opt seccomp=unconfinedplease check Docker docs for more information on security profiles.