Error rendering macro 'rw-search'

null

Downloads

Versions Compared

Old Version 10

changes.mady.by.user franz walder [panagenda]

Saved on

compared with

New Version 11

changes.mady.by.user franz walder [panagenda]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • License: Content Age data collection will only be performed if a valid license is found that includes the Content Age module.

  • Default Schedule: The collection is linked to the design analysis process. As such, it will adhere to its defined schedule as well. The default and recommended setting for design updates is "Weekly, on Saturday", but may be different in your installation. Please check the menu item [Settings] → [Database design re-scan options] for details. No automatic collection will happen before the scheduled time.

  • Schedule Customization: iDNA avoids accessing individual non-system DBs on a regular basis. That is why DB design is - per default - only re-scanned on weekends and then only if changed since last scan. Since this Content Age collection would connect to each Focus DB every week, we added a config parameter that allows specifying an interval in weeks that should pass between scans. Example: setting the ETL parameter "ia_profile_rescan_interval_weeks" to "2" will basically mean "Only scan every second week on Saturday". ETL parameters can be configured in the admin interface ([Settings] → [System configuration...]) in the menu item [Advanced Settings] → [ETL] → [ETL Properties].

  • (Re-)Collection can be triggered manually for one or more databases via the menu item [Settings] → [Design analysis status]. Note: if code analysis is licensed, using this option this will also trigger a re-collection and re-processing of design data. This may take a very long time, depending on the amount of databases to process. The regular scheduled scan on Saturday will only re-collect design data if changes in DB design occurred.

  • DB Scope: Content Age information will be collected from all Focus DBs (database categories "Application" and "Mail-in DB"), excluding files with the NTF extension.

  • Processing: Before collected data is visible in iDNA's user interface it needs to be processed by the nightly data warehouse update.


Retention Period Configuration



Summary (Example Scenario)

...


  • A new Content Age analysis license is applied on Wednesday

  • Retention config for the first half of databases is configured throughout Wednesday and Thursday
  • Content Age collection is automatically triggered on the following Saturday and is completed on Sunday 

  • Nightly processing from Sunday to Monday combines the two sets of data

  • Content Age analysis is available in the UI on Monday morning

  • Retention config is added for another batch of DBs on Tuesday

  • Nightly processing from Tuesday to Wednesday combines the two sets of data again

  • On Wednesday morning, the UI displays updated information based on most recent Retention Config changes


Evaluating Results





Licensing

...