This chapter discusses Flexible Aggregate Reporting framework.
The BI Publisher Periodic Reporting functionality is an Argus Safety add-on feature that you can enable.
For more information on enabling this feature, refer to the Enabling and Configuring BI Publisher Periodic Reporting section in the Argus Safety Install Guide.
Figure 3-1 displays the architecture of BI Publisher Periodic Reporting with Argus Safety.
Figure 3-1 Argus Flexible Aggregate Reporting Architecture
BI Publisher reports can be executed from Argus Safety UI or through the BI Publisher console. Table 3-1 explains the core components involved in the architecture diagram.
Table 3-1 Core Components of the Architecture Diagram
Component | Functionality |
---|---|
Argus Web Console |
The first piece of the application for configuring Argus Safety. Handles the following: - Enabling the BIP module - Supplying the necessary BIP security credentials and setting up the persist duration - Setting up the report template path |
Argus Web |
Provides the report configuration for ICH PSUR and CTPR reports. Supplies the criteria that generates the case series. The batch print screen runs either a legacy periodic report or a BIP report based on user selection. It also lets you generate or reuse already generated case series. |
AG Service |
Internally invokes the BIP Periodic report through WebServices and runs the report in the background. |
Argus Database - BIP Schema |
New schema created during the schema creation that holds all objects used for generating the periodic reports. The objects in the schema are responsible for generating the data needed. |
BIP Server |
Server where BI Publisher reports are located and executed. Report output is temporarily stored in the BIP server. |
For more information on the Argus Web Console, Argus Web, and AG Service, refer to the Argus Safety User Guide.
Note:
The OAM server, if chosen, also needs authentication.