As of Jedox 6.0 SR3, it is possible to use a Jedox Integrator Server Job of type Groovy to execute a backup of all OLAP databases. Such a job can then be scheduled and triggered on a regular basis to produce a backup of each database without the need to shutdown any of the services. For every database, a separate
Having worked on couple of projects in the past with Jedox and their implementations across several institutions, I realized a patten of one task which was common across all of them was pushing back the Jedox content to the relational database for multiple purposes. May it be for archiving, backup, referencing (as client can add their own groupings, elements and more).
Some ETL tools out there use pure scripting to extract, load and transform data. Jedox has a classical ETL interface which allows you to re-use components and structure things in a modular, logical way. If scripting is the thing that you are used to, you can certainly go crazy in Jedox. There are a number of example of scripting jobs and
The Jedox Task Manager gives you key information about a job’s execution. It notifies you every time a job is run, regardless whether there were errors or not. Sometimes though, you might require a bit more sophistication in the notifications. For instance, you might only want to receive a notification when there are errors or warnings in a job. Maybe receive the
In this article we are going to discuss how an user can store a date using ETL and Groovy. In order to test the code you need to be logged in via the webinterface and make use of the ETL manager. In case of storing a date in Jedox the user has two options. Either the user stores the date