In the zip distribution, there is an example of installation including a bin directory and a ENV_R66 file that contains some commands to be used in a shell on a Unix server. It should be easy to adapt those files to fit your needs.
r66server
# start the Waarp R66 server
# no option
r66init
# init database from argument
# [ -initdb ] [ -loadBusiness businessConfiguration ] [ -loadRoles roleConfiguration ] [ -loadAlias aliasConfig ] [ -dir rulesDirectory ] [ -limit xmlFileLimit ] [ -auth xmlFileAuthent ] [ -upgradeDb ]
r66signal
# shutdown locally the server
# [ PID ] optional PID of the server process
r66shutd
# shutdown by network the server
# [-nossl] [-block | -unblock]
r66limit
# change limits of bandwidth
# "[ -wglob x ] [ -rglob w ] [ -wsess x ] [ -rsess x ]"
r66export
# export the log
# [ -purge ]|[ -clean ] [ -start timestamp ] [ -stop timestamp ]
r66cnfexp
# export configuration
# directory
r66confexp
# export configuration as arguments
# [-hosts] [-rules] [-business ] [-alias] [-roles] [-host host]
r66confimp
# import configuration as arguments
# [-hosts host-configuration-file] [-purgehosts] [-rules rule-configuration-file] [-purgerules] [-business file] [-purgebusiness] [-alias file] [-purgealias] [-roles file] [-purgeroles] [-hostid file transfer id] [-ruleid file transfer id] [-businessid file transfer id] [-aliasid file transfer id] [-roleid file transfer id] [-host host]
r66export
# export the log
# [ -purge ] [ -clean ] [ -start timestamp ] [ -stop timestamp ] where timestamp are in yyyyMMddHHmmssSSS format eventually truncated and with possible ':- ' as separators
r66logexport
# export the log (extended)
# [-host host] [ -purge ] [ -clean ] [-startid id] [-stopid id] [-rule rule] [-request host] [-pending] [-transfer] [-done] [-error] [ -start timestamp ] [ -stop timestamp ] where timestamp are in yyyyMMddHHmmssSSS format eventually truncated and with possible ':- ' as separators
r66limit
# change limits of bandwidth
# "[ -wglob x ] [ -rglob w ] [ -wsess x ] [ -rsess x ]"
r66admin
# Administrator Gui
# no argument
# on all client side commands: In addition, for success result, if -logWarn is set (default), the information will be logged using WARN level, while if -notlogWarn is set, the information will be logged using INFO level.
r66info
# get information on remote files or directory
# "-to host -rule rule [ -file file ] [ -exist | -detail | -list | -mlsx ]
r66mesg
# test the connectivity
# -to host -msg "message"
r66req
# get information on transfers
# -id transferId [ -to hostId | -from hostId ] [ -cancel | -stop | -restart [ -start yyyMMddHHmmss | -delay [+]timeInMs ] ]
r66syncsend
# synchronous transfer
# -to hostId -file filepath -rule ruleId [ -md5 ] [ -block size ] [ -nolog ] [ -info "information" ]
r66send
# asynchronous transfer
# -to hostId -file filepath -rule ruleId [ -md5 ] [ -block size ] [ -nolog ] [ -info "information" ]
r66multisend
# R66 Multiple Submit
# (-to hostId,hostID -file filepath,filepath -rule ruleId) | (-to hostId -id transferId) [ -md5 ] [ -block size ] [ -nolog ] [-start yyyyMMddHHmmssSSS | -delay +durationInMilliseconds | -delay preciseTimeInMilliseconds] [ -info "information" ] [ -client ]
r66multisyncsend
# multiple synchronous transfer
# (-to hostId,hostid -file filepath,filepath -rule ruleId) | (-to hostId -id transferId) [ -md5 ] [ -block size ] [ -nolog ] [-start yyyyMMddHHmmssSSS | -delay +durationInMilliseconds | -delay preciseTimeInMilliseconds] [ -info "information" ]
r66gui
# R66 Gui
# no argument
r66spooledsend
# R66 Spooled directory transfer
# (-to hostId,hostid -directory directory -statusfile file -stopfile file -rule ruleId) [-md5] [-block size] [-nolog ] [-elapse elapse] [-regex regex] [-submit|-direct] [-info "information"]