Page Comparison

{scrollbar}

\---\-
\\

Setting up the O3 Automatic Load includes the following facilities:
# 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.
# 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 server to use for that purpose is.
# 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 creations or updates than the hardware can support. O3 manages the creation of datamarts by means of a queue that respects the maximum number of creations defined. 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.|https://www.ideasoft.biz/wiki/pages/viewpage.action?pageId=16712926]

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. 
{note}
{note}
*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  [set up the JBoss mailer.|https://www.ideasoft.biz/wiki/display/O3PS/HowTo+configurar+el+mailer+de+JBoss]

h3.

*Step 3: Setting up the number of Builders.** *

h3.

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
{code:xml}
set PROPERTIES=%PROPERTIES% -DBuilderQueue_maxSession=10
{code}

* Unix <O3>/sh/settings.sh
{code:xml}
PROPERTIES="$PROPERTIES -DBuilderQueue_maxSession=10"
{code}

----
{scrollbar}

----
{children}