Setting up Datamart Load

Owned by Nicolás Palombo (Unlicensed)
Last updated: 27 Oct, 2008Version comment
2 min read
Unknown macro: {scrollbar}

Setting up the O3 Automatic Load includes the following steps:

  1. Activating the use of the database as a repository of O3 Server Configuration.
    This lets you save and manage all information about Multidimensional Models and Datamarts on a Relational Database.
  2. Several Administrator-geared reports that reflect the progress made or problems arising during the Building Process are sent by mail.
    That's why it is necessary to let O3 know which the email server to use for that purpose is.
  3. You may set up the maximum number of datamarts that can be built simultaneously.
    This maximum acts as a control tool to prevent more simultaneous processes than those supported by the hardware.
    O3 manages these automatic updates through the use of a queue.
    This mechanism relieves administrators from the task of accurately programming the launch time of an update process, as O3 does the fine scheduling respecting the maximum number of simultaneous creations by means of queues.

Step 1: Enabling the DB to set up the O3 Server

This activation is made through the Setup and Migration Wizard

To be more precise, in step 3, you may enable the use of the Database for this purpose or not.

This step is required in order to be able to use the datamarts automatic update functionality and must be performed before loading the server.

Step 2: Setting up the sending of emails

The datamart update process includes the following notifications: 

  • Sucessful building notification.
  • Failed Building notification

These messages will be sent to the users in the CubeBuilders role.

In order to set up the email service O3 uses, it is necessary to configure JBoss mailer

Step 3: Setting up the number of Builders

In order to control the maximum number of simultaneous datamarts that can be built, a system property called BuilderQueue_maxSession must be added.

O3 default settings are for a maximum of 3 simultaneous buildings. If this value is the right one for your hardware's, then it is not necessary to change the following settings.

  • Windows <O3>\bat\settings.bat 
    set PROPERTIES=%PROPERTIES% -DBuilderQueue_maxSession=10
  • Unix <O3>/sh/settings.sh 
    PROPERTIES="$PROPERTIES -DBuilderQueue_maxSession=10"
Unknown macro: {scrollbar}