FILEGOVPATH

Syntax

FILEGOVPATH  [ path | OFF ]

path—Specifies the directory on Essbase Server to save client data exports, if something other than the default (cube directory) is preferred. By default, exports to the server are saved to the cube directory, unless you specify a different path in this configuration.
OFF—File governance is turned OFF. Exports to the server are saved either to <Application Directory>/app, or to the absolute path clients provide in their export operations.
no value—If FILEGOVPATH is present in the configuration but has no value, this means that file governance is turned ON, and data exports to the server are always saved to the cube directory on the server. If a client data export specifies an alternate path, the specification is ignored.

By default, file governance is implicitly ON, and the path is equivalent to the cube directory.

See Environment Locations in the Essbase Platform for information about <Application Directory>, cube directory, and other directory locations in Essbase.

Description

This configuration setting sets the default file path location where Essbase should save client-based data exports on the server. This configuration is applicable whether you are using:

MaxL export data with the server and data_file keywords
the DATAEXPORT command for calculation scripts
API calls for exporting data

Example 1

FILEGOVPATH OFF

MaxL client data exports are saved to <Application Directory>/app on the Essbase Server. For example, the following MaxL statement creates the export file as <Domain Root>/applications/essbase/app/exp_file.txt:

export database Sample.Basic data to server data_file 'exp_file.txt';

Example 2

FILEGOVPATH

MaxL client data exports to the server are saved to the appropriate cube directory on the Essbase Server. For example, the following MaxL statement creates the export file as <Domain Root>/applications/essbase/app/Sample/Basic/exp_file.txt:

export database Sample.Basic data to server data_file 'exp_file.txt';

Example 3

FILEGOVPATH /scratch/export/

MaxL client data exports to the server are saved to <path> on the Essbase Server. For example, the following MaxL statement creates the export file as /scratch/export/exp_file.txt:

export database Sample.Basic data to server data_file 'exp_file.txt';

Example 4

FILEGOVPATH /scratch/export/

MaxL client data exports to the server are saved to <path> on the Essbase Server. For example, the following MaxL statement creates the export file as /scratch/export/export_dir/Sample/Basic/exp_file.txt:

export database Sample.Basic data to server data_file '/export_dir/exp_file.txt';