<app> elements: |
|
---|---|
home (required) |
Absolute path of the app home runtime. Typically, <APP_HOME>\file-sync-app\bin |
port (required) |
Port to use for the server, if blank, the default is 4567 |
retrials (optional) |
If an upload request fails, retry this number of times after the first failed request. Example: Request 1 fails, retrials is set to 3, the system will try 3 more times to determine if the request can be successful, a total of 4 requests can run (assuming all fail for any reason) |
maxfileszipped (optional) |
Maximum number of files that are included into one zip file Example: If you have 20 files to send but maxfileszipped is set to 5, 4 separate zip files containing 5 files each will be sent |
maxbyteszipped (optional) |
Maximum number of bytes per one zip file Minimum supported value is 65537 (65.536 kilobytes) Example: If you have 1 file to send that is 200000 bytes in size when zipped, maxbyteszipped is set to 100000, 1 zip file is constructed with the 1 file and then "split" into 2 pieces, each separate piece is sent to the target server, and then reconstructed Example: If you have 10 files to send that are 200000 bytes in size when zipped, maxbyteszipped is set to 100000, 1 zip file is constructed with the 10 files and then "split" into 2 pieces, each separate piece is sent to the target server, and then reconstructed |
bytespersecond (optional) |
File upload bandwidth throttle (bytes transferred per second) Minimum supported value is 4096 (4.069 kilobytes) Note: this setting controls how fast data streams from client to server while the connection is open between the two |
blacklist/extension (optional) |
Blacklist a file extension(s) to always ignore processing on a specific file type Entries must conform to the pattern of "." + <your extension>, if not, the entry is discarded Provide multiple <extension> element entries under the blacklist element to blacklist multiple extensions There is no limit to the number of extensions you can blacklist |
See the Java 8 standard library documentation or other Infor Sync Utility docs on how to create a keystore for secure communication. All communication technically is "unsafe" and vulnerable to snooping if you're not using https / a keystore that is password protected. In a production scenario, this should be enabled, unless the network is not connected to the outside world / internet and the implications of not having this enabled are understood. |
|
ssl\keystore (optional) |
Absolute path to keystore used for secure connections |
ssl\keystorepassword (optional) |
Password to the keystore. This value will be encrypted after a server start/restart |
Do NOT change the thread pool settings without oversight by an experienced administrator. The default settings should not need to change post installation. |
|
threadpool/min (optional) |
Minimum number of threads in the server thread pool configuration |
threadpool/max (optional) |
Maximum number of threads in the server thread pool configuration |
threadpool/timeoutmillis (optional) |
Idle thread timeout in the server thread pool configuration |
<identity> elements: |
|
---|---|
url (required) |
URL of the server including the port |
root (required) |
Root watch directory on the file system All monitored directories must be included under the <root> specified here It is still appropriate for a directory that will NOT be monitored to be included under the <root>, all file system events will be discarded if this occurs |
archive (optional) |
Archive processed files under <root>/archive/<entry path> |
Archived files are physically moved and not copied |
|
ismaster (required) |
If master then true, else false |
masterurl (required when ismaster = false) |
URL of the master server including the port |
masterurlfallback<number> (optional) |
URL of a backup master server including the port A master backup URL provides alternate support in the event the "main" master is unavailable for any reason (hardware failure, maintenance issue, etc.) Backup URLs are consumed in the order they are listed Backup URLs are optional |
masterroot (required when ismaster = false) |
Root directory for the master server This is an absolute path on the master file system If the local machine does not have the same operating system as the master, provide "os" attribute with the value of either "linux" or "windows" (the operating system of the master) |
deleteoutofsync (required) |
Do you want to delete the destination file so the originator and destination are in sync? If a file does not exist on the originator and does exist on the destination, the destination file will be deleted This option will only work / operate if set to true and the <archive> option is NOT true. |
syncstart (optional) |
Sync start time If not blank, runs at the specified military time daily This setting overrides the sync internal (<syncinterval>) |
syncinterval (required if <syncstart> is blank) |
Interval during which the utility performs synchronization work across nodes Sync interval time unit must be specified n seconds If the sync interval provided is less than 60 seconds, 60 seconds is used If the sync interval provided is greater than 43200 seconds (12 hours), 43200 (12 hours) is used If the preferred operating method is for the utility to only perform synchronization work once a day, use the <syncstart> option |
It is optional to provide entries for <synchtomaster> elements, but if an entry or entries are provided, both from and to are needed. If not the master server, provide disrecotries to sync back to master, the <from> mapping MUST be included under the <root> of the server;’s identity, the <to> mapping MUST be included under the <root> of the master. If the local machine does not have the same operating system as the master, provide "to-os" attribute on <synctomaster> with the value of either "linux" or "windows" (the operating system of the master). |
|
synctomaster/entry/from (optional) |
Absolute path of a directory on the local file system to monitor (all children files and directories that fall under this are also monitored for this entry) |
synctomaster/entry/to (optional) |
Absolute path of a directory on the remote file system to receive the files changed from the local file system (all children files and directory structure will be maintained on sync) |
synctomaster/excludes/exclude (optional |
Exclude a specific absolute path which falls under one of your entries When providing an excludes/exclude entry it must fall under one of the <from> entries> |
<node> elements: |
|
---|---|
name (required) |
Human readable name of the node |
url (required) |
URL of the node server including the port |
Root (required) |
Root watch directory on the file system for the node If the local machine does not have the same operating system as the node, provide "os" attribute with the value of either "linux" or "Windows" (the operating system of the node) |
It is optional to provide entries for <syncfrommaster> elements, but if an entry or entries are provided, both from and to are needed. If master provide directories to sync back to a node, the <from> mapping MUST fall under the <root> of this server’s identity, the <to> mapping MUST fall under the <root> of the node. If the local machine is not the same operating system as the node, provide "to-os" attribute on <syncfrommaster> with the value of either "linux" or "windows" (the operating system of the node) |
|
syncfrommaster/entry/from (optional) |
Absolute path of a directory on the local file system to monitor (all children files and directories that fall under this are also monitored for this entry) |
syncfrommaster/entry/to (optional) |
Absolute path of a directory on the remote file system to receive the files changed from the local file system (all children files and directory structure will be maintained on sync) |
syncfrommaster/excludes/exclude (optional |
Exclude a specific absolute path which falls under one of your entries When providing an excludes/exclude entry it must fall under one of the <from> entries> |