Skip to content

Definition: Application Retirement

Application Retirement is the strategic process of taking an application (often a legacy system) out of active service while ensuring necessary data is appropriately retained, preserved, and remains accessible for business, legal, or regulatory compliance needs[cite: 25, 37, 113]. It goes beyond simply turning off a system; it involves managing the underlying data lifecycle.

Key Aspects in the Helix Context:

  • Goal: Often driven by the need to reduce costs associated with maintaining outdated hardware, software licenses, and specialized support staff for legacy applications (like older ECMs or viewers)[cite: 112, 113].
  • Data Handling: A core component is extracting and migrating necessary data from the retiring application to a new system or an archive repository[cite: 37]. Data not actively needed but required for compliance may be archived.
  • Access to Archived Data: Solutions like the MARS RealTime Viewer (RTV) and RTV APIs can provide ongoing, on-demand access to data from retired applications without requiring the original application or licenses to remain active[cite: 37, 63, 78, 114, 115].
  • Process Integration: May involve redirecting data feeds ("Day Forward" processing) that previously went to the retired application to new systems or processes[cite: 37, 60].
  • API Remediation: Can include managing or replacing custom API integrations tied to the retiring application, potentially using tools like MARS Mimic Mode to avoid extensive rewrites of connecting applications[cite: 37, 133, 140].
  • System Examples: Common candidates include legacy ECM systems (e.g., CMOD, CA View, Mobius, FileNet versions), older viewers, or custom business applications[cite: 21, 25, 55, 112].