Manualshelf

Technical References

ManualsBrandsCisco ManualsCloud and Systems ManagementCisco Prime Service Catalog 10.0
71727374757677787980
1-63
Cisco Prime Service Catalog 10.0 Reporting Guide
OL-31037-01
Chapter 1 Advanced Reporting Data Mart
Data Mart Administration
Figure 1-3 CUSTOM Reports Package Process Flow – Part 1
Form Data Custom ETL
The custom Java program not only loads form data from reportable dictionaries and services into
corresponding dimensions in the data mart, it also tracks which dictionaries and services have been
loaded. On its initial run this program loads all data in the transactional database into the analytical
database which supports the data mart. On subsequent cycles it loads data incrementally, that is, only
new or modified data in the transactional database is inserted or updated in the data mart.
In addition to actually loading the data, this program also checks for new reportable dictionaries and
services and, updates the list of such objects. This information, labeled as “Metadata for mapping…” in
the diagram above, is then used by another custom program. This program uses the Framework Manager
API to construct the business view of the data that is available to users in Report Designer and Ad-Hoc
Reporting, so that the names assigned to reportable dictionaries and their attributes are accurately
displayed in the reporting tools.
Data Manager ETL
The DataManager ETL loads statically defined (dimension/fact) data from OLTP database into the
corresponding dimensions and facts in the data mart. The load process is incremental. When this process
is run for the first time, it loads all available data from the transactional database. On subsequent runs it
loads only data which have been inserted or modified after the last run of ETL.
All source tables in the OLTP database have time stamp columns (CreatedOn/ModifiedOn). These
columns are updated whenever a new record is inserted or an existing record is modified. The ETL
process captures new/modified data by comparing the time stamp columns in the source tables against
the date and time the ETL process was last run.
The ETL process has been optimized to handle both inserting new rows and updating existing rows in
the data mart. For example, when a service request is submitted, the request and all its tasks would be
created in the data mart. When the tasks are subsequently updated, the existing task fact is updated to
reflect the new information.
The ETL process runs as follows: