Drop zone configuration in server.properties
Can we configure customize datadropzone folder at different shared location same as export directory by editing server.properties file?
Thank you kin advance
Hey! You will be signed out in 60 seconds due to inactivity. Click here to continue using the site.
Yes you can change the location of the dropzone folder by updating server.properties: https://docs.experianaperture.io/data-quality/aperture-data-studio-v2/set-up/install-data-studio-on-windows/#database-folder-locations
By default, the location of the dropzone folder is <ApertureDataStudio>\data\datasetdropzone\<EnvironmentLanel>\<DatasetLabel>
The default base location of the dropzone folder can be customized to be in a location of your choice by adding or changing the Dataset.dropzone entry in the server.properties file on the server.
(note that any backslash needs to be escaped with an additional backslash)
The change will not take effect until the server is restarted. If the folder does not exist then it will be automatically created (along with all of its dropzones) when the server starts.
Note that External Dropzone folders are supported for Azure and S3: https://docs.experianaperture.io/data-quality/aperture-data-studio-v2/get-started/configure-external-systems/#configureexternalsystemdropzone
Thank you Josh
We tried these recommendations a lot, but unfortunately it's not working. We are not able to change the datasetDropzone new repository.
We tried these paths
But each time the repository is created in the same location:
FYI: gvepsn0021 is a shared FTFS drive
Thank you in advance for your help
Maybe try creating it 'locally' in a different location to ensure that is not the issue. Set it to something like Dataset.dropzone=D:\ApertureDataStudio\data\DROPTEST and restart the server
If that is successful then try setting it to your network drive. Note this comment on the documentation article:
"To configure Data Studio to write to a network drive, use the full UNC path and make sure that the account running the Data Studio Database Service (by default the Local System account) has write access to the network drive folder location"
@Slimani did you ever resolve this issue?
Another customer was having a similar issue and we realised that the casing they were using in the server.properties file did not match the directory they were pointing at
@Slimani Just to clarify on this, it's the setting name in the server.properties file that's case-sensitive:
The documentation has been updated to reflect this:
Hi Josh and Henry,
Thank you for your response.
We use the below line in the server.properties
and we have restarted the service "experian aperture data studio database server 2.4.0" , but the service did not start and gave the below error in the log file:
2021-11-26 10:34:29,848 FATAL c.e.ServerMain [main] 21001: Custom Dataset dropzone 'path=\\OurSharedLocationServerName\daperture_data\datasetdropzone' is not a full absolute path
It seems that Aperture is waiting for an absolute path instead of shared location path.
Thank you in advance for your response.
Try the same setting but removing "path\=". I have tested with a remote dropzone on a network drive (using 2.5.6) with the following setting and it worked:
That should at least get you past the "is not a full absolute path" error.
You may then start to see an error: "Unable to create Dataset dropzone folder: <name>". If you see this, it's almost certainly a permissions issue. The login user account used by the Experian Aperture Data Studio Database Server must have full control over the root dropzone folder on the network location.
Thank you Henry,
Thank you for your support.