- We recommend installing Skedler Reports in a separate VM or Docker container or server.
- Linux Operating System with x86-64-bit architecture
- Centos version 7 and above
- Red Hat Enterprise Linux 7 and above
- Minimum of 2 CPU cores and 8 GB of RAM is recommended for deploying Skedler Reports
- CentOS/RedHat – sudo yum install libnss3.so libnssutil3.
Font config library
- CentOS/RedHat – sudo yum install fontconfig
Skedler Reports requires hostname of the server in which Skedler Reports is installed to be configured in /etc/hosts.
1. Check hostname by giving this command:
In reporting.yml the host parameter is the host in which skedler reports binds.
2. If the host is configured as 127.0.0.1 then make sure you have an entry in /etc/hosts as mentioned below,
Note: If you are binding skedler reports to localhost you can't access it from outside.
3. However. If the bind address is 0.0.0.0, that means skedler reports binds to any IP (configured for your system). In this case, your entry in the host's file(/etc/hosts) should be
4. If the host(IP address of the server) in reporting.yml is changed other than the default value 0.0.0.0 then there should be an entry for the host in /etc/hosts like
5. Reboot the system.
Note: If you are using any proxy server add your hostname to a no_proxy list in the file /etc/environment add the following line,
Elasticsearch: 5.x – 7.2.x
Kibana: 5.x – 7.2.x
Grafana: 4.x – 6.2.x
Open Distro for Elasticsearch: 0.8.0 - 0.9.0
Download the latest version of Skedler Reports from Download page.
Install Skedler Reports rpm package using the below command,
sudo yum install skedler-reports.rpm
NOTE: After the rpm package installation, if you would like to remove the Skedler Reports rpm package use the below command:
sudo rpm -r skedler-reports
The RPM package places config files, script files, and the logs directory in the appropriate locations for a RPM-based system:
|home||Skedler Reports home directory or ||/usr/share/skedler-reports|
|bin||Binary scripts to start Skedler Reports server||/usr/share/skedler-reports/bin|
|conf||Configuration file reporting.yml||/etc/skedler-reports|
|logs||Log files location.||/var/log/skedler-reports|
|Database||Embedded database to store Skedler metadata and history data||/var/lib/skedler/skedler.db and /var/lib/skedler/skedlerHistory.db|
Configure Skedler configurations like hosts configuration, admin user configuration, SSL settings and Datastore configuration in /etc/skedler-reports/reporting.yml
To edit the configuration file sudo nano /etc/skedler-reports/reporting.yml
- To automatically start Skedler Reports when the system boots up, run the following commands
sudo systemctl daemon-reload
- To start Skedler Reports, execute the command as shown below,
sudo systemctl start skedler-reports
- To stop Skedler Reports, execute the command as shown below,
sudo systemctl stop skedler-reports
Once launched, Skedler Reports can be accessed from the following URL, http://<yourServer>:3000
To configure Skedler Reports settings refer the How to configure Datasource and Notification Channel details.
You are now ready to start scheduling Reports.
Activation is required for purchased product license key. If you purchase Skedler Reports license, you will receive a license key by email.
Once Skedler has launched it operates in Enterprise trial with a validity of 21 days. Once the Enterprise trial expires, the product moves to Community Edition and operate withs by limited functionality.
Refer to Upgrade License
- Step-by-Step Guide for Offline License Activation for Skedler
- Step-by-Step Guide to Move Skedler from One Machine to Another