2
.. i18n: Configuration Interface
3
.. i18n: =======================
6
Configuration Interface
7
=======================
9
.. i18n: The main goal of any user connecting to OpenObject BI is to fetch the data from database using the powerful MDX queries.
12
The main goal of any user connecting to OpenObject BI is to fetch the data from database using the powerful MDX queries.
14
.. i18n: To run any MDX Query there is a need to make a cube and the user can define / configure its own custom cube using two interface :
17
To run any MDX Query there is a need to make a cube and the user can define / configure its own custom cube using two interface :
19
.. i18n: .. _schema_configuration-link:
22
.. i18n: ----------------------------------
25
.. _schema_configuration-link:
28
----------------------------------
30
.. i18n: Designer by default displays all schema in the tree form and provide options for adding the new.:
33
Designer by default displays all schema in the tree form and provide options for adding the new.:
35
.. i18n: .. image:: images/1.png
39
.. image:: images/1.png
47
.. i18n: Creating the Schema : Schema defines the database from where the data is to be fetched. It gives a meaning ful name to the database connection.:
50
Creating the Schema : Schema defines the database from where the data is to be fetched. It gives a meaning ful name to the database connection.:
52
.. i18n: .. image:: images/2.png
58
.. i18n: Database Connection specified the paramaters for connecting to the database. It generally includes type of the database (postgres,oracle,mysql), username, password , database to use.:
61
.. image:: images/2.png
67
Database Connection specified the paramaters for connecting to the database. It generally includes type of the database (postgres,oracle,mysql), username, password , database to use.:
69
.. i18n: .. image:: images/3.png
75
.. image:: images/3.png
80
.. i18n: Once we configure the database connection the next step is to load the database using introspection. This will load the structure of the database. by structure we mean tables, columns and the relations. This will help in defining cube easily. As the structure is loaded their will be no query to the database again and again:
83
Once we configure the database connection the next step is to load the database using introspection. This will load the structure of the database. by structure we mean tables, columns and the relations. This will help in defining cube easily. As the structure is loaded their will be no query to the database again and again:
85
.. i18n: .. image:: images/4.png
91
.. image:: images/4.png
96
.. i18n: The next step is to configure the database loaded. This is useful to hide unnecessary table and columns. If database is of openerp it can be auto configured:
99
The next step is to configure the database loaded. This is useful to hide unnecessary table and columns. If database is of openerp it can be auto configured:
101
.. i18n: .. image:: images/4a.png
107
.. i18n: Once the cube schema is created we can go for creating the cube:
110
.. image:: images/4a.png
116
Once the cube schema is created we can go for creating the cube:
118
.. i18n: .. image:: images/5.png
124
.. i18n: Cube is the structure that is based on the schema (database), It will configure the way to retrieve the data:
127
.. image:: images/5.png
133
Cube is the structure that is based on the schema (database), It will configure the way to retrieve the data:
135
.. i18n: .. image:: images/6.png
141
.. image:: images/6.png
146
.. i18n: Cube requires the fact table to be define. Fact table are the key tables in which measures are stored and we can branch to other tables for other parameters. For example for sales we can define sale_order as our fact table as it will gives the details of the sales. Fact table can be join of tables.
147
.. i18n: The fact table is given meaningful name:
150
Cube requires the fact table to be define. Fact table are the key tables in which measures are stored and we can branch to other tables for other parameters. For example for sales we can define sale_order as our fact table as it will gives the details of the sales. Fact table can be join of tables.
151
The fact table is given meaningful name:
153
.. i18n: .. image:: images/7.png
159
.. i18n: And the cube screen will be
162
.. image:: images/7.png
168
And the cube screen will be
170
.. i18n: .. image:: images/8.png
176
.. image:: images/8.png
181
.. i18n: After cube we can decide upon the dimensions to be used for the cube. For example we want to look on products sold , Dates, City etc.. to analyis the sales accordingly.
182
.. i18n: We decide what are the measures to be used. For example items sold. So we can decide the dimension and measures:
185
After cube we can decide upon the dimensions to be used for the cube. For example we want to look on products sold , Dates, City etc.. to analyis the sales accordingly.
186
We decide what are the measures to be used. For example items sold. So we can decide the dimension and measures:
188
.. i18n: .. image:: images/9.png
194
.. image:: images/9.png
199
.. i18n: Adding the dimension Products. So we will be able to see product wise item sold:
202
Adding the dimension Products. So we will be able to see product wise item sold:
204
.. i18n: .. image:: images/10.png
208
.. image:: images/10.png
211
.. i18n: After dimension we explain how to get the prodcuts details in the hierarchy. It requires to configure the fact table:
214
After dimension we explain how to get the prodcuts details in the hierarchy. It requires to configure the fact table:
216
.. i18n: .. image:: images/12.png
222
.. image:: images/12.png
227
.. i18n: After adding the hierarchy we decide from which field the product name will come:
230
After adding the hierarchy we decide from which field the product name will come:
232
.. i18n: .. image:: images/14.png
238
.. image:: images/14.png
243
.. i18n: The fully configured cube tree will look like:
246
The fully configured cube tree will look like:
248
.. i18n: .. image:: images/15.png
252
.. image:: images/15.png
255
.. i18n: Connecting to an Existing Database
256
.. i18n: ----------------------------------
259
Connecting to an Existing Database
260
----------------------------------
262
.. i18n: One can very easily connect to the existing database. The details requiered are
265
One can very easily connect to the existing database. The details requiered are
267
.. i18n: #. Fact Name : Logical Name of the database
269
.. i18n: #. Database Name: Pyhsical Database name to be used
271
.. i18n: #. Database type : Type of the database it can be PostgreSQL, MySQL, Oracle etc.
273
.. i18n: #. Connection type : Port or Socket
275
.. i18n: #. Database Host : Server name like localhost
277
.. i18n: #. Database Port : Port to be used for making connection to the database
279
.. i18n: #. Database Login: Login name for accessing a database
281
.. i18n: #. Database Password:Password for the user in login
284
#. Fact Name : Logical Name of the database
286
#. Database Name: Pyhsical Database name to be used
288
#. Database type : Type of the database it can be PostgreSQL, MySQL, Oracle etc.
290
#. Connection type : Port or Socket
292
#. Database Host : Server name like localhost
294
#. Database Port : Port to be used for making connection to the database
296
#. Database Login: Login name for accessing a database
298
#. Database Password:Password for the user in login
305
.. i18n: Giving this detail will generate a string like ''postgres://postgres:postgres@localhost:5432/terp''
308
Giving this detail will generate a string like ''postgres://postgres:postgres@localhost:5432/terp''
315
.. i18n: Strings so generated is a connection string for making connection to the database.
318
Strings so generated is a connection string for making connection to the database.
320
.. i18n: Writing a Schema
321
.. i18n: ----------------
327
.. i18n: .. describe:: What is Schema ?
330
.. describe:: What is Schema ?
332
.. i18n: Schema in general means shape or more generally plan . In the context of OpenObject BI it defines the logical model, consisting of cubes, hierarchies, and members, and a mapping of this model onto a physical model.
335
Schema in general means shape or more generally plan . In the context of OpenObject BI it defines the logical model, consisting of cubes, hierarchies, and members, and a mapping of this model onto a physical model.
337
.. i18n: The logical model consists of the constructs used to write queries in MDX language: cubes, dimensions, hierarchies, levels, and members.
340
The logical model consists of the constructs used to write queries in MDX language: cubes, dimensions, hierarchies, levels, and members.
342
.. i18n: The physical model is the source of the data which is presented through the logical model. It is typically a star schema, which is a set of tables in a relational database; later, we shall see examples of other kinds of mappings.
345
The physical model is the source of the data which is presented through the logical model. It is typically a star schema, which is a set of tables in a relational database; later, we shall see examples of other kinds of mappings.
347
.. i18n: Making Schema
348
.. i18n: +++++++++++++
354
.. i18n: In OpenObject BI schemas are represented in a XML file. It can be designed in the way OpenERP does. The details of XML file can be seen at *Creating XML*
357
In OpenObject BI schemas are represented in a XML file. It can be designed in the way OpenERP does. The details of XML file can be seen at *Creating XML*