• Apia 2.3.0
• Apia 2.3.1
• Apia 2.4.0

Hardware requirements to install BI:

1. Disk space:

The spaced used by BI depends on the number of cubes that are defined, how they are defined, the number od instances that exist and the number of instances that will be created per year.

The following estimate has been done based on several projects that have already used the BI: With 15 cubes defined (entity, process and/or user) if you have 100,000 instances (number of cells in the table  pro_instance) you need 2Gb on disk for the initial load.

If 10,000 instances are generated per year, disk space will increase in 512Mb every year. 

2. Memory:

BI module uses memory to load all the data in the cube, therefore, the more memory is assigned, the better the performance will be.

In order for the BI module to properly work, it is advisable to use 2Gb memory.

Alternative implementations that can improve BI's performance:

If after assigning the hardware requirements that have been advised, the BI performance is not optimum, (due to the number of users that access the system simultaneously and/or due to the number of data that each cube retrieves), that is, it is possible to install BI in a server different from Apia's (as well as the database used by it). This way, resources used by Apia and the BI are independent.

This would improve the performance, and the cost would be update both servers in each update of Apia, and also that the BI is not integrated in Apia (the access would be through another URL).

[ AHT00005 ]

Installation of Apia analytics (BI)

[ ADF01553 ]		Apia 2.4 Installation handbook
[ ADF00032 ]		Apia's 2.3 Installation handbook
[ ANF00169 ]		Dashboards and Widgets
[ AHT00167 ]		Independence of applications server for BI
[ AHT00131 ]		Installation of ApiaMonitor
[ AHT00097 ]		Install Apia's license
[ ATI01583 ]		Datasheet "Cubes design"
[ ATI01587 ]		Datasheet "Design Reports"
[ ANF00151 ]		Automatic generation of cubes from entities
[ AFC00526 ]		Run analytical queries from another server