.:- STATUM Knowledge Base -:.

Knowledge base: Apia

| Language: English

| History

My Face

Partners

Customers

Consultants

Developers

Categories

Types

Timeline

[ ANF00152 ] Detailed description of the videos of the BI

Summary

This AKI provides the user with a detailed description of the videos generated for the BI: Installation of the BI, Navigator module of the BI, Visualizer module of the BI, Administrator of views of the BI, Automatic generation of cubes by entity and Automatic generation of cubes by process.

It is applied to

Apia 2.3.0.31
Apia 2.4.0.0

Best practice

1 - BI Installation video:

The installation process of Apia analytics is similar to Apia's installation process. For that, the installer and the corresponding .zip file are required.

The installation process of Apia analytics consists of the following steps (the parameters which are requested are described in each one of the steps):

1. Origin of the installation file:

Installation source file: .zip file with the necessary files for the installation of Apia analytics.

2. Origin of Apia's configuration file:

Properties file: Corresponds to the location and name of Apia's configuration file. This file is usually located in: dir/WEB-INF/classes/properties/config.properties.

3. Parameters of data base:

Supplier of DBMS: Type of data base where the data base needed by Apia analytics will be installed.
Server (Name or IP): Name or IP of the data base server where the creation of tables needed by Apia Analytics will be done.
Port: Port where the data base server is located.
Schema: Schema/Instance on which the user will work in the data base.
User **: User with whom the user will accede to the data base.
Password: Password of the user with whom the user will accede to the data base.
BI pool Min: Minimum number of connections to the data base.
BI pool Max: Maximum number of connections to the data base.
Installation user**: User with whom the user will accede to the data base for the installation.
Password: Password of the user with whom the user will accede to the data base for the installation.
BI Max idle conections: Maximum number of inactive connections.
BI pool Max wait time: Maximum time of waiting of a connection.

The installation process has 3 stages:

1. Installation of files of Apia analytics: the installation of all the files related to Apia analytics is performed and also their configuration.

2. Creation of the structure of the data base: Apia Analytics requires a structure of data base to operate correctly. This data base can or cannot be the same that Apia uses (it is recommended that it isn't the same).

3. Updating of Apia's parameters: finally, Apia's parameters are updated so that it operates correctly with the new installation of Apia Analytics.

** The user must have licenses to be able to create tables and views.

2 - Video of the BI Navigator module:

The module BI Navigator allows the user to navigate along the cubes.

It is possible to navigate along the cubes through the utilization of the different buttons that the Toolbar contains:

Olap Navigator: Allows defining which dimensions will be displayed in the rows, which in the columns and which members will be filtered.
MDX: Allows observing the query MDX which recovers the data that the user is observing.
Config Olap Table: Allows defining the ascending descending order, together with the type (multicolumn or simple column)
Show Parent Members: Allows displaying the father members of a query in its own family or column.
Hide Spans: Allows preventing the displaying of repeated titles when multiple dimensions are nested.
Show Properties: Allows observing the properties of the levels to which some property was defined.
Suppress Missing Rows/Columns: Allows deleting rows/columns which have no value.
Swap Axes: Allows swapping axes.
Drill Member: Allows expanding all the instances of a member.
Drill Position: Allows expanding only the instance of the clicked member.
Drill Replace: Allows replacing a member with its sons.
Chart Config: Allows configuring charts.
Configure Print Settings: Allows configuring the printing.
Print to PDF: Allows generating a PDF printing according to the printing configuration.
Export to Excel: Alloes generating an Excel version of the Current view.
Admin Views: Allows managing a cube's views.

3 - Video of the BI Visualizator module:

The module BI Visualizator allows the user only to visualize a certain view, restricting in that way the navigation along the cube.

It is possible to visualize the cubes through the utilization of the different buttons that the Toolbar contains:

Show Properties: Visualiza las propiedades de un miembro de una dimensión (si posee).
Show Chart: Visualiza un gráfico para la consulta actual.
Configure Print Settings: Permite configurar la impresión.
Print to PDF: Permite generar una impresión PDF según la configuración de impresión.
Export to Excel: Permite generar una versión Excel de la vista Actual.

4 - Video of BI views management:

The management of views is carried out from the module BI Navigator. It allows the user to save, edit and/or eliminate views, as well as assign profiles to certain views in Visualizator mode. All the views generated in Navigator mode will be visible for all those users with access to the functionality BI Navigator.

Next, the possible actions from the management of views are listed:

Save the view generated by the navigation which was done, together with its properties (selected controls).
Modify an existing view. This includes name's modification, description, query, properties (controls) and/or profiles that the visualizer mode of the view has got assigned.
Add profiles for the visualizer mode of a existing view.
Set a view as initial view, this action makes the navigation or visualization functionality to be opened by default with that view. If there is no view in the cube marked as initial any of the views that the cube has got defined will be opened.
Generation of folders and modification of existing folders.
Elimination of existing views.
Elimination of existing folders.

5- Video of automatic generation of cubes by entity:

The automatic generation of cubes by entity offers the advantage that an analyst without specific knowledge about Data Warehouse can generate a cube associated to an entity and it is immediately available. The fact of having certain intuition on the different perspectives from which the user wants to analyze the entity Apia, allows handling the attributes of entity which will turn into the dimensions of the cube.

In the functionality of Design of Entities, there appears a new tab called 'Analytic queries', where the cube's configuration is performed. The points to be solved for the cube to be designed are: the dimensions, the levels, the measures, the origin of the data and their load.

Dimensions

The dimensions will be determined by the attributes that the entity possesses. The attributes which are feasible of turning into cube dimensions are those which were entered in the tab Attributes when designing the entity and the ones which belong to the entity's forms.
A cube must possess two dimensions as minimum

Levels

Only levels for the dimensions of type date will be established, that is, when the user wants that an attribute of type DATE is a dimension, the user will have the possibility of selecting which are the detail levels that he desires to observe for that dimension. The possible levels are: Year, Semester, Quarter, Month, Week day, Day, Hour, Minute and Second.

Measures

The measures are also defined taking into account the attributes of the entity and the attributes which belong to the forms of the entity.

A cube must possess at least one measure as minimum.

There are two types of measures: Common measures: this type of measure allows doing summaries, averages, countings, find minimums and maximums. Calculated measures: this type of measure allows making calculations with other measures previously defined. Both the common measures and the calculated measures have the property of being invisible, that is, a measure can be defined only to be part of the calculation of a calculated measure, and that measure won't be displayed in the cube.

Data loading

Each time a new instance of the entity is generated, a register is inserted in the table associated to the cube of the entity (automatic updating). This allows the user not to worry about the data loading to the cube, allowing to have the cube with the data always updated.

Profiles associated to the cube

When the cube is generated the profiles which will have access to the functionality BI Navigator must be associated to accede to it.

Related elements

[ ANF00129 ]		Apia analytic (BI)
[ AHT00005 ]		Installation of Apia analytics (BI)

Related from

[ ANF00129 ]		Apia analytic (BI)
[ AFC00261 ]		Available attributes in cubes' generation by entity
[ ANF00169 ]		Dashboards and Widgets
[ ATI00176 ]		Presentation of the "Administration"module