Installation Instructions
Last updated
Last updated
Download the plugin
Extract the contents of the .zip folder to the directory: /opt/sisense/storage/plugins/
Alternatively, you can navigate to the plugins directory by using the “File Management” option under “System Management” in the Admin tab
Go to Admin > Add-ons
Wait for the plugins build to finish:
Wait until you get this message to refresh the plugins:
Verify that the plugin is listed in the Add-ons list
When you need to restart a plugin in case of errors:
Go to Admin > Add-ons
Find the relevant plugin and disable it
Wait for the plugins build to finish:
Wait until you get this message to refresh the plugins:
After the page is refreshed do the above steps again to enable the plugin.
After the plugins build is finished go back to the dashboard that had the error and refresh it.
If the issue persists or if the plugin is not showing or updating properly - let us know and we will assist you
NOTE: please make sure that the Paldi Components plugin is installed as it holds our code framework that serves all our plugins and therefore is a prerequisite to all our plugins.
For any further help, please send an email to support@paldi.solutions
Edit the plugins pod
Open the terminal and type in:
Go down to resources section and modify the below entries:
Limits > cpu: 1500m
Limits > memory: 4000Mi
Requests > cpu: 1500m
Requests > memory: 500Mi
The image below illustrates how pod resources should eventually look:
Values explanation:
Memory values are set in Mi (1000Mi ~= 1GB)
CPU values are set in m units (1m = 1/1000 of processor time)
Save your changes by doing the following:
Press ESC
type :wq
Preset ENTER
Restart the plugins pod
In the terminal, type in:
Navigate to Admin tab
Open the Add-ons page
Keep the Add-ons page open until the end of this process
This is very important - When you have the Add-ons page open in a separate tab, you can actually see when the build process starts and finishes.
In general, when making changes to the plugins or to the plugins service/configuration, always keep the Add-ons page open in a separate browser tab.
Open a new browser tab and navigate to Admin tab again
Open the System Management
Open the Configuration
Click 5 times on the Sisense logo (or your brand logo)
When the left navigation is loaded, scroll down and open Plugins-Service
Change the plugins.maxBuildTime to 300000 (5 minutes)
Click on Save Changes
Click OK to continue, apply the changes and restart the service
Go to the Add-on page
The build should start automatically after several seconds
Now you have the recommended settings for plugins.
5 minutes is enough for the plugins build to complete on 99% of the servers.
Note:
In addition to the fact that 300000 (5 minutes) is the recommended setting, because the default 60000 (1 minutes) is often not enough and is causing the service to be stuck, this setting can be used to restart the service that was stuck for any reason.
Making any small changes to this number (for example 300000 -> 320000) will restart the service and revive it. This is very useful when you don’t have an actual root admin access to the Linux server itself (which is the case on most Cloud deployments).
Download the plugin
Extract the contents of the .zip folder to the directory: /opt/sisense/storage/plugins/
Alternatively, you can navigate to the plugins directory by using the “File Management” option under “System Management” in the Admin tab
Go to Admin > Add-ons
Wait for the plugins build to finish:
Wait until you get this message to refresh the plugins:
Verify that the plugin is listed in the Add-ons list
When you need to restart a plugin in case of errors:
Go to Admin > Add-ons
Find the relevant plugin and disable it
Wait for the plugins build to finish:
Wait until you get this message to refresh the plugins:
After the page is refreshed do the above steps again to enable the plugin.
After the plugins build is finished go back to the dashboard that had the error and refresh it.
If the issue persists or if the plugin is not showing or updating properly - let us know and we will assist you
NOTE: please make sure that the Paldi Components plugin is installed as it holds our code framework that serves all our plugins and therefore is a prerequisite to all our plugins.
For any further help, please send an email to support@paldi.solutions
Edit the file C:\Program Files\Sisense\app\plugins-service\src\features\plugins\plugins.config.js (The editor should be open as an Admin to be able to save)
Change the last number in the maxBuildTime entry from 60000 to 300000.
Save the file
Restart the Sisense.Plugins service (Task Manager -> Services Tab -> Search for the relevant service)
Download the plugin
Extract the contents of the .zip folder to the directory: C:/program files/sisense/app/plugins
Go to Admin > Add-ons
Wait for the plugins build to finish:
Wait until you get this message to refresh the plugins:
Verify that the add-on is listed in the Add-ons list
When you need to restart a plugin in case of errors:
Go to Admin > Add-ons
Find the relevant plugin and disable it
Wait for the plugins build to finish:
Wait until you get this message to refresh the plugins:
After the page is refreshed do the above steps again to enable the plugin.
After the plugins build is finished go back to the dashboard that had the error and refresh it.
If the issue persists or if the plugin is not showing or updating properly:
Log in to the Sisense server with RDP
Restart the Sisense.Plugins
Go back to the Add-ons page in the website and wait for the build to finish and get the refresh pop-up message.
NOTE: please make sure that the Paldi Components plugin is installed as it holds our code framework that serves all our plugins and therefore is a prerequisite to all our plugins.
For any further help, please send an email to support@paldi.solutions
