File output directory

The RPI file output directory is used when:

Performing a data extract channel connectivity test.
Exporting a selection rule.
Executing an export within an interaction.
Performing file exports and imports within the File System Dialog.
Executing the Load Web Cache Data system task.
Running the audience housekeeper.

In a multi-node or multi-pod environment, the file output directory should be the same network file share mounted to the same location on each pod that requires it. Supported output locations for files output from RPI include Azure Files, AWS EFS, and Google Filestore.

The folder in question is defined by the following system configuration settings:

Configuration type

Setting name

Setting description

Server

GlobalFileOutputDirectory

This setting allows definition of a single cluster-wide folder to be used by multiple tenants.

On installation of a new RPI tenant:

If GlobalFileOutputDirectory has been configured, FileOutputDirectoryUseGlobal will automatically be set to True.
If GlobalFileOutputDirectory is not defined, FileOutputDirectoryUseGlobal will be set to False, and FileOutputDirectory will be set to the default value of C:\RPI\[tenant name]\FileAssets.
If both GlobalFileOutputDirectory and FileOutputDirectory are not set, files are written to C:\.

Tenant

FileOutputDirectoryUseGlobal

This setting allows the file output directory to be defined on a tenant-by-tenant basis.

If set to True, RPI will use the folder defined by GlobalFileOutputDirectory; however, if GlobalFileOutputDirectory is not set, FileOutputDirectory is used instead.
If set to False, RPI will use the folder defined by FileOutputDirectory; however, if FileOutputDirectory is not set, files are written to C:\.

Tenant

FileOutputDirectory

This setting allows the file output directory to be defined on a tenant-by-tenant basis.

If both GlobalFileOutputDirectory and FileOutputDirectory are not set, files are written to C:\.