EDM™ Report Manager
EDM Report Manager's architecture provides an optimized experience when working with reports in EDT applications using the following methods:
Some configuration options are available to modify how EDM Report Manager and OpenWells software process reports.
There are two options available in OpenWells software that reduce the time to generate a report. PreQuery and PreLoad. The options are accessed via Tools menu > Report Setup > Report Tab.
You can optimize individual report’s performance by enabling the Preloading and Pre-query options for each report.
Landmark's testing effort revealed that PreQuery and PreLoad options enabled for specific reports can significantly reduce processing times. The specific reports that benefit from these options are set a enabled by default.
If the PreQuery and PreLoad options are NOT enabled, the EDM Report Manager processes reports as follows:
When you preview a report, OpenWells software checks if the required data is in memory. If the data is not present, the OpenWells application will send the query to the database to get the data.
The EDM database executes the query and returns results. Typically a database will compile the query, and then return the data. If the same type of query is sent to the database again, the database may still have the compiled query in memory so it will only need to execute the actual query.
OpenWells software writes the data in an XML file for the EDM Report Manager to process.
EDM Report Manager then loads the RPT file.
EDM Report Manager binds the RPT file with the XML data file to create a PDF file.
At OpenWells startup:
PreLoad - enables the EDM Report Manager to load the RPT file in step 4 above into memory. Caching the RPT file can substantially reduce processing time.
PreQuery - enables the OpenWells application to send an empty query in step 2 above to the database so that the queries are compiled in advance.
While each of these options speed up the individual report’s performance, they slow down startup of the OpenWells application and consume additional memory. PreLoad consumes memory on the user’s desktop or the CITRIX server, while PreQuery consumes memory on the database server.
Therefore, it is up to you to decide which reports are used on a daily basis and enable the optimization options for these reports.
To increase stability of the EDT applications, reports are managed by EDM Report Manager. Each report requires a memory allocation of approximately 50 MB. When multiple reports are open, as is the case of a batch preview, EDT applications that generate reports are shielded from memory loss because EDM Report Manager handles all work associated with report processing.
EDM Report Manager requires four files to generate a report. Two files ship with each report and are requested from the database when a report is invoked. Two additional files are generated when a report is run. For example, the files associated with a Casing Report are:
|
File Name |
Database |
Generated |
|
OpenWellsCasingReport.rpt |
X |
|
|
OpenWellsCasingReportConfig.xml |
X |
|
|
OpenWellsCasingReportFiltered.xsd |
|
X |
|
OpenWellsCasingReportTables.xml |
|
X |
All files are stored in the user account profile. For example:
<user>\Local Settings\Application Data\Landmark\cache\{Database Name}\OutputReports\Landmark\Casing\OpenWellsCasing
However, it would be less efficient to load the files from disk each time a report is run. To streamline the report generation process, the EDM Report Manager stores each file in cache memory. Cache memory can be accessed by the CPU much more quickly than regular RAM.
Another problem avoided by the program architecture involves the scenario where the cache file directory is deleted. The cache generate process will take a very long time if the cache file is not present in the user’s cache folder. Users who run the EDT applications on Citrix may notice that a script runs when OpenWells software closes that deletes the cache file. If this scenario exists, every time the OpenWells application is launched, it will take a significant amount of time to open the first report for all report types (for example, 60 seconds vs. 20 seconds for a WELLPLAN BHA analysis report).
To solve this problem, the EDM database includes all report cache files. Therefore, even if the cache folder is deleted, EDT applications will copy the cache files from the EDM database to the user’s cache folder.
Related Topics