Technical References

1-64
Cisco Prime Service Catalog 10.0 Reporting Guide
OL-31037-01
Chapter 1 Advanced Reporting Data Mart
Data Mart Administration
Select Data from the Transactional Database
Select new or changed data from the OLTP database, based on extraction views which include the
columns required in the data mart and which filter by comparing the time stamps in the source data to
the date and time the ETL process was last run.
Insert Incremental Data into Staging Area Tables
Staging tables in the OLAP database (indicated by the prefix STG) temporarily hold the new/changed
data from the OLTP database. Staging tables have one to one correspondence with OLTP tables. These
tables are truncated on every run of ETL so they contain only new/ modified data.
Construct Work Area Tables
Work area tables in the OLAP database (indicated by the prefix WRK) hold data extracted and
consolidate it from previous ETL runs. Work area tables are used only for transforming data for
dimensions whose data is derived from multiple tables in the transactional database. The mapping of
source to target tables is given in the Advanced Reporting Module, page 1-16.
Load Data in to the Dimension/Fact Tables
The ETL uses both staging and work tables to insert new/modified data into the appropriate
dimensions/fact tables in the datamart. Business views are created on top these tables and these views
are exposed as query subjects in the package.
Customizing the Data Mart
Service Catalog includes only runtime licenses for the Framework Manager and Data Manager tools
used to populate the data mart. Service Catalog users who have Cognos enterprise development licenses
may wish to customize the data mart contents, including additional client-specific data.
The key to a successful customization is taking into account that the business view of the data,
configured via Framework Manager, includes both a static and dynamic component. The static
component, specifying the universal facts and dimension, is stored in the file
<App_Home>\cognos\Reports\CustomReportsDataModel\ CustomReportsDataModel.cpf
on the reporting server. The ETL uses that file as the basis for the business view, then generates
additional DictionaryData and ServiceData dimensions, depending on which objects have been marked
as reportable. Client customizations to the static component may be applied using IBM Cognos
Framework Manager. Any such customizations are incorporated into the new business view, generated
via the next ETL cycle. Such customizations will have to be reapplied after any application upgrade.