filemanager Overview
The filemanager utility administers preprocessing and file-watching capabilities for a cloud ecosystem such as Amazon AWS or Microsoft Azure.
You can use the filemanager utility for the following preprocessing capabilities:
- •List files on a cloud ecosystem.
- •Copy files on a cloud ecosystem.
- •Copy files from a local system to a cloud ecosystem.
- •Move files on a cloud ecosystem.
- •Rename files on a cloud ecosystem.
- •Delete files from a cloud ecosystem.
You can use the filemanager utility for the following file-watching capabilities:
- •Trigger a file-processing event.
- •Trigger a workflow or mapping.
You can use the filemanager utility from one of the following locations:
- •Client directory. Available under <Infa home>/clients/tools/filemanager
- •Server directory. Available under <Infa home>/tools/filemanager
Logging Options
The filemanager utility provides the following log severity levels for debugging purposes:
- •FINE. Writes severe, info, and warning messages to the log. The fine or debug messages are user-request logs.
- •SEVERE. Writes severe, warning, and error messages to the log. The severe messages include non-recoverable system failures, connection failures, and service errors.
- •WARNING. Writes severe, warning, and error messages to the log. The warning errors include recoverable system failures and warnings.
- •INFO. Writes severe, info, warning, and error messages to the log. The info messages include system and service change messages.
Default Behavior
The filemanager utility exhibits the following default behavior:
- •The filemanager utility treats \ as an escape character and not a separator in cloud paths.
- •The filemanager utility creates a target directory if you do not specify a target directory for move, copy, or rename operations in Amazon AWS cloud ecosystem.
- •The filemanager utility creates a target directory if you do not specify a target directory for a copy operation in ADLS Gen2 storage. For other file operations, the filemanager utility displays an error.
- •The filemanager utility deletes the target directory if you move or rename a file to a target directory that does not exist and then try to move the file back to the source directory.
- •The filemanager utility displays a file name in the logs when you move, copy, rename, or remove a file.
- •The filemanager utility does not display a file name in the logs when you remove a file stored in ADLS Gen2 storage.
- •The list command does not specify whether a listed object is a file or a folder.
- •The watch command triggers the mapping before a file gets copied in Microsoft Azure cloud ecosystem. This action applies to ADLS Gen1 storage and when you use external tools to copy a file.
- •The copy and list commands do not work if you specify a folder path in the parameter -bn<-bucketname>.
Guidelines
Use the following guidelines when you use the filemanager utility:
- •You must have connection, read, and execute permissions to run the filewatcher utility.
- •You cannot copy an empty folder.
- •Do not use multiple / to specify cloud paths.
- •Do not use a file path in a pattern search.
- •Do not use a symbolic link that points to the same directory recursively.
- •Set the environment variables INFA_TRUSTSTORE and INFA_TRUSTSTORE_PASSWORD if the domain is enabled with a custom SSL.
- •Set the environment variable INFA_TRUSTSTORE if the domain is SSL enabled.
- •Set the first three parameters in a command as: filemanager <cloud ecosystem> <command>. For example, filemanager aws list
- •Use the absolute path for file names.
- •Use the parameter -dn<domainname|optional> for multiple domains configured in Informatica Administrator.
- •When yo use the watch command, place the parameter -op<other parameters|optional> at the end of the syntax.
- •Use only the following wildcard characters to specify patterns: