The Historical database stores all completed and running process instances. It is used by the dashboards for enhanced data analysis using DB2 Alphablox. There is only one Historical database per WebSphere Business Monitor installation. The data in the Historical database is never deleted.
The Historical database should only contain two years worth of historical data. This is one of WebSphere Business Monitor product requirements. As mentioned before, the historical data is never deleted automatically, so the DBA is responsible for deleting the data that is greater than two years old. The Historical database stores the information regarding long-running instances as well as completed instances. This information is stored as star schemas rather than in the flat transactional forms used in the State and Runtime databases. The Historical database is optimized for aggregated and long running querying. It is used byDB2 Alphablox in dashboards views to provide advanced multidimensional reports.
The information in the Historical database is replicated from the Runtime database.
In the Historical database, each process instance has its own set of tables. Unlike the State and Runtime databases, each set of tables is a star schema that supports multidimensional reporting.
The Historical database contains dynamic tables that are created according to the deployed Business Measures-Modell. The Schema Generator generates the Historical database schema, which is used to create dynamic tables, and Cube Views definitions.
The Historical database is used by the WebSphere Business Monitor dashboards. The dashboards retrieve the data required to populate some views from the Historical database. For example, the Berichte view focuses on analyzing data extracted from the Historical database.