Configuring Media Life Cycle Management

When it is time to purge old recording files, Web Services sends a purge request to the SpeechMiner database indicating which records to delete. Both Web Services and SpeechMiner need additional configuration to allow the records to purge successfully.

Web Services

To enable Genesys Interaction Recording to purge recording files, configure the Web Services node as follows:

In the backgroundScheduledMediaOperationsSettings section of the server-settings.yml file,

• Set enableBackgroundScheduledMediaOperations to true
• Set defaultBackupExportURI to a backup folder—for example, file:///tmp/archLocDefault is the default backup folder.

For more information about these options, see Configuring Web Services.

SpeechMiner

To enable Web Services to contact Interaction Receiver and purge the requested recordings, use a text editor to add the following to the location based setting group in the json.txt file:

{
    "name":"interaction-receiver",
    "location": "/US/CA",
    "value": {
        "uri-prefix": "http://interactionreceiver:8080/interactionreceiver",
        "userName": "interaction receiver user name",
        "password": "interaction receiver password"
    }
}

Important

The Interaction Receiver user name and password must be the tenant archiving user and password which are set when configuring Recording Crypto Server.

Execute the following command:

curl -u <user:password> -X POST -d @json.txt --header
"Content-Type: application/json" http://<Web Services-cluster-address>/api/v2/settings/speechminer

For more information on the properties of this settings group, see Web Services Settings Groups.

For more information about the location based setting group for encryption, see Encrypting and Provisioning Certificates.

Creating Rules and Schedules

Use Genesys Administrator Extension to create rules and schedules. For step-by-step instructions, see Recording Scheduler Rules.

Consider the following when creating backup and purge tasks:

• Do not schedule backup tasks to run concurrently on the same Web Services node if these tasks back up overlapping records.
• Do not schedule backup and purge tasks to run concurrently if they act on overlapping records.
• Ensure that all the Web Services nodes have accurate clocks.
• Genesys Administrator Extension's time is based on UTC.

Warning

Do not schedule a purge task to run independently in its own rule unless you are willing to lose the associated data. Even if a backup has been scheduled, it is not guaranteed to complete successfully before the purge task is executed.