Automatic External File Delivery
The Automatic External File Delivery feature provides the ability to have any standard DataLoader files (.dat, .mnt, .reo, .rep) left by any external system in a file drop directory so the files can be deployed to stores.
Oracle Retail Xstore Office monitors a specific directory for files. This directory is configured in System - Xadmin Settings - Directory for Automatically Deployed Data Files (AutoFileTransferDirectory).
The interval at which the directory is checked is also configured in System - Oracle Retail Xstore Office Settings - Detection Interval for Automatically Deployed Data Files (AutoFileTransferSchedulerInterval). See System Management, Oracle Retail Xstore Office Configuration Options.
Any files placed in the auto directory, in the appropriate org directory, (/ filetransfer/auto/org${organizationId}/) will be picked up and a deployment will be created for that file. No user intervention is required to move the files to the stores.
The order in which files are consumed by Oracle Retail Xstore Office is not guaranteed. If a specific ordering of records across multiple files is required, Oracle recommends that those files be combined in a single file, in the appropriate order, before dropping them off in this directory.
Setting File Delivery Details
Each file must contain an XML header line that will dictate when and where the file is delivered.
<Header line_count="3" download_id="configurator::7::72::0" application_date="2013-05-26" target_org_node="STORE:102" deployment_name="specified_name" download_time="IMMEDIATE" apply_immediately="true" />
Line Count [optional]
The line_count attribute is used to indicate how many lines of data are in the file (not including the header). If it is not present, the DataLoader will not validate total line count when loading the file, but will still load the file.
Application Date
The application_date attribute is used to determine the date on which the file will be deployed. If the application date attribute is not present, the date that the file is picked up will be used which means the file will be deployed on the same day.
Target Org Node
The target_org_node attribute is used to determine to what org node or store collection the file will be deployed. Its format is <org code>:<org value> (for example, STORE:102) or <CollectionName> (for example, My Collection). If the target org node attribute is not present, *:* will be used which means the file will be delivered to all stores in the organization.
Deployment Name
If the deployment_name field is populated, the value will be used as the name for the deployment, otherwise the auto-suggestion name will be used.
Download Time
The download_time attribute is used to indicate when the file will be downloaded. Possible values are IMMEDIATE and STORE_CLOSE.
If a deployment is scheduled for immediate download, Oracle Retail Xenvironment will begin to download the file immediately. If a deployment is scheduled for download during the daily maintenance, Oracle Retail Xenvironment will wait until the nightly closing process is initiated to begin downloading the file.
If download_time is not present, the deployment will be scheduled with STORE_CLOSE.
Apply Immediately
The apply_immediately attribute is used to indicate when the file will be applied. Possible values are true and false. If set to true, the file is loaded immediately. If set to false, the file is scheduled to be applied during the closing process.If apply_immediately is not present, the deployment will be scheduled with false. See Appendix: About Deployments for more information.