[back to Pulse BI Wiki]
This page presents the technical details of the Pulse BI implementation. Following sections are available:
This section describes the architecture of the Pulse BI implementation. The architecture of the Pulse BI implementation consists of several components as presented in the table below:
This section describes the file system arrangement, as given in the table below:
The directory containing PulseBI configuration.
This section describes the PulseBI program. PulseBI program is responsible for loading the data warehouse configuration, generating schema scripts, and refreshing data marts as specified. The program should be executed in the following way:
PulseBI -param1 "param1 value" -param2 "param2 value" ...
The parameters to the program are given in the table below, with the default value printed in bold:
This section lists and describes the internal functions used by the Pulse BI Application, grouped by its internal use:
Overarching Functions: These 3 Parent Functions execute the requested actions based on the passed-in parameters.
Functions Below are supporting functions for things done during Generate or Refresh steps
Functions below are general purpose functions and are used by myay sub-areas.
The Pulse BI Data Warehouse is structured using the latest recommended design philosophy. It comprises Configuration, Staging and DataMart Tables and are named in a simple and straightforward way. These tables are always accessed via Views and not directly. The stucture can be sumarized as:
All Configuration Tables are named CFG_<DataDictionary_TabName>All Staging Tables are Named STG_<Dimension+FileCode>All Dimension Tables are TBL_<Dimension>All Support Views are named for the table they utilize or what they accessConfiguration Tables
Pulse BI has the following Configuration Tables:
CFG_CubeContains the data from the Cube tab of the Data DictionaryCFG_CubePartitionContains the data from the CubePartition tab of the Data DictionaryCFG_DictionaryContains the data from the Dictionary tab of the Data DictionaryCFG_DimensionContains the data from the Dimension tab of the Data DictionaryCFG_DimensionPartitionContains the data from the DimensionPartition tab of the Data DictionaryCFG_FilesContains the data from the Files tab of the Data DictionaryCFG_LookupContains the data from the Lookup tab of the Data DictionaryCFG_MartContains the data from the mart tab of the Data Dictionary
All data in these tables are loaded from the *.csv files generated by the Data Dictionary as located in \cfg\ folder.
StagingTablesPulse BI will process data in the staging table (STG_<dimension+filecode>) to its dimension table (TBL_,dimension>) via the supporting views. There will be one Table Per Dimension + FileCode in the configurationDimension TablesThese are the tables the Cubes refresh their data from and the SharePoint Dashboards build their graphs and report information from, and are named TBL_,dimension>.Support ViewsThese views allow for Friendly Column Names amongst other flexible features. They are named either the same as the Dimension minus TBL_. e.g. The Dimension of "Class" as a Dimension table named "TBL_Class" and has a view named "Class". There is also a PART_<dimension> view created for use by '-refreshdimensions yes' when a dimension is defined as partitioned (as listed in Dimension Partition tab of the Data Dictionary).
This section describes the data marts in the Pulse BI implementation.
This section describes the PowerPoint dashboards in the Pulse BI implementation.