You can host Ragic on your own servers if necessary, provided that your organization has the ability to maintain your own servers. We strongly recommend companies only use on-premise servers if they have an experienced IT crew who understands how to maintain and keep a server safe and secure.
There is no additional cost for the on-premises option, but there is a 10 users minimum and your plan will need to be paid annually. For detailed information, please refer to pricing page.
JAVA_HOME: the path where JDK 8 is located
RAGIC_HOME: the path where Ragic is located
On the Windows taskbar, right-click the Windows icon and select System. In the Settings window, under Related Settings, click Advanced system settings and hit Environment Variables to create a new one.
If you don’t want to edit the environment variable, you can also just edit ragic.sh (Linux) or ragic.bat (Windows) to add lines like these:
You can also change the lines with JAVA_OPTS="-Xms1g -Xmx1g to tell your server how much memory Ragic can consume. 1g will mean that it takes up 1 GB of memory. If you set it to JAVA_OPTS="-Xms10g -Xmx10g it will give Ragic 10 GB of memory. You should not give Ragic more than 70% of physical memory available on the server, since there will be memory needed for the OS to function properly, and there is still some off-heap memory needed for Ragic to run.
For Windows, find the directory bin folder under your Ragic directory and type ./ragic_dbv7.bat start
For Linux, type ./bin/ragic_dbv7.sh manual
On Linux, you can add nohup so that the process will not end as your user exits the session, or add it to the system services. Also notice that on Linux you will need to use root privilege or sudo to execute the service so that Ragic can be bound to port 80. On Windows, you will need sufficient privileges too to bound to port 80.
When starting or restarting Ragic, you should always make sure there’s only one instance of Ragic running. The easiest way to check is using your browser to connect to your Ragic URL and make sure it’s currently not running. On Linux, you can also use the command ps aux | grep java to check if there’s any java process running already. On Windows, you can go to the process monitor to see if there’s any Java process running. You will need to kill all Ragic Java processes before you start Ragic or running multiple instances of Ragic will result in an error (although sometimes not immediately noticeable).
This is the screen that you should see when you have successfully setup your Ragic Server:
8888 is an available port for us.
Now we are going to install nodeJs, you could get the installation file from here.
If you are on windows:
(1) Double click the installation file.
(2) Open the cmd and type node -v to see if it was installed successfully.
If you are on Linux:
(1) sudo apt-get install build-essential checkinstall
(2) sudo apt-get install libssl-dev
(3) Added these lib for launching on Ubuntu.
sudo apt-get install gconf-service libasound2 libatk1.0-0 libatk-bridge2.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget
(4) Install nvm curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.34.0/install.sh | bash
(5) Set the path. export NVM_DIR="$DIR_WHERE_YOU_INSTALL_NVM/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
(6) Type nvm --help to see if it was installed successfully.
(7) Now we could install nodeJs by nvm. nvm install 10.15.1
(8) Type node -v. If you got a number different with 10.15.1, please type nvm use 10.15.1
After installing nodeJs, we have to install a nodeJs module named Puppeteer.
These steps are the same for all os:
(1) Go to $YOUR_RAGIC_ROOT_DIR/web/sims/js/pdfMaker and type npm i firstname.lastname@example.org
(2) Go to $YOUR_RAGIC_ROOT_DIR and type node web/sims/js/pdfMaker/nodeJs $YOUR_PORT
$YOUR_PORT was the port you set in configuration before.
Start: sudo nohup ./bin/ragic.sh manual
Stop: sudo pkill -f RagicJetty9Server
Please note that it's not recommended to force stop the service, unless it's necessary.
Make sure you make a backup of everything in your Ragic directory before you do any upgrading! You will need to log in to Ragic before you download any of the following patch or full version.
After the download is finished, you will need to upload the file to your server through the page below.
You can also update license through the page if you need.
When you finish setting up your server, remember to go to the private server config, and put your server domain name in the SERVER_NAME property, so that the e-mail sent will contain the correct URL. Also remember any changes to the private server configuration will require a Ragic service restart.
By default, Ragic On-premises uses one of our mail server to send out e-mails. For the Ragic server to send out e-mail using your specified e-mail server, you will need to set up the following SMTP / SMTPS configurations in the “Private Server Config” so that Ragic can use your mail server to send out e-mails. Remember to restart your Ragic service after changing any configurations:
SMTP_SERVER=The SMTP / SMTPS server domain name / IP
SMTP_SENDER_AUTH_USER=User name used to log in to SMTP
SMTP_SENDER_AUTH_PWD=Password used to log in to SMTP
SMTP_SSL_ENABLE=For SMTPS put true, SMTP put false
SMTP_PORT=Port to connect to your SMTP service
SMTP_SSL_PORT=Port to connect to your SMTPS service
SMTP_SENDER_PERSONAL=The name used when Ragic sends out an e-mail
SMTP_SENDER_EMAIL=The reply to address used when Ragic sends out an e-mail
Firewall settings contain inbound connections and outbound connections. If you would like Ragic to be accessible, you would need to open inbound port 80 / 443. On the other hand, if you would like Ragic to access PDF servers, you would need to open outbound port 80.
To update your license files, just go to the private server configuration page, upload your license file, and restart your Ragic service. If your service has already expired, you can also copy your two license files (license.xml and sig) into the cust folder in your Ragic directory, and restart your Ragic service.
To upgrade your Ragic server, download the latest patch of Ragic from https://www.ragic.com/sims/download.jsp and go to the private server config page and find the server update section at the bottom of the page and upload the patch file.
A Ragic service restart is necessary after an update, and a restart link will appear for you to restart your Ragic service. On Linux servers (including QNAP and Synology servers, they are Linux based), you can use the restart link to restart your Ragic service, but on Windows servers, you will need to kill the Java process started by Ragic and manually restart it.
In some cases, we will suggest you do a full update. Then you will need to download a full version of Ragic.
You will need to make changes to the .sh or .bat files in the bin directory again if you have done any modifications to them. So make sure you have a backup of your old .sh or .bat file before you replace it.
You will also need to stop the server before the update and restart the server after the update.
You can download "Ragic On-premises account setup forms patch" and unzip the file. In the "ragic-setup" folder, please copy those .nui files and paste them to the "ragic-setup" folder under your installation path. Then, access any of the system sheets and press the reload button to update.
Note: please do not rename the "ragic-setup" folder. Otherwise, the system may not work as expected.
You can have daily auto backup by adding the following configurations.
DISTR_DBBACKUP_PATH=The directory to store backup (ex : D:/MyBackUp/ )
DISTR_PRESERVED_NUM=The number of backup you want to preserve (ex: 5 )
Remember any changes to the private server configuration will require a Ragic service restart.
Or you can use your own backup software or script to create the backup, all you need to do is to copy the Ragic directory to another location, and it will contain all the necessary files and data to restore Ragic to a previous state.
For Linux servers, you can simply write a cron job and run rsync to periodically sync all your files to another backup server.
You can simply use the backup restore tool to restore a backup that you downloaded from your Ragic account online. But note that because the users in your backup are not actually registered on your on-premises version. After you restore your backup, you will need to edit and resave each user so that they are added to your server, and reset their password to a new default password.
• Ubuntu Linux 10.04 and above (64-bit)
• Red Hat Enterprise 6.x and above (64-bit)
• Suse Linux Enterprise Server 10 SP2, 11.x and above (64-bit)
• Oracle Linux 6.x and above (64-bit)
• RAM: over 8GB
• Disk space: over 200GB
• Windows 7 or later (64-bit)
• Windows Server 2012 or later (64-bit)
• RAM: over 8GB
• Disk space: over 200GB
Mac OS X：
• Intel-based Mac running Mac OS X 10.7.3 (Lion) or later. (64-bit)
• Administrator privileges for installation
• RAM: over 8GB
• Disk space: over 200GB