Information On Concurrent File Access When Using Directory Scanner
Last updated on OCTOBER 25, 2016
Applies to:Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.
An external application is dropping files onto the OAG file system and there is an intention to use the Directory Scanner to pull these files into OAG for processing and onward transfer. Is there anything in the Directory Scanner that will prevent the file from being picked up by OAG before it is fully written by the external application? Does it matter on a Linux system or will OAG continue to read the file until it receives the EOF marker?
Is there something that would suggest that the file would be ignored until it had stabilized in some way before OAG started processing it, for example file size not changing?
The documentation says the files are moved to a working directory for processing. What happens if OAG moves the file before the application that is writing the file has finished writing it?
Do policies support looping?
Q3: Is there a way to prevent the Directory Scanner from processing a file until the process that is writing the file has finished with it?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms