The BIP reporting framework is designed to be compatible with Argus Insight.
All references to hitlist in Argus Safety have been changed to Case Series to keep it in sync with Argus Insight terminology.
All temporary tables required for data population in the aggregate reports are maintained in a separate schema within the Argus Safety database instance. You can access these tables through the Argus Insight DBLink, with the help of proper database grants and privileges.
You can use the same BI Publisher server for Argus Safety and Argus Insight reports. For more configuration information required for running both these products on the same BI Publisher server, refer to the Argus Safety Installation Guide.
You can use the same reporting server for Argus Analytics (OBIEE), Argus Safety, and Argus Insight (BIP).
Argus Insight has introduced an RPD for data analysis of aggregate case series generated using Argus Safety aggregate reports. Argus Insight requires preservation of temp table data so it can be copied into the Argus Insight or Mart database using the ETL process. When aggregate case series data from temp tables is available in the Argus Insight or Mart database, you can use OBIEE RPD to analyze this data using different dimensions and case count measures.
Make the following configuration changes in Argus Console for persisting the BIP temp table data so that the data can be used with OBIEE RPD:
Go to System Configuration -> System Management (Common Profile Switches) -> Reporting->BIP Aggregate Reporting.
Under the BIP Common User and BIP Common User Password rows, add two common profile entries to the system for defining whether to persist data in BIP temp tables, and the number of days for which data should be persisted in these temp tables.
Profile switches must be added under BIP Common User and BIP Common User Password rows. The following information is available for these profile switches:
Table 5-1 Common Profile Entries
| Field Label | Default and Possible Values | Description |
|---|---|---|
|
Persist data in BIP Aggregate Temp Tables |
Default: No Yes No |
Yes: System persists or stores the data of BIP aggregate temp tables for all the case series generated for aggregate reports generation. No: System does not persist data of BIP Aggregate Temp tables. |
|
Number of days for which data of BIP Aggregate Temp Tables should be persisted |
Default: NULL Data of BIP Temp tables is persisted for the number of days defined in this configuration. After the configured period (Number of days from the last modified date of case series), a database or system job purges the data that is no longer required (defined separately). You can override the number of days for persisting data of a particular aggregate case series while generating the report through the BIP Console. |
- |
If Persist data in BIP Aggregate Temp Tables is set to No, the system does not persist data of BIP temp tables.
If Persist data in BIP Aggregate Temp Tables is set to Yes and Number of days for which data of BIP Aggregate Temp Tables should be persisted is not defined, the system throws an error message when you save the value of these configurations. The following message appears:
Please enter the number of days for which data of BIP Temp Tables should be persisted.
In a multi-tenant environment, you can view these configuration entries on the enterprise level.
As part of data persistence and purging, two parameters have been added in BIP aggregate reports for overriding the default value. For example, you can choose not to persist data for a draft report run even if the default value is set to persist BIP temp table data. The following parameters have been added in aggregate reports:
Persist data of Temp Tables
Number of Days for Data Persistence
For more information on these two parameters, refer Appendix A, "Report Parameters and their Definitions".
A data purging is required to remove the data that exceeds the duration specified in the persistence parameters. The purge operation is handled using a database job that is created during the installation of the application.
The data is purged if the current date exceeds report date plus the persistence duration specified while running the report.
After data is purged from the Argus BIP temp tables, the purge is reflected in the Argus Mart database after completion of the ETL process.