Please note: All new versions will be located at GitHub under Waarp new project name :
http://waarp.github.com/Waarp/
The project still remains Open Source under GPL V3.
Presentation of OpenR66: File Transfer Monitor
-
Efficient and secured
Unlimited concurrent number of transfer
Possibility to limit the bandwidth (in point 2 point or globally)
Possibility to limit the CPU usage and the simultaneous number of transfers
Guaranty of delivery (persistence through database and retry)
Virtualization of access paths
Track of meta-data associated with transfers
Encrypted connection support (SSL) with optional strong authentication and Packet Integrity support
Easy integration in security rules (low number of chosen ports, flow multiplexing)
Partner authentication (through encrypted password and optionally through strong SSL Client Authentication)
Rules validation of usage by partner
-
Possibility to have multiple OpenR66 File Transfer Monitors acting as a single one behind a Load Balancer to enable more reliability and scalability
Adaptation to functional needs
Initiator of transfer in different modes SEND or RECV through Rules
Pre and Post Actions according to transfer Rules associated with each transfer
Integration through script
Integration through submission client in Java
Integration through interaction with the database of OpenR66
Integration through a Graphical User Interface (Light Client only)
Integration through native Java code (business code) either through BusinessFactory or through R66Runnable
-
Transmit in synchronous or asynchronous mode
Pre and Post transfer procedures
Native operations
LOG: Write in the log file the given information
RENAME: Rename the file
MOVE: Move the file
VALID FILEPATH: Valid the constructed file path
DELETE: Delete the file
COPY: Copy the file
TRANSFER: Transfer again the file to another OpenR66 server
RESCHEDULE: Reschedule Transfer task if the error code is one of the specified codes and if the new schedule is valid
-
TAR/ZIP: To tar or zip according to arguments
-
External operations
EXEC (or EXEC RENAME): Execute an external procedure (system call) on the basis of args given or constructed (and rename the file according to the result of the command)
EXECOUTPUT: Execute an external procedure (system call) on the basis of args given or constructed but in case of error, it uses the output to setup information status using <STATUS>status</STATUS><ERROR>error message</ERROR>
-
EXECJAVA: Execute an external procedure (Java Class implementing R66Runnable) on the basis of args given or constructed
Integration, Administration and Production
Easily integrated into Security rules
Easily integrated into a production plan
Easily integrated into a supervision tool (HTTP/SNMP)
Allow to handle the configuration in a central point
-
Allow to handler the history of the transfers in a central point
In push or pull mode to or from the central server point
Updated at the desired rhythm
-
No lock of the OpenR66 monitors in case the central server is unavailable
HTTPS native interface for the administration with access control
Allow the administration through script
SNMP support as Agent (MIB included) in SNMP V2 or SNMP V3
-
HTTP native interface for the supervision
History of transfers
Independence with server platforms
Full Java (minimum JDE 5), MD5 in C (optional) or en Java
Tested on Windows, Linux, AIX
-
Solution totally Open Source
Usage mode
Usable with many kind of Databases(centralized or distributed)
Tested with several databases through JDBC : Oracle, PostGreSQL, MySQL, H2 (for a low footprint on a PC)
Database schema is sharable between several OpenR66 servers within one Data Center
In case of a set of Servers acting as a Single One, they do share the same ID and Database and Storage
-
Possibility to not rely on any database, but then some functionality will be off (like extended monitoring or the ability to restart transfer in error, except through XML file analysis - if active -)