Technical Documentation

Understanding the Interaction Archive Player (IAP) Architecture

How IAP Works

Export from Genesys Environment

Using the MLM functionality available within GAX (Engage Premise) or RCBS (Multi‑Cloud), an export schedule queries the GIR system for interactions that match defined criteria.

The export produces audio files together with matching metadata. These files are stored on a shared network drive, local storage, or cloud storage (AWS S3, Azure Blob, etc.).

Technical architecture diagram showing IAP workflow from Genesys export to playback Click image to enlarge

Metadata Processing

IAP includes a processServer task that reads metadata files, translates them into database records, and populates the UI.

Interaction Playback

When a user selects an interaction, IAP retrieves the media location from the database and streams it via the built‑in player.