7 PMDA E2B (R3) Paper Forms - Framework
This chapter discusses the BI Publisher based PMDA (R3) Paper forms architecture.
Generic Architecture - PMDA (R3) Paper Reports
The PMDA (R3) Paper forms utilize the BI Publisher technology for report generation. Reports can be generated either in the PDF or RTF format. The following diagram displays the high level architecture of the PMDA (R3) Paper forms through the BI Publisher.
Argus PMDA (R3) Paper Reporting Architecture
The following table explains the core components involved in the architecture diagram.
| Component | Functionality |
|---|---|
| Safety Server | The server where Argus Safety Application is installed. When a PMDA (R3) Paper report generation request is made manually, this server makes a call to the BI Publisher server (through BI Publisher Web APIs) and obtains the PDF/RTF Report output generated by the BI Publisher Server. |
| AG Service | When a PMDA (R3) Paper report generation request is done through auto scheduling, this server makes a call to the BI Publisher server (through BI Publisher Web APIs) and obtains the PDF/RTF Report output generated by the BI Publisher Server. |
| BI Publisher Server | The server where (R3) Paper report templates are located and executed. Report output is pushed back to Argus once generated using Web APIs. |
| Safety DB Server | ESM: E2B generated XML is available in the SAFETYREPORT table of ESM owner schema, which is taken into BIP owner schema to generate PMDA (R3) paper reports.
Data Source: Database where Argus Safety Case and configuration data resides. BIP DB Objects (R3): The BIP Owner schema where all packages, temp tables, and log tables that aid the PMDA E2B (R3) Paper reports generation are located. |