See also Jedox Supervision Server (SVS)
Drilldown: Expenditure of a consolidated figure along the hierarchy definition to see additional details of the subsequent level (the children of the consolidated element). The opposite of this term is “Roll up”.
Drillthrough: Expenditure of a figure by querying another data source providing more details than the initially used data source.
The required files for both processes contain the phrase “drill through” in their names. Therefore you cannot deduce the running process from the file name. The same applies for the context menu command “drill-through”.
If you have not checked “Enable DrillDown” during installation and you want to enable “Drill Through/DrillDown” later, you have to execute the following steps:
- Change the entry of the file <Install_path>svs\sep.inc.php to:
- Add the following 3 lines to the palo.ini configuration:
Line 1 on Windows OS: worker “<install_path>\svs\SupervisionServer.exe”
Line 1 on 32-bit Linux OS : worker /svs-Linux-XXXX/SupervisionServer.exe (replace XXXX with i386, i486, i586 or i686 – see your svs directory name)
Line 1 on 64-bit Linux OS: worker /svs-Linux-x86_64/SupervisionServer.exe
Line 2 on Windows and Linux: workerlogin information
Line 3 on Windows and Linux: enable-drillthrough
The workerlogin entry is required when configuring the drillthrough functionality. The JedoxSuiteMolapService must be restarted after the changes.
Drillthrough and Drilldown functionality both fetch and process potentially large datasets, which raise the RAM usage of the Supervision Server process. The amount of RAM which Supervision Server is allowed to consume is limited to prevent exhaustion of the system’s ressources. It is recommended practice to include size limitations in drillthrough scripts, and prevent fetching of data if these size limits are surpassed. If necessary, the memory limit of Supervision Server can be increased by modifying the “memory_limit” parameter in the php.ini configuration file of Supervision Server.
Note that if SVS reaches the memory limit, this represents a fatal error. Execution of the script is then interrupted. Fatal errors in the PHP interpreter used by SVS are not recoverable, and the OLAP Server is shut down.
The standard sample sep.inc.drill_through.php that is installed with Setup (with checkmark “Enable DrillDown”) does drill down to base cells of the cube. This works for every cube, and Jedox Integrator (ETL) is not required. In SVS script, you can configure the maximum number of rows that are returned.
Note: OLAP drilldown is performed with full access rights, so a user running drilldown (using the context menu command “drillthrough”) will see all base cell data, even for elements for which this user doesn’t have access rights.
For the following example you will need Jedox Web and Jedox Excel Add-in:
Start Jedox Web and open the Integration Manager. Import the project <install_path>\tomcat\webapps\etlserver\data\samples\sampleDrillthrough.xml. Before you can start the sampleDrillthrough, you must run the jobs of the sampleBiker “Initdata” and “default” in this order to create the necessary dimensions.
Next, execute the job “DrillthroughPersist” for the newly loaded project. This job will create the new Jedox database Biker_ETL with the cube Order2. The Order2 cube has drilldown functionality.
Afterwards, open the file <install_path>\svs\sample_scripts\sample_drill_through.xls. In this file you will find a view of the new database Biker_ETL. Then, right-click on the shown cell and choose “Drill Through” from the context menu. A new Excel worksheet will open, displaying the detailed source data for the cell you have selected.
Note: the example importBikerDrillthrough only covers a certain slice of the cube Biker_ETL; not all cells in this cube will have drilldown data.
If you want to use drillthrough to get detailed Jedox Integrator (ETL) data, you must use the script “sep.inc.drill_through_etl.php” instead of “sep.inc.drill_through.php”.
In the file <install_path>\svs\sample_scripts\ sep.inc.drill_through_etl.php you will find the following Jedox Integrator configuration lines:
$server = @new SoapClient("http://localhost:7775/etlserver/services/ETL-Server?wsdl", array('exceptions' => true));
When “JedoxSuiteTomcatService” for your Jedox Web instance is running, you can test the right configuration of your Jedox Integrator by entering the URL http://localhost:7775/etlserver/services/ETL-Server?wsdl in your browser. If your browser returns “ETL Server” or an XML file with Jedox Integrator details, then the configuration is correct.