You are looking at documentation for an older release. Not what you want? See the current release documentation.
While starting the platform and having eXo Engagement Analytics add-on installed, a job is launched to make the export.
The export ends when all needed information are exported or when the end time defined in exo.properties expires.
In case of restarting the platform, the job resumes its work from the point when it stopped in the last time. In fact, the lecko service job marks every exported element: space stream or user stream.
When the export is fully done, the service will send the report file to the configured FTP in exo.properties.
After successful sending of the export file, eXo Engagement Analytics add-on service restarts its progression to delete the export file and then stops. In the next occurence, it will start a fresh export.
Monitoring
It is also possible to monitor eXo Engagement Analytics add-on via JConsole as some Mbeans are available:
buildLeckoData: This action will start the data export even if exo.addons.lecko.job.enabled
parameter is set to false in exo.properties.
It does nothing if the export is running.
stopLeckoExport: If the exoprt is running, it will stop it.
UploadLeckoData: If the export is finished, it will upload the dump file to lecko's ftp. It does nothins if the service is running.
enableLeckoJob: It is a string Mbean parameter with which you can set
exo.addons.lecko.job.enabled to true or false.
getEnableLeckoJob: It informs if jobs are activated or not.
getJobStatus: It displays information about lecko analytics jobs: the exopt folder, its status (running or not) and the completion percentage.
resetExtraction: It helps to start fresh export: it removes the dump file without sending it and cleans the database.