General Operation
O3 Performance Suite offers a service of periodic and automatic loading of multidimensional models, that lets you organize the frequency of data-extraction processes from different sources for the building or updating of datamarts.
Note
This service exists within the O3 Enterprise Edition functionality. Before you start it, check your O3 licensing corresponds to this Edition.
This new O3 component enables the automatic loading of datamarts through a graphic interface where a powerful automatic execution mechanism is controlled.
Besides, thanks to the declaration of process instances, it is possible to keep a record of the loaded datamarts, establish if situations preventing the generation occurred, (unavailable database), control retrials and intervene manually to load datamarts on demand.
The settings, management and the solving of situations associated to the automatic load of datamarts are described below.
Activating datamart automatic load
To enable the datamart automatic load, it is necessary to follow these steps:
- Declare a Schedule
This is stating the frequency with which a task should be performed and it is done through a graphic interface where the administrator can create them and give them a name. - Schedule a Datamart
A schedule is associated to each datamart.
At the same time, the load parameters and multidimensional model of the datamart are indicated.
For each datamart, O3 creates an process instance responsible of activating the load tasks according to the established frequency.
This process contains the necessary logic to request the load at the right time, and to process its result. (if it was successful, if there were problems, etc.).
Datamart building is performed by a service that receives the requests, launches the update process (O3 Builder) and reports on results. This service receives requests through messages and responds in the same way, being able to define how many simultaneous buildings can be performed.
There are graphic tools that let you monitor datamart building processes and intervene manually on them to launch an immediate building.
Different events that may come up during this process are reported by mail.
There is also a set of logs that report on situations and errors during the load in greater detail.